Best way to stop volatile data being optimised out if variable unreferenced in code?

[CarlFST60L]

Hi,

(Using CW 7.1.2, 52259EVB + MQX)

What is the best way to stop (volatile) data being optimised out if unreferenced in the code?

More info; We have thousands of variables in a single file which is linked to the external NVM (MRAM). As we do software updates, some of these variables are no longer referenced, therefore optimised out. This puts the rest of our variables at different address's for these versions making software updates impossible. Basically, if the MAP still had the varibles that were not referenced, the software would address the correct locations. Manually mapping hte address is not an option.

I had a look through the help files and was unable to find a 'simple' solution.

Thanks,

Carl

[CrasyCat · Accepted solution]

Hello

Please check your ColdFire_Build_Tools_Reference.pdf manual.

There is a pragma force_active as well as linker directives FORCE_ACTIVE, KEEP_SECTION or FORCEFILES that can help you achieve what you are looking for.

CrasyCat