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
The load options in http://www.keil.com/support/man/docs/uv3/uv3_cm_load.htm do not address the problem. 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.
I'm using SiLabs usb debugger for their 8051 chips. The otherwise terrible SiLabs IDE has no problem refreshing it's view of flash directly from flash (what a concept!).
I'm using SiLabs usb debugger for their 8051 chips. The otherwise terrible SiLabs IDE has no problem refreshing it's view of flash directly from flash
Than what is the problem, you just staed that it woeks.
Is it that you are incapable of working outside the Keil IDE?
Erik
I have used the SiLab ide for issues like this. It takes considerable time to make sure the everything is set up properly in the SiLab ide to match the settings of Uvision in order to create the exact image. This can take hours.
I don't want to use some crappy IDE, when the best tool just needs to refresh it's view of flash. This is not a difficult concept.
"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."
What does a flash have in it at the time of manufacture?
Is that known to The AlMighty CReator,
imean the manufacturer..
wonder what this talk is for... once it is been "accepted" to interface for a particular purpose, the flash will be connected to the same, to load the intended program, is it not so,
< b>Flash also needs to know what is in 8051.
"It takes considerable time to make sure the everything is set up properly in the SiLab ide to match the settings of Uvision in order to create the exact image"
As a workaround, can you not just load the image built by uVision into the SiLabs IDE for this?
"I don't want to use some crappy IDE, when the best tool just needs to refresh it's (sic) view of flash."
Have you contacted Keil support about this?
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,
What did you want to say.?
"I don't want to use some crappy IDE, when the best tool just needs to refresh it's (sic) view of flash." whats sic in that,
Have you contacted Keil support about this? Keil being BUSY, has time for BASIC queries..? I wonder,
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