Customer is Ford. Device is s32g3.
In their software, after few functional resets, will escalate to destructive reset. This is kind of duplication of the FRET.
Also, during some earlier debug calls with NXP in s32g2, it was suggested that the FRET value be set to 0.
However, doing the same on our software is causing sBoot Rgm test to fail.
sBoot RGM test has the below two requirements,
If they need to set FRET = 0, then they need to disable sBoot RGM check.
Is this check a must for ASIL B compliance ? Can it be disabled?
-Randy Krakora
Hi Randy,
the sBoot requirements are coming from HW Safety Manual assumptions.
SAF purpose is to help with integration of some assumptions, so for this case it covers partly this assumption:
I don't know background of this issue, what is causing the resets for the customer, but he can always clear the reset escalation counter as per the assumption, depends on what is causing the resets.
Disabling the sBoot check would break this assumption and customer shall justify that this doesn't have any negative safety impact on his app.
Kind Regards,
Radoslav
