Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


Loading

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.

Paul


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.

Regards.


[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]


Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019

Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


Careers

FreeRTOS and other embedded software careers at AWS.



FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Renesas

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner