https://community.nxp.com/t5/S32K/S32K144-CSEc-Strict-Sequential-Boot-Mode/m-p/2087937#M48205 <P>Hello, I have encountered a problem. I enabled the Strict Sequential Boot Mode in Secure Boot on the s32k144 chip. I wanted to see what state the MCU would be in if I modified the boot. As a result, I found that the chip was always in reset state. The reset pin was always low, which made it impossible for me to re-burn the correct boot to release the reset state caused by the CSEc verification failure. I did not enable debug disable and did not disable mess erase. Is there any way to recover?</P> Mon, 28 Apr 2025 05:18:38 GMT soulyoung 2025-04-28T05:18:38Z https://community.nxp.com/t5/S32K/S32K144-CSEc-Strict-Sequential-Boot-Mode/m-p/2087937#M48205 <P>Hello, I have encountered a problem. I enabled the Strict Sequential Boot Mode in Secure Boot on the s32k144 chip. I wanted to see what state the MCU would be in if I modified the boot. As a result, I found that the chip was always in reset state. The reset pin was always low, which made it impossible for me to re-burn the correct boot to release the reset state caused by the CSEc verification failure. I did not enable debug disable and did not disable mess erase. Is there any way to recover?</P> Mon, 28 Apr 2025 05:18:38 GMT https://community.nxp.com/t5/S32K/S32K144-CSEc-Strict-Sequential-Boot-Mode/m-p/2087937#M48205 soulyoung 2025-04-28T05:18:38Z https://community.nxp.com/t5/S32K/S32K144-CSEc-Strict-Sequential-Boot-Mode/m-p/2088336#M48240 <P>Hi <a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222770">@soulyoung</a>&nbsp;</P> <P>There's no way to recover. If strict sequential boot mode fails, the device will stay in reset forever. The only option is to replace the chip. The documentation warns about that several times:</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_0-1745838466688.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/335241i0604BA16D8304A67/image-size/medium?v=v2&amp;px=400" role="button" title="lukaszadrapa_0-1745838466688.png" alt="lukaszadrapa_0-1745838466688.png" /></span></P> <P>&nbsp;</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_1-1745838517416.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/335242i014371B2A621BF16/image-size/medium?v=v2&amp;px=400" role="button" title="lukaszadrapa_1-1745838517416.png" alt="lukaszadrapa_1-1745838517416.png" /></span></P> <P>&nbsp;The last sentence "may execute ROM code" comes from SHE specification but that's not the case here. </P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_2-1745838634382.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/335243iA6EC9F9AAA002708/image-size/medium?v=v2&amp;px=400" role="button" title="lukaszadrapa_2-1745838634382.png" alt="lukaszadrapa_2-1745838634382.png" /></span></P> <P>Regards,</P> <P>Lukas</P> Mon, 28 Apr 2025 11:11:56 GMT https://community.nxp.com/t5/S32K/S32K144-CSEc-Strict-Sequential-Boot-Mode/m-p/2088336#M48240 lukaszadrapa 2025-04-28T11:11:56Z