STM32 MCUs Security

I accidentally configured PCROP protection on my STM32H755XIH6 that has effectively locked me out of almost the entire flash memory, and I'm unable to recover using standard methods.Current Situation:Device: STM32H755XIH6 (2MB dual-bank flash: Bank1=1MB, Bank2=1MB)PCROP Settings:Bank 1: PROT_AREA_START1=0x2 (0x08000200) to PROT_AREA_END1=0xFFF (0x080FFFFF)Bank 2: PROT_AREA_START2=0x2 (0x08100200) to PROT_AREA_END2=0x81FFFFF)Available Space: Only 512 bytes per bank (0x08000000-0x080001FF, 0x08100000-0x081001FF)Problem: Almost all of flash is PCROP-protectedI tried the below methods following some other discussion on the forum:STM32CubeProgrammer GUI - option byte modifications fail with "changes can't be applied after OB_LAUNCH" (It connects under reset but I still get changes cant be applied after OB_LAUNCH error)CLI commands to modify PROT_AREA_START/END - all fail with same errorRDP level cycling/regression (0xAA → 0xBB → 0xAA) - completes but

Hello,I am working with an STM32H573 and I would like to implement OEMiROT.Is it possible to use OEMiROT without activating TrustZone on this device?If it is possible, is there an official or recommended ST method?Any clarification or pointers to documentation or real-world implementations would be appreciated.Thank you.

Hi all, I'm trying to get some knowledge about the use of OEMiRoT using the NUCLEO-H563ZI board following the ST Tutorial How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled - stm32mcu. Once the certificate chain has been created, I'm facing some problems with the Debug Authentication procedure: indeed, after setting the root key and root certificate in the Debug Authentication page of STM32CubeProgrammer, and selecting "Level 3 Intrusive Debug" as stated in section 3.2.1 of the tutorial, I receive both a "Debug Authentication Success" and a "Error: ST-LINK error (DEV_CONNECT_ERR)"; after this, I'm not able to read any of the data stored in the chip flash, neither with STM32CubeProgrammer or STM32CubeIde.This problem adds to those already mentioned in topic STM32H563: CubeProgrammer UART connect fails in PRODUCT_STATE = iROTProvisionedAm I missing something? All other levels of authentication, either secure or non-secure, are returning me the same error wit

At present, as of the last Hal version as far as I know, obk cannot be used in a non trust zone project.FLASH_TYPEPROGRAM_QUADWORD_OBK fails because the NS bits aren't set, among other issues.Is this by design, IE obk can't be used by non TZ, or is this just simply not a completed or fully fixed feature? Here is what I'm doingI've edited HAL_FLASHEx_Erase like#if defined (FLASH_SR_OBKERR) else if ((pEraseInit->TypeErase&~(FLASH_NON_SECURE_MASK)) == FLASH_TYPEERASE_OBK_ALT) { /* OBK erase to be done */ FLASH_OBKErase(); /* Wait for last operation to be completed */ status = FLASH_WaitForLastOperation(FLASH_TIMEOUT_VALUE); } #endif /* FLASH_SR_OBKERR */And my code is:int keyStorageSavePrivate(char* key) { uint32_t status; uint32_t len = strnlen(key, KEY_STORAGE_SIZE - 16); int ret = 0; static uint32_t FlashWord[4]; if (len >= KEY_STORAGE_SIZE - 16) { return 1; } len += 1; // Add string 0 HAL_FLASH_Unlock(); HAL_FLASHEx_OBK_Unlock(); if (len & 0b

Hello,I am working on a project using mbedTLS and Keil MDK to make an HTTPS server running on an STM32F777. To speed up encryption/decryption, I am trying to make use of the CRYP coprocessor (mostly focusing on speeding up AES GCM calculations). My implementation is based on the example given here: https://github.com/STMicroelectronics/STM32CubeL5/tree/master/Projects/STM32L562E-DK/Applications/mbedTLS/Crypto_Selftest.However, when I try to run with my alternative AES GCM implementation, the CRYP coprocessor does not calculate the same tag as mbedTLS. This causes the SSL handshake to fail. I've attached my files for the GCM alternative implementation here. Am I missing something with the way I'm presenting my data?

