I 'm using a omapl138 custom board and developing its USB driver.
I wrote a inf referred to the winusb documents.
When I pluged the usb to the pc,new device could be found and asked for driver.
Unknown device item would be added to the device manage. Open its property detail tab,the device instance id is USB\VID_0000&PID_0000\5&920FCD3&0&2,and hardware ID is USB\UNKNOWN.
In the inf file, I set %DESCRIPTION% correspond to the device id as below.
When I specified this file as driver,it was an error the file didn't contain the hardware information.
I'm not sure whether the usb VID and PID is normal.
Any help will be appreciated.
I'm not entirely sure, but I would suggest that using a VID/PID of 0000/0000 is not a good idea, and I may have even had occasion when developing our company's USB driver where I inspected the USB VID/PID code as all zeroes when I was failing to register, or hadn't quite got the driver working as expected. I would suggest that you change the USB driver VID/PID to a non-zero value whilst you are developing your device, and obviously use your company's VID when it comes to releasing it into the general populace.
Do you know how to change the USB driver VID/PID to a non-zero value.I have read the user guide(Universal Serial Bus 2.0(USB 2.0) Controller),unfortunately didn't get any useful information.Would the usb register settings make the VID/PID value be 0?
The VID/PID are set in the device descriptor for the device and are not part of the hardware interface set up.
If you want a fully working implementation that works with DSP/BIOS and is proven to work reliably, including INF files and documentation, then the company I work for has a driver for the DSP that can provide 1, 2 or 3 emulated usb serial ports. We have a demo example driver to test it out if you are interested too.
We are working with the AM1808 (like the OMAPL-138 but no DSP). I found that for Windows XP the following driver inf file "works".
I have also found that on many systems, the Device Manager reports an error "Driver did not start (code 10)".
I found on another TI-E2E forum a suggested work around of placing a USB Hub between the PC and the target.
I tried this work around and proved that it works for me.
Windows 7 supports USB CDC (the actual standard that LINUX uses for USB network connections) so Windows 7 doesn't need a driver "*.inf" file, it can get the proper driver from Windows update.
That being said, not all installations of Windows 7 are the same. Windows 7 64-bit seems to work OK connecting to the LINUX target via USB, but Windows 7 32-bit does not. Thankfully, the USB Hub trick worked for me.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.