STM32 MCUs Security

We have a board with an STM32H7S3, using STiROT and OEMuROT to run our own application. The application runs in place from external flash, and uses external RAM for data.The process has proven extremely challenging, but we have been able to get the application to run...up to the point where it needs to initialise a peripheral which uses a PLL-dependent clock.OEMuROT does some clock initialisation, but we need to change some of those settings, including turning on additional PLLs.I've tried adding clock setup code to the app (originally generated by CubeMX), but it fails because you can’t change PLL settings while they’re running. So I added a call to the HAL function to reset the clocks first – but that also doesn’t work because we’re running from the external flash at this point, which relies on a PLL!I then tried moving the clock setup code into the bootloader – in the code which runs at the end of proceedings, or at the start – but they also failed.This code has to run from internal

Hello , I am aiming to demonstrate secure storage operation SST using PSA APIs using STM32U585. To verify that TF-M services are operational and Secure/Non-Secure communication works. However I dont find any more stm32cube TFM ready solutions/examples. So i have started from SBSFU examples and cloned TFM Source code from trusted firmware m git and trying to integrate the lib I need . Is this the right way to do so ? is there better starting point? Also it make more sens to put this in secure world however not sure if there is any considerations to think of while doing this . This is what I am trying to do one Secure Storage lifecycle: Write data to Secure Storage using psa_ps_set() Read the data back using psa_ps_get() Verify data integrity using memcmp() Remove the stored object using psa_ps_remove()

I'm using the link below to select boot path and do secure boot device provisioning for my STM32H563 board:https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563Boot path is configured as follows:I have run provisioning.bat, the product state was set to PROVISIONED. The provisioning was successfull, with logs at the end of ob_flash_programming.log:OPTION BYTE PROGRAMMING VERIFICATION:Option Bytes successfully programmedTime elapsed during option Bytes configuration: 00:00:01.334Programming successHowever, inside ob_flash_programming.log, it also shows:PROGRAMMING OPTION BYTES AREA ...Warning: Option Byte: boot_ube, value: 0xB4, was not modified.Warning: Option Byte: hdp2_end, value: 0x0, was not modified.Warning: Option Byte: secbootadd, value: 0xC0000, was not modified.Warning: Option Byte: secwm2_end, value: 0x0, was not modified.Warning: Option Byte: sram2_ecc, value: 0x0, was not modified.Warning: Option Byte: sram2_rst, va

Hello,I have written a custom bootloader for my stm32u5 project and have been testing it for the last few months with multiple working firmware updates.  To give some context, I transfer an encrypted firmware image to an external flash chip over CANfd from the currently running firmware.  The next time the device boots, the bootloader looks for a new encrypted image on the external flash and if found it will decrypt the image, delete the internal flash where the application lives and then flashes the decrypted image. It will then de-init some peripherals and jump to the new application, fairly standard implementation.  All of this has been working flawless until I set RDP = 1(DC) in stm32cubeprog.  Also need to mention that I have set both passwords for RDP regression a while ago, I just have not been setting the RDP level beyond 0.With RDP = 1 the device will boot as it should, and I can send it a firmware update.  I will power cycle the device and it will per

In STM32Cube_FW_H7RS_V1.3.0, file Projects/STM32H7S78-DK/Applications/ROT/STiROT_iLoader/STM32CubeIDE/prebuild.bat:As currently written, it fails in a couple of places. Here are the changes necessary for it to run:(The system won't let me upload the edited batch file.) 

I am attempting to make a previously developed design run with Trustzone enabled. I have been unable to get the HSPI1 PSRAM to function.I've set the peripheral's GTZC's attributes to NSEC|NPRIV.I've set the appropriate GPIO pins' attributes to NSEC.I've set the MPCWM Config to consider the memory as NSEC|NPRIVI've set the appropriate/associated DMA channels as NSEC|NPRIV.None of these seem to have any effect. The Initialization code hangs/timesout in:BSP_HSPI_RAM_Config16BitsOctalRAM in stm32u5a9j_discovery_hspi.c.RCC->AHB2ENR2 shows the HSPI clock enabled.Can anyone point to a minimal working example of using the AP512 on the STM32u5A9J-DK with trustzone enabled?

I am currently working with the STSAFE-A110 and I have noticed a significant lack of documentation for those who need to implement or understand the driver logic.For instance, when generating ECC asymmetric key pairs, the official datasheet mentions the Generate Key command (¶ 4) but does not document its I2C syntax or semantics.Although I am using the STSELib middleware, I have found that its APIs, such as stse_generate_ecc_key_pair() also lack exhaustive documentation. A specific example is the PLAT_UI16 usage_limit parameter; its purpose is never explained.By digging into the STSELib source code, it appears usage_limit parameter is passed directly to the STSAFE-A110 via I2C.Furthermore, in the Doxygen documentation there is an example where usage_limit is set to 100,while the STSAFE-A120 examples use 255. /* ## Generate key pair in slot 1 */ uint8_t slot_1_public_key[stse_ecc_info_table[STSE_ECC_KT_NIST_P_256].public_key_size]; stse_ret = stse_generate_ecc_key_

Hello, everyone.Can the STM32F407VE encrypt multi-byte messages to maintain the confidentiality of messages between the host and client (stm32)? If so, what type of encryption can be run on this processor?Thank you:)

