Skip to main content
Visitor
Nov 17, 2026 4:02 PM UTC
Question

STM32N657 Rev B/X – Secure Boot FSBL2 Fallback, Boot ROM Fixes, Silicon Revision Identification and Rev X Availability

Hello ST Team,

We are developing a product based on the STM32N657 (STM32N657X0H3Q) with Secure Boot enabled and the device configured in CLOSED_LOCKED state.

Our design uses two FSBL copies stored in external serial NOR flash:

  • FSBL1: Offset 0x00000000

  • FSBL2: Offset 0x00040000

We intend to rely on the boot ROM's FSBL2 fallback mechanism to ensure reliable booting and recovery following firmware updates.

However, ES0620 Rev 5 (August 2026) identifies two critical limitations affecting Rev Z silicon:

  • Erratum 2.2.12: FSBL2 boot fails due to SecureBoot after an incorrect FSBL1 image version boot attempt.

  • Erratum 2.2.13: FSBL2 execution fails after testing FSBL1 with an incorrect public key or signature in SecureBoot.

Both limitations are marked "N" for Rev Z and "–" (not applicable) for Rev B and Rev X in Table 3.

We would appreciate ST's clarification on the following points:

1. Confirmation of Fixes in Rev B and Rev X

Can ST confirm that both limitations are fully resolved in Rev B and Rev X silicon, specifically that FSBL2 fallback works on a CLOSED_LOCKED device when FSBL1 fails either the anti-rollback version check or the public-key/signature verification?

2. Boot ROM Fix and Version

Were these issues corrected in the boot ROM implementation? If so, which boot ROM version first included the fixes?

On our Rev B devices, we read BootromVersion = 0x00000501 (v5.1) from address 0x1800100C, as documented in UM3451.

3. FSBL2 Fallback Coverage

On Rev B and Rev X, does FSBL2 fallback also handle other FSBL1 failure conditions, including:

  • Invalid FSBL1 header or magic

  • Header checksum errors

  • Decryption or hash verification failures

  • FSBL1 read failures from external flash

4. Rev Z Failure Behavior

When errata 2.2.12 or 2.2.13 are encountered on Rev Z, what is the actual boot ROM behavior? Does the device enter serial boot mode, remain in a blocking failure state, or take another recovery path?

5. Silicon Revision Identification

Since DBGMCU_IDCODE.REV_ID returns 0x1000 across all revisions (erratum 2.2.5), what is ST's recommended method for identifying Rev Z, Rev B, and Rev X in firmware?

In particular:

  • What values should the boot ROM identification registers at 0x18001000, 0x18001004, and 0x1800100C return for each revision?

  • Can these registers be read directly by the FSBL in Secure state without additional clock or RIF configuration?

6. Boot ROM Change Documentation

Is there an official PCN, application note, or updated reference manual documenting the boot ROM changes between Rev Z and Rev B?

We identified PCN 16539 for the Rev B to Rev X transition but could not locate equivalent documentation for Rev Z to Rev B.

7. Rev X Availability

PCN 16539 indicates December 10, 2026, as the intended start of Rev X deliveries.

  • Is this schedule still valid?

  • Will standard production orders transition exclusively to Rev X after that date, or will Rev B remain available?

These clarifications are important for our secure firmware update strategy, boot recovery design, and production silicon selection.

We would particularly appreciate written confirmation of the FSBL2 fallback behavior under CLOSED_LOCKED Secure Boot conditions, along with any applicable documentation or recommended validation procedures.

Thank you for your support.