LPC500 AJays Hi-Speed USB 2.0 Debug Device NET20DC(PLX CHIP)

【LPC500-圖1】
【LPC500】 AJays Hi-Speed USB 2.0 Debug Device NET20DC(PLX CHIP)_0

原廠並不提供退貨 , 請確認您已經知道如何使用此產品 , 再購買 , 恕不提供[試用]與[退貨] , 敬請見諒.

本公司獨家代理 , 幫您節省關稅運費 , 美國進口 , 特價供應 , 歡迎直接下單.

AJays Hi-Speed USB 2.0 Host-to-Host Debug Device

The NET20DC is a Hi-Speed USB 2.0 Host-to-Host debug cable. It supports Windows kernel-level debugging with the debugger tool, WinDbg. At this time, the NET20DC is supported in Windows Vista only. The NET20DC can be used with any USB host that supports the "Debug Port" defined in the Enhanced Host Controller Interface Specification for Universal Serial Bus. Debugging with the NET20DC aids mobile systems (without 1394/serial ports) debugging. For other systems, the NET20DC provides a backup to debugging over the 1394/serial ports. Hardware requirements include an EHCI host controller that supports kernel debugging and a kernel debugging cable that meets the USB2 Debug Device Functional Specification (.pdf), like the NET20DC. Software requirements include having specific USB kernel debugging driver files. The BIOS must support Hi-Speed USB 2.0 device communication and must be able to identify the Debug Port # on the Target PC.

Supports Windows Kernel Level Debugging

Can be used with any USB Host

For use with the Enhanced Host Controller Interface Debug Port

The NET20DC Driver is included in Windows Vista. Please refer to the following links for more information.

The NET20DC is a Hi-Speed USB 2.0 device offering two upstream ports to connect two computers without a complicated hardware setup. The 480 Mbps bandwidth offers blazing fast transfer rate for kernel driver debugging. For setup and more information please check out our Resources library.

System Requirements

Target Computer: Windows Vista OS 被測機器一定要是VISTA以上(包含WIN7)
Host Computer: Windows 2000 and later OS 主控台只要WIN2000,XP以上皆可

此裝置有方向性 , 左右顛倒就無法使用 , 誤以為故障 , 請注意!!

Debugging Windows Vista
http://www.microsoft.com/whdc/driver/tips/debug_vista.mspx

Boot Parameters to Enable Debugging
http://msdn2.microsoft.com/en-us/library/ms791527.aspx

PDF下載 http://www.lpc.com.tw/pdf/net20dc.pdf

Features

Supports Windows Kernel Level Debugging
Can be used with any USB Host
For use with the Enhanced Host Controller Interface Debug Port
The NET20DC Driver is included in Windows Vista. Please refer to the following links for more information.
- Ajays Technology -----A
- Microsoft -------------B

Debugging Windows Vista

Updated: December 28, 2005

Looking for updates and drivers for your personal computer?

Introduction: The Boot.ini file bug

If you try to set up a kernel debugger on the latest builds of Microsoft Windows Vista, you will notice a major change. Depending on which build you have, the Boot.ini file is either missing from the build or it is present but is ignored.

This tip explains how to configure kernel debugging on a computer that is running Windows Vista. These instructions are designed for the simplest case: a computer on which Windows Vista is the only installed operating system. Instructions for computers that have both Windows Vista and versions of Windows earlier than Windows Vista are only slightly more complex and will be described in detail in the Windows Driver Kit (WDK) for Windows Vista.

Note:
Early beta test builds of Windows Vista still use the Boot.ini file and, on those builds, you can edit the Boot.ini file to set up debugging. You can identify builds that still use Boot.ini by the "NOBCD" boot parameter in the Boot.ini file. The NOBCD parameter was supported only in these early builds of Windows Vista. The NOBCD parameter and the Boot.ini file are ignored in later builds, and the Boot.ini file is not created at all in builds 5253 and later.

Top of page

What has changed?

Windows Vista introduces a new boot loader architecture; a new firmware-independent boot configuration and storage system called Boot Configuration Data (BCD); and a new boot option editing tool, BCDEdit (BCDEdit.exe). These components are designed to load Windows more quickly and more securely.

