Hi Claudio,
The uninitialised option was added at my request. The problem I had was
I declared an array to be filled in later at calibration time. However,
the initialisation behaviour wrote zeroes all over it. That would mean
doing a flash erase before it can be used, which is messy. Leaving the
erase area uninitialised seemed the appropriate way to handle this, and
is like the behaviour of other MSP430 tools.
Regards,
Steve
Claudio Grasso wrote:
I see. (It's a kind of "initialised later" rather than unitialised. :-) )
Thanks.
-----Mensaje original-----
De: daniel.n...@sigicom.se [mailto:daniel.n...@sigicom.se]
Enviado el: Lunes, 30 de Junio de 2003 12:52 p.m.
Para: mspgcc-users@lists.sourceforge.net
Asunto: [Mspgcc-users] Re: Linker question.
Claudio Grasso <c_gra...@crm.com.ar> writes:
> ¿In which case you use uninitialized data in ROM? I can't figure out
> situations when to use such feature.
You could initialise/store the actual data with an external tool
(e.g. in production) via the JTAG or BSL interfaces.
