This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VCOM on USB for NXP LPC18xx device

Hi,

I am working with a board that uses an NXP LPC1837 and want to get the USB VCOM port working.

I downloaded the example (RTOSTutorial_Ex10A-LPC18xx) for the LPC1857 and modified it to match my hardware. ( took out the graphics controller, changed the USART from 3 to 0. Pulled USB1 from the run time environment. Removed SPI. Changed the CPU to LPC1837. Updated the pinouts in RTE_Device.h... I am not using PPWR, PWR_FAULT, and INDI1 on this USB port. )

It compiles and downloads OK.
The calls to USBD_Initialize() and USBD_Connect() return usbOK.

However when I plug into a Windows 7 or Windows 10 PC nothing happens in device manager. Even if I have the driver wrong I should see something happen when I attach the board. I did go ahead and install the VCOM driver that was included with the example.

Anyway, I am using the same 12MHz crystal as on the demo board and the USB0 is pretty vanilla. Not much to customize.

I know my hardware works as I can install and run a Mass storage device demo that NXP makes available for USB0 on this part.

So I am not sure where to look next... is there an update to the VCOM example for this part? Did I forget something. I am using uVision 7.20.0.0. I have read most of the literature on CDC ATM and the example program... will spend the rest of today looking for something that I may have missed.

Thanks

Parents
  • Connect the VCOM device to a USB Analyzer or a Linux machine.
    Linux kernel will tell you the activities on USB Bus, more than what Windows will tell you.
    If Linux kernel doesn't see any activities of your VCOM device, then something wrong with your modification/configuration.

Reply
  • Connect the VCOM device to a USB Analyzer or a Linux machine.
    Linux kernel will tell you the activities on USB Bus, more than what Windows will tell you.
    If Linux kernel doesn't see any activities of your VCOM device, then something wrong with your modification/configuration.

Children
No data