S32GのトピックRe: SAF85xx HSE Update SMR

SAF85xx HSE Update SMR

Nam_Nguyen — Fri, 27 Mar 2026 03:31:58 GMT

Hi NXP,

Do we need to update SMR when just only Signature bytes change due to code content change but code size, start address , key, pointer to signature ... are not changed ?

Re: SAF85xx HSE Update SMR

petervlna — Mon, 30 Mar 2026 11:25:14 GMT

Hello,

The SMR (Secure Memory Region) entry contains the metadata HSE uses to verify your application image. Even if:

the size stays the same
the start address stays the same
the key handle stays the same
the signature pointer stays the same

…any modification to the code content produces a different signature, and HSE must verify the new signature.
Because of this, the SMR entry that holds the signature must be rewritten with the updated signature bytes.
The SMR entry is part of the authenticated boot chain; HSE cannot validate the updated binary unless its corresponding SMR entry reflects the new signature.

FYI: Aptiv has direct NXP FAE, so feel free to get in touch with him for details.

Best regards,

Peter

Re: SAF85xx HSE Update SMR

Nam_Nguyen — Tue, 31 Mar 2026 06:13:12 GMT

Thank you for your response

Re: SAF85xx HSE Update SMR

HuyNguyen_1406 — Fri, 24 Jul 2026 08:11:00 GMT

Hi,
How about in the case I flash new application + new signature (map with new application). in the case " code size, start address , key, pointer to signature" not change, do we need to re install SMR