[quote user="Hans M��ller"]The heap is defined with a size of 64 MBytes. When I use the linker command file as shown above, the resulting .bin file has a size of about 64 MBytes while the whole code itself should be less than 200 kBytes. So it seems the whole heap memory is integrated in resulting binary.[/quote]I have repeated that problem by modifying the StarterWare game example and adding the linker command file and the DMTimerIsr / setStandbyFreq declarations with pragmas.
However, I haven't yet worked a robust way of writing the linker command file to get the initialized sections adjacent in memory to reduce the .bin file size.[quote user="Hans M��ller"]
within the used linker command file, I get a warning
warning #10247-D: creating output section ".sysmem" without a SECTIONS specification
[/quote]The warning #10247-D means the linker is choosing an arbitrary section to place the .sysmem section. If the linker choses the DDR_MEM section the program will run. If the linker choses a different section the program may fail. i.e. that warning means the program may fail unless you check the memory map, and so isn't a robust solution.