How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled

How to start with OEMiRoT on STM32H573 - Arm^® TrustZone^® enabled85min

Target description

Through this practical example, the user will learn how to perform the following operations

• Run the OEMiRoT example of the STM32CubeFW
  • Provisioning preparation
  • Code and data compilation and encrypted image generation
  • Perform the provisioning and install the firmware and data files
  • Execute the installed firmware
  • Perform a full regression
• Debug Authentication
  • Create a certificate chain
  • Perform a regression using the LEAF certificate of the certificate chain
  • Debug opening (Secure and non Secure) using root certificate
  • Attach CubeProgrammer and attach an IDE once debugger is open
  • Read Secure and non secure firmware
  • Perform a partial regression and download new code and data non secure

This OEMiRoT step by step tutorial is divided in two main parts:

• Provisioning
  • Configuration
  • Device Provisioning
  • Application code execution
  • Full regression

• Debug Authentication
  • Certificate chain
  • Debug opening (Secure and Nonsecure)
  • Regression (partial and full)

Prerequisites

• RM0481 STM32H5x3/562 Reference Manual
• Knowledge of STM32CubeProgrammer
• Knowledge of JTAG / SWD interface
  

Hardware

• Discovery board STM32H573I-DK. (or NUCLEO board NUCLEO-H563ZI)

Warning

If you are using a STM32H563 device, the process is the same but you have to use this default folder: STM32Cube_FW_H5_V1.0.0\Projects\NUCLEO-H563ZI

Required tools

• STM32Cube_FW_H5_V1.0.0 or upper
• STM32CubeProgrammer Software programming tool for STM32 (v2.13.0 min)
  • Including STM32TrustedPackageCreator

Information

TPC installed together with CubeProgrammer in bin folder located in default STM32CubeProgrammer path : C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin You can pin this tool to the task bar to simplify the OEMiRoT Getting started process :

• IAR Embedded Workbench rev 9.20.1
• Tera Term or equivalent UART Terminal emulator

Literature

• RM0481 STM32H5x3/562 Reference Manual
• UM2237 STM32CubeProgrammer software description
• UM2238 STM32TrustedPackageCreator tool software description
• AN5054 Secure programming using STM32CubeProgrammer
• AN2606 STM32 microcontroller system memory boot mode

Environment setup

Before starting, the first step is to prepare the environment to be able to go through the OEMiRoT process.

• Download the STM32CubeH5 package and install it

Warning

Place STM32CubeFW_H5 Cube firmware close to the C: root to avoid a long Windows® path.

An STM32H573I-DK directory is included in the Projects directory:

Warning

In case the STM32CubeProgrammer has not been installed in the default folder, the customized installation paths need to be updated in the following script :Projects\STM32H573I-DK\ROT_Provisioning\env.bat (or Projects\NUCLEO-H563ZI\ROT_Provisioning\env.bat if you are using an STM32H563 device) :: ============================================================================== :: General :: ============================================================================== :: Configure tools installation path set stm32programmercli="C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" set stm32tpccli="C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32TrustedPackageCreator_CLI.exe"

1. Introduction

This article shows an OEMiRoT example use case for STM32H573 devices with TrustZone enabled.

All the article is based on the STM32CubeH5 package OEMiRoT example for STM32H573 MCUs.

Warning

If you are using a STM32H563 device the OEMiRoT process is the same but you have to use the files examples in the corresponding folders STM32Cube_FW_H5_V1.0.0\Projects\NUCLEO-H563ZI\ROT_Provisioning STM32Cube_FW_H5_V1.0.0\Projects\NUCLEO-H563ZI\Applications\ROT

2. OEMiRoT step by step: Provisioning / Code execution / Regression

2.1. Step 1 : OEMiRoT and Debug Authentication configuration

2.1.1. OEMiRoT configuration

At this step, the file (OEMiRoT_Config.obk) used to configure the OEMiRoT will be generated. A default file is provided in the example that can be used without modification for a first trial in this path:
Projects\STM32H573I-DK\ROT_Provisioning\OEMiROT\Binary

STM32TrustedPackageCreator will be used to setup this file using the OEMiRoT_Config.xml as an input located in Config folder:

Projects\STM32H573I-DK\ROT_Provisioning\OEMiROT\Config

