Hello,
We are trying to debug a Secondary bootloader for IMXRT 1024 using the iMXRT 1024 evk board and MCUXpresso IDE. Whenever the debug session is launched, we get the following error:
cleo_0-1787762322632.png
============= SCRIPT: IMX93_connect_M33.scp =============
IMX93 M33 Connect Script
Reset pin state: 01
DpID = 0BD11477
TAP 0: 0BD11477 Core 0: M7 APID: 04770041 ROM Table: E00FD003*
TAP 0: 0BD11477 Core 0: M7 APID: 04770041 ROM Table: E00FD003*
APID = 0x04770041
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
m = 0x04770041
n = 0x04770041
... reconnect to see M33
DpID = 0BD11477
APID = 0x04770041
... disables the ECC logic for Cortex-M33 TCM
... disables the ECC logic for Cortex-M33 CACHE
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
... send a request to EdgeLock secure enclave to release the Cortex-M33 TROUT
... check
Error: Wire Ack Fault - target connected?
Resp1 : 0x000000C8
Error: Wire Ack Fault - target connected?
Resp2 : 0x000000C8
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
SCR = 0x00000000
M33_CFG = 0x00000000
TAP 0: 0BD11477 Core 0: M7 APID: 04770041 ROM Table: E00FD003*
M33 kicked off
Error: AP not ready
Error: No Halt Confirmation
============= END SCRIPT ================================
following reset read of core registers failed - Ep(08). Cannot access core regs when target running.
Target error from Commit Flash write: Ep(08). Cannot access core regs when target running.
GDB stub (C:\nxp\LinkServer_25.6.131\binaries\crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.
What is the cause of this issue? Hoe can it be fixed?
Hi @cleo ,
Thank you so much for your interest in our products and for using our community.
I don't think this issue is caused by the secondary bootloader itself.
From the debug log, it appears that MCUXpresso IDE / LinkServer is running the following connect script:
Could you please try below?
1: In MCUXpresso IDE, delete the existing debug launch configuration for this project.
2: Confirm that the project MCU/board is configured for an i.MX RT1024 device (or RT1024 EVK), not an i.MX93 device.
3: Open the launch/debug configuration and verify that the selected device/core is RT1024.
If possible, You can also share a screenshot of the Debug Configuration settings for further review.