Hi
I'm debugging on an iMXRT1020. We use RTT and SystemView extensively. The iMXRT1020 has 256 KB ram on-board. This is configured at reset to be 64 KB ITCM, 64 KB DTCM, and 128 KB OCRAM. We put the _SEGGER_RTT struct in the DTCM, which RTT and SystemView find automatically. That is, until we recently changed the TCM configuration so that at code entry it is reconfigured to 96 KB ITCM, 160 KB DTCM. The additional data we put into DTCM caused _SEGGER_RTT to be placed > 64 KB into the DTCM, which the Segger tools (J-Link GDB Server V6.46g OSX) was unable to find. If we re-arrange things so that _SEGGER_RTT is placed in that 1st 64 KB of DTCM, the tools find it and work.
We're able to work around this, but want to let you know in case this is something that can be fixed in the Segger tools.
Thanks.
-Kevin
I'm debugging on an iMXRT1020. We use RTT and SystemView extensively. The iMXRT1020 has 256 KB ram on-board. This is configured at reset to be 64 KB ITCM, 64 KB DTCM, and 128 KB OCRAM. We put the _SEGGER_RTT struct in the DTCM, which RTT and SystemView find automatically. That is, until we recently changed the TCM configuration so that at code entry it is reconfigured to 96 KB ITCM, 160 KB DTCM. The additional data we put into DTCM caused _SEGGER_RTT to be placed > 64 KB into the DTCM, which the Segger tools (J-Link GDB Server V6.46g OSX) was unable to find. If we re-arrange things so that _SEGGER_RTT is placed in that 1st 64 KB of DTCM, the tools find it and work.
We're able to work around this, but want to let you know in case this is something that can be fixed in the Segger tools.
Thanks.
-Kevin