heap2.c vs lwip's mem.c
Posted by pbeamtn
on November 6, 2008
I have ported the gcc ARM7 project with lwip to IAR, but I have discovered I have 2 different heaps, which seems inefficient. Lwip seems to have some status functions with their implementation, so I can determine how much of the heap is actually used.
My question is this, would FreeRTOS work if I substituted lwip's malloc() and free() instead of those provided by heap2.c? I'm feeling cramped for RAM, and I think this would help. I don't currently dynamically create and kill tasks, etc, so I believe FreeRTOS would just allocate memory at startup.
RE: heap2.c vs lwip's mem.c
Posted by Richard
on November 7, 2008
You can allocate the memory required by FreeRTOS.org any way you want - just provide implementations of pvPortMalloc() and vPortFree() that wrap the lwIP calls if that is your preferred method. The heaps that come with FreeRTOS.org are intended for demo purposes only as each embedded system has different requirements for memory management.
Take care about mutual exclusion and fragmentation though.
Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd..
See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.