IMXRT1170-EVK Debug broken after memory modifications for BOARD_SDRAM

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

IMXRT1170-EVK Debug broken after memory modifications for BOARD_SDRAM

ソリューションへジャンプ
223件の閲覧回数
galenhevo
Contributor II

I was working within my project to enable the BOARD_SDRAM and now cannot flash/debug any apps including blinky.  I tried a fresh workspace with a fresh hello world project and now get this every time when using the default boot mode QSPI_FLASH:

 

MCUXpresso IDE RedlinkMulti Driver v11.9 (Dec 11 2023 18:09:23 - crt_emu_cm_redlink build 2)
Found chip XML file in /home/galen/hevo/recovery_work/evkmimxrt1170_hello_world_demo_cm7/Debug/MIMXRT1176xxxxx.xml
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: DAPLink CMSIS-DAP (ARM)
Serial Number:  0244000030f481cf00000000000000000000000097969905
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: <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 Operation Failed
error closing down debug session - Nn(05). Wire ACK Fault in DAP access



I am able to get a RAM only project to debug when changing the BOOT SW to SDP_MODE.  Any help on a way to recover the board would be much appreciated.

0 件の賞賛
返信
1 解決策
193件の閲覧回数
galenhevo
Contributor II

In the end I was able to recover using the https://github.com/JayHeng/NXP-MCUBootUtility

setting the board to boot in SDP_MODE I could connect with that tool, and flashed a known good hello_world flash image

There is a similar how-to here for another board:
https://docs.phytec.com/projects/freertos-phycore-rt1170/en/latest/developingwithfreertos/flash-reco...

NOTE: in that how-to they are doing a "mass erase" which I didn't try...overwrite worked in my case.

元の投稿で解決策を見る

0 件の賞賛
返信
1 返信
194件の閲覧回数
galenhevo
Contributor II

In the end I was able to recover using the https://github.com/JayHeng/NXP-MCUBootUtility

setting the board to boot in SDP_MODE I could connect with that tool, and flashed a known good hello_world flash image

There is a similar how-to here for another board:
https://docs.phytec.com/projects/freertos-phycore-rt1170/en/latest/developingwithfreertos/flash-reco...

NOTE: in that how-to they are doing a "mass erase" which I didn't try...overwrite worked in my case.

0 件の賞賛
返信