Skip to main content
Visitor
Nov 22, 2026 11:09 AM UTC
Question

STM32N6 – Secure Secret Provisioning (SSP) availability and recommended alternatives

Hello ST team,

We are developing a commercial product based on the STM32N6570 and are planning to use OEMuRoT with Secure Boot and firmware encryption.

We are currently investigating how to securely provision cryptographic secrets into OTP during mass production, especially when using a third-party contract manufacturer.

According to ES0620 Rev. 5, section 2.2.17, Secure Secret Provisioning (SSP) is not supported on STM32N6 due to limitations involving the BSEC_DBGCR and BSEC_AP_UNLOCK registers. The errata also states that no workaround is available, and the limitation appears to affect silicon revisions Z, B, and X.

We would appreciate clarification on the following questions:

  1. What is ST's recommended approach for securely provisioning OTP secrets on STM32N6 during mass production? In particular, how can we prevent a contract manufacturer from accessing sensitive secrets such as OEM_SECRET_FOR_CRYPTED_BOOT and the OEMuRoT application encryption private key?

  2. Is there any alternative secure provisioning workflow supported by ST for STM32N6, considering that SSP is currently unavailable?

  3. Does ST plan to introduce full SSP support in a future silicon revision of STM32N6? If so, is there any tentative timeline or roadmap information that can be shared?

Our main concern is how to securely provision production devices without exposing cryptographic secrets to the contract manufacturer.

Thank you in advance for your guidance.