We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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 Keil Monitor drivers have 'cache' options that you simply may disable to see code changes that are done by some hardware mapping.
Yes, this is the sort of thing I'm looking for. The drivers for the SiLab debuggers do not have this option, so I suppose this is a SiLab problem. But if Uvision can refresh it's view of ram, then it should be able to refresh it's view of flash as well.
I don't need C source level debugging or symbols. I simply want to single step through the new code in the disassembly window.
Cache, Primary memory, etc are in PC, 8051, flash has only one memory, in it, part for code : once set is set, part for data: for day to day purpose
after much consideration, debugging, checking out the program, it is committed to the purpose, its done only once but the right one, so that there is no need for repenting later on, coz everybody agrees memories are delicate.
part for code : once set is set"
You've never heard of In-Application Programming (IAP), and firmware updates, then?
"everybody agrees memories are delicate"
Do they??
What s that?
memories are used with careful consideration, is it not?