I'm currently working on creating a CAN based bootstrap loader for the
DSPF80x family. The issue I have is that the CodeWarrior Debugger (v6.1.2)
refuses to refresh its presentation of any P Memory location unless I close the
current debug session and relaunch a new one. Even "Restart" from the Debug
menu does not help. I've tried just about everything I can think of to refresh
the program memory view within a debug session without success. All data (X
Memory) refreshes without difficulty and is presented as expected.
It appears that the dubugger reads all P memory locations at debugger
launch, locally caches it within the PC, and simply assumes that all Program
memory will never ever again be rewritten. Does anyone have any idea whether
this is true?
Fortunately, this is only an incovenience but it sure would be nice to watch
P memory erase and update as the boot loader module is executing.
Thanks in advance for any input.
Jay E. Pochert
Sr. Software Engineer
Advanced Product Development