Lpc2000

--- In lpc2000@yahoogroups.com, "lhaddix" <lhaddix@...> wrote:
> Well my stack was up there and it's much better now that stack
> top is at 0x40007FE0. Also you need to go into the .ld file and
> say the size of RAM is 0x7fe0 not 0x8000.
> 
> I'll bet this same problem has harpooned more than one programmer.

One client struggled with similar problem for weeks.  The system state
for watchdog recovery was stashed in this area.  Things worked fine
until IAP flash writes were called.

I think if you read the fine print in the user manuals you can work
out not to the 128 bytes at the top if you are using IAP, and 128
bytes at the bottom if you are using ISP.

> My remaining problem...
> 
> Now what I'm up against is that to do a read sector into ram/ modify/
> write back to flash sequence needs a full 32k for the large sectors.

One client had a field update constraint that requires flash updates
to be done by reading, modifying, then updating in one go without any
external input betweeen the erase of the sector and its rewrite.

They had to drop off the LPCs for this reason alone.

One wonders what purpose the designers had in mind for two 64K sectors
in the middle of the flash address space, flanked by 8 x 8K sectors on
either side.  This what they did for LPC2292.

Jaya