RT1024 Bricked on Hard Faults

[AaronSwift]

Why can I not reprogram the RT1024 after a hard fault occurs? The JTAG debugger cannot communicate with the processor core when this happens and we need to use the  NXP-MCUBootUtility-3.4.0 to unbrick the processor. 

[RaRo]

Hello @AaronSwift,

It is probable that there is a wrong configuration in the project which may be causing the RT1024 to hit a hard fault and cannot be reprogrammed.

MCUBootUtility becomes necessary because the tool uses the ROM Bootloader to communicate with the RT1024. The ROM Bootloader avoids the current image to be executed and erase it to write a new one.

Which hard faults are appearing in the code? Are you using an example or its your own application? Are you using a custom or an EVK from NXP board? Could you please try to replicate this behavior in an NXP EVK board in case you have one to test it?

Best regards, Raul.

[AaronSwift]

Hi Raul,

What project configurations could cause this issue? I do not have a hard fault example to give you. However, when this does occur, we cannot attach to the target through the JTAG interface to debug the problem. This problem has been noticed on our custom board and our application code.

[RaRo]

Hello @AaronSwift,

There are a number of project configuration changes that could cause the issue. Could you please take a look at the following information?

• Debugging a Hard Fault - NXP Community
• What Causes Hard Fault - NXP Community
• After changing serial flash on RT1020-EVK, it bric... - NXP Community

Just for double check, could you please check if the hardware requirements for the RT1020 is being meet? Is your application code working with an NXP EVK board? Are the SDK examples working with your custom board? You could use the SDK examples to compare with your application code to find a possible wrong project configuration.

Best regards, Raul.