At this step, the following keys pair will be generated

• ECDSA-256 encryption key
• ECDSA-256 authentication secure key
• ECDSA-256 authentication nonsecure key

To generate a customized configuration file, proceed as follows:

• Open STM32TrustedPackageCreator and select H5.
• Open the OBkey tab.
• Select the OEMiROT_Config.xml file in folder ROT_Provisioning\OEMiROT\Config.
• Update the parameters if needed.
• The default keys can be regenerated.
• For a commercial product it's mandatory to regenerate the keys.

• Generate the file :
  

The OEMiROT_Config.obk file is generated. The modified parameters are saved in Binary \OEMiROT_Config.obk.

2.1.2. Debug Authentication configuration

At this step, the file DA_Config.obk will be generated in DA\Binary folder. This file is used to configure the conditions to reopen a protected device and the debugger. A default file is provided in the STM32CubeFW_H5 example that can be used without modification for a first trial.

STM32TrustedPackageCreator will be used to setup this file using the DA_Config.xml as an input located in DA\Config path.

The following parameters can be defined at this step:

• Hash (SHA256) of the root public key
• Permissions list (full regression, partial regression, debug opening (HDPL1 S/NS, HDPL2 S/NS, HDPL3)

Two files are included in the DA directory:

• DA_Config.xml: configuration based on certificates for H5 crypto parts (this file is used for this tutorial)
• DA_ConfigWithPassword: configuration based on password: when TrustZone is disabled

Warning

The device will be blocked if password provisioning is done during this tutorial since TrustZone is enabled.

To generate a customized configuration file, proceed as follows:

• Open STM32TrustedPackageCreator and select H5.
• Open the OBkey tab.
• Select the DA_Config.xml file.
• Update the parameters if needed. For a first trial we recommend keeping the default key, because in the regression step we will use the default certificate that is linked to the default DA keys.

Warning

If a customized DA key is generated here, make sure the customized root key file is well saved/kept because it will be used later on for debug reopening and regression. If this key is lost, the device might be locked forever.

• For a commercial product it's mandatory to regenerate the Debug Authentication key.

• Generate the file:

2.2. Step 2: Code and data image generation

2.2.1. STM32CubeFW provided code compilation

Check that the STM32H5 IAR™ provided patch is correctly installed and check that your IAR Embedded Workbench™ version is recent enough.

Two code examples for IAR Embedded Workbench™ are provided:

• OEMiROT_Boot corresponds to the Secure Boot.

It performs authenticity and integrity checks of the project firmware and data images.

• OEMiROT_Appli_TrustZone is an example of secure and nonsecure application managed by OEMiROT

OEMiROT_Boot project configuration

Number of code images and Data images is defined in
flash_layout.h file in the ./Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Boot\Inc folder.

In this example we want to use

• 1 secure code image
• 1 non-secure code image
• 1 secure Data image
• 1 non-secure Data image

Please update the file flash_layout.h as shown in figure below  :

Information

During the OEMiROT_Boot execution, if the number of images is wrong, Bootloader is launched to load new code and/or data images.

OEMiROT_Boot project compilation

• Open the Project.eww located in the EWARM directory: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Boot\EWARM
• Open Project -> Option -> General Options: The device and CPU core should be automatically recognized and you should see the following windows:

If the device is not recognized, check that the STM32H5 IAR™ provided patch is correctly installed, and check that your IAR Embedded Workbench™ version is recent enough.

• Perform: Project -> Rebuild all (don’t upload the code, only perform a compilation)

The following binary is created: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Boot\EWARM\STM32H573I_DK\Exe\Project.bin

OEMiROT_Appli_TrustZone project compilation –Secure Project

• Open the Project.eww located in the EWARM directory:

Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\EWARM

• Select the Secure Project:

• Open Project -> Option -> General Options

The device and CPU core should be automatically recognized.

• Open Project -> Option -> Build Actions

Here is the command line which will create an image of the code with STM32TrustedPackageCreator:

• Perform: Project -> Rebuild all (don’t upload the code, only perform a compilation)

The following image is created: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\Binary\rot_tz_s_app_enc_sign.hex Don’t close the EWARM project.

OEMiROT_Appli_TrustZone project compilation –Non-Secure Project

• Select the Nonsecure Project:

• Open Project -> Option -> Build Actions and check the correct paths for the command line

This Postbuild command will create an image of the compiled non secure code thanks to STM32TrustedPackageCreator.

• Perform: Project -> Rebuild all (don’t upload the code, only perform a compilation)

The following image is created: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\Binary\rot_tz_ns_app_enc_sign.hex

2.2.2. Firmware and data encrypted image generation

2.2.2.1. Code image generation

During this step two image files will be created from secure and nonsecure binary code files.

In the previous steps, secure and nonsecure code images have been created directly from the EWARM Postbuild command (rot_tz_ns_app_enc_sign.hex and rot_tz_s_app_enc_sign.hex), but you can also create code images manually:

This tutorial shows an example for a two-code, two-data-images installation, but other configurations are also possible.

We show here how to perform manually an encrypted / signed code image (equivalent to what the Postbuild command has executed).

• Open STM32TrustedPackageCreator and select H5.
• Open the ImageGen tab.
• Select the template for the relevant image: OEMiRoT_S_Code_Image.xml (ROT_Provisioning\OEMiROT\Images directory)
• Update the default configuration if required:
  • Update the firmware area size.
  • Update the version number.
  • Enable the dependency with the other (data) image when a simultaneous installation is required for compatibility reasons.
  • Select the binary file to be used as an input file.
  • Select the output file to be filled with the signed and encrypted binary (HEX format).
• Launch the generation.
• An encrypted signed file will be created: rot_tz_s_app_enc_sign.hex

Resume from step 1 and select the OEMiRoT_NS_Code_Image.xml template in order to generate a rot_tz_ns_app_enc_sign.hex image.

2.2.2.2. Data image generation

During this step, two image files will be created from secure and nonsecure data files.

The provided data files s_data.bin and ns_data.bin are just example files for this tutorial but have no meaning and are not used for the code execution.

This tutorial shows an example for a two-code, two-data-images installation, but other configurations are also possible.

To generate images of secure and nonsecure data you must:

• Open STM32TrustedPackageCreator and select H5.
• Open the ImageGen tab.
• Select the template for the relevant image: OEMiRoT_S_Data_Image.xml (ROT_Provisioning\OEMiROT\Images directory)
• Update the default configuration if required:
  • Update the version number.
  • Enable the dependency with the other data image when simultaneous installation is required for compatibility reasons.
  • Select the binary file to be used as an input file.
  • Select the output file to be filled with the signed and encrypted binary (HEX format).
• Launch the generation.
• An encrypted signed file will be created: s_data_enc_sign.hex

Resume from step 3 and select the OEMiRoT_NS_Data_Image.xml template in order to generate an ns_data_enc_sign.hex image.

2.3. Step 3: Device provisioning, code and data image download into the flash memory, product state setting

The provided “provisioning” script will:

• Set the option bytes of the device.
• Configure the OEMiRoT and the DA on the device.
• Install the images (code and data).
• Set the final chosen product state according to user selection.

Before launching the script, connect STM32CubeProgrammer and check that the device is in open state.

If the device is not in open state, refer to step 5, which explains the regression. If the flash memory is not erased, the provisioning script will erase it anyway.

• Connect the board, with BOOT0 pin not connected to VDD (check that STM32CubeProgrammer is disconnected).
• Open folder OEMiRoT in: Projects\STM32H573I-DK\ROT_Provisioning\OEMiROT
• Double click the provided provisioning.bat script to run it.
• Note: For Linux and Mac operating systems, the end users may have to change manually the attribute of .sh scripts to executable.
• Step 1 and step 2 have been previously executed: press any key to continue with Step 3.
• Step 3: The script will proceed with the option byte programming and flashing the code and data image.

The product state can be chosen (OPEN or PROVISIONED or TZ-CLOSED or CLOSED or LOCKED).

Warning

Reminder: LOCKED is a definitive product step that can’t be changed anymore.

Make a first trial setting the product in PROVISIONED state and complete the tutorial until the end.

2.4. Step 4: Execute the installed firmware

• Open PUTTY (or another terminal emulator).
• Select “Serial" and the COMxx port*.
• Set speed to 115200.
• Data 8 bits / Parity None / Stop 1 bit
• Click Open.

• Reset the board using the SW reset button on the board:

The code installed during the previous steps will be executed.

The menu of the installed code has two options:

• The menu 1 will launch the standard bootloader located in the system flash.
• The menu 2 will display the first 8 bytes and the last 8 bytes of the ns_data.bin

2.5. Flash memory new User application in CLOSED state

In the Terminal emulator choose Start Bootloader: Write 1.

--> This message is displayed:

• Close/disconnect the terminal emulator.

Warning

Don't power OFF power ON the board and don't reset the device.

• Open the project Project.eww in OEMiROT_Appli_TrustZone folder: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\EWARM
• Select the nonsecure project and change const uint8_t UserAppId = 'A' line 61 in main.c file to:

const uint8_t UserAppId = ‘B’; 

• Select: Project-> Rebuild all.

• Connect the board via UART on STM32CubeProgrammer without performing any reset or power OFF power ON (don't disconnect the board from your laptop).

• Select the “Erasing & Programming” tab.
• Browse the nonsecure encrypted code image HEX file that we previously generated in the folder Application\ROT\OEMiROT_Appli_TrustZone\Binary.

• Click Start Programming.
• Disconnect STM32CubeProgrammer.
• Open PUTTY (or another terminal emulator).
• Select “Serial" and the COMxx port.
• Set speed to 115200.
• Data 8 bits / Parity None / Stop 1 bit
• Click Open.

• Reset the board using the SW reset button on the board:
  • Boot Code and new firmware are displayed.

2.6. Step 5 : Regression

• A full regression will erase the user stored contents and secrets.
  • Erase the user flash memory content.
  • Erase the OBkeys.
  • Reset the secure option bytes to their default value.
  • Set the product in Open state.

• If the product is in Open state, a full regression is not needed: the device is not secured and changes can be done without any authentication. In case the regression script is executed, it will indicate some errors.
• If the product is not in Open state, the only way to change the OEMiRoT is to first do a full regression.

Warning

If the DA key has been regenerated in Debug_Authentication_configuration, please follow the section Certificate Chain generation (ROOT certificate) using STM32TrustedPackageCreator to generate a Root certificate which will be needed for regression. If the DA key has not been regenerated, you can continue the exercise.

2.6.1. Full regression from Provisioned state using a script (included in the STM32CubeFW)

The regression can be done using the provided script or using STM32CubeProgrammer.

To perform a full regression:

• Launch the regression script.
  • Note: For Linux and Mac operating systems, the end users may have to change manually the attribute of .sh scripts to executable.

• When asked: “The Trustzone feature is enabled?”, answer “Yes”.
• If the regression has succeeded, the following message should be displayed:

• Connect STM32CubeProgrammer. Check that the flash memory content is well erased and that the option bytes and product state are at their default values.

2.6.2. Full regression from Closed state using STM32CubeProgrammer

• Disconnect STM32CubeProgrammer.
• Redo the exercise starting at step 3, set the “closed” state.
• Click in STM32CubeProgrammer and select Debug Authentication.
• Click “Discover” , and the information window will be filled:

• Enter the paths for the key and the certificate (example with a certificate chain will be shown later, in this example only a single certificate is used (ROOT)):

• Click Continue .
• The opening method and permission are selected. Only the opening method defined by the certificate mask (during provisioning) will be possible.

• Click Execute and you have the following success Message:

• Check with STM32CubeProgrammer that the flash memory content is well erased and that the option bytes and product state are at their default values.
• The TZ will stay enabled and can be disabled using STM32CubeProgrammer.

3. OEMiRoT Step by step: Debug Authentication

3.1. Certificate chain generation

• Perform a full regression (if not already done at step 5), disconnect/reconnect the USB cable.
• Check Step 0 and do/redo Step 1.1.
• Open STM32TrustedPackageCreator, select H5 and select the DA CertifGen tab.
• The example is provided with one root, one intermediate and one LEAF key pair.
• The first certificate to generate is the ROOT certificate.
• This certificate defines the permission defined by the owner generating the certificates.
• The second certificate to generate is the intermediate certificate, chained with the ROOT certificate
• The owner for instance an OEM is defining the permission of this intermediate certificate
• The last certificate to generate is the LEAF certificate, chained with the intermediate certificate

To use the certificate chain for debug opening or regression, the LEAF certificate is used as an input for STM32CubeProgrammer (since this certificate is the last of the chain), but the permission is defined by the aggregation of all mask permissions. For instance, if the debug opening in L3 is not allowed in one of the masks of the chain, this debug opening will not be allowed (even if it is allowed in the LEAF mask). The root certificate can also be used by the owner of the root key for debug opening or regression according to the permission defined during the root certificate generation.

Certificate Chain generation (ROOT certificate) using STM32TrustedPackageCreator

• Select STM32H5 and ROOT; enter the path for the private key, the public root key and where the certificate will be stored (overwrite the default stored certificate).
• Set the permission mask for the ROOT: Setting 1 will give the permission.

• Click .

Certificate Chain generation (INTERMEDIATE certificate)

• Select INTERMEDIATE and enter the path for the private root key and the intermediate public keys.

We use one intermediate certificate for this example, but the same step can be done several times to add several intermediate certificates, each with its own key pair and permission mask.

• Set the permission mask for the INTERMEDIATE certificate.

• Click .

Information

Reminder: every added certificate of the chain can have equal or less permission than the previous certificate of the chain.

Certificate Chain generation (LEAF certificate)

• Select LEAF and enter the path for the private intermediate key and the path for the public LEAF key.

This certificate is the last of the chain.

• Set the permission mask for the LEAF certificate.

• Click 120px|middle

Information

The LEAF certificate can have equal or less permission than the intermediate certificate chained with the LEAF.

3.2. Secure Debug Opening

• Redo the exercise starting at step 3, set the “closed” state.
• Click in STM32CubeProgrammer and select “Debug Authentication”.
• Click “Discover”, and the information window will be filled.

• Enter the path for the key and the certificate (an example with a certificate chain will be shown later, in this example only a single certificate is used (ROOT)):

• Click Continue .

3.2.1. Secure Debug opening using STM32CubeProgrammer and ROOT certificate

Information

For the OEMiRoT example the application code is in HDPL3. A SECURE debug opening in level 2 or in level 3 will make the secure application visible.

• Select the Secure Intrusive Debug (level 3).

• Click Execute, and the following success Message is displayed:

• Disconnect STM32CubeProgrammer.
• Now that the debug is open the secure flash memory content can be read out.

Warning

! Don’t power ON / OFF the board, it closes the debugger.

• With STM32CubeProgrammer: Connect the board.
• The secure part of the flash memory is now visible @0x0C012400.

Information

The memory mapping of the nonsecure code is detailed in Project_s.map located in: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\EWARM\Secure\STM32H573I-DK_S\List

3.2.2. Secure Debug opening, attach IAR®, read flash content and code execution

To attach an IDE:

• Disconnect STM32CubeProgrammer.
• Open the Project.eww located in the EWARM directory:

Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\EWARM

• Select the secure Project:

• Select: Project -> Attach to running target.
• Open the main.c.
• Set a break point, the execution will stop at this point.
• Reset the board (SW reset, black button).

• Select: View Memory1 -> enter the flash memory address.
• The secure code is visible @ 0x0C012400.

3.2.3. Close the debugger through hardware reset

• Close the debug in IAR®
• Disconnect/reconnect the USB cable / A hardware reset will close the debugger again.
• Click in STM32CubeProgrammer and select “Debug Authentication”.
• Click “Discover” , and the information window is filled again, it shows that the state is closed.

3.3. Nonsecure Debug Opening

3.3.1. Nonsecure Debug opening using STM32CubeProgrammer and ROOT certificate

• Enter the path for the root private key and certificate.

• Click Continue.

Information

For the OEMiRoT example the application code is in HDPL3. A NON-SECURE debug opening in level 2 or in level 3 will make the secure application invisible

• Select Nonsecure Intrusive debug (level 3).

• Click Execute and the following success Message is displayed:

• Now that the debug is open the secure flash memory content can be read out.

Warning

! Don’t power ON / OFF the board, it closes the debugger.

• Connect the board to STM32CubeProgrammer if it has not been automatically connected.
• The Nonsecure part of the flash is now visible @ 0x08018400.

Information

The memory mapping of the nonsecure code is detailed in Project_ns.map located in: Projects\STM32H573I-DK\Applications\ROT\OEMiROT_Appli_TrustZone\EWARM\NonSecure\STM32H573I-DK_NS\List

Information

If you try to read the Secure Part of the flash memory @ 0x0C012400 you have an error message:

3.3.2. Nonsecure Debug opening, attach IAR®, read flash content and code execution

To attach an IDE:

• Disconnect STM32CubeProgrammer.
• Open the Project.eww located in the EWARM.
• Select the Nonsecure project.

• Select: Project -> Attach to running target.
• Open the main.c.
• Set a break point, the execution will stop at this point.
• Select: View->Memory-> Memory1 and enter the flash address => The nonsecure code is visible @ 0x08018400.

3.3.3. Close the debugger through hardware reset

• Close the debug in IAR® .
• Disconnect/reconnect the USB cable / A hardware reset will close the debugger again.
• Click in STM32CubeProgrammer and select “Debug Authentication”.
• Click “Discover” , and the information window is filled again, it shows that the state is closed.

3.4. Partial Regression

3.4.1. Partial Regression using the LEAF key and certificate chain

• Enter the path for the leaf private key and LEAF chain certificate:

• Click Continue.

Warning

The LEAF certificate was generated without the permission of partial regression, which implies that in this step it will not be possible to do partial regression with such a LEAF certificate.

• Select Partial regression.

• Click Execute.

The partial regression has not been allowed by the LEAF mask (only a full regression allowed) and you have the following error Message:

• Click on “Discover”, and the window state is filled again.

3.4.2. Partial Regression using the root key and certificate

3.4.2.1. Partial regression ->TZ-CLOSED State

• Enter the path for the root private key and certificate.

• Click Continue.
• Select Partial regression.

• Click Execute and the following success Message is displayed:

• Disconnect from STM32CubeProgrammer.

The product is now in TZ-CLOSED.

3.4.2.2. Run the code

• Open PUTTY (or another terminal emulator).
• Select “Serial" and the COMxx port.
• Set speed to 115200.
• Data 8 bits / Parity None / Stop 1 bit
• Click Open.

• Reset the board using the SW reset button on the board.

-> Only the Boot code is displayed:

• Nonsecure code and data have been erased during partial regression.
• Debug is not possible anymore.
• New code and data can be downloaded.

3.4.2.3. Download a new application code

• Open the project OEMiROT_Appli_TrustZone.
• Select the Nonsecure project.
• Change const uint8_t UserAppId = 'A' line 61 in the main.c file to:

const uint8_t UserAppId = ‘C’; 

• Select: Project-> Rebuild all.
• Open STM32CubeProgrammer and Connect the board.
• Select the “Erasing & Programming” tab.
• Browse nonsecure encrypted code image HEX file that we previously generated in folder Application\ROT\OEMiROT_Appli_TrustZone\Binary

• Click Start Programming.
• Browse non secure encrypted data image HEX file in folder ROT_Provisioning\OEMiROT\Binary

• Click Start Programming.

Warning

!!! A partial regression erases nonsecure code and data. It is necessary to download Code AND Data to visualize new firmware in the terminal.

• Disconnect STM32CubeProgrammer.
• Open PUTTY (or another terminal emulator).
• Select “Serial" and the COMxx port.
• Set speed to 115200.
• Data 8 bits / Parity None / Stop 1 bit
• Click Open.

• Reset the board using the SW reset button on the board.
  • Boot Code and new firmware are displayed.
  • Non secure debug is possible.

Nonsecure debug:

• Disconnect STM32CubeProgrammer.
• Open the Project.eww located in the EWARM.
• Select the Nonsecure Project.

• Select: Project -> Attach to running target.
• Open the main.c.
• Set a break point, the execution will stop at this point.
• Select: View -> Memory -> Memory1 and enter the flash memory address => Non secure code is visible @ 0x08018400.

Warning

!! If code is jumping to secure code, it still works but the user cannot debug / see secure world.

3.5. Full Regression using the LEAF key and certificate

• Close the debug in IAR®
• Click in STM32CubeProgrammer and select “Debug Authentication”.
• Click “Discover”.
• Enter the path for the LEAF private key and LEAF chain certificate.

• Click Continue.
• Select Full Regression:

• Click Execute and the following success Message is displayed:

• Check with STM32CubeProgrammer that the flash memory content is well erased and that the option bytes and product state are at their default values.