| ??? 09/19/08 21:09 Read: times |
#158420 - I2C takes some reading to implement Responding to: ???'s previous message |
In that case, I expect that you were a bit better at reading datasheets than the average noice :)
Quite a lot of people tend to get stuck when they try to figure out how to implement I2C. Especially if they settle for the documentation for their memory chip. It helps a lot to locate the excellent Philips documentation. And you also have to take care of all error conditions, in case there is a transfer error. I don't know how long it took until Wavecom managed to correctly implement the I2C support in their GSM modules. But if the I2C communication locked up, you had to reconfigre to a user-driven GPIO signal and perform any clean-up yourself. And that isn't the only incomplete I2C implementation I have seen in commercial products. It is quite common that a too small subset of the state machine is implemented. |
| Topic | Author | Date |
| are values stored in memory permanent ? | 01/01/70 00:00 | |
| Depends on memory | 01/01/70 00:00 | |
| I A P | 01/01/70 00:00 | |
| could you help me with the IC | 01/01/70 00:00 | |
| serial EEPROM | 01/01/70 00:00 | |
| serial EEPROM with SPI also possible | 01/01/70 00:00 | |
| I have my doubts... | 01/01/70 00:00 | |
| I2C takes some reading to implement | 01/01/70 00:00 | |
| that's the point | 01/01/70 00:00 | |
| Values in the Memory | 01/01/70 00:00 | |
| a caveat | 01/01/70 00:00 | |
| RE: a caveat | 01/01/70 00:00 | |
| Any assemblers? | 01/01/70 00:00 | |
| As long as others are all being strictly technical | 01/01/70 00:00 | |
C standard | 01/01/70 00:00 | |
| Another caveat | 01/01/70 00:00 | |
| sorry for the delay | 01/01/70 00:00 | |
| which? | 01/01/70 00:00 | |
| Maxim too has One-wire EEPROMs | 01/01/70 00:00 |