This article describes an issue that occurs when you try to use the USB 3.0 debugger. We have released an update to resolve this issue. Before you apply the update, check out the Prerequisites for hardware settings in this article.
Consider the following scenario:
You have an Intel® Atom™ Processor Z373x series based or Intel Cherry Trail Cost Reduction (CHT-CR)-based computer that is running Windows 8.1.
The computer has an external USB 2.0 port.
You try to perform kernel debugging on the device by plugging a USB 3.0 cable into the USB 2.0 port.
In this scenario, the debug fails.
This issue occurs because Intel® Atom™ Processor Z373x and CHT-CR platforms do not provide xHCI debugging support because of pin reduction.
To resolve this issue, you can use one of the following methods.
Note After you apply this update, you can perform kernel debugging on Intel® Atom™ Processor Z373x and CHT-CR devices by plugging a USB 3.0 cable into the external USB 2.0 port. This feature is also supported on full Intel® Atom™ Processor Z374x, Z377x, Z378x, Z379x or N28xx/N29xx and CHT devices when plugging a USB 2.0 cable into the external USB 3.0 port, because the external USB 3.0 port is backward-compatible with USB 2.0.
To apply this update, you have to meet the following conditions:
The firmware should have the Extensible Device Controller Interface (xDCI) Debug Port Table 2 (DBG2) entry.
The xDCI controller is exposed correctly to the desired USB debug port.
The OEM firmware has to hide the xDCI controller in PCI, or expose it as an ACPI device instead of as a PCI device.
Note The base address for xDCI will be pointed to by the DBG2 table entry.
The USB cable should be plugged in before the platform starts.
After you apply this update
The following scenarios are not supported:
There is no support for Power Management. This is the same as the Extensible Host Controller Interface (xHCI) debug solution currently available.
There is no support for hot-plug scenarios.
There is no support for USB-reconnection scenarios.
Additionally, after you apply this update, a polling mechanism is added to achieve and process events from the Event buffer. Because a polling mechanism is used, the rate of polling is faster than the rate of hardware events to fill the Event buffer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 8.1 file information and notes
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
6.3.960 0.17 xxx
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
For all supported x64-based versions of Windows 8.1
Additional file information
Additional files for all supported x86-based versions of Windows 8.1
The following table contains the important fields for the xDCI DBG2 table entry:
32 bits (0x20)
<Dynamically Assign based on xDCI PCI BAR0>
Synopsys xDCI (0x0007)
This update also contains two other important fixes that target the Intel SoC devices:
3002859 Miracast display resolution changes after you shut down and then start a Windows 8.1-based computer
3008242 The system does not enter Connected Standby after you install update 2996799 in Windows 8.1
See the terminology that Microsoft uses to describe software updates. Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.