2023-05-10 11:57 AM
I have a Makefile project for an STM32L4 using FreeRTOS that I started with STM32CubeMx. I'm trying to enable one of the Thread-Safe strategies for FreeRTOS. I have tried both strategy #4 and #5, but both of them jump to the error handler on the `STM32_LOCK_BLOCK_IF_NULL_ARGUMENT` check in the `__retarget_lock_acquire_recursive` function in `newlib_lock_glue.c`
It doesn't seem like the locks are being initialized in the Makefile project. Is there any additional setup needed for thread safe implementations of a Makefile project? Otherwise, are there any additional flags that I need to send to gcc (or any of the other arm-none-eabi tools)?
Best regards,
Cory
2023-06-08 03:01 PM
For anyone else having this issue, it was resolved by upgrading my arm-none-eabi build tools from version 11.3 to version 12.2.
2023-06-09 08:39 AM
What does this mean? The newlib (nano) built differently in these versions?