Dear all,
?
I’ve just bought the USB debug cable NET20DC .
However , I get trouble in using it .
?
The Host can’t connect to the Target PC .
?
?
a. Host PC (Windows Vista SP1 32 bit)
-Install driver for NET20DC cable by connecting 2 connectors
to ?Port 1 & Port 2 of Host .
-?And install the driver manually with driver inside the directory “…/debuggers/usb/”
Next, running WinDbg ( latest version) , and Ctrl_K?, choosing debugging with USB
typing?the?name of debugging target? “debug”??
?
b.Target PC (Windows Vista SP2 64 bit)
I checked the PCI space to ensure the EHCI controller supports
“debug capability” and find that address 0x58 has value 0x0a ( Debug capability)
So, I continue :
?
?
-Finding the debug port of Target ( checked with USBView)
==> I find the Port 1 in the back of my PC .
Then I connect the NET20DC , one connector to Host ( Port1)
and other side to Target (Port 1)
?
I use “bcdedit” command to have those setting :
??? + Using USB for debug , targetname=debug? ( checked with > bcdedit /dbgsettings)
??? + Debug = Yes, loadoptions busparams=0.1D.7
?
#??Note: Bus =0 Device = 29 Function= 7?are?got from checking? "USB2 EHCI "in Device manager
?
Next, I restart the “target PC” and I expect that
the Host can connect to target by displaying something in the screen.
?
However, I tried many times without success.
?
I already tried to use “Ctrl-Break” . But nothing is better.
?
?
Do you have experience in this ? ? Best Regards HanNguyen
Dear all,
?
More information , I heard that some chipset
doesn’t?support Port 1 but using Port 2 as debugging
port . I also did the trial with Port 2?but nothing is better.
?
Best Regards
HanNguyen
Nguyen Nhat Han
MobiPhone : 0906.739.923
C?ng ty : Cty TNHH Thiet ke Renesas
From: Nhat Han To: Windows System Software Devs Interest List Sent: Wednesday, August 24, 2011 8:29 AM Subject: [About using USB debug cable]
Dear all,
I’ve just bought the USB debug cable NET20DC . However , I get trouble in using it .
The Host can’t connect to the Target PC .
---------- a. Host PC (Windows Vista SP1 32 bit) ------------ -Install driver for NET20DC cable by connecting 2 connectors to ?Port 1 & Port 2 of Host . -?And install the driver manually with driver inside the directory “…/debuggers/usb/” - Next, running WinDbg ( latest version) , and Ctrl_K?, choosing debugging with USB typing?the?name of debugging target? “debug”??
---------- b.Target PC (Windows Vista SP2 64 bit) ---------- # I checked the PCI space to ensure the EHCI controller supports “debug capability” and find that address 0x58 has value 0x0a ( Debug capability) So, I continue :
-Finding the debug port of Target ( checked with USBView) ==> I find the Port 1 in the back of my PC . - Then I connect the NET20DC , one connector to Host ( Port1) and other side to Target (Port 1)
- I use “bcdedit” command to have those setting : ??? + Using USB for debug , targetname=debug? ( checked with > bcdedit /dbgsettings) ??? + Debug = Yes, loadoptions busparams=0.1D.7
#??Note: Bus =0 Device = 29 Function= 7?are?got from checking? "USB2 EHCI "in Device manager
Next, I restart the “target PC” and I expect that the Host can connect to target by displaying something in the screen.
However, I tried many times without success. --------------
I already tried to use “Ctrl-Break” . But nothing is better.
USB
USB debugging works only on operating systems that are running Windows
Vista and later versions and highly depends on your system hardware.
Before considering USB debugging, check whether your systems can support
it by using the following steps:
From the WinDBG directory on the development system, run USBView.exe
and put a well-known device such as a USB flash drive into the first USB
port on the system.
Check the USBView display to see if the device is in a port of a USB
2.0 Enhanced Host Controller. If so, you might have found the required
port. If not, continue through each USB port on the system. If no port
is found, the development system is unsuitable. To refresh the USBView
display after moving to the next port, press F5.
Get USBView.exe from the directory in which you installed WinDBG and
copy it to the test machine.
Open USBView on the test machine and put a well-known device such as
a USB flash drive into the first USB port on the system.
Check the USBView display to see if the device is in Port1 of a
RootHub of a USB 2.0 Enhanced Host Controller. If so, you might have
found the port needed. If not, continue through each USB port on the
system.
If this procedure finds a valid port on the development system and a
usable Port 1 on the test system, you might be able to debug by using
USB. You must now purchase a USB 2.0 debug cable. These can be difficult
to find and are expensive. To set up the debugging, perform the
following steps:
On the host machine, plug both ends of the cable into USB 2.0 ports
to load the driver that comes with the debug cable.
Unplug one end and plug it into Port 1 of the root hub on the test
machine that you found with the preceding procedure.
To set debug to USB and the targetname to a value that you choose,
follow the procedures in “Modifying Boot Settings of the Test Machine”
later in this paper.
Start WinDbg, click File, and then click Kernel Debug.
On the USB tab, set targetname to the name that was used with the
test machine.
> Dear all, > > More information , I heard that some chipset > doesn’t support Port 1 but using Port 2 as debugging > port . I also did the trial with Port 2 but nothing is better. > > Best Regards > HanNguyen > > --------------------------------------- > Nguyen Nhat Han > MobiPhone : 0906.739.923 > Công ty : Cty TNHH Thiet ke Renesas > --------------------------------------- > > From: Nhat Han > To: Windows System Software Devs Interest List > Sent: Wednesday, August 24, 2011 8:29 AM > Subject: [About using USB debug cable] > > > Dear all, > > I’ve just bought the USB debug cable NET20DC . > However , I get trouble in using it . > > The Host can’t connect to the Target PC . > > > ---------- > a. Host PC (Windows Vista SP1 32 bit) > ------------ > -Install driver for NET20DC cable by connecting 2 connectors > to Port 1 & Port 2 of Host . > - And install the driver manually with driver inside the directory “…/debuggers/usb/” > - Next, running WinDbg ( latest version) , and Ctrl_K , choosing debugging with USB > typing the name of debugging target “debug” > > ---------- > b.Target PC (Windows Vista SP2 64 bit) > ---------- > # I checked the PCI space to ensure the EHCI controller supports > “debug capability” and find that address 0x58 has value 0x0a ( Debug capability) > So, I continue : > > > -Finding the debug port of Target ( checked with USBView) > ==> I find the Port 1 in the back of my PC . > - Then I connect the NET20DC , one connector to Host ( Port1) > and other side to Target (Port 1) > > - I use “bcdedit” command to have those setting : > + Using USB for debug , targetname=debug ( checked with > bcdedit /dbgsettings) > + Debug = Yes, loadoptions busparams=0.1D.7 > > # Note: Bus =0 Device = 29 Function= 7 are got from checking "USB2 EHCI "in Device manager > > Next, I restart the “target PC” and I expect that > the Host can connect to target by displaying something in the screen. > > However, I tried many times without success. > -------------- > > I already tried to use “Ctrl-Break” . But nothing is better. > > > Do you have experience in this ? > > Best Regards > HanNguyen
Dear all,
?
??? Additionally, I did “Disable” the “Legacy USB support”.
on target PC.
?
Beside, it takes long time for my target PC to finish
“boot”?.
?
Best Regards
HanNguyen
Nguyen Nhat Han
MobiPhone : 0906.739.923
C?ng ty : Cty TNHH Thiet ke Renesas
From: Nhat Han To: Windows System Software Devs Interest List Sent: Wednesday, August 24, 2011 8:33 AM Subject: Re: [About using USB debug cable]
Dear all, ? More information , I heard that some chipset doesn’t?support Port 1 but using Port 2 as debugging port . I also did the trial with Port 2?but nothing is better. ? Best Regards HanNguyen
--------------------------------------- Nguyen Nhat Han MobiPhone : 0906.739.923 C?ng ty : Cty TNHH Thiet ke Renesas ---------------------------------------
From: Nhat Han To: Windows System Software Devs Interest List Sent: Wednesday, August 24, 2011 8:29 AM Subject: [About using USB debug cable]
Dear all,
I’ve just bought the USB debug cable NET20DC . However , I get trouble in using it .
The Host can’t connect to the Target PC .
---------- a. Host PC (Windows Vista SP1 32 bit) ------------ -Install driver for NET20DC cable by connecting 2 connectors to ?Port 1 & Port 2 of Host . -?And install the driver manually with driver inside the directory “…/debuggers/usb/” - Next, running WinDbg ( latest version) , and Ctrl_K?, choosing debugging with USB typing?the?name of debugging target? “debug”??
---------- b.Target PC (Windows Vista SP2 64 bit) ---------- # I checked the PCI space to ensure the EHCI controller supports “debug capability” and find that address 0x58 has value 0x0a ( Debug capability) So, I continue :
-Finding the debug port of Target ( checked with USBView) ==> I find the Port 1 in the back of my PC . - Then I connect the NET20DC , one connector to Host ( Port1) and other side to Target (Port 1)
- I use “bcdedit” command to have those setting : ??? + Using USB for debug , targetname=debug? ( checked with > bcdedit /dbgsettings) ??? + Debug = Yes, loadoptions busparams=0.1D.7
#??Note: Bus =0 Device = 29 Function= 7?are?got from checking? "USB2 EHCI "in Device manager
Next, I restart the “target PC” and I expect that the Host can connect to target by displaying something in the screen.
However, I tried many times without success. --------------
I already tried to use “Ctrl-Break” . But nothing is better.
Dear Don Burn,
?
Thank you for your information !
?
But it doesn’t help me because
as I described in previous email,the setting procedure follows
the guidance from http://msdn.microsoft .com.
?
I did really tried it but not successful.
?
It’s said that the connection can be made when
I do all the steps as guidance . But it failed .
?
And I don’t know if someone has similar issues.
?
How can I check that my NET20DC run correctly ? ? # I’ll use CATC to capture the packet and confirm it soon. ? Best Regards HanNguyen ? ?
--------------------------------------- Nguyen Nhat Han MobiPhone : 0906.739.923 C?ng ty : Cty TNHH Thiet ke Renesas ---------------------------------------
From: Don Burn To: Windows System Software Devs Interest List Sent: Wednesday, August 24, 2011 8:41 AM Subject: Re:[ntdev] [About using USB debug cable]
USB USB debugging works only on operating systems that are running Windows Vista and later versions and highly depends on your system hardware. Before considering USB debugging, check whether your systems can support it by using the following steps:
1.??? From the WinDBG directory on the development system, run USBView.exe and put a well-known device such as a USB flash drive into the first USB port on the system. 2.??? Check the USBView display to see if the device is in a port of a USB 2.0 Enhanced Host Controller. If so, you might have found the required port. If not, continue through each USB port on the system. If no port is found, the development system is unsuitable. To refresh the USBView display after moving to the next port, press F5. 3.??? Get USBView.exe from the directory in which you installed WinDBG and copy it to the test machine. 4.??? Open USBView on the test machine and put a well-known device such as a USB flash drive into the first USB port on the system. 5.??? Check the USBView display to see if the device is in Port1 of a RootHub of a USB 2.0 Enhanced Host Controller. If so, you might have found the port needed. If not, continue through each USB port on the system.
If this procedure finds a valid port on the development system and a usable Port 1 on the test system, you might be able to debug by using USB. You must now purchase a USB 2.0 debug cable. These can be difficult to find and are expensive. To set up the debugging, perform the following steps:
1.??? On the host machine, plug both ends of the cable into USB 2.0 ports to load the driver that comes with the debug cable. 2.??? Unplug one end and plug it into Port 1 of the root hub on the test machine that you found with the preceding procedure. 3.??? To set debug to USB and the targetname to a value that you choose, follow the procedures in “Modifying Boot Settings of the Test Machine” later in this paper. 4.??? Start WinDbg, click File, and then click Kernel Debug. 5.??? On the USB tab, set targetname to the name that was used with the test machine.
> Dear all, > ? > More information , I heard that some chipset > doesn’t?support Port 1 but using Port 2 as debugging > port . I also did the trial with Port 2?but nothing is better. > ? > Best Regards > HanNguyen > > --------------------------------------- > Nguyen Nhat Han > MobiPhone? : 0906.739.923 > C?ng ty? ? : Cty TNHH Thiet ke Renesas > --------------------------------------- > > From: Nhat Han > To: Windows System Software Devs Interest List > Sent: Wednesday, August 24, 2011 8:29 AM > Subject: [About using USB debug cable] > > > Dear all, > > I’ve just bought the USB debug cable NET20DC . > However , I get trouble in using it . > > The Host can’t connect to the Target PC . > > > ---------- > a. Host PC (Windows Vista SP1 32 bit) > ------------ > -Install driver for NET20DC cable by connecting 2 connectors > to ?Port 1 & Port 2 of Host . > -?And install the driver manually with driver inside the directory “…/debuggers/usb/” > - Next, running WinDbg ( latest version) , and Ctrl_K?, choosing debugging with USB > typing?the?name of debugging target? “debug”?? > > ---------- > b.Target PC (Windows Vista SP2 64 bit) > ---------- > # I checked the PCI space to ensure the EHCI controller supports > “debug capability” and find that address 0x58 has value 0x0a ( Debug capability) > So, I continue : > > > -Finding the debug port of Target ( checked with USBView) > ==> I find the Port 1 in the back of my PC . > - Then I connect the NET20DC , one connector to Host ( Port1) > and other side to Target (Port 1) > > - I use “bcdedit” command to have those setting : > ??? + Using USB for debug , targetname=debug? ( checked with > bcdedit /dbgsettings) > ??? + Debug = Yes, loadoptions busparams=0.1D.7 > > #??Note: Bus =0 Device = 29 Function= 7?are?got from checking? "USB2 EHCI "in Device manager > > Next, I restart the “target PC” and I expect that > the Host can connect to target by displaying something in the screen. > > However, I tried many times without success. > -------------- > > I already tried to use “Ctrl-Break” . But nothing is better. > > > Do you have experience in this ? > > Best Regards > HanNguyen
I was told by persons who know that the usb debug port interface is a
non-starter on many if not most and perhaps almost all platforms.
try 1394.
Mark Roddy
On Thu, Aug 25, 2011 at 12:40 PM, Hagen Patzke wrote:
> On 8/25/2011 5:29 PM, Nhat Han wrote: > > as I described in previous email,the setting procedure follows > > the guidance from http://msdn.microsoft .com. > > > > # I did really tried it but not successful. > > - Sometimes USB ports connected via cables dont work. > Try a USB port which is soldered directly to the mainboard PCB. > > - Are you using an USB Root Hub on debug target and host? > What did USBView print in the details pane for both? > > - What are the USB root hub types on target and host > that you want to use (e.g. ICH10)? > > - Did you see the proper USB IDs for your NET20DC cable > with USBView on debug target and host? > > > Just some brainstorming. Hope it is useful. > > — > NTDEV 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 >
Mm
On Aug 25, 2011 12:57 PM, “Mark Roddy” wrote: > I was told by persons who know that the usb debug port interface is a > non-starter on many if not most and perhaps almost all platforms. > > try 1394. > > Mark Roddy > > > On Thu, Aug 25, 2011 at 12:40 PM, Hagen Patzke wrote: > >> On 8/25/2011 5:29 PM, Nhat Han wrote: >> > as I described in previous email,the setting procedure follows >> > the guidance from http://msdn.microsoft .com. >> > >> > # I did really tried it but not successful. >> >> - Sometimes USB ports connected via cables dont work. >> Try a USB port which is soldered directly to the mainboard PCB. >> >> - Are you using an USB Root Hub on debug target and host? >> What did USBView print in the details pane for both? >> >> - What are the USB root hub types on target and host >> that you want to use (e.g. ICH10)? >> >> - Did you see the proper USB IDs for your NET20DC cable >> with USBView on debug target and host? >> >> >> Just some brainstorming. Hope it is useful. >> >> — >> NTDEV 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 >> > > — > NTDEV 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
On Aug 25, 2011 12:57 PM, “Mark Roddy” > mailto:xxxxx> wrote: > > I was told by persons who know that the usb debug port interface is a > > non-starter on many if not most and perhaps almost all platforms. > > > > try 1394. > > > > Mark Roddy > > > > > > On Thu, Aug 25, 2011 at 12:40 PM, Hagen Patzke > mailto:xxxxx> wrote: > > > >> On 8/25/2011 5:29 PM, Nhat Han wrote: > >> > as I described in previous email,the setting procedure follows > >> > the guidance from http://msdn.microsoft .com. > >> > > >> > # I did really tried it but not successful. > >> > >> - Sometimes USB ports connected via cables dont work. > >> Try a USB port which is soldered directly to the mainboard PCB. > >> > >> - Are you using an USB Root Hub on debug target and host? > >> What did USBView print in the details pane for both? > >> > >> - What are the USB root hub types on target and host > >> that you want to use (e.g. ICH10)? > >> > >> - Did you see the proper USB IDs for your NET20DC cable > >> with USBView on debug target and host? > >> > >> > >> Just some brainstorming. Hope it is useful. > >> > >> — > >> NTDEV 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 > >> > > > > — > > NTDEV 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>