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] [May 2015 Threads]
Hi:
I use heap4.c for my system memory management. now, I found that system halt some times and printf it halt in heap4.c line 281 configASSERT( ( pxLink->xBlockSize & xBlockAllocatedBit ) != 0 ); it seems that the system try to free memory which is not actually allocated.
I wander to know in which case it will happen ? I check my code, pvPortMalloc and vPortFree are always implement in pair....
thank you in advanced.
Vincent
pvPortMalloc and vPortFree are always implement in pair...
That would be one explanation, calling vPortFree() too often.
Another explanation would be if you overwrite allocated memory. You asked for 1024 bytes and your code is using just a few more bytes.
You can also inspect pxLink->xBlockSize
and see if it has a reasonable value.
Anyway, it looks like your code is causing corruption of the heap space, somewhere.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.