FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [November 2008 Threads] heap2.c vs lwip's mem.cPosted 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.
Paul
RE: heap2.c vs lwip's mem.cPosted 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.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|