Hello,
I'm debugging a firmware update problem and notice that uVison2 and 3 do not refresh the dissasembly or code memory views.
In other words, my app writes the new code into flash, but Uvision still thinks the old code is there.
Is there a way to get the latest version of uVision to refresh it's view of flash?
Thanks,
Mark
"I need to know what's actually in flash memory, not what I think is in flash memory or what Uvision thinks is in flash memory."
Do you simply need to know what's there, as Christoph Franck is saying, or do you also want to continue symbolic debugging of the newly-loaded image?
For the former, doesn't the memory display window read directly from the target?
For the latter, how does the SiLabs IDE know where to get its symbol information to match the new image?
What interface are you using between uVision and your target?
Whats meant by symbolic debugging of the newly-loaded image,
Andy, I don't need symbolic debugging. I just need to single step at the assembly level for a little while through the newly written code. What I see now when I single step through the new code is the disassembled old code. A memory view of the new area also shows the old data. I am using the SiLab usb jtag debugger.
ok, understood,
" where do u get the new code"
"sometimes , just sometimes, dont u ever feel like a zombie working in Embeddede systems..."
The new code comes in from the serial port.
dont u ever feel like a zombie
evidently YOu did
Erik