Hi,In paragraph 1.2 “Launch the provisioning script” I read that:Launch one of the provided scripts depending on your IDE:For EWARM or MDK-ARM: launch the provisioning.bat script.For STM32CubeIDE: launch the provisioning.sh script.I have Windows and STM32CubeIDE. Can I run the provisioning.sh script on Windows?Looking into the env.sh script, I found the following code:  echo ${OS} | grep -i -e windows -e mingw >/dev/null if [ $? == 0 ]; then echo "" echo " ==========================================" echo "| For Windows OS, please use .bat scripts. |" echo " ==========================================" echo "" echo " Press any key to continue..." echo read -p "" -n1 -s exit 0 fi  It seems that the script cannot be run on Windows.Could you please advise how to run the provisioning script for STM32CubeIDE on Windows?Thank you very much for your support.Best regards,Marco

Hi,I am doing a feasibility study for SBSFU on an STM32H750, specifically firmware encryption and authenticity check. I am using the XCUBE expansion pack v2.8.0.- Using prepareimage.py & modified keys.py along with default prebuild and postbuild.sh- Using a single download + single active slot in external memory- All protections are disabledModifications to default example:- Adjusted default linker script to increase active + download slot size- Modified keys.py to append 0xFF bytes to binary before encryption to meet 16 byte multiple requirementMethod altered: AES_CBC:encrypt- generating new AES and ECDSA keys as mentioned in readme.txtAs mentioned in AN5056, section 4.2, I modified SECBOOT_CRYPTO_SCHEME to SECBOOT_ECCDSA_WITH_AES128_CBC_SHA256. I can see that prebuild.sh detects this change and adjusts accordingly. Observations:I have tested the firmware installation using ECDSA signature without encryption to get the following errors.1. Error on first boot after f

Hello everyone,My team and I are working with a custom board based on the STM32WB55RG. Due to limited pin availability, we need to use USB as a virtual COM port for serial communication. We successfully configured the USB Virtual COM and were able to print messages on the console without any issues.However, we encountered a problem after integrating SBSFU.The USB Virtual COM works fine within the SBSFU application, but once the SBSFU process completes and our custom application starts, the USB stops functioning. We can no longer see messages in the terminal, even though our application is running as expected by debugging it with the USART / LPUART.We have already checked the USB and clock configurations in both the SBSFU app and our custom application, and everything seems to be set up correctly. Furthermore, we also attempted the following:Forcing a USB re-enumeration by pulling the D+ pin low for a few milliseconds.Playing around with initializing and de-initializing the USB in both

Hi,we are experiencing an issue with the STM32G0B0 when RDP level 1 is enabled, following the steps below:Flash the device using J-LinkStart the device and let the application set RDP = 1Enter the STM32 ROM bootloader (via UART)Disable RDP protection (perform mass erase)Program new firmware with bootloaderReboot the device and set RDP = 1 againAfter this sequence, the device remains locked.Even if we apply multiple resets using the NRST pin, the device does not recover.The only way to unlock the device is to completely power-cycle it (turn the power off and on again).Is it possible to re-enable RDP protection and start the new firmware without removing power from the device?Thank you for your support.

I would like to implement a  secure firmware update solution that will work in both an STM32G4A1 and an STM32U0 83.  Different applications, but I would like to use the same basic bootloader and PC update application.  Both would updated over USB.  They have basically the same security features and both have the AES-GCM accelerators.I've been watching the MOOC - Security series to learn how to do this.  I got to the end of  "Security Part4 - STM32 security in practice - 15 Secure firmware update" and had some questions since there isn't any lab video for this module like there are for the modules that came before it. I've also looked at the Silicon Labs AN0060: Bootloader with AES Encryption app note, which is similar in implementation to what I am thinking of doing. The link for the slides for the MOOK module is at the bottom of this page:https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/STM32_secur

