If you want to modify the linker command file you need to modify the file located at the next path c:\Freescale\Freescale_MQX_4_0\mqx\source\bsp\<platform>\cw\*.lcf.

However I suggest you to use the TAD in order to verify the memory usage.

This plug-in gives you the possibility to check the memory block summary. Also you can optimize the stack usage of each task by configuring a stack size for each task in such a way that for example 95 % of a task’s stack would be used under full application load (worst case stack usage by your application).

The Lightweight memory blocks TAD view you show above shows that the memory pool, or heap, is less than half the available size in the K60F you are using. That device has 128KB of internal SRAM starting at address 0x1FFF_0000. But your TAD view shows the memory pool starting at 0x2000_1F30, which means the first 71KB of RAM is not being allocated to the memory pool. To compare, I loaded the web_hvac example for the cw10 project in MQX v4.0.2.2, and below is the TAD view I get. Notice the starting address is much lower, and the memory pool has 107KB available.

Looking at your linker command file, it appears to be set correctly. I would guess your application has a large amount of statically linked variables, which is using up over half of your RAM. You can review the .MAP file generated by the linker for your application to see the RAM used by the linker, and what is using it.