Burning fuses

[yanz]

How can I burn fuses using NXP-MCUBootUtility tool without connect to flashloader first (there are no SW6 related GPIOs on custom board)?

Is it possible?

Thank you in advance

[Dhruvit]

Hi @yanz,

I hope you are doing well.

Please make sure the imx board one is using is supported by NXP-MCUBootUtility.
-NXP-MCUBootUtility supports given below boards.
 i.MXRT1021, i.MXRT1051/1052, i.MXRT1061/1062, i.MXRT1064 SIP
-NXP-MCUBootUtility supports common eFuse memory operation (eFuse Programmer)

->The flash loader is responsible for initializing the microcontroller and setting up the communication channel between the microcontroller and the host computer.
->Without the flash loader, the NXP-MCUBootUtility tool will not be able to communicate with the microcontroller and access its registers to program the fuses.

Thanks & Regards,
Dhruvit Vasavada

[yanz]

The correct answer is:

It seems this is because blhost send configure-memory command to flashloader, but flashloader fail to configure flash and hung by the process. So, MCUBootUtility cannot communication with flashloader anymore.
You can set the "Boot Device" to "LPSPI NOR/EEPROM" and connect.

MCUBootUtility will not check eeprom so that it can connect successfully. After that you can scan and burn the fuse.

[Dhruvit]

Hello @yanz ,

I hope you are doing well.
Thanks for the clarification.

You can set the "Boot Device" to "LPSPI NOR/EEPROM" and connect.
MCUBootUtility will not check eeprom so that it can connect successfully. After that, you can scan and burn the fuse.

->If this answers your query, can I close this case?

Thanks & Regards,

Dhruvit Vasavada

[Dhruvit]

Hello @yanz ,

I hope you are doing well.
Thanks for the clarification.

You can set the "Boot Device" to "LPSPI NOR/EEPROM" and connect.
MCUBootUtility will not check eeprom so that it can connect successfully. After that, you can scan and burn the fuse.

->If this answers your query, can I close this case?

Thanks & Regards,

Dhruvit Vasavada

[yanz]

Sure