Hi, all:
MCUXpresso IDE RedlinkMulti Driver v11.9 (Dec 11 2023 18:02:10 - crt_emu_cm_redlink build 2)
Found chip XML file in E:/4_workplace_test/14_testqt/evkmimxrt1170_iled_blinky_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
Error: Wire Ack Fault - target connected?
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
Error: Wire Ack Fault - target connected?
Error: Wire Ack Fault - target connected?
============= END SCRIPT ========================================
Probe Firmware: CMSIS-DAP (ARM)
Serial Number: 024400002faba2a000000000000000000000000097969905
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#8&1c056edf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
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: <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.
error closing down debug session - Nn(05). Wire ACK Fault in DAP access
I tried change to serial boot loader, but it still not work.
The attachment contains the ELF file that I compiled.
What do I need to do to recover the MIMXRT1170-EVKB ?
Thank you!
已解决! 转到解答。
Hello @pupu_ji ,
The output log that you provide me, occurs commonly when the core has in an unknown state and the debugger can't stop them, this can happen in low power states or if the project has an issue in any clock configuration.
To recovery your EVKB you can follow this application note ( RT board recovery for debugger connect issues - NXP Community). Although the application note uses the MIMXRT1060-EVK, it's the same with MIMXRT1170-EVKB. Also, after of recover the EVKB, you can try writing an SDK example. It could be the example called "Iled_blinky_cm7", this in order to corroborate that the EVKB works properly.
Also, if you experience any issue, do not hesitate to let me know.
BR,
Habib.
Hello @pupu_ji ,
The output log that you provide me, occurs commonly when the core has in an unknown state and the debugger can't stop them, this can happen in low power states or if the project has an issue in any clock configuration.
To recovery your EVKB you can follow this application note ( RT board recovery for debugger connect issues - NXP Community). Although the application note uses the MIMXRT1060-EVK, it's the same with MIMXRT1170-EVKB. Also, after of recover the EVKB, you can try writing an SDK example. It could be the example called "Iled_blinky_cm7", this in order to corroborate that the EVKB works properly.
Also, if you experience any issue, do not hesitate to let me know.
BR,
Habib.
Hello @amira ,
In order to provide you a better support, can you open a new post?
In this post you can provide me your specific problem in detail, without any problem you can tag me and with pleasure I will answer you.
BR,
Habib