I have the NUCLEO-H753ZI example running on my board. All works fine without the security features. When I enable both the SFU_MPU_PROTECT_ENABLE and SFU_IWDG_PROTECT_ENABLE. I keep having a watchdog when it tries to execute the firmware. I commented the #define SFU_IWDG_PROTECT_ENABLE and enable the SFU_VERBOSE_DEBUG_MODE. It gets stuck  at verifying the user FW as shown below.= [SBOOT] SECURE ENGINE INITIALIZATION SUCCESSFUL= [SBOOT] STATE: CHECK STATUS ON RESETINFO: A Reboot has been triggered by a Hardware reset!= [SBOOT] STATE: CHECK NEW FIRMWARE TO DOWNLOAD= [SBOOT] STATE: CHECK USER FW STATUSA FW is detected in the slot SLOT_ACTIVE_1= [SBOOT] STATE: VERIFY USER FW SIGNATUREWhen I breakpoint I can see that it is stuck at this as USB stops running after the first SFU_LL_SECU_SetProtectionMPU call which is the SFU_INITIAL_CONFIGURATION.TRACE(" @%d:%x size:%x sub:%x perm:%x exec:%x\r\n",MPU_InitStruct.Number, MPU_InitStruct.BaseAddress, MPU_InitStr

Can you help with new research on secure boot?   I am a cyber security researcher at the University of Bristol in the UK. I would like to your views on Secure boot.   My area of interest is developer-centred security, specifically in the issues that developers face when trying to build secure IoT devices.    If you have ever looked at implementing secure boot, or used it in your current development, or maybe think it to complicated, then I would really like to hear from you. Please take just 8 to 10 minutes to do this short survey on secure boot. https://universityofbristol.eu.qualtrics.com/jfe/form/SV_06xKUNve9ioJ5T8   If you have any questions, you can contact the researchers directly at fe23957@bristol.ac.uk

Hello.  I am experimenting with securing a STM32H503 using password authentication, which will ultimately be an automated process.I created a simple password for testing and created the password hash in board_password.bin and da_password.bin(just for comparison, I also used Segger's advice and tried certutil and the resulting board_password.bin file is identical, so I'm pretty sure the password hash worked).I set the chip to PRODUCT_STATE provisioning and programmed the chip with the password using the following:STM32_Programmer_CLI.exe -c port=SWD speed=fast ap=1 mode=Hotplug  -ob PRODUCT_STATE=0x17STM32_Programmer_CLI.exe -c port=SWD speed=fast ap=1 mode=Hotplug -w board_password.bin 0x8FFF000Both of these commands succeeded with no errorsAs recommended, I locked the OTP so I wouldn't accidentally damage it by overwriting by:STM32_Programmer_CLI.exe -c port=SWD speed=fast ap=1 mode=Hotplug -ob LOCKBL=0x1Again, no errorsFinally I set PRODUCT_STATE to PROVISIONED and aga

I have legacy SBSFU based system running on an stm32f429 for a few years now, based on the STM32F413ZHT6 demo code that was present in the package. I am now interesting to using the KMS feature of SBSFU but after reading um2622 /seeing https://www.youtube.com/watch?v=YjiNaTHQp2s I am a bit at a dead end on how to start as none of the kms files seem to be compiled in my bootloader. I am now getting the impression there is no KMS support at all on an stm32F4, this based on the fact that for example Figure 14 with the project folder structure in um26222 shows images with _KMS but this does not exist for the stm32f4 version I started from. So is KMS a no-go on STM32F4 because it uses features not available on STM32F4 ?Looking at Figure 4 SBSFU security IPs vs. STM32 series of  um2262 this seems to be the case if I understand that correctly (it seems to be needing this Firewall thing) ?If it is not supported, I would suggest adding this information at the very

