2411047_en-US

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

2411047_en-US

2411047_en-US

HSE: Error code 0x67030001 after first two resets following MU install

I have followed the install procedure for installing through MU interface in FULL_MEM mode, as described in section 3.2.3.1 in Firmware Reference Manual version 2.7.

Installing works exactly as described, but when I perform a functional reset (step 7) I get HSE error code 0x67030001. This persists after a second reset but reliably goes away after a third.

I have a few questions:

  1. Is the particular value of uppermost bits (0x6703) significant?
  2. What could cause the HSE driver to enter an error state on startup but recover following exactly two resets?
  3. What is the most likely cause for the error in the first place?
Re: HSE: Error code 0x67030001 after first two resets following MU install

Hi @Emma_G-gbg 

As indicated in the HSE_B Firmware Reference Manual, the GSR register logs fatal and warning events in its 16 least significant bits:

  • Bits 0-7 indicate fatal errors.
  • Bits 8-15 indicate warnings (non-fatal failures).

The 16 most significant bits are reserved for NXP internal errors.

Since bit 0 is set on your device, this indicates that a fatal error occurred, causing the HSE to shut down. In this state, a device reset is required to recover and exit the shutdown mode.

Could you please share the values of the FSR register and HSE_CONFIG_GPR3 (0x4039C028)? Also, after performing the reset, did you wait until the HSE_STATUS_INIT_OK flag in GPR3 was set?

Additionally, in the thread S32K3 recovery issue when install HSE fw via MU, a demo for HSE firmware installation via MU was shared. It may serve as a useful reference.


BR, VaneB

Re: HSE: Error code 0x67030001 after first two resets following MU install

Hi @Emma_G-gbg 

Resets 1 & 2: FSR = 0x00400000. Bit 24 (HSE_STATUS_INIT_OK) is not set, which indicates that HSE had not yet completed its initialization. The GSR value 0x67030001 shows that bit 0 (HSE_ERR_GENERAL) is set, which triggered an HSE sub-system shutdown.

Reset 3: FSR = 0x09600000. Bit 24 (HSE_STATUS_INIT_OK) is now set, indicating that HSE completed its initialization successfully. The GSR value0x00000000 shows that no HSE errors/warnings were reported.

A possible cause of this behavior could be that the application is performing clock initialization, XRDC configuration, or Flash operations before HSE initialization is fully completed.

Re: HSE: Error code 0x67030001 after first two resets following MU install

After the first two resets the values were as follows:

HSE_CONFIG_GPR3: 0x10000081
DCMRWP1: 0xA5000400
GSR: 0x67030001
FSR: 0x00400000

Then after the third reset values were:

HSE_CONFIG_GPR3: 0x000000C1
DCMRWP1: 0xA5000400
GSR: 0x00000000
FSR: 0x09600000  
Re: HSE: Error code 0x67030001 after first two resets following MU install

Hi @Emma_G-gbg 

Regarding XRDC, refer to the note in Section 14.6.3 of the HSE_B Firmware Reference Manual, Rev. 2.7.

For clock initialization, the relevant information can be found in Section 2.4.2.3.3 of the same document.

Re: HSE: Error code 0x67030001 after first two resets following MU install

Thank you, I'm looking into flash synchronization now.

I was not aware that clock or XRDC init could affect HSE startup, where is this described?

Tags (1)
No ratings
Version history
Last update:
Wednesday
Updated by: