??? 03/11/08 12:49 Read: times |
#152117 - pass on one bit of experince Responding to: ???'s previous message |
A slave needs to act in "hardware - real time".....
This means that the micro needs to have the I2c routine as one of the top priority interrupts, top priority code.... otherwise you will loose data. Hardware slaves act in real time and there minimal or no delay in action in receiving I2c commands. Soft I2c is thwart with danger... and can be hard to get to work "reliability". Trust me I have some issues with soft i2c slaves. Joe |
Topic | Author | Date |
soft I2C slave | 01/01/70 00:00 | |
pass on one bit of experince | 01/01/70 00:00 | |
the cost of developing a bit banged IIC slave ... | 01/01/70 00:00 | |
If you want to find Public Source Code... | 01/01/70 00:00 | |
like this.. | 01/01/70 00:00 | |
Can you add a flip-flop? | 01/01/70 00:00 | |
Only 1 master and 1 slave..or | 01/01/70 00:00 | |
what is the sensor? | 01/01/70 00:00 | |
Why soft? | 01/01/70 00:00 | |
GPIO/something else or micro | 01/01/70 00:00 | |
Simplest way | 01/01/70 00:00 | |
Thank's Andy | 01/01/70 00:00 | |
Don't just thank me... | 01/01/70 00:00 | |
Many thank's![]() | 01/01/70 00:00 | |
all SILabs, most NXP LPC9xx | 01/01/70 00:00 | |
No Shortage!! | 01/01/70 00:00 | |
Devices Found = 263. | 01/01/70 00:00 | |
know of none | 01/01/70 00:00 |