I am using S32 Design Studio 3.5 with an RDT environment and the GHS toolchain, and I have encountered an issue with the Memory Map view.
When I perform Flash erase and write operations while running from RAM, the actual memory contents are updated correctly (I can confirm this by reading the data back). However, the Memory Map view does not refresh and continues to display the old values.
Details:
Environment: S32DS 3.5 + RDT + GHS toolchain
The project builds and runs successfully.
Flash erase/write operations work as expected (verified by reading memory).
The Memory Map view in S32DS does not update automatically to reflect these changes.
My questions are:
1)Is this a known issue with the S32DS 3.5 Memory Map view?
2)Is there a way to force refresh so that the Memory Map shows the updated contents after runtime Flash operations?
3)Could this behavior be related to the toolchain (GHS), or is it an IDE limitation?
Any advice or workaround would be highly appreciated.
Thanks in advance!
Hi @sochoi,
Memory Monitors should be updated once the memory is written, however, Eclipse's Memory View does not update while the part is running. For instance, the C40_Ip_Example project writes into sector 0x00600000. After writing with C40_Ip_MainInterfaceWrite, I can see the memory updated when stopping:
Regarding your questions:
1) No. This is not a known limitation. Try suspending or doing single steps through the project.
2) You can change the view to traditional and refresh the view directly:
You could also remove and re-add the memory monitor, which should force a re-read.
3) Not really, as this is IDE behavior. Toolchain configuration should not affect the memory display for Eclipse.
Best regards,
Julián
