??? 11/20/08 11:12 Modified: 11/20/08 11:14 Read: times |
#160146 - No need to "increment"... Responding to: ???'s previous message |
...but you DO need to read the datasheet more carefully. Everything you say about the addresses of the EEPROM and the need for adding an offset to the dptr are based on sheer misinterpretation of the datasheet on your part, if you have read it at all. The EEPROM in the AT89S8252 starts at exactly the same address as the EEPROM in the AT89S8253, and that isn't at either address 02000h or 03000h, but plain simply at address 0 (page 7 of the datasheet: The EEPROM address range is from 000H to 7FFH). Also, if it were different, this would be mentioned in the MIGRATION document, which happens to exist for these two devices.
Why your original product "worked" I can only guess, but probably (I emphasize: not fact, mere speculation) because the controller ignores the top 7 bits in the supplied address anyway. Again: RTFM |
Topic | Author | Date |
AT89S8253: EEPROM programming via serial COM | 01/01/70 00:00 | |
simple example | 01/01/70 00:00 | |
Problem | 01/01/70 00:00 | |
No need to "increment"... | 01/01/70 00:00 | |
Problem in migrating from AT89S8252 to AT89S8253 - Pls help! | 01/01/70 00:00 | |
Confusion | 01/01/70 00:00 | |
It's Dataflash not EEPROM address, but... | 01/01/70 00:00 | |
I assume that you have external RAM | 01/01/70 00:00 | |
Problem in migrating from AT89S8252 to AT89S8253 - Pls help! | 01/01/70 00:00 | |
Probable answer | 01/01/70 00:00 | |
Probable answer for serial re-program EEPROM | 01/01/70 00:00 | |
AT89S8252, change in serial programing![]() | 01/01/70 00:00 | |
Problem in migrating from AT89S8252 to AT89S8253 - Pls hel | 01/01/70 00:00 | |
Please explain your hardware | 01/01/70 00:00 |