AnsweredAssumed Answered

pvPortMalloc failes after the scheduler is started

Question asked by yuliap on Aug 26, 2015
Latest reply on Aug 26, 2015 by Erich Styger

Hi,

I have trouble with the pvPortMalloc function. My project contains the FreeRTOS component from Erich Styger and lwip from KSDK. I set the momery scheme to 3 in FreeRTOS and define a large heap in the CPU component. Large enough for all the memory allocations I need. The process initialization goes as expected, the memory is allocated without errors. When the scheduler is started a thread calls netconn_new, which in the end calls pvPortMalloc. The return value is zero. If I move the netconn_new call to before the scheduler, the memory allocation returns a sensible value. It looks almost like when the scheduler is started, the malloc is not functioning any more. Does anyone have any ideas about what it could be? My HW is custom..

 

Regards,

Julia

Outcomes