Hi,
We are have an issue with the secure boot configuration.
1. After set BOOT_SEQ to 1 the value at 0x400000 is 1 and the FSR report 0x0B600000 as normal
2. After install SMR and reset, I attach the debugger and the BOOT_SEQ return 0 and FSR report 0x00000000 which is ABNORMAL
I executed the script to do the HSE handshake and reset target board 2/3 times, the FSR value is 0x0F600000 which is normal.
It means the HSE is still exist and works but unstable
Is there any reason for this?
解決済! 解決策の投稿を見る。
I find out that after configure the SMR, functional reset must be used instead of destructive reset. After changing to functional reset, the HSE Firmware works well.
We can close this topic.
https://community.nxp.com/t5/S32K/s32k3-hse-basic-secure-boot-protect-problem/m-p/1943667
If FSR register remains 0x00000000 even after about 1s after reset, it means that HSE firmware has not been started at all. What can you see in GSR register? Is bit 0 set? And what can you see in HSE GPR register at 0x4039_C028?
It's unusual that BOOT_SEQ is changed back to 0. HSE FW or SBAF is not supposed to do that. Isn't that changed by your application?
Regards,
Lukas
Could you please discuss this issue with local NXP FAE assigned to you? Or just create new ticket here:
https://support.nxp.com/s/?language=en_US
... and it will be forwarded to them. Thank you.
I find out that after configure the SMR, functional reset must be used instead of destructive reset. After changing to functional reset, the HSE Firmware works well.
We can close this topic.
https://community.nxp.com/t5/S32K/s32k3-hse-basic-secure-boot-protect-problem/m-p/1943667