MIMXRT1024-EVK stuck in maintenance mode

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MIMXRT1024-EVK stuck in maintenance mode

Jump to solution
899 Views
bridgenet
Contributor II

I have the RT1024-EVK that has been working fine.  I was converting a program to C++ and while debugging the new image that was downloaded it did not run properly and I think faulted as it was trying to invoke the C++ constructors.  Seems with this program present in QSPI I can no longer load a new program and access the debugger.  Now It pops up a file explorer window on my Windows 10 computer even though I am not holding the SW9 button down.  I went through a number of posts on other boards (1050/1060) and when I attempt to update lpc4322_mimxrt1024_evk_qspi_if_crc.bin or lpc4322_bl_crc.bin firmware via drag and drop I get a fail.txt file contents:  error: The application file format is unknown and cannot be parsed and/or processed.  The red LED seems to be flashing a sequence but it is hard to decipher what it is, looks like 16 flashes, pause 3 flashes.  Any thoughts on how to recover the debugger operation?

Details.txt contents:

# DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 023800003251a38500000000000000000000000097969905
HIC ID: 97969905
Auto Reset: 0
Automation allowed: 0
Overflow detection: 0
Daplink Mode: Interface
Interface Version: 0246
Bootloader Version: 0244
Git SHA: cac2d1e68a23e83eea0a9649537b48f50b864fb9
Local Mods: 1
USB Interfaces: MSD, CDC, HID, WebUSB
Bootloader CRC: 0xe493996b
Interface CRC: 0x864adfd5
Remount count: 1

 

0 Kudos
1 Solution
876 Views
bridgenet
Contributor II

 

For the next person that has to do this it would have been nice if NXP gave more details on what had to be done but I finally figured it out using the hint from Jeremy:

1. Disconnect USB debug port from PC and move jumper from J43 to DFU Boot Jumper J42 (J43 not needed to reflash and there are no spare jumpers on the board so used J43).

2. Download and install LPCScrypts: https://www.nxp.com/design/microcontrollers-developer-resources/lpcscrypt-v2-1-2:LPCSCRYPT

3. I used a dedicated 5V supply, not sure if needed. Cycle power and connect USB debug port to your PC.

3. Change your directory to:

C:\nxp\LPCScrypt\scripts>dir
Volume in drive C is OS
Volume Serial Number is 547F-9135

Directory of C:\nxp\LPCScrypt\scripts

09/08/2022 11:27 AM <DIR> .
09/08/2022 11:27 AM <DIR> ..
05/25/2017 04:38 PM 606 aeskey.cmd
05/25/2017 04:38 PM 1,218 boot_lpcscrypt.cmd
05/25/2017 04:38 PM 1,022 encrypt_and_program.cmd
05/25/2017 04:38 PM 228 encrypt_and_program.scy
05/25/2017 04:38 PM 135 ListComPorts.cmd
05/25/2017 04:38 PM 162 ListLPCComPorts.cmd
05/25/2017 04:38 PM 1,749 LPCScrypt_CLI.cmd
05/25/2017 04:38 PM 4,606 program_CMSIS.cmd
05/25/2017 04:38 PM 4,022 program_JLINK.cmd
9 File(s) 13,748 bytes
2 Dir(s) 734,259,691,520 bytes free

3. Run program_CMSIS.cmd from a CMD window and below will appear


LPCScrypt - CMSIS-DAP firmware programming script v1.8.2 April 2017.

Connect an LPC-Link2 or LPCXpresso V2/V3 Board via USB then press Space.

Press any key to continue . . .

Booting LPCScrypt target with "LPCScrypt_158.bin.hdr"
LPCScrypt target booted
.
Programming LPCXpresso V2/V3 with "LPC432x_IAP_CMSIS_DAP_V5_182.bin"

- LPCXpresso V2/V3 programmed sucessfully and has the unique ID: OSAUCQNQ
- To use: remove DFU link and reboot.

Connect Next Board then press Space (or CTRL-C to Quit)

Press any key to continue . . .
Terminate batch job (Y/N)? y

C:\nxp\LPCScrypt\scripts>cd ..

C:\nxp\LPCScrypt>cd bin

