Lpc2000

--- In lpc2000@yahoogroups.com, "Leighton Rowe" <leightonsrowe@y...> 
wrote:
> > I am also having problems with the LPC2114.  It would 
consistently 
> > hang in "Copy RAM to Flash" and "Erase sectors", and when running 
> at 
> > cclk=60MHz, it would generate a Prefetch Abort after 29 seconds 
> (58 
> > seconds when running at cclk=30MHz).
> 
> Are you using the prepare sector command before u erase/write them? 
> What area in flash are u trying to write over? Just curious. 

I am using the prepare sectors command.  Without it, I get the 
expected error codes.
I am using sector 14 (1C000h-1DFFFh).

 
> > I contacted Promax, and after a while I learned that my chip 
might 
> > also be affected by the firmware bug, and that the problem mostly 
> > happens with cclk > ~11 MHz.  As a workaround, until I get new 
> chips, 
> > I now disable the PLL around the two IAP calls, running them at 
> > cclk=Fosc=10MHz.  It now seems to work.  This of course also 
> messes 
> > up the peripherals since pclk is also changed, but since all 
> > interrupts must be disabled (my interrupt handlers are in flash), 
> not 
> > much can work during IAP anyway.
> 
> As long as u call the IAP function passing in the frequency value 
of 
> the physical crystal, I think PLLs shouldn't matter...enabled or 
> disabled. I have my PLL enabled running @60Mhz now on a 12MHz Xtal, 
> and I can call IAP to write flash without trouble using 12Mhz as 
the 
> frequency value. 

The manual states that you should pass the cclk frequency, and not 
Fosc.  I would also have thought that the use of the PLL shouldn't 
matter as long as you passed the right frequency value, but my 
experiments show otherwise.  Try disabling the PLL.


> Interrupt events can mess the IAP process. Hopefully that's the 
only 
> firmware bug to worry about. 

It is not.  And I wouldn't call it a firmware (IAP) bug if the 
processor crashed because an un-disabled interrupt came during an IAP 
call and tried to execute out of flash.

Karl Olsen