Yahoo Groups archive

Lpc2000

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

Message

Re: IAP questions (LPC2101) - conserving flash

2006-03-11 by noltstein

Hi Bob,

Thanks very much for the reply, Bob.  The information is very helpful.

Even though the current product, as spec'ed, mentions something like 4
updates max over the life of the product, it never occurred to me that
*if* we were go to 8...10... 15 updates (you know how these things
go), the reliability might not be as high.

Regarding the 2102, I'll "run it up the flagpole" so to speak... as
you can imagine, I always get push-back when I ask for anything!  In
fact I initially spec'ed the '03 (at least during design/development),
saying we can always drop down to the '01 or '02 for production if
everything will fit.... and man-o-man, you should have heard the wailing!

Have a nice weekend & thanks again for the help.

Dan

--- In lpc2000@yahoogroups.com, "lpc2100_fan" <lpc2100_fan@...> wrote:
>
> Hi, 
> 
> sounds all doable. However, I do remember that there was a max number
> of programming cycles mentioned without erasing in between. Because
> you can not dedicate a whole sector to the NV-data, there will be only
> a limited number of writes possible before the Flash writes become
> unreliable. If I remember it correctly it was something about 10
> writes before you need to erase the sector again.
> May be a LPC2102 is the better solution, you would have a whole sector
> available and also double the RAM to buffer a whole sector while
> erasing / re-writing. 
> 
> As you mentioned only a handful updates of this block during the
> lifetime, the 2101 might still be OK. 
> 
> Bob
> 
>

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.