IMXRT685EVK - Suddenly can't run debug image

[jlee1990]

Platform: MCUXpresso IDE v11.5.1

Board: mimxrt685audevk

SDK:SDK_2_11_1_MIMXRT685-AUD-EVK

Issue:

I am working on the RT685-AUD-EVK board, everything was fine couple days ago. But I suddenly not able to debug it successfully (even with the example-led project that provided by SDK).

Once I click the debug, it do load the image and connect to device through Jlink, but the program just hang and not able to halt at main. If I press the suspend bottom, I see the PC is stock at 0x1c04a (also another address, 0x1300cba4, below it).

Test with jlink.exe below:

SEGGER J-Link Commander V7.70e (Compiled Aug 31 2022 17:13:04)
DLL version V7.70e, compiled Aug 31 2022 17:11:40

Connecting to J-Link via USB...O.K.
Firmware: J-Link LPCXpresso V2 compiled Aug 23 2021 09:30:06
Hardware version: V1.00
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 723699336
VTref=3.300V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMXRT685S_M33
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMXRT685S_M33" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x84770001)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FE000
CPUID register: 0x410FD213. Implementer code: 0x41 (ARM)
Feature set: Mainline
Found Cortex-M33 r0p3, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FE000
[0][0]: E00FF000 CID B105100D PID 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
[1][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33
[1][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT
[1][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB
[1][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM
[1][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM
[1][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI
[0][1]: E0040000 CID B105900D PID 000BBD21 DEVARCH 00000000 DEVTYPE 11 Cortex-M33
Cortex-M33 identified.
J-Link>

[jlee1990]

A quick update regards to this issue:

After compared with another RT685-EVK board, I found the JP-39 (QSPI memory data3 pin) had been removed unintentionally.

Therefore I got hang at 0x0001C04A since the QPI flash didn't work properly without jumper. ( Also, if I remove flash memory region from the memory map, it work too.)

Thanks,

Jason Lee

[jay_heng]

See the reason that PC is stuck in 0x1c04a :

https://www.cnblogs.com/henjay724/p/14027404.html

[jlee1990]

Hi Jay, 

Thanks for the reply. But I still don't understand how to fix that Debug Mailbox issue. Shouldn't the default JLink script from the MCUXpresso IDE just work? I never touched any setting for the Jlink script, but suddenly got that issue.

I've enclosed the Jlink output from the IDE here. The booting process seems to match what you said from the article. "Link target -> execute script (InitTarget() & ResetTarget()) -> Flash download"

But the PC still stock at 0x0001C04A.

I also try to use the script provided from SDK (SDK_2_11_1_MIMXRT685-AUD-EVK\boards\mimxrt685audevk\driver_examples\gpio\led_output\mdk\JLinkSettings.JLinkScript), but that script didn't work as well.

Best, 

Jason Lee