| ??? 08/20/01 02:36 Read: times |
#14231 - RE: AT89S8252\'s EEPROM |
I believe that the eeprom is treated as address 0x2000 by programmers, even though it is 0x0000 in xdata.
How to deal with it with a compiler ? I don't know. There could be a keyword to treat the data as existing at 2 different addresses. For the short term, if it is a small amount of data, you could let the program initialize the locations using the magic technique. |
| Topic | Author | Date |
| AT89S8252's EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252's EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252's EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\\\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\\\\\\\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252's EEPROM - J.Guy | 01/01/70 00:00 | |
| RE: AT89S8252\\\\\\\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\\\\\\\\\\\\\\\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\\\\\\\\\\\\\\\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'s EEP | 01/01/70 00:00 | |
| RE: AT89S8252's EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\\\'s EEPROM | 01/01/70 00:00 | |
| RE: AT89S8252\'s EEPROM Jacek | 01/01/70 00:00 | |
| RE: AT89S8252\'s EEPROM J.Guy | 01/01/70 00:00 | |
RE: AT89S8252's EEPROM | 01/01/70 00:00 |