I'm working with the STM32U385/375 for a project, and have started my investigation into how to convert it to a secure root of trust application by working with the OEMiROT examples.In stock form it works well. The provisioning works, the update over the y-modem link works just fine, etc. However, I want to build a combined binary and not deal with separate non-secure and secure binaries to apply for an update.Accordingly, I changed MCUBOOT_APP_IMAGE_NUMBER in OEMiROT_Boot/Inc/flash_layout.h from 2 to 1, like so:#define MCUBOOT_APP_IMAGE_NUMBER 1 /* 1: S application only if FLASH_NS_PARTITION_SIZE = 0 , else S and NS application binaries assembled in one single image. 2: Two separated images for S and NS application binaries. */The build works fine, the first part of the provisioning script works fine, the appropriate value is updated in appli_flash_layout.h, and the programming begins. However, it fails with this error:========== Error while executing "Programming the option bytes and

Hi,I'm developing a secure boot application for STM32H563ZI microcontroller. I started with a very simple application following ST template code and tutorials like this one: https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563  Everything runs as expected when I try to run my application using the NUCLEO-H5 board. However, this is not true when I do the same provisioning process in my H5 custom board. The only difference I can see between the two tests is that in the custom board I'm using the STLink-V2 programmer, while the Nucleo is programmed by the embedded STLINK-V3EC.Here are some additional points:1) in both cases the provisioning script reaches the end, saying "The board is correctly configured".2) in the custom board, I see the flash full of zeros after provisioning; I checked it with stm32CubeProgrammer3) I have no problems in flashing firmware through stm32CubeProgrammer or stm32CubeIde in my custom board

I've downloaded archive "en.STM32CubeExpansion_Crypto_v4.0.1.zip", now I'm trying to install it in STM32CubeMX with "From Local..." feature, but I'm getting error. How can I install the library in CubeMX?Thank you.

What I want to achieve:During startup all code is verified, starting with SMiRoT (as root-of-trust) then SMuRoT, then SecureManager then non-secure application.If the application has been modified (vberification fails) the startup shall end in system bootloader.Unfortunately, this does not work as our tampered/modified non-secure application is still started/executed instead of jumping into bootloader.Secure manager is installed with the provisioning script. We have modified the BOOT_UBE setting via TrustedPackageCreator from 0xB4 (OEM-iRoT - user flash) to 0xC3 (ST-iRoT - system flash) and re-generated Option_Bytes.csvWhat I see is that when connecting the STM32CubeProgrammer, the value for BOOT_UBE still shows 0xB4.And in the log during SFI flashing (provisioning.py -v --sfi-flash) it shows this:DEBUG - Warning: Option Byte: BOOT_UBE, value: 0xB4, was not modified.DEBUG - Warning: Option Bytes are unchanged, Data won't be downloadedDEBUG - Time elapsed during option Bytes config

Hello, I have a problem with setting readout protection in the STM32L496 device in software. The protection is set to "BB". After setting and power on reset, the microcontroller seems to not work (it looks like as if it was "stuck up"). I connected the ST-Link programmer and run STM32Cube programmer and it shows option byte RDP set correctly to BB value. Also, in the FAULT ANALYZER section it displays "CPU: LOCKUP". I don't know why it happens and how to solve it. The software code that sets the RDP protection is shown below:  __disable_irq(); while (FLASH->SR & FLASH_SR_BSY); FLASH->KEYR = 0x45670123; FLASH->KEYR = 0xCDEF89AB; FLASH->OPTKEYR = 0x08192A3B; FLASH->OPTKEYR = 0x4C5D6E7F; FLASH->OPTR = 0xFFEFF8BB; FLASH->CR |= FLASH_CR_OPTSTRT; while (FLASH->SR & FLASH_SR_BSY); FLASH->CR |= FLASH_CR_OBL_LAUNCH; 

