[quote user="AartiG"]
To achieve this, you would need to relink the application but this time, in the linker command file, all sections EXCEPT this special section should be marked as NOLOAD.
[/quote]
To add to my previous reply, the key here is that the second link step should be identical to the first except for the difference in the linker command file with regard to which section is marked NOLOAD. Everything else should be identical, (ie) object files, linker options, order of files passed to the linker etc.
Although using different build configurations to generate the two builds (as I suggested in my previous post) should work, a safer way to ensure that the exact same object files are being used for the second link, is to perform the second link step on a command line or via a post build step in CCS. So you can perform the first build in CCS, then copy the linker step as it appears in the CCS build console and use that on command line to perform the second link, with the only change being the linker command file. Note that everything else should be exactly the same and in the same order. Alternately you could add the command line directly as a post build step in CCS or add it to a batch file and invoke the batch file as a post build step. More on post build steps here: http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Pre_and_Post_Build_Steps
Hope this helps you achieve what you were looking for.