• State Not Answered
  • Locked Locked
  • Replies 30 replies
  • Subscribers 22 subscribers
  • Views 4065 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Mark Johnson

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
  • 0 in reply to Andy Neil

    If it read the ROM, all it would have would be the binary executable

    Sometimes, that's all you need. Usually, it's better than nothing at all.

    I ran into pretty much the same problem while writing a firmware upgrade function for the ADuC845 - the emulator doesn't even consider that ROM contents might change, so there's no way to check execution of an flash EEPROM write operation. I don't need symbol info - I only need to know if ROM address 0x1234 has the value 0xAB after I issue the appropriate write command.

Reply
  • 0 in reply to Andy Neil

    If it read the ROM, all it would have would be the binary executable

    Sometimes, that's all you need. Usually, it's better than nothing at all.

    I ran into pretty much the same problem while writing a firmware upgrade function for the ADuC845 - the emulator doesn't even consider that ROM contents might change, so there's no way to check execution of an flash EEPROM write operation. I don't need symbol info - I only need to know if ROM address 0x1234 has the value 0xAB after I issue the appropriate write command.

Children