Lpc2000

Thanks, Jayasooriah.

This however leaves me with more questions than before. I am not 
particularly interested in code read protection. However, my company 
designed a board using LPC2138/LPC2148 and I would like to know if I 
am likely to encounter problems when programming those boards, what 
kind of problem will they be and if can or can't I avoid them. We use 
plain UART0 interface for the one-time programming (occasionally, a 
firmware upgrade might kick in, also using the standard bootloader). 
We will be using the Philips utility for the task. If you have some 
info about that, please let me know.

Guille

--- In lpc2000@yahoogroups.com, Jayasooriah <jayasooriah@...> wrote:
>
> Hi Guile,
> 
> I found a number of things broken in the boot loader.  These have 
stopped 
> me (and from the posts here, a lot of others) from doing what they 
should 
> be able to do.
> 
> I stay away from being critical of design choices made by whoever 
> implemented the boot loader.  However when things are broken and 
this 
> interferes with operational aspects of the boot loader, I call it 
as I see it.
> 
> * The boot loader is critical to CRP but you can crash it at will 
even when 
> CRP is enabled.
> 
> * The flash algorithms in the boot loader are not implemented 
properly and 
> cause problems, including corruption boot loader itself.
> 
> The work-around is to replace the boot loader.  One can understand 
why 
> Philips objects to open source boot loader given product selection 
appears 
> to be based on what the boot loader does on startup.
> 
> Someone suggested I should give up on open source boot loader 
project and 
> just concentrate on providing custom boot loaders for people who 
need one 
> ... and I have taken this advice onboard.
> 
> Regards,
> 
> Jaya
> 
> >Message: 7
> >    Date: Tue, 21 Feb 2006 15:56:04 -0000
> >    From: "Guillermo Prandi" <yahoo.messenger@...>
> >Subject: Re: trashed 2148 bootloader
> >
> >Hi, Jayasooriah.
> >I too would like to hear about your findings.
> >If you'd just post your findings in cold objective words instead of
> >making misterious announces I doubt anybody would have anything to
> >criticize. Anyway, if they do, it's their problem. Please just post
> >what you've found (avoiding offending wording like "completely
> >broken", "piece of crap" and things like that) and any workarounds
> >you may have developed for it and I'll be really GLAD to read about
> >it.
> >
> >Guille
> 
> Send instant messages to your online friends 
http://au.messenger.yahoo.com
>