nRF52840 FreeRTOS vTaskDelete assertion

RE: nRF52840 FreeRTOS vTaskDelete assertion

Radoslaw Koppel — Fri, 06 Nov 2020 14:54:21 GMT

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.

RE: nRF52840 FreeRTOS vTaskDelete assertion

krisburch — Thu, 05 Nov 2020 16:23:45 GMT

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

RE: nRF52840 FreeRTOS vTaskDelete assertion

Radoslaw Koppel — Thu, 05 Nov 2020 07:56:15 GMT

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.

RE: nRF52840 FreeRTOS vTaskDelete assertion

Vidar Berg — Wed, 04 Nov 2020 15:06:21 GMT

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