Main Config: ... have some not configured or wrong parameter values[FREERTOS]

I was running a project in STM32CubeIDE with 4 Tasks and it ran fine. Now I wanted to add a fifth task and after adding it and the oly thing I had changed was the Name (Task05 instead of myTask05) I got an alert box when saving the .ioc file:

grafik

I did not let generate code, instead went here to ask what to do. Where can I lookup, what’s run wrong? Here is some more information on version etc. :

I must say that the cause doesn’t seem to be the newly added Task, since, when I revert to the already working 4 tasks, I’m getting the same error/warning. So it must be something that had been introduced during the past 2 years when I didn’t touch the project but may have updated the STM32CubeIDE environment (1.19.0, that’s not the latest but I’m intentionally not with the latest because they dropped the CubeMX-Editor integration).

That sounds like a question for STMicro, and isn’t related to FreeRTOS.

Looking at the image you shared, it seems like an issue with the heap options:

Check those and see if you can find what is wrong there.

Thanks. Following your hint, I can reveal this:

Am I doing something mean? :slight_smile: Too little heap space?

Here another piece of information, FWIW:

Does increasing this fixes the error? Try changing it to 8192 (8KB) or 16384 (16KB) and see if this makes any difference.

It seems that the only place I can influence the Total Heap size is in this place where 5*1024 can be seen. This is the number of tasks (5) multiplied by a chunk, 1024 Bytes in this case. Increasing that by a factor of 2 (2048) doesn’t seem to reflect in the figure of 3160 or the chunks of 632 bytes shown for every task.

It won’t change the per task stack but the HEAP_STILL_REMAINING should no longer be 0 and the error should go away.

It won’t change the per task stack but the HEAP_STILL_REMAINING should no longer be 0 and the error should go away.

per task stack? You mean heap, right?

The space is allocated from heap but it is used for task stack. Does it fix your problem? If not, please share your complete code.

I changed to heap_3 model and the error flag goes away, but

HEAP_STILL_AVAILABE | -3160

while TOTAL_HEAP_SIZE | 5*1024

Those are not relevant when using heap_3. Glad that you are able to solve your problem.