Default value in EEPROM 24XX series

[diptipanchal]

We are using 24XX series EEPROM of microchip make. I have read the data from the EEPROM (without writing data to EEPROM), it always give as 0xFF. Atleast i have checked in 5 EEPROM.

In the datasheet, it is not mentioned what should be the default value?

Could anyone let me know what should be the default value in EEPROM.

-
Dipti

[microbit_virgin]

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.

HTH
-- Kris

-----Original Message-----
From: msp430@... [mailto:msp430@...] On Behalf Of
diptipanchal
Sent: Wednesday, 23 July 2008 4:46 PM
To: msp430@...
Subject: [msp430] Default value in EEPROM 24XX series


We are using 24XX series EEPROM of microchip make. I have read the data from
the EEPROM (without writing data to EEPROM), it always give as 0xFF. Atleast
i have checked in 5 EEPROM.

In the datasheet, it is not mentioned what should be the default value?

Could anyone let me know what should be the default value in EEPROM.

-
Dipti
--
View this message in context:
http://www.nabble.com/Default-value-in-EEPROM-24XX-series-tp18604798p1860479
8.html
Sent from the MSP430 - Discuss mailing list archive at Nabble.com.


------------------------------------

To unsubscribe from the msp430 group, send an email to:
msp430-unsubscribe@...

Yahoo! Groups Links

[diptipanchal]

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@...] On Behalf
Of Microbit_P43000
Sent: Wednesday, July 23, 2008 12:33 PM
To: msp430@...
Subject: RE: [msp430] Default value in EEPROM 24XX series

 

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.

HTH
-- Kris

-----Original Message-----
From: msp430@... <mailto:msp430%40yahoogroups.com>
[mailto:msp430@... <mailto:msp430%40yahoogroups.com> ] On
Behalf Of
diptipanchal
Sent: Wednesday, 23 July 2008 4:46 PM
To: msp430@... <mailto:msp430%40yahoogroups.com>
Subject: [msp430] Default value in EEPROM 24XX series

We are using 24XX series EEPROM of microchip make. I have read the data
from
the EEPROM (without writing data to EEPROM), it always give as 0xFF.
Atleast
i have checked in 5 EEPROM.

In the datasheet, it is not mentioned what should be the default value?

Could anyone let me know what should be the default value in EEPROM.

-
Dipti
--
View this message in context:
http://www.nabble.com/Default-value-in-EEPROM-24XX-series-tp18604798p186
0479
<http://www.nabble.com/Default-value-in-EEPROM-24XX-series-tp18604798p18
60479>
8.html
Sent from the MSP430 - Discuss mailing list archive at Nabble.com.

------------------------------------

To unsubscribe from the msp430 group, send an email to:
msp430-unsubscribe@... <mailto:msp430-unsubscribe%40egroups.com>


Yahoo! Groups Links

 



[Non-text portions of this message have been removed]

[Ian Okey]

2008/7/23 <dipti.panchal@...>:

> 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
>
>
>
> It does not mention it because, while it is normal for the device to be in

its erased state it is not normally guaranteed, so relying on this for your
device operation is a somewhat risky strategy.  If you must have some magic
value in a given location then it is up to you to put it there.

Ian


[Non-text portions of this message have been removed]

[Arie de Muijnck]

----- Original Message -----
From: <dipti.panchal@...>
To: <msp430@...>
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@...] 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

[diptipanchal]

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]

[microbit_virgin]

Good point. I would rely on a unique signature, like 4-6 bytes long.
At reset, check for that signature in EEPROM - if not there, it's a default
device. I always use this principle in RAM to work out whether an MCU is in
cold or warm start.

B rgds
Kris

-----Original Message-----
From: msp430@... [mailto:msp430@...] On Behalf Of
Arie de Muijnck
Sent: Thursday, 24 July 2008 6:15 AM
To: msp430@...
Subject: Re: [msp430] Default value in EEPROM 24XX series


----- Original Message -----
From: <dipti.panchal@...>
To: <msp430@...>
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@...] 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