Lpc2000

Keil has the following copyright notice plastered everywhere in their 
USB code.

   This file is part of the uVision/ARM development tools.
   Copyright (c) 2005 Kiel Software. All rights reserved.

You don't even have permission to adapt the code for a commercial 
project using Keil tools. If you are using an evaluation version of 
their tools you don't even permission to commercialise your own code 
with your own copyright.

If you had permission to use and port their USB code then

1) You don't need a hardware analyser.
2) You don't need to throw out their excellent C structures.

In fact the C structures are essential for productive debugging.

There have been some comments about what needs to be done to port the 
code to GCC (assuming you have permission). These comments are really 
close to the mark.

I have no intention of letting myself become vulnerable to copyright 
issues. I see Keil as having made strategic decisions they intend to 
gain commercially from. I am not going to subvert that.

It is standard practice for companies to produce an SDK (Software 
Development Kit) for developers to make productive use of their product 
line. Developing from scratch using a data sheet is not commercially 
sane for this level of complexity. In effect Keil has done the work for 
Philips (if they allow you to adapt their examples). Of course if 
Philips got the message that their product sales will suffer without an 
independent SDK then they may rethink the absence.

John Heenan

--- In lpc2000@yahoogroups.com, Steve Franks <stevefranks@i...> wrote:
>
> >Again, I have kids to feed and a company to run.  Sorry.
> 
> I notice this keeps coming up.  Name your price, then.  Sounds like it
> may become a preffered option for those with no budget for hardware
> analysers.  Guess philips missed the proverbial boat somewhere in
> their usb implementation.  The rest of us'll stick to the ftdi &
> cp2101 chips, I guess.  Ethernet keeps looking better and better...
> 
> Steve
>