AnsweredAssumed Answered

MIMXRT1060-EVK Stops responding to onboard debugger and does not run the preprogrammed example

Question asked by Richard Tilson on Jul 29, 2020
Latest reply on Aug 3, 2020 by Sabina Bruce

While developing on the mimxrt1060-evk I tried to use the OCRAM (0x2020_0000) as the loading point for my application. The program failed and the chip threw Hardfaults. However, after I corrected the configuration in the IDE, the MCU stopped responding to the built in debugger and is not executing the preprogrammed example. I am not sure what happened and not sure how to proceed with diagnosing the issue.

 

The configuration boot switch SW5 is all set to the off position, and the SW7 switch has 1,2,4 set to off and 3 set to on. I have not attempted to write any programs to the flash chips or change the onboard programming from the factory.

 

How do I come out of this state?

 

The redlink log file:

[Started server]
[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = ARM
Description = CMSIS-DAP
Serial Number = 02290000060ba1d500000000000000000000000097969905
VID:PID = 0D28:0204
Path = \\?\hid#vid_0d28&pid_0204&mi_03#7&33a7b045&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink> ProbeStatus
Index = 1
Manufacturer = ARM
Description = CMSIS-DAP
Serial Number = 02290000060ba1d500000000000000000000000097969905
VID:PID = 0D28:0204
Path = \\?\hid#vid_0d28&pid_0204&mi_03#7&33a7b045&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 64
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Probe Handle 1 Open
redlink> WireIsConnected 1
FALSE
redlink> WireSwdConnect 1
DpID = 0BD11477
redlink> CoresConfigured 1
TRUE
redlink> CoreList 1
Error: Wire Ack Fault - target connected?
redlink> ProbeStatus
redlink> quit

Outcomes