The traditional Windows NT boot loader, Ntldr, is replaced by Windows Boot Manager (Bootmgr.exe) and a set of system-specific boot loaders. In the new configuration, Windows Boot Manager is generic and unaware of the specific requirements for each operating system, and each system-specific boot loader is optimized for the system that it loads.

What happened to Boot.ini?

On BIOS-based computers that are running only Windows Vista, the Boot.ini text file is gone (not hidden) and any remnants of it on interim beta test builds are ignored. On computers with both earlier versions of Windows and with Windows Vista, the Boot.ini file remains to support the older versions but it does not affect booting in Windows Vista.

On EFI-based computers that are running Windows Vista, boot options are still stored in NVRAM. However, in Windows Vista you use BCDEdit to edit boot options on an EFI-based computer just as you would on a BIOS-based computer, instead of accessing NVRAM directly by using Windows APIs or specialized tools such as NvrBoot.

Windows Vista also includes new BCD classes that are supported by the WMI provider and enable you to edit BCD programmatically. For information about BCD classes, see the end of this tip.

How do I edit the boot options?

BCDEdit (Bcdedit.exe) is a command-line tool that edits boot options in Windows Vista. It replaces Bootcfg (a boot options editing tool that is included in Windows XP and Windows Server 2003) and NvrBoot (a boot options editing tool for EFI-based computers).

Use BCDEdit to edit the boot configuration in Windows Vista. You can continue to use Bootcfg and NvrBoot and to edit the Boot.ini file in versions of Windows earlier than Windows Vista, even if they are installed on a computer that also has Windows Vista installed.

Top of page

Configuring kernel debugging in Windows Vista

You can use the following procedure to create a boot entry for debugging in Windows Vista. This procedure uses BCDEdit, which is the boot option editing tool for Windows Vista.

Briefly, the steps are:

1.
Open a Command Prompt window with elevated privileges.
2.
Edit the global debugging settings, if necessary.
3.
Display the global debugging settings.
4.
Create a new boot entry by copying an existing boot entry.
5.
Add the new boot entry to the boot menu.
6.
Enable debugging on the new boot entry.
7.
Verify that debugging is set on the new boot entry.
8.
Change the default boot entry.
9.
Reboot the computer.

The rest of this tip describes each step in more detail.

1. Open a Command Prompt window with elevated privileges.

The Command Prompt window must have elevated privileges, even if you are a member of the Administrator group on the computer.

1.
Click the Start button, point to All Programs, and then click Accessories.
2.
Right-click Command Prompt, and then click Run Elevated.

2. Edit the global debugging settings, if necessary.

In Windows Vista, the debugging connection type (serial, 1394, or USB) and the attributes of the connection type (debugport or channel) are determined by a global parameter, dbgsettings, that affects all boot entries, although you can set the debugging connection type and attributes individually for particular boot entries.

The default global debugging settings for Windows Vista are:

Debug Vista CodeBlock

To change the global debugging settings, use the following command syntax.

Debug Vista CodeBlock

For example:

Debug Vista CodeBlock

If the command succeeds, BCDEdit displays the following message:

The operation completed successfully.

3. Display the global debugging settings.

To verify that a command to change the global debugging setting was successful, use the following command to display all boot settings on the system.

In the list that appears, the global debugging settings are the last entry in the list.

The following example shows the settings after the example bcdedit /dbgsettings 1394 channel:1 command from step 2 earlier in this tip.

...

Kernel Debugger Settings Group
------------------------------
Identifier:             {dbgsettings}
Type:                   20100000
Debugger type:          1394
Debugger 1394 channel:  1

...

4. Create a new boot entry by copying an existing boot entry.

At the command prompt, type the following command. This command copies the Microsoft Windows boot entry that was last used to boot Windows, identified as {current}, and creates a new boot entry named DebugEntry. (This name is used throughout the rest of this tip. You can assign any name to the new entry.)

If the command succeeds, BCDEdit displays a message such as:

The entry was successfully copied to {68602c25-5097-11da-99de-000802209f1b}.

The global universal identifier (GUID) that appears between braces in the preceding message is the identifier of the new boot entry. You use the identifier to represent the entry in all subsequent BCDEdit commands.

If the command fails, be sure that you are running in a Command Prompt window with elevated privileges and that all of the command parameters are spelled correctly, including the braces around {current}.

5. Add the new boot entry to the boot menu.

