2021-05-12 11:50 AM
STM32CubeMX version 6.2.1, target STM3G474VE, CMSIS v2. If you create a time with "static" allocation, the "FreeRTOS Heap Usage" tab shows no heap usage by that timer. However, osTimerNew() always allocates the TimerCallback_t structure from the heap, even for "statically" allocated timers. So every timer uses at least 8 bytes of heap space.
I haven't done a thorough look at CMSIS v1, but at a quick glance it appears to correctly statically allocate all memory for a "static" timer. At least as long as the config param "memory allocation" is set to "dynamic/Static".
2021-05-19 09:49 AM
Hello @Bob S,
Please excuse the somewhat late reply and thank you for having reported.
I see your point and I will bring it up internally to be reviewed by our development team to see how we can address a modification.
I'll keep you posted with the updates.
Thank you for bringing this up.
Khouloud.
2021-05-20 10:16 AM
Thank you.