STM32H503 OEMiROT: Unable to update new User application via USB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-25 03:53 AM - last edited on ‎2024-08-05 06:33 AM by Amel NASRI
Hello,
I am trying to run OEMiRoT on STM32H503 (NUCLEO-H503RB - MB1814B).
I followed the instructions specified: https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_OEMiRoT_on_STM32H503
In step 6 ("Flash new User application in CLOSED state") after choosing option 1 ("Start Bootloader") in the terminal emulator, I cannot connect the board via UART/USB to the STM32CubeProgrammer.
To connect the board via UART to the STM32CubeProgrammer I had to perform a reset (RESET button). However, I cannot connect the board to the STM32CubeProgrammer via USB (User USB connector - CN3). The board with the USB cable connected performs continuous restarts.
Solved! Go to Solution.
- Labels:
-
STM32 Security
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-01 12:44 AM
The problem is MPU, which prevents execution outside of OEMiROT. Disabling OEMIROT_MPU_PROTECTION in boot_hal_cfg.h allows the application to be updated via USB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-31 09:15 AM - edited ‎2024-07-31 09:18 AM
Hello @Nowy,
To resolve this issue, ensure the board is properly powered and verify the boot configuration settings (BOOT0 and BOOT1 pins). Make sure they are correctly set for USB bootloader mode.
Additionally, refer to:
- STM32CubeProgrammer User Manual for detailed instructions on using the STM32CubeProgrammer
- STM32H503xx devices Application Note and Reference Manual for information on pin configurations and boot modes.
I hope my answer has helped you. When your question is answered, please select this topic as solution that answered you, it will help others find that answer faster.
Thanks for your contribution.
Dor_RH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-01 12:36 AM
Hello @Dor_RH,
Thank You for your response. When using OEMiROT, the system bootloader is activated by software (OEMiROT) - jumping to the address of the system bootloader. The system bootloader activation method You mentioned refers to a hardware initiation (BOOT0 and BOOT1 pins).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-08-01 12:44 AM
The problem is MPU, which prevents execution outside of OEMiROT. Disabling OEMIROT_MPU_PROTECTION in boot_hal_cfg.h allows the application to be updated via USB.
![](/skins/images/9117C6B72C9F598A212AA17633C1CC28/responsive_peak/images/icon_anonymous_message.png)