Lpc2000

Hello Leighton,

The version of the bootloaders that do not have the improved timing
behavior is different for the LPC210x  and all other LPC2000 family
members in the 64-pin or 144-pin package. 

For devices in the 64-pin package like yours, the updated version
should be V1.63 or later. So, the bootloader you have could show the
problem, however, as mentioned in the Errata Sheet it affects up to
10% of the devices ot in other words, 90%+ of the devices will never
show this problem. 

The most critical event is an IAP call while running the device with
max speed at hot temperature (could be 10% failure rate). The least
critical running it at 10-12 MHz room temp (you will probably never
see the issue). 

Look at this Errata like a patch from some big company for their
Exploration software. In all likelyhood the devices that did not show
the problems in a given enviroment will continue to work fine in the
same enviroment. A change in enviroment, speed, temperature... could
however trigger the misbehavior. So, if you have the opportunity to
upgrade your bootloader version it is a good idea to do so, if not and
your environment does not change, no sweat.

Hope this helps to clarify the issue. 

Best regards, Robert

--- In lpc2000@yahoogroups.com, "Leighton Rowe" <leightonsrowe@y...>
wrote:
> Thanks Hugh,
> 
> I'm currently running IAP's on a PLL using lpc2129's (version 1.53 
> bootloader). So far, no problems yet.
> 
> I notice that the errata also applies to lpc's with bootloader 
> versions below 1.52. 
> 
> It is possible that lpc's (bootloader 1.52 and above) won't 
> experience this problem?
> 
> Leighton
>  
> 
> --- In lpc2000@yahoogroups.com, "Hugh O'Keeffe" <hugh.okeeffe@a...> 
> wrote:
> > Has everyone seen the LPC2000 errata at:
> >  
> > http://www.semiconductors.philips.com/acrobat/erratasheets/2105.pdf
> >  
> > Interestingly, there is a new version of the boot loader (the on-
> chip code
> > that resides in LPC2000) which is upgradeable using the Philips 
> ISP utility.
> > Details and files are here:
> >  
> > 
> http://www.semiconductors.philips.com/files/products/standard/microco
> ntrolle
> > rs/utilities/lpc2000_bl_update.zip
> >  
> >  
> > It seems that the IAP software (in the boot loader) has some 
> timing issues
> > resulting in a possible 1 in 10 flash programming failure, 
> particularly when
> > the PLL is enabled and running > 12MHz. Note: this effects all 
> methods of
> > flash programming (i.e. via UART using Philips ISP or JTAG using 
> Ashling
> > PathFinder or other Debuggers) as these all call the IAP routines. 
> >  
> > I have personally tried the upgrade and it works smoothly using 
> the Philips
> > ISP utility; I 'm looking at implementing a PathFinder script for 
> Ashling
> > users to allow updating via JTAG
> >  
> > HTH, Hugh @  <http://www.ashling.com/support/lpc2000/>
> > http://www.ashling.com/support/lpc2000/
> > 
> > 
> > [Non-text portions of this message have been removed]