nRF52840 FreeRTOS vTaskDelete assertion

[krisburch]

Hi there,

I am using the Nordic SDK 16.0.0 on an nRF52840 with FreeRTOS. I am quite familiar with using FreeRTOS, but hadn't needed to delete a task until recently. It seems that even when I create a simple task that deletes itself, I get an assertion on the vTaskDelete call. Is this a known issue or unsupported on this FreeRTOS port? I have referenced the FreeRTOS manual, and I am calling the function correctly. Nothing is done after the call to vTaskDelete, and it doesnt matter if I pass in the task handle or NULL (current task option), it still asserts. 

An example assertion is shown in the screenshot of the call stack. Thank you

[Vidar Berg]

Hi,

I was able to replicate the same assert here, but it's not clear to me why vPortFree() is called when it's not implemented, or what the correct solution to this is. I have to ask some of my colleagues who have more experience with Freertos and get back to you. 

Best regards,

Vidar

[Radoslaw Koppel]

The issue means that a memory manager chosen does not support memory freeing. Look into source/portable/MemMang and choose the memory manager that fits your needs the best.

[krisburch]

Thanks - unfortunately this is not quite enough info for me. If I would like to change over to using the heap_4.c model, is there anything other than removing heap_1.c from the project and instead linking heap_4.c that needs changed? Does the nRF52 FreeRTOS port support all of these heap_x.c options? Are there any FreeRTOSConfig.h options that need changed to use another memory model? Thank you

[Radoslaw Koppel]

Just remove heap_1.c and add heap_4.c file.

Configure the required heap size: configTOTAL_HEAP_SIZE - you probably have it done for heap_1.c already.

nRF52 supports any of the memory models. The only problematic one may be heap_3.c that relays on the compiler malloc and free functions - it may require additional configuration in the compiler environment that depends on the compiler used.