| ??? 05/30/07 08:52 Read: times |
#140034 - work around For That Responding to: ???'s previous message |
Ok,that's what I was trying to but ... silly me !
I have put a lengthy printf instruction for debugging purpose in the middle of the putbyte function. With that code I have short clock pulses and "very" long SDA states. Yesterday, I grabbed an old clunky HP1631 logic analyzer and got rid of printf calls. I now have the shortest SCL clock period at 13,5µs based on nop calls delays. I have now to spend more time on debugging as I can see all SCL/SDA transactions. |
| 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 |