FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

A debug problem

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

A debug problem

‎10-26-2021 05:48 AM
2,813 Views
john71
Senior Contributor I

I work with MIMXRT1160-EVK.

First I build a project.

Then I start Debug  and this message pops-up first

error.png

 

Then I get

MCUXpresso IDE RedlinkMulti Driver v11.4 (Sep 13 2021 15:04:52 - crt_emu_cm_redlink build 16)
Found chip XML file in D:/Workspace_MCUXpresso_11.4/evkmimxrt1160_hello_world_cm7/Debug\MIMXRT1166xxxxx.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: RT1160_connect_M7_wake_M4.scp =============
RT1160 Connect M7 and Wake M4 Script
DpID = 6BA02477
APID = 0x84770001
Error: Wire Ack Fault - target connected?
View cores on the DAP AP
DpID = 6BA02477
============= END SCRIPT ========================================
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 024400000208827100000000000000000000000097969905
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#9&350958c4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
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
Debug bus selected: MemAp 0
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
(100) Target Connection Failed
error closing down debug session - Nn(05). Wire ACK Fault in DAP access

 

The I connec an external debugger J-LINK and I get

J-Link is connected.
Device "MIMXRT1166XXX6_M7" selected.
Firmware: J-Link V10 compiled Aug 9 2021 10:30:48
Hardware: V10.10
S/N: 50119084
Feature(s): GDB
Checking target voltage...
Target voltage: 3.33 V
Listening on TCP/IP port 2331
Connecting to target...
ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Could not connect to target.
Please check power, connection and settings.

Server has been shut down.

What should I do?

 

0 Kudos
Reply
4 Replies

‎10-26-2021 06:59 PM
2,802 Views
jeremyzhou
NXP Employee
NXP Employee

Hi,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
Is it the first time for you to debug the board, in my opinion, the error is related to hardware settings, so I'd like to suggest you to following the link to get started with the i.MX RT1160.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply

‎10-27-2021 05:58 AM
2,797 Views
john71
Senior Contributor I

Recently I successfully downloaded couple of example projects on the board. Right now I'm stuck with the problem. I thought my dev. board is busted somehow but we have a new one and we have the same problem on it.

May be I've messed up with MCUXpresso settings?

0 Kudos
Reply

‎10-27-2021 07:12 PM
2,790 Views
jeremyzhou
NXP Employee
NXP Employee

Thanks for your reply.
From my experience, I'd like to suggest you follow the below steps to solve the issue.
1) Reset the PC, then open the MCUXpresso IDE;
2) Regarding the MIMXRT1160 EVK, set the SW1 to Serial Downloader, then power on the board;
3) Importing a sample demo from the SDK library for the MIMXRT1160 EVK in the MCUXpresso IDE, then debug the demo.
4) After that, power off and recover the SW1 to the previous set, then power on again.
5) Give a debug again.

Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply

‎10-27-2021 11:01 PM
2,784 Views
john71
Senior Contributor I

Thanks. I did so. Now I can flash and debug a standalone project. On my project I get

MCUXpresso IDE RedlinkMulti Driver v11.4 (Sep 13 2021 15:04:52 - crt_emu_cm_redlink build 16)
Found chip XML file in D:/Workspace_MCUXpresso_11.4/evkmimxrt1160_hello_world_cm7/Debug\MIMXRT1166xxxxx.xml
Reconnected to existing LinkServer process.
============= SCRIPT: RT1160_connect_M7_wake_M4.scp =============
RT1160 Connect M7 and Wake M4 Script
DpID = 6BA02477
APID = 0x84770001
View cores on the DAP AP
DpID = 6BA02477
TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
TAP 0: 6BA02477 Core 1: M4 APID: 24770011 ROM Table: E00FF003
============= END SCRIPT ========================================
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 024400000208827100000000000000000000000097969905
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#9&350958c4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0043000: CID B105900D PID 04001BB908 CSt CSTF type 0x12 Trace Link - Trace funnel/router
NXP: MIMXRT1166xxxxx
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1160_SFDP_QSPI.cfx
Image 'iMXRT1160_FlexSPI_SFDP_QSPI Sep 14 2021 15:10:31'
Opening flash driver MIMXRT1160_SFDP_QSPI.cfx
Sending VECTRESET to run flash driver
Flash variant 'JEDEC_FlexSPI_Device' detected (16MB = 256*64K at 0x30000000)
Closing flash driver MIMXRT1160_SFDP_QSPI.cfx
Connected: was_reset=false. was_stopped=false
Awaiting telnet connection to port 3330 ...
GDB nonstop mode enabled
Opening flash driver MIMXRT1160_SFDP_QSPI.cfx (already resident)
Sending VECTRESET to run flash driver
Flash variant 'JEDEC_FlexSPI_Device' detected (16MB = 256*64K at 0x30000000)
Writing 243260 bytes to address 0x30000000 in Flash
30004000 done 6% (16384 out of 243260)
30008000 done 13% (32768 out of 243260)
3000C000 done 20% (49152 out of 243260)
30010000 done 26% (65536 out of 243260)
30014000 done 33% (81920 out of 243260)
30018000 done 40% (98304 out of 243260)
3001C000 done 47% (114688 out of 243260)
30020000 done 53% (131072 out of 243260)
30024000 done 60% (147456 out of 243260)
30028000 done 67% (163840 out of 243260)
3002C000 done 74% (180224 out of 243260)
30030000 done 80% (196608 out of 243260)
30034000 done 87% (212992 out of 243260)
30038000 done 94% (229376 out of 243260)
3003C000 done 100% (245760 out of 243260)
Sectors written: 4, unchanged: 0, total: 4
Erased/Wrote sector 0-3 with 243260 bytes in 11208msec
Closing flash driver MIMXRT1160_SFDP_QSPI.cfx
Flash Write Done
Flash Program Summary: 243260 bytes in 11.21 seconds (21.20 KB/sec)
============= SCRIPT: RT1160_reset.scp =============
SYSTEM Reset
DpID = 6BA02477
TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
TAP 0: 6BA02477 AP 1: APID: 24770011 ROM Table: E00FF003
TAP 0: 6BA02477 AP 2: APID: 54770002 ROM Table: 00000002
APID = 0x84770001
Setting M4 spin code
Setting M4 clock
Resetting M4 core
Releasing M4
View cores on the DAP AP
DpID = 6BA02477
TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
TAP 0: 6BA02477 Core 1: M4 APID: 24770011 ROM Table: E00FF003
R15 = 0x00223104
Vector table SP/PC is the reset context.
PC = 0x300024C1
SP = 0x20040000
XPSR = 0x01000000
VTOR = 0x30002000
============= END SCRIPT ===========================
16: Target error from status-poll: Nn(05). Wire ACK Fault in DAP access
Unknown/broken state: Nn(05). Wire ACK Fault in DAP access: <cannot read registers>Unknown
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access

0 Kudos
Reply