hi all,
till date I could never get USB debugging to work for me, can someone please
let me know the steps and the hardware required to get this going.
I havethe netchip usb 2.0 debug cable and hardware with me…
–
- amitr0
I can’t say that I’ve ever tried using the usb transport, so this is just my understanding:
-
The target has to be running Vista +
-
You must connect the cable to the ‘usb debugging port’ (0) on the target. As I understand it, there’s no way to tell in software which port is the right one, not all USB EHCI controllers will necessarily have one, and even on those that do, it may not be externally accessible.
Is there some reason why you can’t use 1394 or serial?
mm
the platform doesnt have pcmcia, firewire or com ports and we need to debug
On Tue, Dec 1, 2009 at 7:22 PM, wrote:
> I can’t say that I’ve ever tried using the usb transport, so this is just
> my understanding:
>
> 1. The target has to be running Vista +
>
> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
> target. As I understand it, there’s no way to tell in software which port
> is the right one, not all USB EHCI controllers will necessarily have one,
> and even on those that do, it may not be externally accessible.
>
> Is there some reason why you can’t use 1394 or serial?
>
>
> mm
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
- amitr0
has anyone tried a usb to 1394 converter to debug???
On Tue, Dec 1, 2009 at 7:24 PM, amitr0 wrote:
> the platform doesnt have pcmcia, firewire or com ports and we need to debug
>
>
>
>
>
> On Tue, Dec 1, 2009 at 7:22 PM, wrote:
>
>> I can’t say that I’ve ever tried using the usb transport, so this is just
>> my understanding:
>>
>> 1. The target has to be running Vista +
>>
>> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
>> target. As I understand it, there’s no way to tell in software which port
>> is the right one, not all USB EHCI controllers will necessarily have one,
>> and even on those that do, it may not be externally accessible.
>>
>> Is there some reason why you can’t use 1394 or serial?
>>
>>
>> mm
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> –
>
> - amitr0
>
–
- amitr0
Won’t work on the target side. The kernel can only talk to “native” fw
cards.
Is it a laptop?
Jim
On Tue, Dec 1, 2009 at 12:09 PM, amitr0 wrote:
> has anyone tried a usb to 1394 converter to debug???
>
>
>
> On Tue, Dec 1, 2009 at 7:24 PM, amitr0 wrote:
>
>> the platform doesnt have pcmcia, firewire or com ports and we need to
>> debug
>>
>>
>>
>>
>> On Tue, Dec 1, 2009 at 7:22 PM, wrote:
>>
>>> I can’t say that I’ve ever tried using the usb transport, so this is just
>>> my understanding:
>>>
>>> 1. The target has to be running Vista +
>>>
>>> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
>>> target. As I understand it, there’s no way to tell in software which port
>>> is the right one, not all USB EHCI controllers will necessarily have one,
>>> and even on those that do, it may not be externally accessible.
>>>
>>> Is there some reason why you can’t use 1394 or serial?
>>>
>>>
>>> mm
>>>
>>> —
>>> WINDBG is sponsored by OSR
>>>
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>>
>>
>>
>>
>> –
>>
>> - amitr0
>>
>
>
>
> –
>
> - amitr0
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
The USB port 0 can be located with usbview tool from the WDK.
Please search the newsgroups; the USB setup had been discussed several times
(with mixed results)
Many laptop platforms do have a hidden com port connector, or on their
docking station.
–pa
“amitr0” wrote in message news:xxxxx@windbg…
> the platform doesnt have pcmcia, firewire or com ports and we need to
> debug
>
>
>
> On Tue, Dec 1, 2009 at 7:22 PM, wrote:
>
>> I can’t say that I’ve ever tried using the usb transport, so this is just
>> my understanding:
>>
>> 1. The target has to be running Vista +
>>
>> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
>> target. As I understand it, there’s no way to tell in software which
>> port
>> is the right one, not all USB EHCI controllers will necessarily have one,
>> and even on those that do, it may not be externally accessible.
>>
>> Is there some reason why you can’t use 1394 or serial?
>>
>>
>> mm
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> –
>
> - amitr0
>
Actually I suspect it will not work on the host side, since Windbg installs
it own driver for the 1394 card.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Jim Donelson” wrote in message news:xxxxx@windbg…
> Won’t work on the target side. The kernel can only talk to “native” fw
> cards.
> Is it a laptop?
> Jim
>
>
> On Tue, Dec 1, 2009 at 12:09 PM, amitr0 wrote:
>
>> has anyone tried a usb to 1394 converter to debug???
>>
>>
>>
>> On Tue, Dec 1, 2009 at 7:24 PM, amitr0 wrote:
>>
>>> the platform doesnt have pcmcia, firewire or com ports and we need to
>>> debug
>>>
>>>
>>>
>>>
>>> On Tue, Dec 1, 2009 at 7:22 PM, wrote:
>>>
>>>> I can’t say that I’ve ever tried using the usb transport, so this is
>>>> just
>>>> my understanding:
>>>>
>>>> 1. The target has to be running Vista +
>>>>
>>>> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
>>>> target. As I understand it, there’s no way to tell in software which
>>>> port
>>>> is the right one, not all USB EHCI controllers will necessarily have
>>>> one,
>>>> and even on those that do, it may not be externally accessible.
>>>>
>>>> Is there some reason why you can’t use 1394 or serial?
>>>>
>>>>
>>>> mm
>>>>
>>>> —
>>>> WINDBG is sponsored by OSR
>>>>
>>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>>> http://www.osr.com/seminars
>>>>
>>>> To unsubscribe, visit the List Server section of OSR Online at
>>>> http://www.osronline.com/page.cfm?name=ListServer
>>>>
>>>
>>>
>>>
>>> –
>>>
>>> - amitr0
>>>
>>
>>
>>
>> –
>>
>> - amitr0
>> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging
>> and
>> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
>> the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4652 (20091201)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4652 (20091201)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
You mean there isn’t even a header plug somewhere on the motherboard that
might provide a serial port? Or a masked area shaped like a header plug that
with a few minutes and a soldering iron you could GET a serial port? The MB
doesn’t have a 16550 ANYWHERE in it’s real estate?
Can you change platforms?
Gary G. Little
H (952) 223-1349
C (952) 454-4629
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of amitr0
Sent: Tuesday, December 01, 2009 7:54 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] USB debug
the platform doesnt have pcmcia, firewire or com ports and we need to debug
On Tue, Dec 1, 2009 at 7:22 PM, wrote:
I can’t say that I’ve ever tried using the usb transport, so this is just my
understanding:
1. The target has to be running Vista +
2. You must connect the cable to the ‘usb debugging port’ (0) on the
target. As I understand it, there’s no way to tell in software which port
is the right one, not all USB EHCI controllers will necessarily have one,
and even on those that do, it may not be externally accessible.
Is there some reason why you can’t use 1394 or serial?
mm
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
–
- amitr0
— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Information from ESET Smart Security, version of virus signature
database 4650 (20091130)
The message was checked by ESET Smart Security.
http://www.eset.com
“Gary G. Little” wrote in message
news:xxxxx@windbg…
> You mean there isn’t even a header plug somewhere on the motherboard that
> might provide a serial port? Or a masked area shaped like a header plug
> that
> with a few minutes and a soldering iron you could GET a serial port? The
> MB
> doesn’t have a 16550 ANYWHERE in it’s real estate?
Even no soldering needed - now you can buy a ready TTL to RS232 converter.
Seen these in several web stores in UK.
–pa
i am not optimistic abt that, it is a customer laptop, they might not want
us to open it and mess with it, putting back a laptop once opened proves to
be a more difficult task at times than kernel debugging 
we are trying to request the customer to help us, since they are a big OEM,
they would definietely have their reference boards, it is just that how much
they want to help us…
On Wed, Dec 2, 2009 at 5:44 AM, Pavel A. wrote:
>
> “Gary G. Little” wrote in message
> news:xxxxx@windbg…
>
> You mean there isn’t even a header plug somewhere on the motherboard that
>> might provide a serial port? Or a masked area shaped like a header plug
>> that
>> with a few minutes and a soldering iron you could GET a serial port? The
>> MB
>> doesn’t have a 16550 ANYWHERE in it’s real estate?
>>
>
> Even no soldering needed - now you can buy a ready TTL to RS232 converter.
> Seen these in several web stores in UK.
>
> --pa
>
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
- amitr0
pavel,
how do i figure out from outside the cabinet, which port is port 0? even
with usbview???
On Tue, Dec 1, 2009 at 10:53 PM, Pavel A. wrote:
> The USB port 0 can be located with usbview tool from the WDK.
> Please search the newsgroups; the USB setup had been discussed several
> times
> (with mixed results)
>
> Many laptop platforms do have a hidden com port connector, or on their
> docking station.
>
> --pa
>
>
> “amitr0” wrote in message news:xxxxx@windbg…
>
>> the platform doesnt have pcmcia, firewire or com ports and we need to
>> debug
>>
>>
>>
>> On Tue, Dec 1, 2009 at 7:22 PM, wrote:
>>
>> I can’t say that I’ve ever tried using the usb transport, so this is just
>>> my understanding:
>>>
>>> 1. The target has to be running Vista +
>>>
>>> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
>>> target. As I understand it, there’s no way to tell in software which
>>> port
>>> is the right one, not all USB EHCI controllers will necessarily have one,
>>> and even on those that do, it may not be externally accessible.
>>>
>>> Is there some reason why you can’t use 1394 or serial?
>>>
>>>
>>> mm
>>>
>>> —
>>> WINDBG is sponsored by OSR
>>>
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>>
>>>
>>
>>
>> –
>>
>> - amitr0
>>
>>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
- amitr0
Start plugging the same device (like a mouse) into each port, looking at usbview after each plugin to see how the physical port maps to the logical number
d
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of amitr0
Sent: Wednesday, December 02, 2009 12:48 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] USB debug
pavel,
how do i figure out from outside the cabinet, which port is port 0? even with usbview???
On Tue, Dec 1, 2009 at 10:53 PM, Pavel A. > wrote:
The USB port 0 can be located with usbview tool from the WDK.
Please search the newsgroups; the USB setup had been discussed several times
(with mixed results)
Many laptop platforms do have a hidden com port connector, or on their docking station.
–pa
“amitr0” > wrote in message news:xxxxx@windbg…
the platform doesnt have pcmcia, firewire or com ports and we need to debug
On Tue, Dec 1, 2009 at 7:22 PM, > wrote:
I can’t say that I’ve ever tried using the usb transport, so this is just
my understanding:
1. The target has to be running Vista +
2. You must connect the cable to the ‘usb debugging port’ (0) on the
target. As I understand it, there’s no way to tell in software which port
is the right one, not all USB EHCI controllers will necessarily have one,
and even on those that do, it may not be externally accessible.
Is there some reason why you can’t use 1394 or serial?
mm
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
–
- amitr0
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
–
- amitr0
— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I don’t know why, but pluggin in a device doesn’t refresh on my laptop.
that apart, if i have multiple usb host controllers (ICH9 based) each having
port1-n, which one should be it?
there is no port 0 anywhere…
On Wed, Dec 2, 2009 at 2:23 PM, Doron Holan wrote:
> Start plugging the same device (like a mouse) into each port, looking at
> usbview after each plugin to see how the physical port maps to the logical
> number
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *amitr0
> Sent: Wednesday, December 02, 2009 12:48 AM
>
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] USB debug
>
>
>
> pavel,
>
>
>
> how do i figure out from outside the cabinet, which port is port 0? even
> with usbview???
>
>
>
>
>
> On Tue, Dec 1, 2009 at 10:53 PM, Pavel A. wrote:
>
> The USB port 0 can be located with usbview tool from the WDK.
> Please search the newsgroups; the USB setup had been discussed several
> times
> (with mixed results)
>
> Many laptop platforms do have a hidden com port connector, or on their
> docking station.
>
> --pa
>
>
> “amitr0” wrote in message news:xxxxx@windbg…
>
> the platform doesnt have pcmcia, firewire or com ports and we need to debug
>
>
>
> On Tue, Dec 1, 2009 at 7:22 PM, wrote:
>
> I can’t say that I’ve ever tried using the usb transport, so this is just
> my understanding:
>
> 1. The target has to be running Vista +
>
> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
> target. As I understand it, there’s no way to tell in software which port
> is the right one, not all USB EHCI controllers will necessarily have one,
> and even on those that do, it may not be externally accessible.
>
> Is there some reason why you can’t use 1394 or serial?
>
>
> mm
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> –
>
> - amitr0
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
> –
>
> - amitr0
>
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
- amitr0
Port 1 in USB view is the port 0 you want. USBview does not refresh automatically on device plug in. Hit F5 to force a refresh each time you plug the device into a different port.
You should make sure you use a USB2 device when plugging into the ports, so that it shows up on the USB2 controller not the USB1 controller.
Easiest way IMO, is to use a USB flash drive.
Joe.
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of amitr0
Sent: Wednesday, December 02, 2009 1:01 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] USB debug
I don’t know why, but pluggin in a device doesn’t refresh on my laptop.
that apart, if i have multiple usb host controllers (ICH9 based) each having port1-n, which one should be it?
there is no port 0 anywhere…
On Wed, Dec 2, 2009 at 2:23 PM, Doron Holan > wrote:
Start plugging the same device (like a mouse) into each port, looking at usbview after each plugin to see how the physical port maps to the logical number
d
From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.commailto:xxxxx] On Behalf Of amitr0
Sent: Wednesday, December 02, 2009 12:48 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] USB debug
pavel,
how do i figure out from outside the cabinet, which port is port 0? even with usbview???
On Tue, Dec 1, 2009 at 10:53 PM, Pavel A. > wrote:
The USB port 0 can be located with usbview tool from the WDK.
Please search the newsgroups; the USB setup had been discussed several times
(with mixed results)
Many laptop platforms do have a hidden com port connector, or on their docking station.
–pa
“amitr0” > wrote in message news:xxxxx@windbg…
the platform doesnt have pcmcia, firewire or com ports and we need to debug
On Tue, Dec 1, 2009 at 7:22 PM, > wrote:
I can’t say that I’ve ever tried using the usb transport, so this is just
my understanding:
1. The target has to be running Vista +
2. You must connect the cable to the ‘usb debugging port’ (0) on the
target. As I understand it, there’s no way to tell in software which port
is the right one, not all USB EHCI controllers will necessarily have one,
and even on those that do, it may not be externally accessible.
Is there some reason why you can’t use 1394 or serial?
mm
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
–
- amitr0
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
–
- amitr0
— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
–
- amitr0
— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>
If memory serves, there was a boot parameter in Vista that allows to
select the USB controller, in case there are several of them, like this:
bcdedit -set {current} loadoptions busparams=0.1d.7
Does it still exist in win7?
–pa
“Joe Ballantyne” wrote in message
news:xxxxx@windbg…
> Port 1 in USB view is the port 0 you want. USBview does not refresh
> automatically on device plug in. Hit F5 to force a refresh each time you
> plug the device into a different port.
>
> You should make sure you use a USB2 device when plugging into the ports,
> so that it shows up on the USB2 controller not the USB1 controller.
>
> Easiest way IMO, is to use a USB flash drive.
>
> Joe.
>
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of amitr0
> Sent: Wednesday, December 02, 2009 1:01 AM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] USB debug
>
> I don’t know why, but pluggin in a device doesn’t refresh on my laptop.
>
> that apart, if i have multiple usb host controllers (ICH9 based) each
> having port1-n, which one should be it?
>
> there is no port 0 anywhere…
>
>
>
> On Wed, Dec 2, 2009 at 2:23 PM, Doron Holan
> > wrote:
> Start plugging the same device (like a mouse) into each port, looking at
> usbview after each plugin to see how the physical port maps to the logical
> number
>
> d
>
> From:
> xxxxx@lists.osr.commailto:xxxxx
> [mailto:xxxxx@lists.osr.commailto:xxxxx]
> On Behalf Of amitr0
> Sent: Wednesday, December 02, 2009 12:48 AM
>
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] USB debug
>
> pavel,
>
> how do i figure out from outside the cabinet, which port is port 0? even
> with usbview???
>
>
> On Tue, Dec 1, 2009 at 10:53 PM, Pavel A.
> > wrote:
> The USB port 0 can be located with usbview tool from the WDK.
> Please search the newsgroups; the USB setup had been discussed several
> times
> (with mixed results)
>
> Many laptop platforms do have a hidden com port connector, or on their
> docking station.
>
> --pa
>
>
> “amitr0” > wrote in
> message news:xxxxx@windbg…
> the platform doesnt have pcmcia, firewire or com ports and we need to
> debug
>
>
>
> On Tue, Dec 1, 2009 at 7:22 PM,
> > wrote:
> I can’t say that I’ve ever tried using the usb transport, so this is just
> my understanding:
>
> 1. The target has to be running Vista +
>
> 2. You must connect the cable to the ‘usb debugging port’ (0) on the
> target. As I understand it, there’s no way to tell in software which port
> is the right one, not all USB EHCI controllers will necessarily have one,
> and even on those that do, it may not be externally accessible.
>
> Is there some reason why you can’t use 1394 or serial?
>
>
> mm
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> –
>
> - amitr0
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> –
>
> - amitr0
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> –
>
> - amitr0
> — WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
></mailto:xxxxx></mailto:xxxxx>