Clarification on FULL_MEMORY vs AB_SWAP Update for Secure Boot (S32K3)

[Sanjana_k]

# Hello NXP Team

I successfully performed the FULL_MEMORY update and the HSE firmware was installed without any errors.

Before I proceed with Secure Boot configuration, I need clarification on the following:

1. Is the FULL_MEMORY update sufficient for enabling Secure Boot, or is the AB_SWAP update mandatory?

   • In other words, can Secure Boot be achieved if I only performed FULL_MEMORY, or must the device be moved to AB_SWAP update status?

2. Do I need to run CQC_UPDATE and SBAF_UPDATE after FULL_MEMORY, or are these only required in specific scenarios (for example, future firmware upgrades)?

3. After the firmware update step, is the next step directly Secure Boot key provisioning and SMR/SECBOOT configuration?

4. Please confirm the recommended NXP sequence for enabling Secure Boot on S32K3 after firmware installation.

Thank you.

[lukaszadrapa]

Hi @Sanjana_k 

1. Secure boot can be used with both versions of the HSE firmware.

2. SBAF update should be done only if you have some older device with outdated SBAF. Latest version of HSE firmware for S32K344 is 0.2.55 and compatible SBAF version is 00 05 00 00 00 0F 00 06 (0.15.0). See section "14.6.4.1 Secure BAF version number" in HSE Firmware reference manual to find where to get the version of your current SBAF.
CQC_UPDATE is a project which can provide ADKP and which can advance the life cycle. Advancing of the life cycle is rather the very last operation in our development but you can provide ADKP if needed. Just do not advance the life cycle because a lot of HSE operations can be done in CUST_DEL life cycle only.

3. As mentioned earlier, secure boot configuration should be done once as one of the last operations when the application is already finished.

4. We 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)

Regards,
Lukas

[Sanjana_k]

#Thank you@lukaszadrapa  for your guidance.
I am working on S32K344 EVB. I flashed the HSE firmware using:

"C:\NXP\HSE_FW_S32K3XX_0_2_1_0"

The firmware flashing was successful, but when I run the application it gets stuck at:

WaitForHSEFWInitToFinish();

I want to confirm:

1. Is this the correct/compatible HSE firmware version for S32K344?

2. What usually causes the application to stay inside WaitForHSEFWInitToFinish()?

3. How can I download the latest HSE firmware version?

   • When I open Documentation → Secure on the NXP website, the page appears empty.

4. I already submitted the NDA request, but I haven’t received any reply yet.

   • Is there any other way to access the latest firmware ?

Please guide me on how to resolve this and access the correct firmware package.

Thank you.

[lukaszadrapa]

The latest version for S32K344 is 0.2.55.0, so I recommend to use this one. Version 0.2.1.0 is quite outdated.

“The firmware flashing was successful” – which installation method did you use? Could you check if bit 0 in HSE GPR register at address 0x4039_C028 is set?

If it hangs in WaitForHSEFWInitToFinish(), the firmware is either not installed or it was not possible to start the firmware due to some fatal error in HSE.

Please share value of HSE GPR register at 0x4039_C028 and also FSR and GSR register in MU_0 module.

Where to download HSE firmware - go to S32K3 Standard Software:

https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW32K3-STDSW-D

Select: Automotive SW - S32K3 - HSE Firmware

Select firmware version:

0.2.55.0 K3xx Std SR-RTM HSE FW release

Service Release for K3x2,K3x4 Std HSE FW

Regards,

Lukas

[Sanjana_k]

#Hello@lukaszadrapa  Sir,
May I know if there has been any update regarding our query?
Kindly help us with this error.

[Sanjana_k]

#Hello@lukaszadrapa 

 While running the program, I am encountering an issue where it gets stuck in the Default_Handler. Upon debugging, I noticed two errors: UsageFault and HardFault.

I have attached the relevant image for reference. Could you please review it and guide me on the next steps to resolve this issue?

[lukaszadrapa]

Hi @Sanjana_k 

"While running the program" - which project exactly? According to your screenshots, the firmware is already installed, so currently it's just about your project. You can try to step the code to see where it crashes exactly or you can try to follow this document:

https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-...

Regards,

Lukas