Dave Perreault <> wrote, >Since the eeprom overlaps the registers, you have two chouces: the EEPROM was already relocated. Oliver -- Oliver Betz, Muenchen (oliverbetz.de)

Since the eeprom overlaps the registers, you have two chouces: 1. Write to the second mapping of the 1k flash at 400. 2. Move the eeprom somewhere else rater than the default. Regards Dave Oliver Betz wrote: >Hello All, > >iSYSTEM tells me that there is a bug at least in the 9S12D64 and >9S12DT128 (not in the DP256) so that it's not possbile to write >EEPROM directly (without "monitor" code) via the BDM interface in >special mode. > >The problem arises when accessing EEPROM latches and registers using >only BDM commands - no code executed on the target. > >As I'm curious, I played a bit and it seems that writing the data >word to the flash address via BDM results in setting the ACCERR bit. > >There is no applicable errata listing, and Motorola support doesn't >know about the issue, so I can't find whether and when this issue >will be solved (in which mask set). _If_ it is really a >Motorola/Freescale issue. > >Can anybody tell me more about this problem? > >TIA, > >Oliver

Hello All, iSYSTEM tells me that there is a bug at least in the 9S12D64 and 9S12DT128 (not in the DP256) so that it's not possbile to write EEPROM directly (without "monitor" code) via the BDM interface in special mode. The problem arises when accessing EEPROM latches and registers using only BDM commands - no code executed on the target. As I'm curious, I played a bit and it seems that writing the data word to the flash address via BDM results in setting the ACCERR bit. There is no applicable errata listing, and Motorola support doesn't know about the issue, so I can't find whether and when this issue will be solved (in which mask set). _If_ it is really a Motorola/Freescale issue. Can anybody tell me more about this problem? TIA, Oliver -- Oliver Betz, Muenchen