Lpc2000

--- In lpc2000@yahoogroups.com, "unity0724" <unity0724@...> wrote:
>
> Umm.....Some questions, don't mind:
> - How do I know there is no Trojan Horse inside??
> - How do I know your code does not over-cooked my flash??
>   or make it raw/medium when I actually ordered well done??
> - How do I know your code could handle Exception Interrupt 
>   properly?? without crashing??
> - How do I know your code does not have CSI bugs??
> - How do I know if you could understand the watchdog hardware
>   in detail and handle it properly upon a watchdog reset event??
> - How do I know if I will not have CRP problem, after installing
>   your that boot loader?? And What's that "CRP feature to extent
>   supported by hardware"??
> - How do I know if you are able to get Philips to ship with your
>   bootloader?? Or I need to re-load everychip? Or you could 
>   provide free bootloader upgrade every chip programming 
>   services??
> - How do I know if you are Philips Certified/Appointed consultant??
> Thanks!!
> 

To add to the list:

- why should I break the most basic rule of design and rely on 
something that in turn relies on undocumented and unsupported 
features from a manufacturer?

- what do I do when I'm in production and Philips supply a batch of 
parts that have some change in them that renders your boot-loader or 
some feature of it ineffective? 

I assume that one of the reasons for Philips implementing the boot-
loader the way it is is that it gives them the flexibility to change 
the hardware without changing the documented interface to it.

Brendan