SEGGER J-Link GDB Server V6.46h Command Line Version , JLinkARM.dll V6.46h (DLL compiled Jun 28 2019 17:11:34)
When the FLASH memory is erased, the GDB server reads the values from the 0x8000000 address range as they were before erase. The aliased address 0x000000 is read correctly. The program (C program) reads the flash correctly. The Jlink gdb server displays data before the erase 0x8000000
In the example below you can see sample code. The program stops in the software breakpoint.
![](https://forum.segger.com/index.php/Attachment/3404-code-png/)
And the pointers. The *ptr1 is read wrong.
![](https://forum.segger.com/index.php/Attachment/3405-data-png/)
The data is shown as read:
![](https://forum.segger.com/index.php/Attachment/3406-jlink-png/)
And some memory dumps. The jlink gdb server shows that the data was read from the 0x8000000+ address but it returns the old data instead the new one.
![](https://forum.segger.com/index.php/Attachment/3408-0x8-png/)
When the FLASH memory is erased, the GDB server reads the values from the 0x8000000 address range as they were before erase. The aliased address 0x000000 is read correctly. The program (C program) reads the flash correctly. The Jlink gdb server displays data before the erase 0x8000000
In the example below you can see sample code. The program stops in the software breakpoint.
And the pointers. The *ptr1 is read wrong.
The data is shown as read:
And some memory dumps. The jlink gdb server shows that the data was read from the 0x8000000+ address but it returns the old data instead the new one.