Yahoo Groups archive

Lpc2000

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

Message

Re: loading hex-es....(Tricky Situation)

2004-07-03 by Leighton Rowe

> Why is this tricky? Buffer four 128 byte blocks to get a 512 
> byte block. The only times you fail totally is if you do not 
> implement retries on a block error or the link fails 
> permanently. The ISP loader is then your saviour. If you can 
> afford to buffer all 8kb, then you have an extra level of 
> safety. The code we load into RAM to do this is about 3kb, uses 
> a few hundred bytes of RAM for stacks and so on, so even the 
> smallest LPC has 12k of RAM for buffering.
> 
> If you have a lot of RAM data you need to preserve, why not put 
> in spare Flash, perform the load, and restore the RAM?
> 
> As a caution, I suspect but have no proof that most Flash write 
> failures are down to poor power supplies.
> 

Fair enough...using multiple blocks is worth trying out then. With 
16k RAM buffering wouldn't be a problem at all. The ISP on my system 
is available only for the 1st load because of the hardware setup I 
got enclosed case & P0.14 as an LED driver). I'll have to get around 
ISPs with IAP routines for future downloads.

Thanks for the caution. 
Leighton

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.