I am trying to integrate a very simple TouchGFX Application into the SBSFU (I only really need SB right now) application, on STM32U5A9J-DKI've switched out the Nonsecure application for mine, I've modified flash_layout to do primary only, no external loader, 1 image. I modified the template loader script to have a Framebuffer section that spans SRAM3 (minus the secure section) and SRAM5. I'm using the startup_stm32...c that the original nonsecure application uses.Right now. It builds and boots, and shows "Jumping to first Image Slot" and just sits. I think it's getting into the Appli_Secure, because the Users LEDs on my board are lighting up.I found some verbiage elsewhere that indicates that I likely need to unsecure the IOs and SRAMs that the new NonSecure application uses, but when I start doing that, things go haywire.For example, I've got my project setup so that I can switch back to using the original demo Appli_NonSecure with my modifed flash_layout.h and linker script, and so I

I've been watching the MOOC - Security series and had some questions.  There is a link in the info block to a forum for any questions, but the link no longer works.  https://www.youtube.com/watch?v=g7ykhnmh7sAIs this the right place?I got to the end of  "Security Part4 - STM32 security in practice - 15 Secure firmware update" and had some questions since there isn't any lab video for this module like there are for the modules that came before it.

I am working with the STM32U585RIT6 and need to implement a secure firmware update. In my application code, I don’t want to handle flash management or low-level update logic. I only want to generate a secure binary file and perform the update.I reviewed the SBSFU and X-CUBE-SFI examples. The X-CUBE-SFI solution requires a license and an HSM card, which I do not want to use. The SBSFU example available under B-U585I-IOT02A/Projects/Application/SBSFU involves multiple procedures and is somewhat difficult to understand.Given these constraints, how should I approach implementing a secure firmware update?

Hi all,I was doing a firmware update from my raspberrypi to my MCU through I2C, and I facing this write protection issue.On initial flash with swd, I was flashing bootloader + main app to their required locations with their meta data like CRC program length into flash locations 0x08012810, 0x08012820 respectively. I am facing this issue while I try to erase and program new value "Write protection error at 0x08012800 - check flash protection settings".Mcu used : STM32G070CBT6 (F: 128 Kb, R: 36kb), , Page size 2KBOption bytes used : WRP1A_STRT = 0x3f WRP1A_END = 0x00, WRP1B_STRT = 0x3f WRP1B_END = 0x00 

Hello, I am trying to use SAES with a wrapped key to decrypt firmware updates on an stm32u5g9vjtxq. I am not sure how I should be changing the InitVect in CRYP_AES_CBC mode after hcryp is already initialized with HAL_CRYP_Init.  To elaborate on what I am trying to do I have created a wrapped key that is being stored in OTP memory along with the IV used to encrypt / decrypt that wrapped key.  My bootloader calls HAL_CRYPEx_UnwrapKey using the OTP memory address of the wrapped key and the IV also stored in OTP.  I then want to change the IV to match that of what was used to encrypt the new firmware image, the unwrapped key is what was used to encrypt the firmware image.  I am not sure how to accomplish this without having to call HAL_CRYP_Init again...I think the second call to HAL_CRYP_Init looses the unwrapped key and replaces it with whatever is defined in hcryp.Init.KeySelect which I have set to CRYP_KEYSEL_HW.To summarize I need to be abl

Hello!I have a custom PCB using the STM32U5A9 microcontroller.I've been developing my code using Cube IDE with CubeMX generated software including TouchGFX.I need to implement secure boot and OTA. I am following the SBSFU example for the B-U585I-IOT02A board and struggling to incorporate my project in the Non-secure user application segment of that demo project. I’m also trying to go the other way around and implement the SBSFU infrastructure and files into my custom project.First question - all I need is secure boot and OTA is it true that I do not need to enable the Trust Zone? If so, how should I modify the SBSFU build process to only include one image?Second question - It’s been difficult to follow the SBSFU code especially the slot addresses and programming to replicate it within my custom project. The postbuild script for the SBSFU_Boot project pulls firmware size values from image_macros_preprocessed_bl2.c to populate addresses in other scripts like SBSFU_Update.sh. How is this

