S32K312 HSE Reference

[Yiming2]

hello I am studying the HSE boot flow part in HSE reference for the new project development.

but I found a conflict in the figure.8 start-up flow in Rev2.6 -22 August 2025 version.

Q:Why does it directly enter the intallation boot when " FW-IMG available is not in secure NVM " and even we don't require a FW-IMG installation? If I do not want to install HSE FW(i.e. in case a virgin MCU with no HSE FW installed and no pink image in pflash, will it always go into the installation boot?

[Robin_Shen]

Hi

Note the top of Figure 8, the Start-up flow. It first Search for a valid IVT header tag in application NVM. If no IVT is found, it will proceed to Normal boot.

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[Yiming2]

Hi,
I think there is no relationship between what you said and my question.
In the figure 8, when the valid IVT header found , it still need to check if the FW-IMG avaiable in secure NVM in the end. If the FW-IMG avaiable in secure NVM is "no", It will enter the Installation boot(if I don't put the pink image into the Applicaiton NVM and No Utest content changed).So in this case, I can not understand the reason why Why does it directly enter the intallation boot when " FW-IMG available is not in secure NVM " and even we don't require a FW-IMG installation?.

[Robin_Shen]

Thank you for your patience.

Got confirmation from a SW architect that this flow chart is indeed only intended for when the HSE Firmware Feature Flag is set.

The document modification request has been submitted and will be fixed in a later release.

[Robin_Shen]

I apologize for my previous reply; your reminder made me understand your point.
I have already contacted the AE team for assistance with this issue.