topic Re: Debug problem due to DAP Bus in iMXRT1170 EVKB in i.MX Processors

Debug problem due to DAP Bus in iMXRT1170 EVKB

KKR231 — Thu, 04 Jul 2024 09:49:33 GMT

While debugging i got the problem

Probe Firmware: MCU-LINK on-board (r0E2) CMSIS-DAP V2.250 (NXP Semiconductors)

Serial Number: NVUYDXEI5YUN1

VID:PID: 1FC9:0143

USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&38ddcd02&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

connection failed - Em(04). Cannot provide power to DAP bus... Retrying

Failed on connect: Em(04). Cannot provide power to DAP bus.

Connected&Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000000. Info: <None>

Last stub error 0: OK

Last sticky error: 0x0 AIndex: 0

No debug bus (MemAp) selected

DAP Speed test unexecuted or failed

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled

How can I solve it?? Pl guide me

Re: Debug problem due to DAP Bus in iMXRT1170 EVKB

kerryzhou — Fri, 05 Jul 2024 04:09:07 GMT

Hi @KKR231 ,

Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.

Whether you can do the CMSIS DAP debug in the MIMXRT1170-EVKB previously?

Do you update the CMSIS DAP version or not recently?

I think your situation may related to the following 2 points:

1. You may download some abnormal app to the flash, that will cause the debugger connection issues, you can refer to my document:

https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT-board-recovery-for-debugger-connect-issues/ta-p/1635260

2. If you update the CMSIS DAP version

You can power on the board with the external DC power supply, or you also can find anoter USB cable to connect the SDP USB interface to power on it.

As I know, new CMSIS DAP have the power on issues, need to use ansother USB or the DC power to power on the board.

Please try it on your side.

If you still have question about ti, please kindly let me know.

Best Regards,

Kerry

Re: Debug problem due to DAP Bus in iMXRT1170 EVKB

KKR231 — Mon, 08 Jul 2024 04:10:25 GMT

Still i got following problem during flashing RT

"Executing flash operation 'Erase' (Erase flash) - Mon Jul 08 09:37:17 IST 2024

Checking MCU info...

Scanning for targets...

Executing flash action...

MCUXpresso IDE RedlinkMulti Driver v11.9 (Dec 11 2023 18:02:10 - crt_emu_cm_redlink.exe build 2)

( 0) Reading remote configuration

Found chip XML file in C:/Users/Admin/Documents/MCUXpressoIDE_11.9.0_2144/workspace/FreeRTOS_TAD_logs/evkbmimxrt1170_iled_blinky_cm4/Debug\MIMXRT1176xxxxx.xml

( 5) Remote configuration complete

Reconnected to existing LinkServer process.

============= SCRIPT: RT1170_connect_M7_wake_M4.scp =============

RT1170 Connect M7 and Wake M4 Script

DpID = 6BA02477

Error: No power acknowledge on DAP bus

Setting M4 spin code

Error: Wire Ack Fault - target connected?

Setting M4 clock

Error: Wire Ack Fault - target connected?

Resetting M4 core

Error: Wire Ack Fault - target connected?

View cores on the DAP AP

DpID = 6BA02477

Error: Wire Ack Fault - target connected?

============= END SCRIPT ========================================

Probe Firmware: MCU-LINK on-board (r0E2) CMSIS-DAP V2.250 (NXP Semiconductors)

Serial Number: NVUYDXEI5YUN1

VID:PID: 1FC9:0143

USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&38ddcd02&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

connection failed - Em(04). Cannot provide power to DAP bus... Retrying

Failed on connect: Em(04). Cannot provide power to DAP bus.

Connected&Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000000. Info: <None>

Last stub error 0: OK

Last sticky error: 0x0 AIndex: 0

No debug bus (MemAp) selected

DAP Speed test unexecuted or failed

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

(100) Target Operation Failed

Unable to perform operation!

Command failed with exit code 1"

I set SW1 in serial mode but it's not working.

Re: Debug problem due to DAP Bus in iMXRT1170 EVKB

kerryzhou — Mon, 08 Jul 2024 05:29:16 GMT

Hi @KKR231 ,

Thanks for your updated information.

Please follow me:

1. Board power off, then SW1 : 1-off,2-off,3-off,4-on

2. Find another USB cable, connect to the J20

3. power on the board.

4. open the MCUbootutility tool:

https://github.com/JayHeng/NXP-MCUBootUtility/releases/tag/v6.2.0

the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility

Use the mcubootutility to do the mass erase:

After the erase finished, then can switch the SW1 back to internal boot mode, SW1:1-OFF,2-OFF,3-ON, 4-OFF, then use the on board CMSIS DAP download the code in the mcuxpresso IDE again.

Please try it.

If you still have question about it, please kindly let me know.

Best Regards,

kerry