Join our technical discussions about Freescale Microcontrollers: M68HC12. (Freescale Semiconductor is a Subsidiary of Motorola).
|
OK - im not so sure that securing the device is the reason for my not being able to write eeprom when the device is secured. However,writting eeprom with the device security bit is not set works perfectly. I have routines setup to send ascii strings for debugging out of the serial port (which work) and when the device security bit is set, i do not get access error or protection violations writting to eeprom, but the contents of eeprom arent changing! eeprom is located at 0x800 to about 0xa00 and the program code is located at 0xc000 to about 0xd5f1 or so. I really would like to secure the device, but allow access to eeprom. At this point i really have no idea why i cant have both. My eeprom routines work when the device is not secured, and when the device is secured, writting to eeprom doesnt work, but not eeprom error flags are set when i try to erase and re-write it during runtime. I never write the protection registers for the eeprom. only the flash. What could this be!? Thanks for the help, i really appreciate it. --Eric |