STM32WB Application recieves hardfault keyword after TL_Enable() is called

EIvan.2 · ‎2022-01-29

In a project with STM32WB55RG + FreeRTOS, calling TL_Enable() often results in a Hardfault with the keyword @SRAM2A_BASE: 0x1170FD0F (picture).

Hardfault is repeated regularly until you make a small change in the code in any part of the program. After making a random change, with some probability, the stack starts working normally every time it is started. Even one line of code in any part of the program can have an impact on startup. Tried all possible options.

Code generated with CubeMx. Interrupt handlers have been added. Any thoughts on diagnosing the problem?

Remy ISSALYS · ‎2022-02-02

Hello,

Can you give us your stack version please ?

Thanks,

remy

EIvan.2 · ‎2022-02-02

Hi,

I am using version 13.0 (stm32wb5x_BLE_Stack_full_fw).

Two days ago I changed the HAL-timer from TIM16 to TIM17, also with the help of the CubeMX. Since then, the situation has not repeated.

Remy ISSALYS · ‎2022-02-14

Hello,

When you have Hardfault issue, did you use TIM1 or not ? And can you check flash status when CPU2 is in hardfault ?

Thanks,

Remy