In Windows Vista, new boot loader entries are not added to the boot menu automatically. If you skip this step, the boot menu might not appear (because there is only one boot loader entry) or the menu appears, but does not list the new boot loader entry.

You can place the boot loader entries in any order. Separate each identifier (the GUID or a reserved identifier, such as {current}) with a space. To add the DebugEntry boot entry to the boot menu after the {current} entry, use the following command.

In this command, {ID} is the GUID of the DebugEntry boot loader entry, including the braces ({}), as the following example shows:

To verify that the display order is correct, use the following command:

When you type bcdedit without additional parameters, BCDEdit displays the boot manager entry and the boot loader entries in the order that they will appear in the menu.

The Windows Boot Manager entry also includes the boot menu display order, as the following example shows.

Debug Vista CodeBlock

6. Enable debugging on the new boot entry.

Use the following procedure to enable debugging on the DebugEntry boot entry that you created in step 4 earlier in this tip. The first step is necessary because you need the GUID of the boot entry for the command that sets debugging.

1.
To list all of the boot loader entries on the computer, type the following command.
2.
Find the boot entry named DebugEntry and copy the GUID, including the surrounding braces ({}), from the Identifier attribute of the entry.
Debug Vista CodeBlock
3.
To enable debugging on the DebugEntry boot entry, use the following command syntax.

where {ID} represents the GUID that you copied from the boot entry in step 2.
The following example demonstrates this command with the GUID from the example in step 2.

If the command succeeds, BCDEdit displays the following message at the command prompt.
The operation completed successfully.

7. Verify that debugging is set on the new boot entry.

Use the following procedure to verify that debugging is set on the new DebugEntry boot entry.

1.
To list the boot loader entries on the computer, use the following command.
2.
Find the boot entry named DebugEntry. The result should include a Kernel debugger attribute on the entry with a value of Yes, as the following example shows.
Debug Vista CodeBlock

8. Change the default boot entry.

The default boot entry is the boot entry that the boot manager selects when the boot menu timeout expires. Unlike earlier versions of Windows, in Windows Vista the order of boot entries in the boot menu (the display order) does not determine which boot loader entry is the default.

By default, the Microsoft Windows boot entry that the system creates is the default entry. Because the default entry is also the boot entry that is used to boot the system most recently, it is identified as {current}.

If you want the new debug-enabled boot loader entry, DebugEntry, to be the default boot entry, use the following command.

where {ID} is the GUID of the DebugEntry boot entry, as the following example shows.

If the command is successful, BCDedit displays the following message at the command prompt.

The operation completed successfully.

To see this change, use the bcdedit command (without parameters) to display the entries that appear in the boot menu.

This command produces the following output. Notice that all instances of the DebugEntry GUID have been replaced by the reserved identifier {default}.

The identifiers {default} and {current} are reserved identifiers that indicate the default boot entry and the boot entry that was used most recently to boot the system. If a boot entry is both the default and the current entry, its identifier is {current}. If a boot entry is not the default or the current entry, BCDEdit restores its original GUID as its identifier.

You can identify the boot entry by its name (in the Description attribute), but you must use the identifier, not the description, in BCDEdit commands.

Debug Vista CodeBlock

9. Reboot the computer.

When you reboot your computer, the Windows Boot Manager displays the boot menu. You can select the Microsoft Windows boot entry or the DebugEntry. If you do not select either choice, the Windows Boot Manager selects the default, DebugEntry.

Debug Vista CodeBlock

Top of page

For more information:

Windows Driver Kit
Tools for Debugging Drivers

Platform SDK
Boot Configuration Data (BCD)
BCD Classes

Windows Hardware Development Central
Development Tools and Testing: Overview
Debugging Tools for Windows - Overview

Looking for drivers and updates for your personal computer?

B. Boot Parameters to Enable Debugging

Debugging Windows Vistahttp://www.microsoft.com/whdc/driver/tips/debug_vista.mspx

Boot Parameters to Enable Debugginghttp://msdn2.microsoft.com/en-us/library/ms791527.aspx

A. Debugging Windows Vista

http://msdn.microsoft.com/en-us/library/ms791527.aspx

Windows Driver Kit: Driver Development Tools

Boot Parameters to Enable Debugging

When a kernel debugging connection is established, the system gives a kernel debugger control over its execution. Also, when a bug check occurs or a kernel-mode program communicates with a debugger, the computer waits for a response from a kernel debugger before it continues.

