NXP S32G3:Secure boot for bootloader:Issue in HSE_Init after reset

[kavyapk]

Hello ,

I am using Board: S32G399RDB3 with an AUTOSAR application and NXP Boot on the M7 core.

HSE vesrion:HSE_DEMOAPP_S32G3XX_0_2_51_0

we are doing secure boot for bootloader with smr and cr configuration (preboot verification).

we are installing smr and publishing sysimage, we are performing mcu reset.  After this  hse init is not happening.  It is stuck in the loop given below

Could you please help us for understanding the HSE  behaviour 

[kavyapk]

Hi,
For the initial state before secure boot configuration and during secure boot configuration , the status bit for set for HSE_STATUS_INIT_OK and HSE_STATUS_RNG_INIT_OK . But after the smr install and sysy image publish when we perform reset ,there after these status bits are cleared.
Could you help us to understand this hse behaviour

[carlos_o]

Hi @kavyapk, 

I'm working in your issue. I'll come ASAP with further information.

[kavyapk]

Hello,

I am putting some of our observations here

1.Initilally we thought Hse shutdown happened ,that is why init status we are not getting.But as per HSE_H reference manual ,if we do functional reset we should get the hse_status_init_ok, and we tried and still the bit was not set.

2.Second thing is from reference manual which says HSE_STAUS_INIT will set only after post boot verification is suuceessful.

So I would like to understand on this since we are getting HSE_STATUS_BOOT_OK after reset and but not the HSE_STATUS_INIT_OK.

In CR configuration we are proposing prebootsmr map,as shown below.

Is this is enough for secure boot smr verification or do we have to do both preboot and postboot smr map in CR entry .

We are asking beacuse in the above mentioned firmware manual snip there are saying about 3 stage verification.

Could you please comment on this scenario

[carlos_o]

Hi @kavyapk,

Your issue seems to not be related to your SMR configuration. 

What I'm understanding is that when you perfom the mcu_reset as fuctional reset you get both bits cleared (HSE_STATUS_INIT_OK and HSE_STATUS_RNG_INIT_OK). 

At your code at HSE_FW_INSTALL_SEC_BOOT. Did you maintain the following?

HSE_MU_SendEvent(HSE_HOST_PERIPH_CONFIG_DONE);

Also, your SMR Entry config looks to be set properly.

In case you don't have the SendEvent fuction before the status check please add it and retry.

Let me know your results

[kavyapk]

Hello @carlos_o ,

Thankyou for your response

Yes I am already sending this event before checking status,

[carlos_o]

Hi @kavyapk,

Thanks for clarifying.

Could you please run the Demo App without modifications to verify if your SoC are working properly? 

[kavyapk]

Hello @carlos_o ,

As per the log we are getting from console reagarding other HSE status other that RNG init and HSE init before and after the reset it shows soc is working properly.

Below shown is the console after secure boot config and followed reset

After reset console log

[carlos_o]

Hi @kavyapk,

Thanks for sharing you console output after reset.

I want to see if you get the HSE_STATUS_RNG_INIT_OK and HSE_STATUS_INIT_OK from the example or if you have the same behavior as you application. 

[kavyapk]

Hello @carlos_o,
We have checked with demo app also,there we are observing clock init issue .