Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2100] Re: LPC2100 Flash Endurance // own test results

2003-12-02 by microbit

Thanks for the clarification Bob.
Flash endurance performance at high temperatures always seems to be an issue
where manufacturers just *don't* provide characterisation :-)

B regards,
Kris



----- Original Message -----
From: "lpc2100_fan" <lpc2100_fan@...>
To: <lpc2100@yahoogroups.com>
Sent: Wednesday, December 03, 2003 5:13 AM
Subject: [lpc2100] Re: LPC2100 Flash Endurance // own test results


> Hi,
>
> as usual, Philips specification is rather conservative. Under very
> simple lab conditions in an automated test we did not see any failures
> within 500,000 cycles. This was just done as a sanity check. So under
> "normal" conditions, which is that not all reprogramming cycles will
> happen at maximum temperature, the number of reprogramming cycles will
> be 1 or 2 orders of magnitude higher than the specified 10,000 cycles.
> I guess this is where the difference between the marketing statement
> "our device can do 1 Mio cycles" and the worst case specification "we
> guarantee (under worst case conditions) 10k cycles" comes into the game.
>
> Bob
>
> --- In lpc2100@yahoogroups.com, "microbit" <microbit@c...> wrote:
> > Thanks Amit !
> > Will check what version UM  I have.
> >
> > ----- Original Message -----
> > From: "Amit KB" <emailakb@y...>
> > To: <lpc2100@yahoogroups.com>
> > Sent: Wednesday, December 03, 2003 4:29 AM
> > Subject: Re: [lpc2100] LPC2100 Flash Endurance
> >
> >
> > > Hi Kris
> > >
> > > This information is added in the October version of the UM.
> > >
> > > 10,000 erase and write cycles are guaranteed per 512 byte line.
> > > Check it out.
> > >
> > > Bye
>
>
>       Yahoo! Groups Sponsor
>             ADVERTISEMENT
>
>
>
>
> To unsubscribe from this group, send an email to:
> lpc2100-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.