Im a new to FreeRTOS and was going through the source code. I found the following line of code in the heap_1.c file line no. 98: /* Ensure the heap starts on a correctly aligned boundary. */ pucAlignedHeap = ( uint8_t * ) ( ( ( portPOINTER_SIZE_TYPE ) & ucHeap[ portBYTE_ALIGNMENT ] ) & ( ~( ( portP…

Yes you are correct. Initially I thought the first column of the tables in your initial reply was address of the each index of the same ucHeap array. Just now I realized that those values refer to the starting location of ucHeap array at different cases. Thanks.

I think you are right. If we only consider last 4-bits of the address, does the following correctly depict what you are trying to point: ucHeap: 0000 0001 0010 0011 0100 0101 0110 0111 1000 +---------+--------+--------+---------+--------+--------+--------+----…

[image] tonyjosi: There is some difference, the & ucHeap[ portBYTE_ALIGNMENT ] is same for each row as portBYTE_ALIGNMENT is a macro for each port defined as a constant number, eg. 8. This is not correct. The expression & ucHeap[ portBYTE_ALIGNMENT ] necessarily means ucHeap + portBYTE_ALIGNM…

Memory alignment in heap_1.c file

Kernel

rtel (Richard Barry) August 30, 2021, 8:38pm 2

Topic		Replies	Views
FreeRTOS Memory Management Kernel	3	1018	March 6, 2020
commit id 1825: Heap_x functions Kernel	1	218	February 17, 2013
portBYTE_ALIGNMENT in heap_4.c Kernel	4	1169	July 22, 2013
8 byte alignment Kernel	2	218	March 8, 2007
Questions on size_t data type usage and data alignment in heap_2.c in MemMang folder Kernel	2	210	August 15, 2015

Memory alignment in heap_1.c file

Related topics