S32K3 Secure debug HSE

[kjy106906]

Hello @VaneB 

I saw your post!

https://community.nxp.com/t5/S32K-Knowledge-Base/S32K3-Restrict-the-debug-access-with-a-password-whe...

WARNING: ONCE YOU REALIZE THIS PROCESS YOU CAN NOT CONFIGURE HSE IN THE DEVICE.

What is the cause of this?

[MFaheem]

@VaneB Can you please point out in which document can i find information about your reply "that HSE Firmware cannot be installed after advancing the LC beyond CUST_DEL" 

[VaneB]

Hi @MFaheem 

While it is not explicitly mentioned, the HSE_B Firmware Reference Manual, Rev. 2.4 states that the HSE Firmware Usage feature flag must be programmed before the HSE firmware installation can be performed, and this programming can only occur in the CUST_DEL lifecycle.

Additionally, the S32K3xx Reference Manual, Rev. 9 specifies that depending on the HSE firmware feature flag, the application password must be programmed before lifecycle advancement; otherwise, SBAF does not attempt lifecycle advancement.

[VaneB]

Hi @kjy106906 

As explained in the thread shared above, for the process to take effect it is necessary to advance the Life cycle (LC) to OEM_PROD or IN_FIELD. HSE FW can only be installed in the CUST_DEL LC, therefore since the LC has already been advanced, HSE FW can no longer be installed.

If you want to use HSE and implement password protection, we provide some examples in the HSE DemoApp (S32K3 Standard Software > Automotive SW - S32K3 - HSE Firmware) and in the S32K3 MCUs for General Purpose HSE Demo Examples.

BR, VaneB