iMXRT 1176 not booting from application code (Error: Wire Ack Fault - target connected?)

[HMUser]

Hi,

We have a MaaXBoard RT running with iMXRT 1176 with external Octal SPI flash. We have developed driver and created .cfx file. 

The driver is verified by using Boot utility tool as well as MCUXpresso GUI Flash tool. We are able to successfully Program/Read/Erase extenal flash. So, the driver seems to be working fine.

We are getting an issue during boot-up after loading application file. The MCU boots to flashloader instead of application file.

Below is the console log displayed:

 MCUXpresso IDE RedlinkMulti Driver v11.6 (Jul 12 2022 16:58:24 - crt_emu_cm_redlink build 4)
Found chip XML file in ../flash_cli_freertos_hello_cm7/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
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
============= END SCRIPT ========================================
Probe Firmware: MCU-LINK r0FF CMSIS-DAP V0.078 (NXP Semiconductors)
Serial Number: XHJPKS3KETS2V
VID:PID: 1FC9:0143
USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&13472939&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: MIMXRT1176xxxxx
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI MaaxBoard_RT_OPI.cfx
Image 'iMXRT1170_SFDP_FlexSPI1_OPI Oct 17 2022 10:32:00'
Opening flash driver MaaxBoard_RT_OPI.cfx
Sending VECTRESET to run flash driver
Flash variant 'iMXRT1170_SFDP_FlexSPI1_OPI Oct 17 2022 10:32:00' detected (32MB = 256*128K at 0x30000000)
Closing flash driver MaaxBoard_RT_OPI.cfx
Connected: was_reset=true. was_stopped=false
Awaiting telnet connection to port 3330 ...
GDB nonstop mode enabled
FreeRTOS stack backtrace is disabled in Non-stop mode (use All-stop)
Opening flash driver MaaxBoard_RT_OPI.cfx (already resident)
Sending VECTRESET to run flash driver
Flash variant 'iMXRT1170_SFDP_FlexSPI1_OPI Oct 17 2022 10:32:00' detected (32MB = 256*128K at 0x30000000)
Writing 59900 bytes to address 0x30000000 in Flash
Sectors written: 0, unchanged: 1, total: 1
Erased/Wrote sector 0-0 with 59900 bytes in 28msec
Closing flash driver MaaxBoard_RT_OPI.cfx
Flash Write Done
Flash Program Summary: 59900 bytes in 0.03 seconds (2089.15 KB/sec)
============= SCRIPT: RT1170_reset.scp =============
SYSTEM Reset
DpID = 6BA02477
APID = 0x84770001
Tokenizer error - at character '\x9'
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
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Vector table SP/PC is the reset context.
PC = 0x00000200
SP = 0x00000200
XPSR = 0x01000000
VTOR = 0x30002000
Error: Wire Ack Fault - target connected?
Set DEMCR = 0x010007F1
Error: Wire Ack Fault - target connected?
============= END SCRIPT ===========================
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
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\MCUXpressoIDE_11.6.0_8187\ide\plugins\com.nxp.mcuxpresso.tools.bin.win32_11.6.0.202207121507\binaries\crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

iMXRT1170 

[mrichardson]

Was there ever a follow up to this?  I am getting this out of the box with all of the example programs provided for an MIMXRT685-AUD-EVK.  What does "Wire ACK Fault in DAP access" indicate?  The error I get from the target is reason 15: "Target error from Commit Flash write" with a message that it "Cannot halt processor".

[jeremyzhou]

Hi，
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
Firstly, I hope you can clarify the below sentence.

The driver is verified by using Boot utility tool as well as MCUXpresso GUI Flash tool. We are able to successfully Program/Read/Erase extenal flash.

Next, I'd like to know whether this error always arises when trying to enter debug mode.

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.
------------------------------------------------------------------------------

[HMUser]

Hi @jeremyzhou,

Thanks for your reply.

1. Below is the console log of Flash GUI Tool. From the logs, it shows that, I'm able to erase flash and program the application file successfully.

Executing flash operation 'Program' (Program file into flash: flash_cli_freertos_hello_cm7.axf) - Wed Oct 19 08:16:48 IST 2022
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.6 (Jul 12 2022 16:58:24 - crt_emu_cm_redlink.exe build 4)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in ./MCUXpressoIDE_11.6.0_8187/workspace/flash_cli_freertos_hello_cm7/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
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
============= END SCRIPT ========================================
Probe Firmware: MCU-LINK r0FF CMSIS-DAP V0.078 (NXP Semiconductors)
Serial Number: XHJPKS3KETS2V
VID:PID: 1FC9:0143
USB Path: \\?\hid#vid_1fc9&pid_0143&mi_00#7&13472939&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
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: MIMXRT1176xxxxx
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI MaaxBoard_RT_OPI.cfx
Image 'iMXRT1170_SFDP_FlexSPI1_OPI Oct 17 2022 10:32:00'
Opening flash driver MaaxBoard_RT_OPI.cfx
Sending VECTRESET to run flash driver
Flash variant 'iMXRT1170_SFDP_FlexSPI1_OPI Oct 17 2022 10:32:00' detected (32MB = 256*128K at 0x30000000)
Closing flash driver MaaxBoard_RT_OPI.cfx
( 65) Chip Setup Complete
Connected: was_reset=true. was_stopped=false
( 70) License Check Complete
Loading 'flash_cli_freertos_hello_cm7.axf' ELF 0x30000000 len 0xE9FC
Opening flash driver MaaxBoard_RT_OPI.cfx (already resident)
Sending VECTRESET to run flash driver
Flash variant 'iMXRT1170_SFDP_FlexSPI1_OPI Oct 17 2022 10:32:00' detected (32MB = 256*128K at 0x30000000)
Writing 59900 bytes to address 0x30000000 in Flash
( 0) Mass erasing Flash
Mass erased flash in 60865msec
1 of 1 ( 0) Writing sectors 0-0 at 0x30000000 with 59900 bytes
( 0) at 30000000: 0 bytes - 0/59900
( 27) at 30000000: 16384 bytes - 16384/59900
( 54) at 30004000: 16384 bytes - 32768/59900
( 82) at 30008000: 16384 bytes - 49152/59900
(100) at 3000C000: 16384 bytes - 65536/59900
Sectors written: 1, unchanged: 0, total: 1
Wrote sector 0-0 with 59900 bytes in 327msec
Closing flash driver MaaxBoard_RT_OPI.cfx
(100) Finished writing Flash successfully.
Flash Write Done
Loaded 0xE9FC bytes in 61286ms (about 0kB/s)
Reset target (system)
Starting execution using system reset
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

error closing down debug session - Nn(05). Wire ACK Fault in DAP access

2. However, the similar error also appears at the end(Program using Flash GUI tool) after system reset.

[jeremyzhou]

Hi @HMUser ,
Thanks for your reply.
Firstly, I was wondering if you can introduce the steps of generating MaaxBoard_RT_OPI.cfx, next, upload the schematic of the MaaXBoard, and lastly, I'd like to suggest you use the tool to read the image to verify whether the image was programmed correctly.
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.
------------------------------------------------------------------------------