NXP s32k312 HSE Reset Issue

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

NXP s32k312 HSE Reset Issue

Jump to solution
995 Views
Anitha7
Contributor III

Hi, @lukaszadrapa 

I have installed HSE (Hardware Security Engine) without using an IVT (Image Vector Table). The installation completed successfully.

Bootloader stored at 0x400000

Application stored at 0x442000

After performing a reset, the software works correctly with the debugger connected. However, if I disconnect the debugger and perform a reset, the software does not start.

Previously, when HSE was not used, the same IVT header worked correctly, both with and without the debugger.

Observations:

  • I can see the IVT header present in memory.

  • It seems that after a reset without the debugger, the startup does not proceed correctly.

  • I'm suspecting this might be related to how the boot flow or IVT is handled when HSE is enabled.

Request for Clarification / Help:

  • Could you please explain the difference in the startup flow with HSE versus without HSE?

  • How does the presence of HSE affect the interpretation or usage of the IVT?

  • What could be the reason the software works with the debugger but fails to boot without it when HSE is present?

  • Are there specific settings that must be configured differently for standalone boot with HSE?Note: I am not using secure boot 

  • Anitha7_0-1754460623258.png

     

Tags (2)
0 Kudos
Reply
1 Solution
932 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @Anitha7 

There are almost no differences when HSE is / isn't used. 

Which RTD is used? Why I’m asking:

The S32K3 reference says:

"Before configuring HSE_CLK, you must wait for the SBAF to enter WFI by reading core status register of HSE CPU (PRTN0_CORE2_STAT)."

So, it’s necessary to wait for WFI bit before running clock initialization when HSE  is installed. This is not implemented in older RTD drivers, corresponding code was added in RTD version 5.0.0 and higher. If you use older version, it’s necessary to add waiting loop for WFI bit before clock initialization. Maybe this is the root cause.

Have you tried to attach your debugger (I mean hot-sync without reset) after the fail to see what happened?

Regards,

Lukas

View solution in original post

0 Kudos
Reply
1 Reply
933 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @Anitha7 

There are almost no differences when HSE is / isn't used. 

Which RTD is used? Why I’m asking:

The S32K3 reference says:

"Before configuring HSE_CLK, you must wait for the SBAF to enter WFI by reading core status register of HSE CPU (PRTN0_CORE2_STAT)."

So, it’s necessary to wait for WFI bit before running clock initialization when HSE  is installed. This is not implemented in older RTD drivers, corresponding code was added in RTD version 5.0.0 and higher. If you use older version, it’s necessary to add waiting loop for WFI bit before clock initialization. Maybe this is the root cause.

Have you tried to attach your debugger (I mean hot-sync without reset) after the fail to see what happened?

Regards,

Lukas

0 Kudos
Reply