> My doubt is where the implementation of lpc17_ usbinitialize() is
> located? I guess that it won't implemented yet, so what could be the
> start point to add support?

 

Right, I misunderstood.  Sorry, it is too early in the morning here.

 

That looks like some unused logic that came into the LPC17xx port.  The LPC17xx has no board-specific initialization (but it could if there were some special GPIOs).

 

It is really kind of funny... the function does not exist, but causes no problem because it is weakly defined.

 

The correct initalization point for USB is, of course, up_usbinitialize and that is called from arch/arm/src/common/up_initialize.c.  I have removed all references to lpc16_usbinitialize() from CVS.  I was tempted to leave it in because it might be needed someday for some board-specific initialization.

 

Greg