| ??? 12/06/10 14:07 Read: times |
#179913 - Problem solved (I think) Responding to: ???'s previous message |
I think I've found the problem. After sending out the bytes I was polling the wrong status bit before starting the NAck polling. Unsurprisingly if you start NAck polling too soon, you don't get the right answer. I blame the poor quality of the example code combined with the mistake in the device datasheet (it said master where it should have said slave). My application doesn't work fully, but the EEPROM bit seems to work now.
When will we get example code worthy of the name? Sigh |
| Topic | Author | Date |
| I2C EEPROMs, best data sheets? | 01/01/70 00:00 | |
| as we are on 8052.com... | 01/01/70 00:00 | |
| my first | 01/01/70 00:00 | |
| what uC | 01/01/70 00:00 | |
| bit-banging I2C master for EEPROMs is trivial | 01/01/70 00:00 | |
| yes, the code is trivial, but ... | 01/01/70 00:00 | |
| Probably majority units don't suffer from the busy-loops | 01/01/70 00:00 | |
| Smart Door Knobs | 01/01/70 00:00 | |
| Andy, Michael | 01/01/70 00:00 | |
| ADuC7026 | 01/01/70 00:00 | |
| WP pin ? | 01/01/70 00:00 | |
| It works sometimes | 01/01/70 00:00 | |
| Timing - erase? | 01/01/70 00:00 | |
| can you givenot enough time? | 01/01/70 00:00 | |
| No erase, no abort | 01/01/70 00:00 | |
| Hidden erase | 01/01/70 00:00 | |
| STOP too short | 01/01/70 00:00 | |
Problem solved (I think) | 01/01/70 00:00 | |
| I2C | 01/01/70 00:00 |