Hello,
I built the following synthetic test case to illustrate my problem:
- MIMXRT1170-EVK board set to boot mode "Serial Downloader", SW1-3=OFF, SW1-4=ON
- ROM code is running, no custom firmware is running
- From JLink commander, issue a single read from an invalid memory address 0xCCCCCCCC
- Any subsequent read (from valid addresses) fails.
Do you have any idea what blocks the subsequent reads?
Attachments:
Jlink commander: jlink_mem_read_failure.txt
JLink DLL log: JLinkLogOverride.log
Background info: The real problem happens during a gdb debugging session using optimized C code (-Og). For some reason (I'm still trying to understand the root cause), gdb interprets debug symbols in the wrong way and tries to read from 0xCCCCCCCC which fails of course. Gdb ignores the error and continues. However, because of the issue illustrated above, the debugging session is useless now. I would expect that an invalid read access can be tolerated.
Thanks in advance for any comments.
Udo
I built the following synthetic test case to illustrate my problem:
- MIMXRT1170-EVK board set to boot mode "Serial Downloader", SW1-3=OFF, SW1-4=ON
- ROM code is running, no custom firmware is running
- From JLink commander, issue a single read from an invalid memory address 0xCCCCCCCC
- Any subsequent read (from valid addresses) fails.
Do you have any idea what blocks the subsequent reads?
Attachments:
Jlink commander: jlink_mem_read_failure.txt
JLink DLL log: JLinkLogOverride.log
Background info: The real problem happens during a gdb debugging session using optimized C code (-Og). For some reason (I'm still trying to understand the root cause), gdb interprets debug symbols in the wrong way and tries to read from 0xCCCCCCCC which fails of course. Gdb ignores the error and continues. However, because of the issue illustrated above, the debugging session is useless now. I would expect that an invalid read access can be tolerated.
Thanks in advance for any comments.
Udo