I try to enable the PCROP Feature on a STM32H753I am using the STM32CubeProgrammer and connect via ST-Link V2After connecting, I go to the "OB" page and set the PROT_AREA_END1 value to 0xFFF and activate the DMEP1Then I press the "Apply" button and this happens in the log:Option byte command : -ob PROT_AREA_END1=0xFFF PROGRAMMING OPTION BYTES AREA ... Bank : 0x00 Address : 0x5200201c Size : 308 Bytes UPLOADING OPTION BYTES DATA ... Bank : 0x00 Address : 0x5200201c Size : 308 Bytes OPTION BYTE PROGRAMMING VERIFICATION: Error: Expected value for Option Byte "PROT_AREA_END1": 0xFFF, found: 0x0 Error: Option Byte Programming failedAnd then, I always get the error Message "Option Byte Programming failed"The RDP has level 0, but the same error occures, if I try to set RDP to level 1 at the same time.In the documentation I found no hint, that there is any other prerequisite must be met to set the PCROP.Has anyone an idea what the problem could be?(In generally the chip works, I can eras

Hello ST team,I am studying the flash security mechanisms (RDP, WRP, PCROP) on STM32L476RG and I understand how to configure Option Bytes using STM32CubeProgrammer or firmware.What I am trying to understand is the hardware-level enforcement flow of Option Bytes:• During reset / power-up, which hardware blocks read the Option Bytes?• How are these values propagated to the Flash controller and debug access logic?• At what point relative to CPU reset release are these protections enforced?I understand that enforcement happens before user firmware execution, but the reference manual does not describe the internal sequence in detail.Could you please clarify (at a high level) how Option Bytes are latched and enforced by hardware during the boot/reset sequence on STM32L4 devices?Thank you.

Hello,starting from the example application of the OEMiRot boot project, I noticed that the NS application size is limited to 640kB in the flash_layout.h  (#define FLASH_NS_PARTITION_SIZE (0xA0000) /* 640 KB for NS partition */)Since there is 1MB avalaible in the slot, I would like to increase this size from 640kB to 896kB. A first naive change is just to change the define from 0xA0000 to 0xE0000 which leads to the state that the bootloader doesn't find a bootable image anymore.How do I set a larger non-secure application size to have a benefit of the 1MB flash slot? Best regards,Stefan

Hi!I'm working on a Trustzone enabled application in STM32U5A5 nucleo board and have some questions in my mind. I have used the configurations of the example project for the Trustzone, which you can find below: - TZEN=1 - SECWM1_PSTRT=0x0 SECWM1_PEND=0xFF meaning all 128 pages of Bank1 set as secure - SECWM2_PSTRT=0xFF SECWM2_PEND=0x0 meaning no page of Bank2 set as secure, hence Bank2 non-secure I have enabled SAU and left it with the default configuration. I've also enabled the GTZC_S. In my application, I'm using TAMP mechanism of the RTC to create an interrupt when the output signal doesn't match the input signal. First question:My application can boot from the secure app and jump to non-secure app without any problems. But in the MX generated NonSecure_Init() function, after the line SCB_NS->VTOR = VTOR_TABLE_NS_START_ADDRThe SCB->VTOR_NS register doesn't change, remains as 0x0 (according to the SFR in the debug interface). After the boot to non-secure

I am trying to use the DA function of the STM32H573. I can successfully write the OBK file (with TrustZone disabled) and regression via STM32_Programmer_CLI.exe. However, I encountered an issue when trying to read the plaintext of the OBK payload in my code. I am unable to obtain the correct plaintext through SAES and DHUK.Here is part of my code:int32_t OBK_Flash_ReadEncrypted( void *pData) { uint32_t Offset =0x0100; uint32_t Length = 0x60; uint32_t i = 0U; CRYP_HandleTypeDef hcryp = { 0U }; uint32_t SaesTimeout = 100U; uint8_t DataEncrypted[MAX_SIZE] = {0U}; uint8_t *p_source = (uint8_t *) (FLASH_OBK_BASE_S + Offset); uint8_t *p_destination = (uint8_t *) DataEncrypted; uint32_t a_aes_iv[4] = {0x8001D1CEU, 0xD1CED1CEU, 0xD1CE8001U, 0xCED1CED1U}; for (i = 0U; (i < Length); i++, p_destination++, p_source++) { *p_destination = *p_source; } __HAL_RCC_SBS_CLK_ENABLE(); __HAL_RCC_SAES_CLK_ENABLE(); /* Force use of EPOCH_S value for DHUK */ //WRITE_REG(SBS_S->EPOCH

I've got an STM32U385 on a custom board that is unresponsive.The software is based on the OEMiROT trustzone example.The sequence of events that lead to this, as nearly as I can remember were:1.) Set up the device with provision.bat, with RDP level 2. This worked fine. The device ran as it should.2.) Regress the device using regression.bat, this process failed, but left the device in an accessible state for the debugger.3.) I connected the boot0 pin to VDD, connected with the programmer in hot plug mode, set RDP to 1.4.) I set RDP to 0 and TZ enabled to 0, which worked.5.) I disconnected the boot0 jumper, and tried loading code normally, it then failed at address 0x80004000. Reading out that address with the programmer revealed that it was not programmed, but instead remained all 0xff's. I tried several times to program, always with the same result, the first part of memory, up to address 0x80003fff programmed correctly, and the rest failed.6.) I tried running the regression script agai

Hello everyone,I am trying to implement SBSFU (Secure Boot Secure Firmware Update) on NUCLEO-G474RE using STM32CubeExpansion_SBSFU_V2.7.0.Initially, everything was working fine and I was able to program the board normally.What I didI followed the SBSFU documentation and examples.While configuring SBSFU, I modified Option Bytes, specifically Write Protection (WRP) addresses to match the SBSFU memory layout.After applying the option bytes, the problem started.Current problemNow I cannot program or erase the MCU anymore.I get the following errors:1.In STM32CubeIDE'Launching SBSFU (1)' has encountered a problem.Failed to execute MI command:load ...\SBSFU.elfError finishing flash operation2. In STM32CubeProgrammerFull chip erase failsMass erase fails with error:Error: Mass erase operation failed. Please verify flash protection3.I also tried:Full chip eraseErase selected sectorsHardware reset / power cycle“Under reset” connection modeFactory reset via STM32CubeProgrammer→ All fail with

I wanted to start a discussion about the WE999 , which has been getting a lot of attention recently among mobile users. Many players are talking about its smooth interface, fast performance, and simple design that makes it easy for beginners to understand.From a user point of view, WE999 feels lightweight and works well on most Android devices. The app runs smoothly even on low-end phones, which is a big plus. Navigation is simple, and the overall layout is clean and user-friendly. https://w999game.com/

Hi,based on the ST example where the 640kB RAM is splitted into 2 * 320kB for secure/non-secure application, I want to change this to 32kB/608kB for secure/non-secure app. After modification of the linker files for the secure/non-secure app, the non-secure app runs into an hardfault right at the start. The error is that some ns access is done in secure area in SRAM1 (at address 0x2001f840).I first started the project on the STM32H563 eval board and simply copied the settings of MPU and GTZC over to the STM32H562. These settings are working on the STM32H563, so I can properly jump there into the non-secure app.Are there any difference in setting the memory areas for secure/non-secure/priviledged feature?Here are the settings.linkerfile non-secure:define symbol __ICFEDIT_region_RAM_start__ = 0x20008000;define symbol __ICFEDIT_region_RAM_end__ = 0x2009FFFF;linkerfile secure:define symbol __ICFEDIT_region_RAM_start__ = 0x30000000;define symbol __ICFEDIT_region_RAM_end__ = 0x30007FFF;v

I'm trying to understand how the HDPL1 is calculated based on an OBK file.I have dumped the contents of HDPL1 / 0x0BDF0100 and can see that for a 16 length password, I have 96 bytes written, as follows0x0BFD0100 to 0x0BFD0120, unknown calc, how is this calculated?0x0BFD0120 to 0x0BFD0140 SHA-256 of password0x0BFD0140 to 0x0BFD0160 zeros

We have a query regarding STM32U375 PKA peripheral.As per datasheet, the peripheral is available for this variant. Under the "STM32Cube/Repository/STM32Cube_FW_U3_V1.2.1/Drivers/STM32U3xx_HAL_Driver/" we can also see that stm32u3xx_hal_pka.c and stm32u3xx_hal_pka.h driver files are available. However, the ST official product page - does not seem to mention this peripheral as a part of STM32U375 series.    Also, we cannot see this peripheral in graphical configuration .ioc. Please let us know if this is available as part of STM32U375 series and how to use it.We also need STM32U375.svd for debugging support, please share this file.

I have a project which runs fine using CMOX_PQC_ML_DSA_44_DET_SIGN_LOWRAM_ALGO but I would like to see how much faster I can get with CMOX_PQC_ML_DSA_44_DET_SIGN_ALGO. When I use it, cmox_pqc_dsa_sign returns 0x9000c, which apparently means "Not enough memory".I am also wandering what kind of memory we are speaking about because it does not seems to request heap memory and I don't expect it to detect if stack is large enough at runtime.I am going to have exactly the same question for CMOX_PQC_ML_DSA_65_DET_SIGN_ALGO and CMOX_PQC_ML_DSA_87_DET_SIGN_ALGO.Perhaps a more general question: is there a documentation for the cmox_pqc library ?