??? 11/15/09 08:41 Read: times |
#170840 - BitBang's Amost Always.... Responding to: ???'s previous message |
Bit bang interfaces such as you are attempting with an I2C serial EEPROM almost always require debugging with an oscilloscope to get the timing correct and to match the data sheet specified requirements.
Have you connected an o-scope up to your circuit to check it out? Have you looked at the pullup resistor values to make sure that the I2C lines have reasonable rise time to work with the SCL clocking rate you are trying to generate? Have you looked carefully at the signal integrity of the SCL and SDA lines to ensure that there are good VOL levels at the MCU and at the Serial EEPROM? Have you arranged for support of the Write Protect / Write Enable signal? Make sure you have the device strapped correct to correspond to the slave addresses you are trying to use. Once you resolve all these types of issues you may be able to get your Serial EEPROM working. It will be the work that you do that will move things forward. Michael Karas |
Topic | Author | Date |
AT24C256 | 01/01/70 00:00 | |
help | 01/01/70 00:00 | |
BitBang's Amost Always.... | 01/01/70 00:00 | |
Why use void functions | 01/01/70 00:00 | |
thanks | 01/01/70 00:00 | |
Writing to specific address | 01/01/70 00:00 | |
Send sensible address values. | 01/01/70 00:00 | |
I2C_0.0.zip | 01/01/70 00:00 | |
no luck, | 01/01/70 00:00 | |
You have more pins to mis-wire. | 01/01/70 00:00 | |
i2c used, What should be the address | 01/01/70 00:00 | |
Read Murray's excellent Help Files | 01/01/70 00:00 | |
Incorrect reply | 01/01/70 00:00 | |
Please take some time to READ the Help | 01/01/70 00:00 | |
single byte read write working | 01/01/70 00:00 | |
I2C_0.1.zip released!![]() | 01/01/70 00:00 |