Preparative Procedures; Secure Acceptance - ST STM32U585 Series User Manual

3

Preparative procedures

This chapter describes the procedures to prepare the environment and the product before starting to use the
product or before testing the product:
• Secure acceptance: procedures to check the product to be tested
• Secure preparation of the operational environment: procedures to set up the environment needed to manage
and test the product.
• Secure installation: procedure to program and configure the product to be tested
• Tera Term connection preparation procedure: procedure to configure the Tera Term tool before starting to
test the product.
3.1

Secure acceptance

Secure acceptance is the process in which the user securely receives the TOE and verifies the integrity and
authenticity of all its components.
The TOE is distributed as an MCU with a source code package.
The integrator receives the MCU directly from ST via a secure courier.
To ensure that MCU is not manipulated during TOE delivery, the integrator must verify that the user Flash is virgin
(reading 0xFF everywhere with STM32CubeProgrammer) or must do an RDP regression (Level 1 -> level 0) that
erases the user Flash.
The software package can be obtained through the standard ST support channels.
Note that it is the responsibility of the integrator to choose the correct STM32CubeU5 MCU Package version.
• How to accept the STM32U585xx microcontroller: by reading, with STM32CubeProgrammer (for more
details, refer to UM2237), the DBGMCU_IDCODE register value (0x2001 6482) at the 0xE004 4000
base address (for more details, refer to RM0456), and the bits 0, 2, 5, and 7 of byte at the 0x0BFA 0501
base address in system memory that are all set:
– DBGMCU identity code register (DBGMCU_IDCODE)
◦
◦
◦
– System memory byte at 0x0BFA 0501 base address
◦
◦
◦
◦
• How to accept STM32Cube_FW_U585_Security_certification_V1.0.0 software package: By comparing the
SHA256 value of the STM32Cube_FW_U585_Security_certification_V1.0.0.exe file obtained with
the sha256sum.exe tool, to those in the
UM2852 - Rev 1
Base address: 0xE004 4000
Address offset: 0x00
Reset value: 0x2001 6482
• Bits [31:16] REV_ID[15:0]: revision 0x2001: revision X
• Bits [15:12] Reserved
• Bits [11:0] DEV_ID[11:0]: device identification
• 0x482: STM32U575/585
Bit 7 (DPA enable): 0b1
Bit 5 (OTFDEC enable): 0b1
Bit 2 (PKA enable): 0b1
Bit 0 (AES enable): 0b1
[Security Target] document.
UM2852
Preparative procedures
page 5/27