Flash memory changes are shown incorrectly

[unsvp]

Changes in Flash memory does not update automatically or via Refresh button or after Edit.
Flash memory changes can appear in a bootloader firmware, EEPROM emulation, by debugger commands, etc.

Steps to reproduce the behavior:

1. Flash any software
2. Open Memory view for the software program code
3. Erase corresponding flash page/sector (e.g. putty + openocd)
4. NotOK: observed memory region contains cached data (0x08000000..0x080001FF), not FFs:

5. NotOK: create new memory region with the same address -> nothing happened
6. NotOK: edit address of the region -> nothing happened
7. Workaround: delete the region and create new with the same address -> data is correctly shown.

[haneefdm]

We have no clue what is FLASH or what is RAM. You refesh (or we auto refresh) and ask gdb to give us new memory contents. Then, we show you whatever GDB tells us. GDB may not ever update memory it thinks is read-only.

You have to figure out how to tell your compiler toolchain that certain areas of your memory are read/write. This is what GDB relies on. We are not compiler, linker of gdb experts.

Please see if Google or AI can help you with gdb or the compiler toolchain. Openocd could also help perhaps. Not sure.

Workaround: delete the region and create new with the same address -> data is correctly shown.

This is interesting though. Unless it is the first time that memory was requested from GDB (meaning GDB cache was empty). then it surprising.

In your debugger you can enable debug logs to see the memory read requests and see what gdb is returning to you. If GDB is returning invalid/stale values then I don't know what we can do about that.

See if you force GDB not to cache. We never talk to your GDB so, we can't do anything.

https://sourceware.org/gdb/current/onlinedocs/gdb.html/Caching-Target-Data.html