There are four basic debugging methods that you can configure by using boot parameters:

Single-computer (local) debugging
Debugging with a null-modem cable
Debugging with an IEEE 1394 cable (only if the target computer and the host computer are both running Microsoft Windows XP or a later version of Windows)
Debugging with a USB 2.0 debug cable (only if the target computer is running Windows Vista or a later version of Windows and the host computer is running Windows 2000 or a later version of Windows)

Boot Parameters for Local Debugging in Operating Systems Prior to Windows Vista

To enable kernel debugging on a single computer, add the /debug parameter to a boot entry. Do not add any other debugging-related parameters to a boot entry.

The first boot entry in the following sample Boot.ini file includes the /debug parameter.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Local Debugging" /fastdetect /debug
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /fastdetect

The following Bootcfg command enables local debugging. The Bootcfg /debug switch, with a value of ON, adds the /debug parameter to a boot entry. The /ID switch identifies the boot entry.

bootcfg /debug ON /ID 1

The following sample Bootcfg display of a system with a Boot.ini file shows the result. The first boot entry is configured for local debugging.

Boot Entries
------------
Boot entry ID:    1
OS Friendly Name: Windows XP Local Debugging
Path:             multi(0)disk(0)rdisk(0)partition(2)WINDOWS
OS Load Options:  /fastdetect /debug

Boot entry ID:    2
OS Friendly Name: Microsoft Windows XP
Path:             multi(0)disk(0)rdisk(0)partition(2)WINDOWS
OS Load Options:  /fastdetect

Boot Option for Local Debugging in Windows Vista and Later

To enable kernel debugging on a single computer, use the BCDEdit /debug boot option.

To use BCDEdit, open a Command Prompt window with elevated privileges (right click Command Prompt and click Run as administrator from the shortcut menu).

The /debug option has the following syntax:

bcdedit /debug [{ID}] { on | off }

The {ID} is the GUID associated with a boot entry. If an {ID} is not specified, the settings apply to the current boot entry. The following command enables kernel debugging for the current Windows operating system boot entry:

bcdedit /debug on

The following command enables kernel debugging for the specified Windows operating system boot entry:

bcdedit /debug {18b123cd-2bf6-11db-bfae-00e018e2b8db} on

You can use the bcdedit /enum command to view the current boot entries, their settings, and to identify the GUID associated with each entry.

For more details, see BCDEdit /debug.

Boot Parameters to Debug with a Null-modem Cable in Operating Systems prior to Windows Vista

To enable debugging with a null-modem cable, add the /debug parameter with the /debugport and /baudrate subparameters to a boot entry.

The first boot entry in the following sample Boot.ini file is configured for debugging with a null modem cable.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Debugging with Cable" /fastdetect /debug /debugport=COM1 /baudrate=57600
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /fastdetect

Set the value of the /debugport subparameter to a COM port on the computer. Set the value of the /baudrate subparameter to the connection speed of the cable. (19200 bits per second is the default.)

The following Bootcfg command enables debugging on the first boot entry. It sets the debugging port to COM1, and it sets the baud rate to 57,600 BPS.

The Bootcfg /debug switch with a value of ON adds the /debug parameter to the boot entry. The Bootcfg /port switch adds the /debugport subparameter with a value of COM1. The Bootcfg /baud switch adds the /baudrate subparameter with a value of 57600. The /ID switch identifies the boot entry.

bootcfg /debug ON /port COM1 /baud 57600 /ID 1

The following Bootcfg sample shows the resulting boot entry on an Itanium-based system. The newly added parameters are displayed in bold type.

Boot Entries
------------
Boot entry ID:    1
OS Friendly Name: Windows Server 2003, Enterprise
OsLoadOptions:     /debug /debugport=COM1 /baudrate=57600
BootFilePath:     DeviceHarddiskVolume1EFIMicrosoftWINNT50ia64ldr.efi
OsFilePath:       DeviceHarddiskVolume3WINDOWS

Boot Options to Debug with a Null-modem Cable in Windows Vista and Later

To enable debugging with a null-modem cable in Windows Vista and later, use BCDEdit and set the debugging connection type to "SERIAL". You can set this globally by using the BCDEdit /dbgsettings command followed by serial, or set it for a specific boot entry by using the BCDEdit /set command followed by debugtype serial. You must also use the BCDEdit /debug command to enable kernel debugging globally or for the desired operating system.

