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

Doron
Fri Jul 13 17:42:02 CDT 2007

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@gmail.com> wrote in message
news:1184289906.966483.291690@j4g2000prf.googlegroups.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
>

woodhead99
Sat Jul 14 22:06:53 CDT 2007

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

Alex
Mon Jul 16 04:30:17 CDT 2007

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

woodhead99
Mon Jul 16 10:31:13 CDT 2007

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...@gmail.com> 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
>

Maxim
Mon Jul 16 14:00:19 CDT 2007

> 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

woodhead99
Mon Jul 16 20:37:58 CDT 2007

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.