S32K314 secure boot: BSB mode

[liTian_one]

After program the relevant firmware for enabling secure boot, and after powering off and on again, the software remained at 0x2040012e.

What could be the reason for this?  Or is there any way I can find out the cause?

[lukaszadrapa]

Hi @liTian_one 

The device is in recovery mode. This mode is entered when: IVT is not present or corrupted or there are more than 8 consecutive functional/destructive resets or when secure boot fails.

In case of JTAG recovery mode, the device just hangs in endless loop in RAM, so user can take appropriate actions and the device is not bricked.

Based on your description, it’s caused by failing secure boot.

You can follow demo code from:

https://www.nxp.com/webapp/Download?colCode=S32K3_HSE_DemoExamples

Example:

c:\NXP\S32K3_HSE_DemoExamples_1_0_0\S32K3_HSE_DemoExamples\Secure_Boot\S32K344_Basic_SecureBoot\

We also provide Secure Boot application note including demo projects. It can be downloaded from:

https://www.nxp.com/products/S32K3

Application note can be found here:

Documentation -> Secure Files -> Secure Boot Application note v0.1.1.0 (AN744511)

Associated demo project can be downloaded here:

Design Resources -> Software -> Secure Files -> SecureBootAppNoteDemo (SW745310)

Common problem is wrong alignment of your application. Please take a look at this section from the application note:

Regards,

Lukas

[liTian_one]

The settings of IVT (0x00400000) should be correct, and the addresses of APP header and APP code are (0x004020c0) and (0x00402100) respectively.

[lukaszadrapa · Accepted solution]

How did you generated the GMAC? Do you follow the S32K344_Basic_SecureBoot example or do you generate the GMAC externally? Maybe this could be useful for you:

https://community.nxp.com/t5/S32K/Request-for-PC-side-GMAC-example-for-S32K344-Basic-Secure-Boot/td-...

[liTian_one]

The cause of the problem has been identified.thank you