If BCDEdit has not been used, the default global debug settings are for serial communications, using COM1 and a baud rate of 115,200.

To display the current settings, use the following command:

bcdedit /dbgsettings

debugtype               Serial
debugport               1
baudrate                115200

To use BCDEdit, open a Command Prompt window with elevated privileges (right click Command Prompt and click Run as administrator from the shortcut menu).

To set the global debug settings to serial communications, use the following syntax:

bcdedit /dbgsettings serial [DEBUGPORT:port] [BAUDRATE:baud]

The following example shows how to specify serial communications as the global debug setting.

bcdedit /dbgsettings serial debugport:1 baudrate:115200

To set the debug settings to serial for a specific boot entry, or for the current entry, use the following syntax:

bcdedit /set [{ID}] [ debugtype serial | [DEBUGPORT port] | [BAUDRATE baud] ]

If no {ID} is specified, the settings apply to the currently active boot entry.

The following example shows how to specify the serial debug settings for a specific boot entry.

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} debugtype serial

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} debugport 1

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} baudrate 115200

You can use the bcdedit /enum command to view the current boot entries and their settings.

For more details, see BCDEdit /debug and BCDEdit /dbgsettings.

Boot Parameters to Debug with a 1394 Cable in Operating Systems prior to Windows Vista

If your host computer and target computer are both running Windows XP or later, you can perform kernel debugging with an IEEE 1394 (FireWire) cable.

To enable debugging with an IEEE 1394 cable, add the /debug parameter with the /debugport and /channel subparameters to a boot entry. Set the value of the /debugport subparameter to 1394. Set the value of the /channel subparameter to the cable channel.

The first boot entry in the following sample Boot.ini file is configured for debugging with a 1394 cable.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Debugging with 1394" /fastdetect /debug /debugport=1394 /channel=44
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Microsoft Windows XP Professional" /fastdetect

The following Bootcfg command enables debugging with a 1394 cable and sets the debugging channel to 44. The /dbg1394 switch with a value of ON adds the /debug parameter and /debugport=1394 subparameter to the boot entry, and the /ch switch adds the /channel subparameter to the boot entry. The /id switch identifies the second boot entry.

bootcfg /dbg1394 ON /ch 44 /id 2

The following Bootcfg displays shows the result of the command on a system with a Boot.ini file. The newly added parameters are displayed in bold type. The computer now has boot options for both a nondebug startup of Windows XP and a startup that enables debugging with a 1394 cable. The nondebugging startup is the default.

Boot Entries
------------
Boot entry ID:   1
Friendly Name:   "Microsoft Windows XP Professional"
Path:            multi(0)disk(0)rdisk(0)partition(1)WINDOWS
OS Load Options: /fastdetect

Boot entry ID:   2
Friendly Name:   "1394 Debug Windows XP"
Path:            multi(0)disk(0)rdisk(0)partition(1)WINDOWS
OS Load Options: /fastdetect /debug /debugport=1394 /channel=44

Note To perform kernel debugging with a 1394 cable when the target computer is running Windows Server 2003 (with no service packs installed) or Windows XP with Service Pack 1 (SP1), you must disable the 1394 host controller on the target computer and install the 1394 virtual driver that is included in the Debugging Tools for Windows package on the host computer. For instructions about these required steps, see the "Disabling the 1394 Host Controller" and "Installing the 1394 Virtual Driver" topics in the ms791527.internet_link_sm(en-us,MSDN.10).gif Debugging Tools for Windows documentation.

Boot Parameters to Debug with a 1394 Cable in Windows Vista and Later

To enable debugging with an IEEE 1394 cable in Windows Vista and later, use BCDEdit and set the debugging connection type to "1394". You can set this globally by using the BCDEdit /dbgsettings command followed by 1394, or set it for a specific boot entry by using the BCDEdit /set command followed by debugtype 1394. You must also use the BCDEdit /debug command to enable kernel debugging globally or for the desired operating system.

To use BCDEdit, open a Command Prompt window with elevated privileges (right click Command Prompt and click Run as administrator from the shortcut menu).

To set the debug settings for 1394 globally, use the following syntax:

bcdedit /dbgsettings 1394 [channel:channel]

The following example shows how to specify 1394 as the global debug setting.

