??? 12/22/05 13:57 Read: times |
#105733 - limited feasibility of I2C PnP Responding to: ???'s previous message |
Hello,
I have implemented a similar plug-n-play I2C in one of my projects, although there is no possibility of Hot-pluggin/unplugging. I have 6 different I2C devices on the board which I provide empty sockets for particular I2C chips that are optionally used, and the firmware looks for a known list of devices at initialization. This works well. Scanning 128 devices would be A. slow, B. managing different bus speeds (100 kHz, 400 kHz, 1 MHz) would be cumbersome and C. although the basic protocol is the same, the byte-level transactions are different for different devices. As for hot-plug I2C, 10 second time-out is way too much. 10-100 mS is okay I suppose since it takes about 100 microseconds for a byte on the slowest 100 kHz I2C bus. Resetting the I2C bus (generating stop, start, pumping 9 bits and again start and stop condition) will get the bus into a known initial state again and the erring device may be removed from the list of active I2C devices. Girish |
Topic | Author | Date |
Plug & play by I2C ,is it possibe? | 01/01/70 00:00 | |
You have two problems? | 01/01/70 00:00 | |
I know | 01/01/70 00:00 | |
with a "master" with IIC hardware it sho | 01/01/70 00:00 | |
lot of time not needed ! | 01/01/70 00:00 | |
limited feasibility of I2C PnP | 01/01/70 00:00 | |
the fact is | 01/01/70 00:00 | |
Re: the facts is | 01/01/70 00:00 | |
CAN | 01/01/70 00:00 | |
unkowm state | 01/01/70 00:00 | |
I must try | 01/01/70 00:00 | |
Inappropriate Design Choice? | 01/01/70 00:00 | |
Hot-swap I2C | 01/01/70 00:00 | |
a fvew points | 01/01/70 00:00 | |
ACCESS.bus is PnP I2C | 01/01/70 00:00 | |
just recalled![]() | 01/01/70 00:00 |