This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uvision not seeing changed flash

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

Parents
  • "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?

Reply
  • "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?

Children