| ??? 12/06/10 09:41 Read: times |
#179896 - ADuC7026 Responding to: ???'s previous message |
It's an ARM core. The chip comes with an I2C hardware interface, and I can reliably read from the EEPROM. The problem I'm having is that I can't write to the EEPROM. I've bought an I2C bus analyser, so I can snoop on the bus, but I don't know exactly why the EEPROM isn't happy.
My system could quite happily use busy loops as I'm only reading configuration values at startup, but I'm reluctant to throw away what I have to go bit banging. |
| 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 |