Other Parts Discussed in Thread: SYSBIOS
Tool/software: Code Composer Studio
phenomenon:
- In baremetal project, the linker can allocate space correctly for heap with the size that is specified in the argument "-heap HEAPSIZE". The size here can be set to as large as 0x7FFFFFF8, and I can see the allocation information in the .map file.
- In SYSBIOS project, when I make the default heap size >= 0x20000000 (512MiB) using codes like 'BIOS.heapSize = 0x20000000; I cannot find the allocation for heap space in the .map file of the final outputed executable. The used size of the DDR3 is 0x0.
- In SYSBIOS project, when I smaller the heap size, like 0x1FFFFFF8, then I can see the allocation of the heap section in the .map file.
- tried c6000 CGT 8.1.3 and 7.4.21, the same.
- tried SYSBIOS 6.45 / 6.50, the same.
I've check the links below:
In that link, it says this problem is caused by linker's bug that cannot allocate space for very large array.
Question:
- It's been 4 years, has the linker's bug been fixed?
- It looks like the linker can treat the argument '-heap' correctly, so is there any workaround for the SYSBIOS that it can make use of the argument '-heap' of the linker to allocate the default SYSBIOS heap? Because by default, SYSBIOS set the '-heap 0x0' in the generated linker.cmd file.