S32K311 HSE Firmware Flashing Algorithm and Lifecycle Unlock Inquiry (Using P&E Cyclone FX)

[KARL5]

We currently have a project using the S32K311 MCU. The customer has provided HseLib_HseFwInstall_Driver.hex and app.hex, and we are using a P&E Cyclone FX programmer. We would like to ask the NXP experts to help confirm the algorithm selection for a brand-new MCU:

1. Which algorithm should be used when flashing the HseLib_HseFwInstall_Driver.hex onto a brand-new MCU(nxp_s32k311-1x32x212k_hse_enabled.arp or nxp_s32k311-1x32x212k_hse_disabled.arp)?

2. Which algorithm should be selected after the HSE driver is flashed?

3. How can we confirm if the HSE driver is successfully installed?

4. If the MCU's lifecycle is locked, how can it be unlocked?

Thank you in advance.

[Robin_Shen]

Hi

Based on the name HseLib_HseFwInstall_Driver, it appears to be a Chinese customer and references the HSE_Lib demo provided by China FAE.

A1. nxp_s32k311-1x32x212k_hse_disabled.arp

A2. I suggest you ask the customer whether the HSE FW they installed is FULL_MEM or AB_SWAP.
If you are installing FULL_MEM, select nxp_s32k311_1x32x212k_hse_enabled.arp.
If you are installing AB_SWAP, select nxp_s32k311_1x32x168k_ab_swap.arp.

A3. Check HSE GPR register at 0x4039C028. Bit '0' says if HSE firmware is installed or not.

A4. I'm not sure which stage LifeCycle has advanced to. If you're asking about debug access, I suggest you refer to "82.11 Debug across device LifeCycles" in S32K3XXRM Rev12. 

Trusted: Debug is possible after successful authentication (Challenge/Response handshake with correct credentials)

See also:
...\s32k3_hse_lib_rtd400hf01_20260427\Doc\S32K3_SecureDebug_UserGuide.pdf This document needs to be obtained from China FAE or your customer.
NXP Automotive S32K311-SECUREDEBUG is supported!
NXP: Using PEmicro Tools to Enable S32K3xx Secure Debug Support

Best Regards,
Robin