When I flash any vglite SDK examples onto my rt1160, nothing shows on screen. Furthermore, any subsequent attempts to flash another project onto the board gives the following error:
Executing flash operation 'Program' (Program file into flash: evkmimxrt1160_fbdev_freertos_cm7.axf) - Tue Jul 08 14:40:37 EDT 2025
Checking MCU info...
Scanning for targets...
Executing flash action...
LinkServer RedlinkMulti Driver v25.3 (Mar 25 2025 18:39:17 - crt_emu_cm_redlink build 945)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in /home/tzhuang/.workspaces/tmp-june-11/evkmimxrt1160_fbdev_freertos_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
Setting M4 spin code
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
Setting M4 clock
Error: Wire Ack Fault - target connected?
Resetting M4 core
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?
View cores on the DAP AP
DpID = 6BA02477
============= END SCRIPT ========================================
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 02440000020b6f0900000000000000000000000097969905
VID:PID: 0D28:0204
USB Path: /dev/hidraw1
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
connection failed - Nn(05). Wire ACK Fault in DAP access.. Retrying
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
Using memory from core 0 after searching for a good core
Failed on connect: Nn(05). Wire ACK Fault in DAP access
Connected&Reset. Was: NotConnected. DpID: 6BA02477. CpuID: 00000000. Info:
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 Operation Failed
error closing down debug session - Nn(05). Wire ACK Fault in DAP access
Unable to perform operation!
Command failed with exit code 1 The issue can be fixed by putting the board into SDP mode and serially flashing a working project. However, flashing any vglite demo puts the board into a bad state again.
The following demos work for me (with the expected output on my display):
The following demos put the board into a bad state:
Hi @tzhuang,
It seems to be an issue about the SDRAM configuration not being enabled in the flash build configuration. Please add the symbol definition for XIP_BOOT_HEADER_DCD_ENABLE=1 or XIP_BOOT_HEADER_XMCD_ENABLE=1 and try to build and flash the image again. For more information on what these symbol definitions do, please look at Table 3 of the following AppNote: How to Enable Debugging for FLEXSPI NOR Flash
Hi @tzhuang,
I was able to recreate the issue on my side. I tested a vglite example with SDK 2.16.000 and it worked fine. Then I changed to the latest SDK (v25.06.00) and I get a Wire ack fault immediately after flashing the image. My hypothesis is that something changed from SDK 2.xx to 2x.xx that broke the vglite examples.
I have reported this issue internally to the SDK team and will come back as soon as I receive a response.
Thanks for reporting this issue!
BR,
Edwin.
Hi @tzhuang,
What SDK version are you using? Are you using VS Code extension or standalone MCUXpresso? If standalone, what version are you using?