| ??? 09/20/08 13:16 Read: times |
#158443 - why do you think it IS the code? Responding to: ???'s previous message |
Also, as I have already said, try to separate the problems: write the EEPROM in known good programmer or hardware and try to read it out using the '51; and then the other way round. This might shed some light on where lies the problem.
Also, separate possible compiler problems: try to write/read 4 *bytes* at a time (e.g. an array of 4 bytes, or simply, 4 separate bytes), rather than float. If you succeed in this, you can then proceed to the float. JW PS. You said a single byte works - is it on this very hardware? Post the related code. |
| 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 |