Re: Issues about USB composite device driver
- From: chris.aseltine@xxxxxxxxx
- Date: Wed, 5 Dec 2007 09:02:13 -0800 (PST)
On Dec 5, 9:30 am, "abei" <aboutwh...@xxxxxxx> wrote:
1. OS can't find the usbccgp.sys driver and install it automatically for our
device. I had searched the c: partition(my system disk) but can't find the
usbccgp.sys file. My Windows system is XP sp2. Why and where can I get the
usbccgp.sys file?
You need to get the USB\COMPOSITE compatible ID for your device and
then usbccgp.sys will be loaded automatically for your device. The
criteria for getting that compatible ID assigned to your PDO by usbhub
are here:
http://msdn2.microsoft.com/en-us/library/aa476434.aspx
2. I write a inf file and reference usbhub.sys to install driver for our
device. Yes! usbhub.sys can work!
usbhub.sys is not the generic parent in XP and later operating
systems, what you are doing is wrong (I am surprised by your report,
unless you switched to Win2k).
driver work well. But when I try to install driver for other interface, it
failed! The failed position is when I try to select configuration for USB
device with USBD_CreateConfigurationRequestEx and submit it to host driver.
Laterly, I found some useful information from DDK document. It said that
host driver can't support selecting configuration in composite USB device.
But the problem is that where can I get the interface information and pipe
information(ep address and pipe handle etc.) if I can't get those
information from selecting configuration?
The documentation says you can't select an *alternate* configuration
for your composite device. Meaning, the generic parent always selects
configuration zero on the device and you cannot change that.
Your client drivers obviously still need to send the SELECT_CONFIG URB
to get the pipe handles, etc., as you say, but usbccgp will feed those
to you directly. If the select config URB is failing, it's because
you're sending an invalid request to the generic parent driver.
So, I would check the values that you are passing down. Remember,
each child device will think it is talking to the "first" or "zero"
interface on your device, even though it is really second, third,
fourth, etc.
-Chris
.
- Follow-Ups:
- Re: Issues about USB composite device driver
- From: abei
- Re: Issues about USB composite device driver
- References:
- Issues about USB composite device driver
- From: abei
- Issues about USB composite device driver
- Prev by Date: Re: USB 2.0 ISO Allways at Beginning of SOF?
- Next by Date: Re: Occasional performance issue with EngModifySurface
- Previous by thread: Re: Issues about USB composite device driver
- Next by thread: Re: Issues about USB composite device driver
- Index(es):
Relevant Pages
|