I'm trying to debug an application located in DDR and running on the M4 core of the i.MX6SX.
I'm using a Segger JLink+ probe and a i.MX6SoloX Sabre SDB board.
The A9 core boots U-Boot from QSPI NOR, then I load the M4 application using tftpboot and start the application using bootaux command.
To debug, I start the JLink GDB server (see attached script) then I connect using Eclipse.
I'm able to debug (breakpoints, stepping...) when the code is located in internal RAM (OCRAM or TCM).
When the code is located in DDR, I can set a breakpoint and stop on it. But then I cannot do anything, the M4 program counter is stuck and I cannot do stepping, examine memory...
Did anyone already experienced this problem? Any idea to solve this?
Original Attachment has been moved to: iMX6SoloX_Connect_CortexM4.JLinkScript.zip