TechTalkz.com Logo Ask the Experts!

Go Back   TechTalkz.com Technology & Computer Troubleshooting Forums > Tech Support Archives > Microsoft > Microsoft Device Drivers

how to get USB device attachment information

Microsoft Device Drivers

 
 
Thread Tools Display Modes
Unread 04-12-2007, 12:51 AM   #1
woodhead99
Guest
 
Posts: n/a
how to get USB device attachment information

Hi, all
Is there a way to obtain some attachment information from a
usb function driver, such as the hub's hardware id, symbolic name,
connection port index , bus addresses of this device and the upstream
hub?
woodhead

 
Unread 04-12-2007, 12:55 AM   #2
Doron Holan [MSFT]
Guest
 
Posts: n/a
Re: how to get USB device attachment information

not generically, no. why do you need this information?

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"woodhead99" <woodhead99***********> wrote in message
news:1184289906.966483.291690@j4g2000prf.googlegro ups.com...
> Hi, all
> Is there a way to obtain some attachment information from a
> usb function driver, such as the hub's hardware id, symbolic name,
> connection port index , bus addresses of this device and the upstream
> hub?
> woodhead
>


 
Unread 04-12-2007, 12:56 AM   #3
woodhead99
Guest
 
Posts: n/a
Re: how to get USB device attachment information

On Jul 14, 6:42 am, "Doron Holan [MSFT]" <dor...@online.microsoft.com>
wrote:
> not generically, no. why do you need this information?
>

We used to rely on SetupDixxx and CM_xxx to enumerate our devices and
did some initializations to our devices in the mass production tool.
The devices are numbered in the order they are enumerated. But when
some devices fail or unplugged, most of the rest devices are re-
numbered, and thus the info on the screen will totally confuse the
operators.

in such a frequently changing environment, it is only the hubs that
won't change all the time. And I think the hub port index is the only
anchor that we can bind the device to in the device connection map. In
this way, the device connection map won't shuffle drastically on
sudden changes, and we can elegantly spot the offending device even
some connections change on the bus . We did try IOCTL_USB_XXX to find
some hub-device relation clues. But the info for the device is too
poor to help to obtain a device handle. In fact, my life will be easy
if USBD can return just one byte of device address, or port idx. Am i
greedy?

We also tried some nasty search in the registry, but the method seems
not quite reliable.
woodhead

 
Unread 04-12-2007, 01:00 AM   #4
Alex.Z
Guest
 
Posts: n/a
Re: how to get USB device attachment information

I just know the tool usbview, it can only tell the PID, VID, and
enpoint index when the
USB device plug in. But the info is not accurate sometimes.


woodhead99
> On Jul 14, 6:42 am, "Doron Holan [MSFT]" <dor...@online.microsoft.com>
> wrote:
> > not generically, no. why do you need this information?
> >

> We used to rely on SetupDixxx and CM_xxx to enumerate our devices and
> did some initializations to our devices in the mass production tool.
> The devices are numbered in the order they are enumerated. But when
> some devices fail or unplugged, most of the rest devices are re-
> numbered, and thus the info on the screen will totally confuse the
> operators.
>
> in such a frequently changing environment, it is only the hubs that
> won't change all the time. And I think the hub port index is the only
> anchor that we can bind the device to in the device connection map. In
> this way, the device connection map won't shuffle drastically on
> sudden changes, and we can elegantly spot the offending device even
> some connections change on the bus . We did try IOCTL_USB_XXX to find
> some hub-device relation clues. But the info for the device is too
> poor to help to obtain a device handle. In fact, my life will be easy
> if USBD can return just one byte of device address, or port idx. Am i
> greedy?
>
> We also tried some nasty search in the registry, but the method seems
> not quite reliable.
> woodhead


 
Unread 04-12-2007, 01:01 AM   #5
woodhead99
Guest
 
Posts: n/a
Re: how to get USB device attachment information

usbview helps a lot but still not enough.

I guess, somewhere in the pdo's device extension hide the mysterious
connection information.

woodhead

On 7 16 , 5 30 , "Alex.Z" <zhouxl...***********> wrote:
> I just know the tool usbview, it can only tell the PID, VID, and
> enpoint index when the
> USB device plug in. But the info is not accurate sometimes.
>
> woodhead99
>


 
Unread 04-12-2007, 01:02 AM   #6
Maxim S. Shatskih
Guest
 
Posts: n/a
Re: how to get USB device attachment information

> won't change all the time. And I think the hub port index is the only
> anchor that we can bind the device to in the device connection map.


Unique ID from the config descriptor is also OK. More or less easily available
from software, and can be easily written to the device using the marker pen :-)

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

 
Unread 04-12-2007, 01:06 AM   #7
woodhead99
Guest
 
Posts: n/a
Re: how to get USB device attachment information

On 7 17 , 3 00 , "Maxim S. Shatskih" <ma...@storagecraft.com> wrote:
> > won't change all the time. And I think the hub port index is the only
> > anchor that we can bind the device to in the device connection map.

>
> Unique ID from the config descriptor is also OK. More or less easily available
> from software, and can be easily written to the device using the marker pen :-)
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> ma...@storagecraft.comhttp://www.storagecraft.com


erm... the disadvantages are the serial number is too long for
workers to compare and the production process has to be modified and
becomes less efficient.

 
 

Thread Tools
Display Modes



< Home - Windows Help - MS Office Help - Hardware Support >


New To Site? Need Help?

All times are GMT. The time now is 09:28 PM.


vBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO
Copyright © 2005-2013, TechTalkz.com. All Rights Reserved - Privacy Policy
Valid XHTML 1.0 Transitional