This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi
We're migrating from CCS4, compiler 6.x.x, to CCS 5.1, compiler 7.3.1. In CCS4, the project did not have a .sysmem section as we explicity avoid the use of malloc etc, favouring instead MEM_alloc to allow better control over memory allocation.
The same project migrated to CCS5, on a clean build, the linker will complain there is no .sysmem section and so it creates one by itself.
An obivous workaround is to simply create the section, but the question is rather why I need to do this in the first place? Is this a known issue in 7.3.1 (creating sections even though nothing has referenced the malloc set of functions)?
Thanks all
Richard
Added: the warning codes:
#10210-D creating ".sysmem" section with default size of 0x400; use
#10247-D creating output section ".sysmem" without a SECTIONS
and the target device is a TMS320C6472
Found it. We have an intermediate library build, and that was set to automatic runtime support library. rts64plus.lib was pulled in, and it in turn has a memory object (if unused, why pulled in?) that wants system memory for heap.
Thanks
Richard