Does enabling Secure Boot in the RT600 family make it unusable in other devices?

[hxp123]

I have a device that is running an RT600 family MCU. I'd like to make a custom development board and I'm curious if I can re-use that RT600 or not.

I believe secureboot is enabled on this RT600, and - as I currently understand it - enabling secure boot sets OTP fuses which will make my custom dev board firmware not be accepted by the MCU.

Is my understanding about this correct? Does enabling secureboot prevent it from being used with any firmware not signed by the original private key?

thank you

[hxp123]

Hi Kerry, thank you so much for the quick response. I understand.

[kerryzhou · Accepted solution]

Hi @hxp123 ,

   Your understanding is correct.

  If you do the secure boot, then you also need to prepare the related secure app firmware to match it, and download to the flash, then it will be used correctly.

  If just normal app without the related secure configuration, can't be boot any more, as it lack the sign or secured information.

  More details, please refer to the user manual secure chapter, and our tools: SPT and the MCUbootutlity:

1. SPT

https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-s...

2. MCUbootutility

https://github.com/JayHeng/NXP-MCUBootUtility/releases/tag/v5.3.0
the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility

Wish it helps you!

Best Regards,

Kerry