public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* Data Reliability
@ 1999-12-07 18:54 Bob Canup
  0 siblings, 0 replies; 5+ messages in thread
From: Bob Canup @ 1999-12-07 18:54 UTC (permalink / raw)
  To: MTD

Is Vipin correct that there is a problem if there is a power loss when
writing to flash in embedded systems? Yes, no question.

There are 2 main ways of handling any problem. 1. Fix the problem once
it occurs. 2. Avoid the problem in the first place.

I have already given two ways to avoid the problem: use the flash in
Read Only mode, or have a power supply which signals impending power
loss and holds itself up long enough to allow an ordered shut down.

It has been my experience that it is generally better to avoid problems
than to attempt to fix them after they have occurred. Sometimes this is
not possible. For example: hard drives have to have ECC built into them
because it is virtually impossible to keep from having read errors.

I don't see any practical ways of fixing the problem of trashed flash
chips once it occurs. Does anyone else have any other suggestions as to
how to either avoid the problem or fix it once it happens?




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread
* RE: Data Reliability
@ 1999-12-07 19:43 Bjorn Eriksson
  1999-12-13 10:46 ` Kira Brown
  0 siblings, 1 reply; 5+ messages in thread
From: Bjorn Eriksson @ 1999-12-07 19:43 UTC (permalink / raw)
  To: 'Bob Canup', MTD


>I have already given two ways to avoid the problem: use the flash in
>Read Only mode, or have a power supply which signals impending power
>loss and holds itself up long enough to allow an ordered shut down.

Definitely my choice. Anyone else working on this?


//Björnen.




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread
* RE: Data Reliability
@ 1999-12-21 11:59 Bjorn Eriksson
  1999-12-20  8:37 ` Kira Brown
  0 siblings, 1 reply; 5+ messages in thread
From: Bjorn Eriksson @ 1999-12-21 11:59 UTC (permalink / raw)
  To: 'Kira Brown'; +Cc: MTD


>We've already done it.  Since we have not a lot running on the system, a
>shutdown -h takes less than a third of a second on a 99MHz AMD Elan SC410
>driving an 8Mbyte DoC2000.  We didn't write any special code other than a
>little thingy (technical term) that watches one of the processor GPIO pins
>for a falling edge and executes a shutdown if it sees one.  One of those
>funky 1F memory retention caps provides the power to do this.  (Do those
>things scare anyone else or is it just me?)

 Uhm, do you let your SC410 keep cruising at 99MHz? ISTR that these "funky 
memory retention caps" (FMRC:) holds up kinda bad under heavy load. I've 
got myself a seriously funky MRC that's either 3F or 700uF depending on how 
heavy a load I've got at the point of power failure.

P.s Do you know any venues for SC4xx designs/info/refs? Considering how 
many people are designing with this beast there preciously little noise on 
the Web. Right now I'm fighting GPCSA who stubbornly asserts his right to 
drive *ALL* the GPIO_CS's :-) D.s


//Björn Eriksson



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~1999-12-21 20:27 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-12-07 18:54 Data Reliability Bob Canup
  -- strict thread matches above, loose matches on Subject: below --
1999-12-07 19:43 Bjorn Eriksson
1999-12-13 10:46 ` Kira Brown
1999-12-21 11:59 Bjorn Eriksson
1999-12-20  8:37 ` Kira Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox