| ??? 09/20/08 10:11 Read: times |
#158434 - serial EEPROM Responding to: ???'s previous message |
Dear Arvind,
Arvind Shrivastava said:
Yup!!! ...
I am facing a problem in writing and reading floating values in EEPROM. I am using P89V51RD2 microcontroller and AT24C512 EEPROM ... Previously also I have queried the same question but at that time i got to change my UC to PIC. The solutions you all have provided is working fine with PIC UC with internal EEPROM. But now I have to interface the EEPROM with 8051 and the same problem is still persisting. Arvind First of all EEPROM doesnot understand the terms like long, float, double, int, char, what it knows is byte(s). While storing / reading from EEPROM you actually read or write 'n' bytes(make sure write & read points to same location) Secondly PIC was only one of the possibility (not the only option) you can use a controller that has inbuilt I2C engine with external EEPROM, Many derivatives from phillips (I dont know about p89v51rd2) has inbuilt I2C engine (ref to p89c66x & p89lpc9xx). Regards, Mahesh |
| Topic | Author | Date |
| problem in FLOAT values in AT24C512 EEPROM | 01/01/70 00:00 | |
| What problem? | 01/01/70 00:00 | |
| reply | 01/01/70 00:00 | |
| So how do you know it's the EEPROM? | 01/01/70 00:00 | |
| serial EEPROM | 01/01/70 00:00 | |
| read CODE ... | 01/01/70 00:00 | |
| why do you think it IS the code? | 01/01/70 00:00 | |
| What are the possibilities? | 01/01/70 00:00 | |
| Other possibilities | 01/01/70 00:00 | |
| Reads clock 9 bits too | 01/01/70 00:00 | |
| Also seeming to be missing... | 01/01/70 00:00 | |
| On Sequential reads, the eeprom | 01/01/70 00:00 | |
| Acknowledge bit | 01/01/70 00:00 | |
| You are right Henry. It should be 'bit'. | 01/01/70 00:00 | |
| code is given ... plz read ... | 01/01/70 00:00 | |
| But, Arvind, you DON'T send the ACK after reading! | 01/01/70 00:00 | |
| What code? What tests? | 01/01/70 00:00 | |
| try to read your name | 01/01/70 00:00 | |
| commented code ... | 01/01/70 00:00 | |
| Where is your 9th clock in Read... | 01/01/70 00:00 | |
Dan Henry has already found the mistake! | 01/01/70 00:00 |