Hello everyone,
I’m working on a project with Secure Manager on STM32H573IIK3Q using the STM32H573-DK board. I have followed the official tutorial from ST to make my application compatible with Secure Manager:
https://wiki.st.com/stm32mcu/wiki/Security:How_to_make_your_application_compatible_with_Secure_Manager
So far the system works fine — I can blink LEDs and run a basic non-secure application without issues.
However, as soon as I integrate FreeRTOS and switch the HAL timebase source from SysTick to TIM7, the program immediately stops and goes into the BusFault_Handler() after TIM7 interrupt.
Steps to reproduce:
1) Follow the Secure Manager tutorial and set up SM provisioning
2) Confirm basic GPIO/LED blinking works
3) Add FreeRTOS middleware (no other changes)
4) In Clock Configuration → SYS, change Timebase Source to TIM7
5) Build and flash — program immediately hits BusFault_Handler()
Environment / versions
STM32CubeMX: 6.17.0
STM32Cube FW_H5: V1.6.0
STM32CubeIDE: 2.1.0
Thank you for any help.
Hello @Jocelyn RICARD ,
Thank you for your feedback.
I wanted to double-check everything and go through the steps again, but I found something interesting: after reconnecting my board, the application runs without any problems. However, when I debug it with ST-Link, it crashes again like before.
To summarize:
MyApp with FreeRTOS — works when running on the board normally
MyApp with Secure Manager + FreeRTOS/TIM7 — works only when not debugging
MyApp with Secure Manager, without FreeRTOS and TIM7 — works even when debugging
So maybe this situation gives a hint about where the issue is? I also attach screen of the Fault Analyzer.