C:\nxp\LPCScrypt\bin>lpcscrypt querypart
partID = 0xa00bcb3c 80
decode = LPC4322: BankA 512KB
Core Clock = 180000000

4. Shut it off and move J42 back to J43. Power back up, reconnect USB and you should be able to run the debugger now.

 

View solution in original post

0 Kudos
4 Replies
892 Views
jeremyzhou
NXP Employee
NXP Employee

Hi @bridgenet ,

Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
1) Any thoughts on how to recover the debugger operation?
-- Maybe you can try to use the Jlink to connect the J34 to program the lpc4322_bl_crc.bit to LPC4322 to update the bootloader.
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.
-------------------------------------------------------------------------------

0 Kudos
890 Views
bridgenet
Contributor II

Thanks for the suggestion but I don't have a Jlink and am using the development board that has everything built in.  We are evaluating the RT1024 processor for possible use in a new product line.  There has to be another way as this can't be the first time it has happened.

Thanks,

Kev

0 Kudos
883 Views
jeremyzhou
NXP Employee
NXP Employee

Hi @bridgenet ,
Thanks for your reply.
Maybe you can try to update the firmware by using the LPCScrypt.
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.
-------------------------------------------------------------------------------

0 Kudos
877 Views
bridgenet
Contributor II

 

For the next person that has to do this it would have been nice if NXP gave more details on what had to be done but I finally figured it out using the hint from Jeremy:

1. Disconnect USB debug port from PC and move jumper from J43 to DFU Boot Jumper J42 (J43 not needed to reflash and there are no spare jumpers on the board so used J43).

2. Download and install LPCScrypts: https://www.nxp.com/design/microcontrollers-developer-resources/lpcscrypt-v2-1-2:LPCSCRYPT

3. I used a dedicated 5V supply, not sure if needed. Cycle power and connect USB debug port to your PC.

3. Change your directory to:

C:\nxp\LPCScrypt\scripts>dir
Volume in drive C is OS
Volume Serial Number is 547F-9135

Directory of C:\nxp\LPCScrypt\scripts

09/08/2022 11:27 AM <DIR> .
09/08/2022 11:27 AM <DIR> ..
05/25/2017 04:38 PM 606 aeskey.cmd
05/25/2017 04:38 PM 1,218 boot_lpcscrypt.cmd
05/25/2017 04:38 PM 1,022 encrypt_and_program.cmd
05/25/2017 04:38 PM 228 encrypt_and_program.scy
05/25/2017 04:38 PM 135 ListComPorts.cmd
05/25/2017 04:38 PM 162 ListLPCComPorts.cmd
05/25/2017 04:38 PM 1,749 LPCScrypt_CLI.cmd
05/25/2017 04:38 PM 4,606 program_CMSIS.cmd
05/25/2017 04:38 PM 4,022 program_JLINK.cmd
9 File(s) 13,748 bytes
2 Dir(s) 734,259,691,520 bytes free

3. Run program_CMSIS.cmd from a CMD window and below will appear


LPCScrypt - CMSIS-DAP firmware programming script v1.8.2 April 2017.

Connect an LPC-Link2 or LPCXpresso V2/V3 Board via USB then press Space.

Press any key to continue . . .

Booting LPCScrypt target with "LPCScrypt_158.bin.hdr"
LPCScrypt target booted
.
Programming LPCXpresso V2/V3 with "LPC432x_IAP_CMSIS_DAP_V5_182.bin"

- LPCXpresso V2/V3 programmed sucessfully and has the unique ID: OSAUCQNQ
- To use: remove DFU link and reboot.

Connect Next Board then press Space (or CTRL-C to Quit)

Press any key to continue . . .
Terminate batch job (Y/N)? y

C:\nxp\LPCScrypt\scripts>cd ..

C:\nxp\LPCScrypt>cd bin

C:\nxp\LPCScrypt\bin>lpcscrypt querypart
partID = 0xa00bcb3c 80
decode = LPC4322: BankA 512KB
Core Clock = 180000000

4. Shut it off and move J42 back to J43. Power back up, reconnect USB and you should be able to run the debugger now.

 

0 Kudos