Hello,I would like clarification on the behaviour of STM32U3 devices when Readout Protection (RDP) Level 1 is enabled.Configuration:TrustZone: DisabledDebug interface: SWD/JTAGQuestions:With RDP Level 1, is Flash completely unreadable by any third-party tool or by any boot mode (system memory boot, RAM boot, etc.), except when accessed by application code running on the MCU?With RDP Level 1, is application debugging still supported (attach debugger, halt, step, breakpoints), and are there any known limitations compared to RDP Level 0?Any confirmation or documentation reference would be appreciated.Thank you,Vijay

Hi, I am trying to implement DA on an stm32H563, I have created the .obk file, and was selected in the Stm32Programmer. I have changed the product_state to provisioning and I got the message "Do you want to use the default?"I clicked YES and I got the default DA, located in ..\STM32CubeProgrammer\bin\DA_Default_Config\STM32H5I was able to perform a full regression and then I tried again to flash and secure the chip, and this time I did choose "NO" to the default. Now I have tried my DA password and the default and none of them works. Also, I did at first tried to provision the mcu with my obk file, but was complaining about the OB not in provisioning. So after the provisioning I got locked out.Can the board be saved in any way or I have just bricked an mcu?I am using the STM32H563 NucleoThanksAle

I'm working on a project which is being ported over to be TrustZone aware, part of this project makes use of an OCTOSPI configured in memory mapped mode for file access. Base settings come from the IOC however the memory mapping is executed in source.In the non-TrustZone project this works without issue, however in the TrustZone aware one it is triggering a SecureFault upon trying to access a memory region. // Sample access that causes the SecureFault uint32_t testAccess = *(uint32_t *)0x90008000; The SAU reports an AUTHVIOL error for the address 0x9000_8000.The SAU is configured to enable NonSecure access to the region 0x9000_0000 through 0x9FFF_FFFF.The MPCWM settings have also been configured to mark the same region as NonSecure and UnprivilegedThe OCTOSPI DMA channel is configured for NonSecure and UnprivilegedThe MPU is disabled, however we have also tested with enabling the MPU in both contexts and mapping the same region to be Non-Secure, Unprivileged with no succ

Hello,After creating a new project based on the FreeRTOS_Queues_ThreadFlags_TrustZone example from MX and generating code, there is a compile error:[build] C:/Users/tuoma/AppData/Local/stm32cube/bundles/gnu-tools-for-stm32/13.3.1+st.9/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: CMakeFiles/FreeRTOS_Queues_ThreadFlags_TrustZone_AppliNonSecure.dir/Src/stm32n6xx_hal_timebase_tim.c.obj: in function `HAL_InitTick': [build] C:/Users/tuoma/STM32Cube/Example/FreeRTOS_Queues_ThreadFlags_TrustZone/AppliNonSecure/Src/stm32n6xx_hal_timebase_tim.c:56:(.text.HAL_InitTick+0x1e): undefined reference to `HAL_RCCEx_GetTIMGFreq' [build] Memory region Used Size Region Size %age Used [build] RAM: 66120 B 511 KB 12.64% [build] collect2.exe: error: ld returned 1 exit status [build] ninja: build stopped: subcommand failed. [build] ninja: build stopped: subcommand failed. [proc] The command: cube-cmake --build C:/Users/tuoma/STM32Cube/Example/FreeRTOS_Queues_ThreadFlags_Trus

I have a working program on my own board using a STM32G081KBU6. Debug using SWD and programming a release version works fine. As long as RDP remains at Level 0, I'm able to debug, erase and reprogram updates to the board.Usually for other ST MCU's that I've used, once I've finalized a release version, I usually do the bare minimum of changing RDP to Level 1 to prevent code readout. If I need to do a firmware update, I'll just regress RDP back to Level 0 and update to the new version.However, for this device, once I change the RDP to level 1, it seems like the SWD debug port is completely killed, and Cube programmer is unable to connect to the device anymore.I've tried all the connection and reset modes in Cube programmer, including powering the board on and trying to connect immediately. I'll only keep getting this error.I'm sure that I did not accidentally set RDP to Level 2, as the setting was done in Cube Programmer itself, and I've verified this on more than one board. Note al