bcdedit /dbgsettings 1394 channel:32

To set the debug settings to serial for a specific boot entry, or for the current entry, use the following syntax:

bcdedit /set [{ID}] [ debugtype 1394 | channel channel ]

If an {ID} is not specified, the settings apply to the current boot entry.

The following example shows how to specify the 1394 debug settings for a specific boot entry, and how to use the /debug option to enable kernel debugging for that boot entry.

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} debugtype 1394

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} channel 32

bcdedit /debug {18b123cd-2bf6-11db-bfae-00e018e2b8db} on

You can use the bcdedit /enum command to view the current boot entries and their settings.

For more details, see BCDEdit /debug and BCDEdit /dbgsettings.

Boot Parameters to Debug with a USB 2.0 Debugging Cable in Operating Systems prior to Windows Vista

Debugging with a USB 2.0 debugging cable is not supported on a target computer running a version of Windows prior to Windows Vista.

Boot Parameters to Debug with a USB 2.0 Debugging Cable in Windows Vista and Later

If your target computer is running Windows Vista or later, and your host computer is running Windows 2000 or later, you can perform kernel debugging with a USB 2.0 debugging cable.

To enable debugging with a USB cable in these versions of Windows, use BCDEdit and set the debugging connection type to "USB". You can set this globally by using the BCDEdit /dbgsettings command followed by usb, or set it for a specific boot entry by using the BCDEdit /set command followed by debugtype usb. You must also use the BCDEdit /debug command to enable kernel debugging globally or for the desired operating system.

To use BCDEdit, open a Command Prompt window with elevated privileges (right click Command Prompt and click Run as administrator from the shortcut menu).

To set the debug settings for USB globally, use the following syntax:

bcdedit /dbgsettings usb [targetname:targetname]

The following example shows how to specify USB as the global debug setting.

bcdedit /dbgsettings usb targetname:U1

To set the debug settings to serial for a specific boot entry, or for the current entry, use the following syntax:

bcdedit /set [{ID}] [ debugtype usb | targetname targetname ]

If no {ID} is specified, the settings apply to the current boot entry.

The following example shows how to specify the USB debug settings for a specific boot entry, and how to use the /debug command to enable kernel debugging for that boot entry.

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} debugtype usb

bcdedit /set {18b123cd-2bf6-11db-bfae-00e018e2b8db} targetname u2

bcdedit /debug {18b123cd-2bf6-11db-bfae-00e018e2b8db} on

You can use the bcdedit /enum command to view the current boot entries and their settings.

For more details, see BCDEdit /debug and BCDEdit /dbgsettings.

Boot Parameters to Debug the Boot Process in Windows Vista and Later

If your target computer is running Windows Vista or later, and your host computer is running Windows 2000 or later, you can perform boot debugging of one of the boot components.

To enable boot debugging, use the BCDEdit /bootdebug command and specify the appropriate boot component. If you wish to perform kernel debugging after Windows starts, use the BCDEdit /debug command as well.

You must also select a debugging connection (serial, 1394, or USB 2.0). This can be done with either the BCDEdit /dbgsettings or BCDEdit /set command, just as in normal kernel debugging. command to enable debugging.

For more details, see BCDEdit /bootdebug.

Send feedback on this topic
Built on November 19, 2009

【LPC500-圖2】
【LPC500 】AJays Hi-Speed USB 2.0 Debug Device NET20DC(PLX CHIP)_1

【LPC500-圖3】
【LPC500 】AJays Hi-Speed USB 2.0 Debug Device NET20DC(PLX CHIP)_2

LPC500 AJays Hi-Speed USB 2.0 Debug Device NET20DC(PLX CHIP)

SPEC:

PDF下載 http://www.lpc.com.tw/pdf/net20dc.pdf

Features

Supports Windows Kernel Level Debugging
Can be used with any USB Host
For use with the Enhanced Host Controller Interface Debug Port
The NET20DC Driver is included in Windows Vista. Please refer to the following links for more information.
- Ajays Technology
- Microsoft

說明:

電腦畫面與實物皆有色差，以實際出貨為準。

其他產品:

同目錄共有1個商品: 第一個| 上一個| 下一個| 最後一個

對此產品來信發問.

產品系列:

mini-Displayport	Displayport	mini-DVI	USB 3.0	AJAYS
HDMI	DVI	VGA	1394	週邊