??? 05/28/07 14:29 Modified: 05/28/07 14:40 Read: times |
#139919 - timing Responding to: ???'s previous message |
Jan,
I had put delays between SDA and SCL changes in previous versions. I deleted them in order to check signals on the scope. My guess is : I wouldn't be able to read data and to receive ack from slave devices if I didn't respect timings between SDA and SCL. I just checked slowing delay loop to 255 while (i--); instructions and adding calls to this i2c_delay routine between every (SDA,SCL) changes without success ... Thanks |
Topic | Author | Date |
I2C eeprom 24c02 byte write stuck in ack | 01/01/70 00:00 | |
timing | 01/01/70 00:00 | |
timing | 01/01/70 00:00 | |
what\'s the problem, exactly? | 01/01/70 00:00 | |
timing | 01/01/70 00:00 | |
how do you know that? | 01/01/70 00:00 | |
How do you know that? | 01/01/70 00:00 | |
do you have some other version of code? | 01/01/70 00:00 | |
do you have some other version of code? | 01/01/70 00:00 | |
A work around For That | 01/01/70 00:00 | |
work around For That | 01/01/70 00:00 | |
Well in my guess, you have same problem:-) as mine | 01/01/70 00:00 | |
Polling the 24C02 EEPROM for ready | 01/01/70 00:00 | |
OOPS wrong logic | 01/01/70 00:00 | |
I thought that I should try your code | 01/01/70 00:00 | |
Polling the 24C02 EEPROM for ready | 01/01/70 00:00 | |
great, but do not forget to mention | 01/01/70 00:00 | |
The Clock | 01/01/70 00:00 | |
addition - show the full picture - 'edit' to above![]() | 01/01/70 00:00 | |
i2c function signatures | 01/01/70 00:00 | |
hello friend | 01/01/70 00:00 |