Continuous Reset after Software Reset when using HSE FW on S32K311

[NewbieNerd]

Hello S32K3 Teams.
I hope you are doing well.
I’m currently facing the issue described below and would appreciate your guidance on how to handle it properly.


Platform

- MCU: S32K311
- HSE FW: Full-Memory variant installed using the HSE Demo
- App: my original application reflashed after installing HSE FW

Symptom

- On power-up (or after reconnecting the battery), the app boots and runs normally.
- When my app calls a software reset, the MCU enters a continuous reset loop.
- If I disconnect the battery and reconnect it, the device starts and works normally again until I call SW reset.

Questions

- When HSE FW (Full-Memory) is installed, do I need to explicitly reset/terminate HSE or perform any HSE-specific shutdown/hand-off before triggering a software reset?
- If yes, what is the correct API sequence?
- Example: is there an HSE service (via MU) that should be called to gracefully stop/soft-reset HSE, or to clear pending services, watchdog, or FCCU-related conditions before SW reset?
- Could you please point me to the official HSE API names and usage examples I should call from my main application (non-AUTOSAR project)?
- Are there any known causes for repeated resets after SW reset with HSE installed on S32K3 devices (e.g., required SRAM reservation, MU/HSE status that persists across resets, watchdog, FCCU, or boot flow interactions)? want to see (e.g., MC_RGM FES/DES, MU FSR/GPR, etc.), please advise.

Documentation request

- Please share or grant access to the HSE Firmware Reference Manual and the HSE Service API Reference Manual for S32K3/S32K311.
- If there’s an app note or training slide that describes the reset/boot interplay with HSE and any required SRAM reservation or API calls prior to reset, I’d appreciate links.

Thanks in advance for your guidance!

Best regards,

[davidtosenovjan]

According to your description it is not clear whether you are doing some HSE related application or it happens only because of presence of HSE FW itself. If not, then the difference may be different memory layout and different booting time.

Question is what is causing repeated reset, whether it is just SW reset itself (after reset and boot, code execution reach the same point resetting it again) – in such case for such experiments it is suitable at least to condition SW reset with something. Or whether it is different cause, for instance watchdog - some operation of HSE takes up to 1s, for instance AB_SWAP, what may prolong boot time.

I am not aware of specific requirement for graceful termination of HSE module. Asynchronous reset may always happen externally and it should not affect MCU behavior significantly.

At first you should investigate  RGM_FES/DES registers to understand periodic reset reason.

The HSE-B FW RM is a secure file, so following procedure is needed to follow unless you have already done it before:

https://www.nxp.com/docs/en/user-guide/nxp-secure-access-rights-registration.pdf

For better understanding you may also see following link:

https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS

HSE Service API Reference Manual is included in installation folder of particular HSE FW, for instance as follows:

c:\NXP\HSE_FW_S32K312_0_2_40_0\docs\S32K312_HSE_Service_API_Reference_Manual.pdf