AnsweredAssumed Answered

no_init in Coldfire CW6.3 LCF linker command file?

Question asked by Doug Paulsen on Jun 2, 2014
Latest reply on Jun 3, 2014 by Doug Paulsen

It seems like it should be straightforward, but I'm having difficultly understanding how to declare un-initialized RAM in LCF-type linker files. 


The use of the NO_INIT keyword in PRM linker files is discussed here and there in the forums and I've used it in other 8-bit CW projects, but my current interest is for Coldfire processors.  Under CW 6.3, these deploy a LCF linker command file.  I not been able to locate any documentation indicating the NO_INIT (or similar) keyword is valid there.


Obviously, there are a few variables which would be vary helpful to persist over a PIN reset.  The CW default is for all un-initialized variables to be cleared to zero, which I understand and appreciate.  This is my first Coldfire project, but other experiences with other micro/compiler combinations make declaring un-initialized variables quite easy.  One wonders why CW makes it so obtuse in the case of Coldfire processors.  Is there perhaps a hardware restraint?


Regardless, I would appreciate any comments/directions on setting up uninitialized segments in LCF files.