2023-10-13 03:17 AM
Hello Team
We are using ST's T-FM environment for STM32U585 MCU. We have observed one strange behaviour while using the non secure callable function in the non secure code. The problem is such that till the call to "TX_PORT_SPECIFIC_PRE_INITIALIZATION"(in the Azure RTOS init function) I am able to execute a function declared in the secure_nsc.c(secure gateway), but if I try to call this function after TX_PORT_SPECIFIC_PRE_INITIALIZATION, I am getting hardfault_error(). The hardware fault analysis shows the following results:
Please help us out in the possible causes and solution for the issue
(in the non secure code)
Flow of the APIs:
MX_ThreadX_Init()
tx_kernel_enter()
_tx_initialize_kernel_enter()
TX_PORT_SPECIFIC_PRE_INITIALIZATION
2023-12-14 02:12 AM
I am also looking answer to exactly same question. Need quick support from ST.
2023-12-15 05:51 AM
2024-01-15 02:18 AM
Hello,
In case your question concerns specifically Azure RTOS Integration in TF-M Environment you can have a look at this:
Azure RTOS Integration in TF-M Environment - B-U58... - STMicroelectronics Community
Guillaume