Thanks for all your inputs....
--
Dipti
________________________________
From:
msp430@... [mailto:
msp430@...] On Behalf
Of Arie de Muijnck
Sent: Thursday, July 24, 2008 1:45 AM
To:
msp430@...
Subject: Re: [msp430] Default value in EEPROM 24XX series
----- Original Message -----
From: <
dipti.panchal@... <mailto:dipti.panchal%40mt.com> >
To: <
msp430@... <mailto:msp430%40yahoogroups.com> >
Sent: Wednesday, July 23, 2008 09-24
Subject: RE: [msp430] Default value in EEPROM 24XX series
>
> In my application, based on this default value of the EEPROM, its
gonna
> perform some 'X' task. If in future this default value i.e. 0xFF would
> change then my application won't perform 'X' task. That is why I want
to
> be 100% sure whether it has to be 0xFF or not.
>
> Just a doubt, If it comes in erased state why datasheet does not
mention
> about it ??
> Dipti
> ________________________________
> From:
msp430@... <mailto:msp430%40yahoogroups.com>
[mailto:
msp430@... <mailto:msp430%40yahoogroups.com> ] On
Behalf
> Of Microbit_P43000
>
> Non-volatile memory like EEPROM always comes in the 'erased' state IOW
> 0xFF.
> So, this is normal in your EEPROM.
> AFAIK the only exception is large NAND flash, which can/will have bad
> sector
> markers.
And also: the very nice pin-compatible FRAM chips from Ramtron (100 ns
R/W
time, and almost infinite write operations allowed) just happen to come
with
a somewhat random 0x00 - 0xFF pattern.
Don't ever trust an initial state - program it explictly in production,
maybe using some special 'init' command in the application.
Arie de Muynck
[Non-text portions of this message have been removed]
