Release Note XHCI DR WIN

****************************************************************************
**************** D720200 & D720200A Design Resources Release ***************

****************************************************************************
Release Note
September 28.2012
Renesas Electronics uPD720200 & uPD720200A
USB 3.0 Host Controller Driver Kit (x86 and x64)
for Windows XP, VISTA, 7 and Server 2008 Release 2
Kit Version : 2.1.39.0 : September 28th, 2012
Copyright (C) 2010-2012 Renesas Electronics Corporation All Rights Reserved
****************************************************************************
NOTE1:
This installer package is generated with the InstallShield2010 SP1.
If the previous driver package (v0.X.X.X , v1.0.1.0 or v1.0.7.0) is installed,
please uninstall the previous driver package and install new package.
--------------------------------------------------------------------------Table of Contents
--------------------------------------------------------------------------1. Command Line Options
2. How to install/uninstall the driver package
3. History
----------------------------------------------------------------------------------------------------------------------------------------------------1. Command Line Options
----------------------------------------------------------------------------------------------------------------------------------------------------1) Silent install
Ex.) setup.exe /s
-To install this driver package silently, "setup.iss" file is needed.
This package includes the "setup.iss" in which the following folder
path is set.
"C:\Program Files\Renesas Electronics\USB 3.0 Host Controller Driver".
If you want to change the install path, you need to generate setup.iss as
follows: setup /r /f1".\setup.iss"
2) Check existence of USB3.0 Host Controller
Ex.) setup.exe /v"CHECK_HW_EXIST=1"
-When this command line option is set, the installer checks existence of
the USB3.0 Host Controller (uPD720200/uPD720200A). If the uPD720200/uPD720200A
is not in the PC, this installer does not install the device drivers.
##Caution##
To install the device drivers with this command line option after
uninstalling the device drivers, it is necessary to restart the PC.
3) Not install the USB3.0 Monitor application (nusb3mon.exe/dll)
/v"NO_MONITOR=1"
-When this command line option is set, the USB3.0 Monitor Application
(nusb3mon.exe/dll) is not installed. Refer to USB 3.0 Specification
Section 11.1 and driver version 1.0.1.0Beta below for further description
of the monitor function for user notification of USB 3.0 devices connected
to USB 2.0 ports.
##Caution##
If the USB3.0 Monitor Application is already installed, it is necessary to
uninstall the USB3 driver package of previous version before installing the
new USB3 driver package (v1.0.19.0 or later).
4) Not install the USB3.0 Utility application (nusb3utl.exe)
/v"NO_UTILITY=1"
-When this command line option is set, the USB3.0 Utility Application
(nusb3utl.exe) is not installed. The Utility Applicatoin shows the
Driver Version and Firmware Version.
##Caution##
If the USB3.0 Utility Application is already installed, it is necessary to
5) Disable the Selective Suspend function
Ex.) setup.exe /v"SET_SELSUS_MODE1=1"
-Selective Suspend function is enabled by default starting with Ver2.0.20.0.
This option disables the Selective Suspend function. The Selective Suspend
function is described in section 1.4 & 2.8 of "USB 3.0 Host Controller Driver
Application Note (ISG-NC1-200030)". Please see that document for more detail.
##Note##
This option is supported from Ver.2.0.20.0.
The Selective Suspend function for External Hubs is supported from Ver.2.0.20.
0.
6) Hide the pop-up message
Ex.) setup.exe /v"CHECK_HW_EXIST=1 NO_MESSAGE=1"
-This option suppresses the pop-up message when it is used with the "CHECK_HW_E
XIST"
option. If you want to hide the pop-up message on the "CHECK_HW_EXIST" option,
you should use this option on the command line.
-This option is described in section 2.5 & 2.9 of "USB 3.0 Host Controller Driv
er
Application Note (ISG-NC1-200030)". Please see that document for more detail.
##Note##
This option must be used only with the "CHECK_HW_EXIST" option. If this option
is used
by itself, it has no effect.
7) Disable the Dynamic U1/U2 state control function

Ex.) setup.exe /v"U1U2_DISABLE=1"
-The Dynamic U1/U2 state control function is enabled by default starting with
Ver2.0.4.0. If you want to disable the Dynamic U1/U2 state control function,
you should use this option on the command prompt.
##Note##
8) Disable the check box to disable the Dynamic U1/U2 state control function
on "nusb3utl.exe"
Ex.) setup.exe /v"U1U2_UTL_DISABLE=1"
-From ver2.0.26.0, the USB 3.0 Host controller Utility supported the check-box
to disable the Dynamic U1/U2 state control function. In the default setting,
this check-box is set to appear.
If you don't want to display this checkbox in the USB3.0 Host controller
Utility, you should use this option on the command prompt.
##Note##
9) Display the Custom Property page in the device manager
Ex.) setup.exe /v"DP_PROPERTY=1"
-From ver2.1.16.0, the USB 3.0 Host controller Driver supported the Custom
Property page to display the firmware version and disable the Dynamic U1/U2
state control function.
##Note##
The Custom Property page is not displayed in default setting with Ver2.1.16.0.
----------------------------------------------------------------------------------------------------------------------------------------------------2. How to install/uninstall the driver package
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Please see the "USB 3.0 Host Controller Driver Application Note (Preliminary)".
A) How to install the driver package
1. Installing the driver package to a computer. (Run "setup.exe")
2. Installing the hardware
3. Installing the driver for USB 3.0 host controller.
B)How to uninstall the driver package
RENESAS-USB3-Host-Driver-xxxx-Setup.exe can uninstall only by using "Programs
and Features" in Control Panel.
1.
2.
3.
4.
Open the "control panel".

Click the "Programs and Features".
Select the Renesas Electronics USB 3.0 Host Controller Driver.
Click "Uninstall" button.
----------------------------------------------------------------------------------------------------------------------------------------------------3. History
----------------------------------------------------------------------------------------------------------------------------------------------------Version 2.1.39.0 : September 28, 2012
--------------------------------------------------------------------------- Windows Logo Information
Submission ID: 1520317
Product Name: Renesas Electronics USB3.0 Host Controller
Category: Device
Subcategory: Bus Controllers and Ports > USB Controller
Unclassiified
Qualification Level: Signature Only - Microsoft Windows XP family, x86
Signature Only - Microsoft Windows XP family, x64
Logo - Microsoft Windows Vista family, x86 Basic
Windows 7
Windows 7 x64
Logo - Certified for Microsoft Windows Server 2008 Relea
se 2 family, x64
[1. Modified driver]
1-1.Additional remediation was implemented for the following issues:
[ver 2.1.36.0's history, item 2-2]
2-2. When continuously starting & stopping the video capture with
a specific USB2.0 Camera, the specific USB2.0 camera cannot
restart the video capture.
1-2.There is a possibility that BSOD occurs when performing the Common
Scenario Stress-with-IO test in WHQL, when connecting an external
USB hub to USB 3.0 Host Controller.
1-3.There is a possibility that BSOD occurs when S3/S4->resume is executed
with the xHCI Backwards Compatibility Tree on enabling the driver
verifier.
1-4.The host driver clears USBLEGCTLSTS register after the host driver
obtained Ownership from Ver2.0.30.0. Therefore, BIOS needs to set
"SMI on OS Ownership Enable" bit in USBLEGCTLSTS register to '1b'
if BIOS has set "HC BIOS Owned Semaphore" to '1b' and hands Ownership
off after S3/S4->Resume.
If a system using SMIB signal doesn't set "SMI on OS Ownership Enable"
to '1b' after S3/S4->Resume, there is a possibility that the host
driver cannot obtain Ownership and Device Manage shows the yellow bang
for USB 3.0 Host Controller.
In order to solve this issue, we modified the host driver to set
"HC BIOS Owned Semaphore" bit to '0b' forcibly if "HCHalted" bit of
USBSTS register is '1b'.
1-5.There is a possibility that BSOD occurs when users connect the xHCI
Backwards Compatibility Tree to USB 3.0 Host Controller and operate all
the devices in the xHCI Backwards Compatibility Tree and uninstall USB
3.0 Host Controller in Device Manager.
##Note##
This issue only occurs on Windows XP. We have never seen this issue on
Windows Vista/7/Server2008R2.
1-6.There is a possibility that BSOD occurs when the upper or lower filter
driver is installed to USB 3.0 Host Controller driver and the xHCI
Backwards Compatibility Tree is connected to USB 3.0 Host Controller.
1-7.There is a possibility that BSOD occurs when the xHCI Backwards
Compatibility Tree is connected to USB 3.0 Host Controller and
operating all devices and a setting of a ISO device application is
changed on enabling the driver verifier.
1-8.A specific USB 3.0 Flash device isn't detected when a specific USB 3.0
Hub, which has the USB 3.0 Flash device connected, is connected to the
USB 3.0 Host Controller.
1-9.There is a possibility that BSOD occurs when more than one device with
the same VID/PID and serial number is connected at the same time on
enabling the driver verifier.
1-10.There is a possibility of BSOD when Hot plug operation is done with
the xHCI Backwards Comptibility Tree.
[2. Solved interoperability issue caused by function driver]
2-1.A specific web camera does not work by using the specific function
driver. This function driver sets the bad Frame Number when the
function driver starts the ISO transfer request.
2-2.There is a possibility that BSOD occurs if a function driver behaves
as causing a conflict between a transfer request and cancelling the
transfer for the same endpoint. We have never seen these drivers.
[3. Add function]
3-1.Added the registry of SymbolicName when a device is connected.
--------------------------------------------------------------------------Version 2.1.36.0 : May 31, 2012
Category: Device
Unclassiified
Windows 7
Windows 7 x64
se 2 family, x64
[1. Modified driver]
1-1.Modified the driver not to issue SetFeature(RemoteWake) in a PC, in which
SystemWake is in PowerSystemSleeping3.
1-2.There is a possibility that BSOD occurs when the Stress Test of Pnpdtest.exe
is excuted with connecting USB HUB having USB devices.
1-3.Additional remediation was implemented for the following ver 2.1.32.0 issue:
[ver 2.1.32.0's history, item 2-4]
2-4. USB3.0 Devices connected with USB3.0 HUB are not detected after S3/S4 re
sume.
This issue occurs only under the following conditions.
- C_PORT_CONNECTION of the downstream port of the hub is not changed aft
er resume.
- The PERSTB of the system is asserted after resume.
[2. Solved interoperability issue caused by function driver or system]
2-1.Fixed the interoperability issue of the specific docking station integrated
SuperSpeed HUB.
2-2.When continues to start & stop the vedio capture with the specific USB2.0 Ca
mera,
the specific USB2.0 cannot start the video capture.
2-3.There is a possibility that BSOD occurs when a USB device, which a function
driver sends the Power IRP before our device driver handles the "IRP_MN_START
_DEVICE",
is connected.
--------------------------------------------------------------------------Version 2.1.32.0 : March 23, 2012
Category: Device
Unclassiified
Windows 7
Windows 7 x64
se 2 family, x64
[1. Add function]
1-1. IOCTL_USB_USER_REQUEST(UWSBUSER_GET_POWER_STATE_MAP) is supported.
1-2. HUB's icon isn't shown on the Devices and Printers of Windows7.
[2. Modified driver bugs]
2-1. There is a possibility of BSOD when OUT transaction with data shorter than
8byte
is transferred. Short packet is out of this issue.
We have never seen this BSOD on the real system. We found this on code revi
ew.
V2.1.16.0 or later version includes this bug.
2-2. There is a possibility of BSOD when a user changes the resolution of the vi
deo
capture application and an ISO device is disconnectd.
ew.
2-3. There is a possibility of BSOD when OverCurrent indication occurs before Wi
ndows
OS detects the device.
ew.
2-4. USB3.0 Devices connected with USB3.0 HUB are not detected after S3/S4 resum
e.
This issue occurs only under the following conditions.
- C_PORT_CONNECTION of the downstream port of the hub is not changed after
resume.
- The PERSTB of the system is asserted after resume.
2-5. Driver did not check the descriptor size. If USB devices send the descripto
r
with invalid size, driver might behave in undefined operation.
2-6. When BIOS does not release the ownership of xHCI after S3/S4 resume, host d
river
should not have been loaded.
2-7. Wrong bandwidth information is displayed in the popup message when availabl
e
bandwidth is consumed.
[3. Solved interoperability issue caused by function driver or system]
3-1. PC freezes when any of the specific devices are disconnected.
3-2. The following specific devices can't work
A) The specific Wireless Headset does not produce sound in Windows XP envir
oment.
B) The specific Keyboard is not detected.
This issue only occurs on V2.1.16.0 or later verion.
C) The specific Keyboard is not detected after remote wakeup under the cond
ition
that ForceHCResetOnResume is set to 1.
D) The specific AV Portable Player disappears from Device Manager after it
is
disabled in Device Manager.
E) Time from when the specific USB2.0 Flash is connected until it is detect
ed
is over 30 seconds. This issue only occurs on V2.1.16.0 or later version
and
on uPD720200A.
3-3. PC freezes when the specific Audio device is disconnected actively.
This issue only occurs on V2.1.25.0 or later version.
3-4. Monitor function of the specific docking station cannot work correctly afte
r
resume when multi-display mode is used.
3-5. When multiple USB3.0-hubs including the specific hub are connected by casca
de
connection and host driver is disabled and enabled, the hub connected with
the specific hub's downstream port is not detected.
3-6. When one of the multiple USB3.0 hubs in cascade connection is the specific
HUB, it is not detected after S3-Resume.
3-7. When a specific smart phone is working in tethering mode, communication
speed is too slow to keep the connection.
--------------------------------------------------------------------------Version 2.1.28.1 : January 5, 2012
--------------------------------------------------------------------------- Windows Logo Information is same as Ver2.1.28.0
- Installer was modified.
As informed in IBB-NK1-110005 20111213-1, the workaround required that
a user had to delete the yellow bang on the device manager.
With the use of this installer package, a user does not have to delete
the yellow bang after updating the host driver from v2.1.16.0 or older.
---------------------------------------------------------------------------
Version 2.1.28.0 : November 7, 2011

Category: Device
Unclassiified
Windows 7
Windows 7 x64
se 2 family, x64
- The following issues, which depend on specific devices, were fixed.
1. A specific Audio device (Native Instruments AUDIO 8 DJ) isn't unloaded in
the device manager when this device is disconnected from USB 3.0 Host
Controller.
- The following additional issues were fixed.
-- Driver
1. Remote Wakeup function doesn't work from Hybrid sleep by a wireless mouse
connected to USB 3.0 host controller.
This issue doesn't occur with ver 2.0.XX.0 drivers
2. Additional remediation was implemented for the following ver 2.1.27.0 issue:
[ver 2.1.27.0's history, item 2]
There is a possibility that a multi-display isn't displayed after
S3->Resume when the USB-to-VGA device connected to the USB 3.0 Host
is used in multi-display mode. This issue occurs depending on USB-to-VGA
device driver version.
3. The "/usbss" test time for the Signal Check Tool for Windows was too long
(double or triple time) compared to ver 2.0.34.0 or older.
4. There is a possibility that BSOD occurs when a SuperSpeed device which
doesn't transfer the "SuperSpeed Endpoint Companion Descriptor is
connected to USB 3.0 Host controller.
5. A SuperSpeed device is reconnected in SuperSpeed mode after
S3/S4->resume if the SuperSpeed device transfers the
USB 2.0 Descriptor to USB 3.0 Host controller.
6. A device cannot do Isochronous Transfer when an illegal start frame is
specified by the function driver for an Isochronous transfer.
7. There is a possibility that BSOD occurs when performing the Common Scenario
Stress-with-IO test in WHQL, when connecting a external USB hub to USB 3.0 Ho
st
Controller.
--------------------------------------------------------------------------Version 2.1.27.0 : September 30, 2011
---------------------------------------------------------------------------
- Windows Logo Information

Category: Device
Unclassiified
Windows 7
Windows 7 x64
se 2 family, x64
1. A specific USB Full Speed device that can't respond to a standard request
isn't detectd.
2. There is a possibility that a multi-display isn't displayed after
S3->Resume when the USB-to-VGA device connected to the USB 3.0 Host
is used in multi-display mode. This issue occurs depending on USB-to-VGA
device driver version.
3. There is a possibility that the Bluetooth communication is cut off with
a specific Bluetooth module.
4. There is a USB speaker which only requests a data transfer by a URB within
about 1ms. In this case, sound is cut off depending on CPU performance.
5. iPad isn't detected on iTunes application after S3->Resume.
6. BSOD ("Blue Screen of Death," i.e., system halt) occurs when PC shutdown
is performed while a specific Bluetooth module (Billionton BT-0003) is
connected and a specific Bluetooth module driver version is being used.
This issue doesn't occur with the latest Bluetooth module driver version.
-- Driver
1. There is a possibility that BSOD occurs or USB 3.0 Hub isn't detected on
Windows XP when hot plug operation is done with a USB 3.0 Hub having USB
devices already connected to it.
2. USB 3.0 Host controller Driver forcibly caused BSOD from ver2.1.16.0 to ver
2.1.25.0 when Host System Error of USB 3.0 occurred.
When we updated to ver 2.1, we had a mistake in which the USB 3.0 Host
Controller Driver focibly caused BSOD.
3. A USB device isn't detected when the USB device is connected to a downstream
port on a specifc USB 3.0 Hub that moves to U2 state even though the U1/U2 ti
meout
value is zero.
4. There is a miscalucuation of U2 Exit Latency.
--Monitor
1. The pop-up message is wrong when a USB 3.0 device is connected to USB 2.0 po
rt
while running the Simplified Chinese OS.
2. The pop-up message is wrong when USB 3.0 Host Controller does not have
enough bandwidth available while running the Polish OS.
--------------------------------------------------------------------------Version 2.1.25.0 : August 26, 2011
Category: Device
Unclassiified
Windows 7
Windows 7 x64
se 2 family, x64
1. There is a possibilty that UB435-Q (KWorld Computer Co., Ltd) isn't detected
during Hot-plug operation.
-- Driver
1. When DeviceIoControl() of IOCTL_USB_GET_NODE_CONNECTION_DRIVERKEY_NAME
issued, an error occurs.
This issue only occurs with Ver 2.1.16.0 & Ver 2.1.19.0.
2. A PC, in which SystemWake is in PowerSystemSleeping3, cannot enter Hybrid sl
eep.
3. PC doesn't enter Sleep (S3 State) or Hibernate (S4 State) when it should
on Windows XP while a USB Hub is connected to the USB 3.0 Host controller.
This issue depends on the PC. (This issue occurs when ACPI filter driver is
installed for USB HUB.)
4. USB Mouse isn't detected when users perform the below steps.
a) Connect Mass Storage device & USB Mouse
b) Operate "Safely Remove Hardware" for Mass Storage device.
(Don't disconnect Mass Storage device)
c) Enter sleep (S3 State)
d) Change the port of Mass Storage device & USB Mouse during S3 State
5. There is a possiblity that BSOD occurs or SuperSpeed device isn't detected
when users perform the below steps.
a) Connect USB 3.0 Hub to USB 3.0 Host Controller
b) PC enters HybridSleep & resumes
c) After resuming, SuperSpeed device is connected to USB3.0 Hub
This issue only occurs with USB 3.0 Hub supporting RemoteWakeUp.
6. There is a possibility that a data transfer stops with UAS drive.
This issue only occusr with Ver 2.1.19.0.
7. Re-examined U1 Timeout value.
U1 transition control was slow from USB 3.0 Host Controller because
U1 Timeout value was big in ver 2.1.19.0,

--Utility
1.When nusb3utl.exe runs and USB 3.0 Host Controller is disabled, Windows OS
requests the restart.
----------------------------------------------------------------------------------------------------------------------------------------------------Version 2.1.19.0 : June 30, 2011
Category: Device
Unclassiified
Windows 7
Windows 7 x64
se 2 family, x64
1. Remote Wakeup funtion from Logitec G15 Gaming Keyboard doesn't work.
2. There are specific models of Creative ZEN which aren't detected.
-- Driver
1. USB3.0 devices aren't detected when users perform the below steps.
a) Turn on a PC.
b) Enter sleep (S3 state) without connecting USB3.0 devices.
c) Connect USB3.0 devices to a USB3.0 port during S3 state.
d) USB 3.0 HDD isn't detected.
The USB3.0 devices aren't detected after the PC resumes from S3 state.
This issue only occurs with Ver.2.1.16.0.
2. There is a possibility of bluescreen caused by Hot-Plug operation of a
USB3.0 Hub connecting USB3.0 devices. This issue only occurs with Ver2.1.16.0
.
3. There is a possibility that USB devices can't be detected after remote
wakeup. This issue only occurs with Ver.2.1.16.0. We will add information
about remote wakeup in the USB3.0 Host Controller Driver Application Note
in near future.
--CoInstaller
1. Upon opening the "Advanced" tab of Renesas USB 3.0 Host Controller in Device
Manager and changing the aero theme of "the visuals and sounds on your comput
er",
the firmware version and check box of "Disable USB 3.0 power management
functions" disappears.
--------------------------------------------------------------------------Version 2.1.16.0 : April 22th, 2011

Category: Device
Unclassiified
Qualification Level: Logo - Designed for Microsoft Windows XP family, x86 - D
FW
Logo - Designed for Microsoft Windows XP family, x64 - D
FW
Logo - Microsoft Windows Vista family, x86 Basic - Basic
Logo - Device - Compatible with Windows 7
Logo - Device - Compatible with Windows 7 x64
se 2 family, x64
- Tuned the Host Driver to improve performance of Stream Transfer.
With this improvement, the Stream API of the Host Driver was changed.
- Tuned the Host Driver to improve the intialization time of USB3 Host Controll
er,
when an External USB Hub is connected to USB3.0 Root port.
- Changed the Dynamic U1/U2 state control function.
End user doesn't need to reconnect the USB 3.0 devices when the Dynamic
U1/U2 state control (USB 3.0 Power Management) is changed by RENESAS Electron
ics
USB3.0 Host Controller Utility (nusb3utl.exe).
##Caution##
Don't add the registry ("SSLinkTimeoutMode" & "PMFeatureEnable") to disable t
he
USB3.0 Power Management after the driver is installed by the installer or inf
installation.
Please see section 1.5 of "ISG-NK1-100001-AN_005-DriverPackageInformation.pdf
(ISG-NK1-100001, Rev.0.05, 2011/04/20)".
- Added the custom Property Sheet Page to display the FW version and
change USB3.0 Powermanagement in the Device Manager. The default setting of
this page is disabled.
If you want to use this page, please install the driver package with using
the following command-line. Please see the section 1.7 & 2.12 of
"ISG-NK1-100001-AN_005-DriverPackageInformation.pdf(ISG-NK1-100001, Rev.0.05,
2011/04/20)".
<Command Line>
setup.exe /v"DP_PROPERTY=1"
- Changed the Remote wakeup function behavior based
From v2.1.16.0, the following 2 cases cannot wake
1. Disconnected the USB mouse which is connected
SB Hub.
2. Connected the USB device to the USB Hub which
upon Windows 7.
up the system.
to the downstream port of U
the USB mouse is connected.
- The following issues were fixed.

-- Driver
1. When a user initially connects a USB compound device (smart phone, etc.)
to a USB 3.0 port, there is a possibility that it will not be correctly

detected (enumerated), unless it is first plugged into a USB 2.0 port on
the same system. This driver update fixes this problem and allows device
detection (enumeration) to occur correctly the first time a compound
device is plugged into a USB3.0 port.
2. When the Remote Wake Up is excuted by keyboard, an unwanted string is ent
ered.
To solve this issue, you need to add the parameter (DWORD(32bit) value)
to the following registry key.
<Registry Key>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\nusb3xhc\Parameters
<DWORD (32bit) value>
ForceHCResetOnResume
<Value data>
1h
3. When the hot plug operation is done with the external USB Hub, there is
a possibility that the USB Hub is not detected.
##Note##
This issue doesn't occur when the Selective Suspend Function is disabled.
--------------------------------------------------------------------------Version 2.0.34.1 : March 31th, 2011
--------------------------------------------------------------------------- Windows Logo Information is same as Ver2.0.34.0.
- The following issue was fixed.
-- Utility
1. When the USB3.0 Power management functions(U1/U2 functions) are disabled
with the USB3.0 Host Controller Utility, the Kingstone DT Ultimate 16GB
is not detected after S4-Resume. This issue also occurs when the host
controller driver is installed with the commandline option "U1U2_DISABLE=1"
.
--------------------------------------------------------------------------Version 2.0.34.0 : February 18th, 2011
Category: Device
Unclassiified
FW
FW
se 2 family, x64
-- Driver
1. If an ISDN-USB device (AVM FRITZ! Card USB V2.1) is connected to an Express
Card,
and the ExpressCard is then disconnected during the S3 state, the PC cannot
resume
from the S3 state.
2. There is a possiblility that a bluescreen occurs when S4->resume is running
after an Expresscard to which some HID devices were connected, is disconnec
ted
during S4.
3. There is a possibility that a bluescreen occurs when a filter driver betwee
n
the function driver and the Host driver issues a request, but the function
driver does not start.
4. The Devices and Printers of Windows 7 show the unwanted Icon of a printer.
5. PC cannot run "System Image Recovery" from External HDD on USB3.0 Port.
6. The USB-FDD device is not detected when it is first connected to USB 3.0 po
rt.
-- Utility (nusb3utl.exe)
7. On a PC where both D720200 and D720200A are implemented, Utility tool shows
the
wrong FW version when nusb3utl.exe is run. This bug is derived from v2.0.26.
0
driver package.
--------------------------------------------------------------------------Version 2.0.32.0 : December 17th, 2010
Category: Device
Unclassiified
FW
FW
se 2 family, x64
- The following issues, which depend on a specific device, were fixed.
1. D-Link DWA160 (USB-WLAN Module) cannot find access points.
2. USB 2.0 Gigabit Ethernet Adapter (WS-NWU220G) does not work after S3/S4-R
esume.
3. After ISDN-USB device (AVM FRITZ! Card USB V2.1) is disconnected during t
he S3 state,
the PC cannot resume from the S3 state.
1. When a USB3.0 ExpressCard is reconnected while the USB3.0 Host Controller

Utility
(nusb3utl.exe) is open, it shows the error message, "USB3.0 Host Controll
er not found!".
2. After S3/S4-resume, the USB 3.0 Host Controller driver cannot detect a US
B 2.0 device
on which a Low Speed device is changed during the S3/S4 state.
#Note# This issue occurs only when the Remote WakeUp function function is
enabled in
the function driver.
--------------------------------------------------------------------------Version 2.0.30.0 : November 30th, 2010
Category: Device
Unclassiified
FW
FW
se 2 family, x64
- Tuned the host driver to improve performance.
- Added the process to clear USBLEGCTLSTS register after the host driver obtaine
d
Ownership. This process prevents BIOS and OS PCI driver from violating Ownersh
ip
access when the host driver hands it off.
- The USB3.0-SATA Bridge LSI used by "Goodway NU6120", "Fujitsu HLMD001C" and
"Mach Xtreme MXUB3MFX" freezes when it receives a Hot-Reset from the host.
From V2.0.30.0, we added recovery processes.
1. There is a possibility that a bluescreen occurs when in S3/S4 and resume
occurs.
2. When a User is using the USB 3.0 Host Controller Utility (nusb3utl.exe) a
nd
presses [F1] key on the keyboard, a blank pop-up is shown.
3. When a User is using USB 3.0 Host Controller Utility (nusb3utl.exe) and
presses [F4] key, [BackSpace] key or [Enter] key on the keyboard,
an error message is shown.
--------------------------------------------------------------------------Version 2.0.26.0 : October 7th, 2010
---------------------------------------------------------------------------

Category: Device
FW
Logo - Designed for Microsoft Wi
ndows XP family, x64 - DFW
Logo - Microsoft Windows Vista f
amily, x86 Basic - Basic
Logo - Device - Compatible with
Windows 7
Windows 7 x64
Logo - Certified for Microsoft W
indows Server 2008 Release 2 family, x64
- Added a new function in "nusb3utl.exe" which can disable/enable
"Dynamic U1/U2 state control function".
1. Bluescreen occurred when 3G modem card (TD-SCDMA RX-310) is connected
to the PC through
USB3 Host Controller.
2. Yellow bang issues occurred when the following USB devices are connec
ted
to the PC through USB3 Host Controller.
a) Pinnacle Systems PCTV MCE IR Transceiver (Receiver)
b) Philips OVU4003/00 (Remote Receiver)
c) Philips RC1534501/00 (Remote controller)
--------------------------------------------------------------------------Version 2.0.20.0 : August 13th, 2010
Category: Device
FW
Logo - Designed for Microsoft Wi
ndows XP family, x64 - DFW
Windows 7
Windows 7 x64
Logo - Certified for Microsoft W
indows Server 2008 Release 2 family, x64
- Supported Windows Server 2008 Release 2 (x64)
- Supported the Selective Suspend function for an External Hub.

Please see section 1.4 & 2.8 of "USB 3.0 Host Controller Driver Application
Note" for more detail.
1. On "Devices and Printers" of Windows 7, the Bus reported in the devic
e
description in the device's Property page was not shown when USB devices were
connected to the computer through the USB 3.0 Host Controller.
2. USB3 Driver didn't support the Dynamic U1/U2 state control function f
or
USB3 Devices which support the Periodic Endpoint.
3. There was an issue with the Control transfer. This issue occurred in
the
following cases.
Case1. Yellow bang issues occurred when USB devices are connected
to the PC through USB3 Host Controller.
Case2. USB3 Host Controller cannot receive Vendor Requests.
##Caution##
This issue occurs in Ver2.0.4.0 only. This does not occur with
Ver1.0.20.0 or earlier.
4. After suspend & resume with Microsoft's Zune HD connected through the
USB 3.0 Host Controller, Device manager showed the yellow bang for this
device.
- Hardware Ids of the device's Property page were designed as mixed-case on all
Windows OS. From Ver2.0.20.0, Hardware Ids of device's Property are designed
as follows.
Windows XP
: Vid_XXXX (Designated by mixed-case)
Windows 7/Vista : VID_XXXX (Designated by capital letters only)
--------------------------------------------------------------------------Version 2.0.4.0 : May 14th, 2010
- Dynamic U1/U2 state control function was enabled.
- Driver Provider Name in the INF file was changed from NEC Electronics
to Renesas Electronics.
- "Discontine storage access" issue was fixed.
(Although we fixed "Discontinue storage access" issue in V1.0.19.0,
we found some cases where this issue was reproduced.)
--------------------------------------------------------------------------Version 1.0.20.0 : March 31th, 2010
##Note##
The Drivers in this package are certified with WLK1.5.

From the WLK1.5, categories for which USB3.0 xHCI drivers should be submitted
were changed as follows.
Submission Categories
USB3 Host Controller : Device - USB Controller
USB3 Root Hub
: Unclassified
With this change, the INF file for driver installation is separated into
two files. The nusb3xhc.inf is for the USB3 Host Controller, and the
usb3hub.inf is for the USB3 Root hub.
- The following bugs were fixed
1. UQ WiMAX USB module (UD01SS) is not detected correctly.
2. There is a possibility that bluescreen occurs when attempting hot plug
operations at the downstream port of the USB2.0 HUB connected with
the USB3.0 port.
--------------------------------------------------------------------------Version 1.0.19.0 : Februay 5th, 2010
- The following functions were added.
1. One of the notifications that we reported in the IBB-ND0-100001
(Notification and product restriction information, Dec 14th 2009),
"Discontinue storage access after sleep (S3) and hibernation (S4) in
PC system", is fixed.
2. When disabling an SS Device with "safely remove," the USB port connected
to the SS device is placed in U3 instead of U0.
- Added command line option to this installer.
/v"NO_MONITOR=1"
- When this command line option is set, the USB3.0 Monitor Application
(nusb3mon.exe/dll) is not installed.
##Caution##
If the USB3.0 Monitor Application is already installed, it is necessary to
--------------------------------------------------------------------------Version 1.0.18.0 : December 1st, 2009
--------------------------------------------------------------------------We received Device Logo in the USB Controller Subcategory of the WLK1.4.
As for system logo test,
Microsoft announced testing process for USB3.0 xHCI Controller below.
http://www.microsoft.com/whdc/whql/resources/news/whqlnews_112409.htm
Product Name: NEC Electronics USB3 Host-01
Category: Device
Qualification Level: Signature Only - Microsoft Windows XP family, x86 - Uncla

ssified
Signature Only - Microsoft Windows XP family, x64 - Uncla
ssified
- The following bugs were fixed.
1. When host driver is disabled and uPD720200 goes to D3hot state,
CLKREQ# does not work.
2. When connectiong a certain Keyboard with fingerprint function,
PC can't enter S3/S4/S5 state.
3. When using a certain ZIP Drive, file transfer is aborted.
--------------------------------------------------------------------------Version 1.0.17.0 : Nobember 2nd, 2009
--------------------------------------------------------------------------- This version includes the CAT files signed by
Microsoft Windows Hardware Compatibility Publisher.
This device driver complies with WHQL certification as Unclassified
Category on Windows XP, Vista & 7.
The Submission ID for WHQL certification is 1371310.
- The following bug was fixed.
1. Function drivers were not unloaded when disconnecting gold tree from
the roothub port of USB3 HC.
2. After Warm Reset was issued, enumeration process might fail.
- InstallShield project file, License.rtf and versionDLL were updated.
- The following functions were added.
1. When Link Errors frequently occur in the SuperSpeed-Port, driver changes
the connection from the SuperSpeed to HighSpeed.
2. Transfer throughput was improved.
3. Dynamic U1/U2 state control function was disabled. When enabling U1/U2
function, the device that used SuperSpeed link with host went down unexpec
tedly.
We decided to disable this function to get interoperability.
To get better interoperability, please use the FW version 3.0.2.1
released Nov.2nd 2009 or later.
--------------------------------------------------------------------------Version 1.0.14.0 : October 6th, 2009
The Submission ID of WHQL certification is 1358042.
- The following bugs are fixed.
1. If the USB Device has multiple Endpoints with same EndpointAddress,

the USB Device is not enumerated.
2. A USB2.0 Device connected with mulitiple layered USB2.0 HUB is not detecte
d
after resuming Sleep and Hibernate.
- Updated InstallShield project file, script file, customDLL & versionDLL.
- Added the following functions to this installer.
1. Command line option for checking existence of USB3.0 Host Controller.
/v"CHECK_HW_EXIST=1"
When this command line option is set, the installer checks existence of
the USB3.0 Host Controller(uPD720200). If the uPD720200 is not in the PC,
this installer does not install the device drivers.
##Caution##
To install the device drivers with this command line option after uninstall
ing
the device drivers, it is necessary to restart on the PC.
2. Previously, this installer did not install device drivers to the PC
in which device drivers with same version are already installed.
In this version, it reinstalls the device drivers to the PC.
--------------------------------------------------------------------------Version 1.0.12.0 : September 11th, 2009
--------------------------------------------------------------------------- Updated End User Licence Agreement.
- This version includes the CAT files signed by
- This package includes "Install Shield 2010 Project Files" in the EXE folder
so that cusotmers can customize the install package.
- Installer Wizard Messages, "nusb3mon.exe" and "nusb3utl.exe" support
the following languages.
LCID : Language
0401 : Arabic
0404 : Traditional Chinese
0405 : Czech
0406 : Danish
0407 : German
0408 : Greek
0409 : English
040A : Spanish (Traditional)
040B : Finnish
040C : French
040D : Hebrew
040E : Hungarian
0410 : Italian
0411 : Japanese
0412 : Korean
0413
0414
0415
0416
0419
041B
041D
041E
041F
0424
0804
0816
0C04
0C0A
2C0A
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Dutch
Norwegian (Bokmal)
Polish
Portuguese (Brazilian)
Russian
Slovak
Swedish
Thai
Turkish
Slovenian
Simplified Chinese
Portuguese(Standard)
Chinese (Hong Kong)
Spanish (Modern)
Spanish (Latin America)

1. Bluescreen sometimes occurs when starting WebCam application.
2. The mouse-supported SelectiveSuspend function does not work when
it wakes up from suspend state.
3. Can't access CD-ROM Media in a Blu-Ray Drive.
- Optimized SS/HS bulk transfer performance
--------------------------------------------------------------------------Version 1.0.10.0 : August 26th, 2009
- All files except for the CAT files are the same as Version1.0.10.0 Beta2
--------------------------------------------------------------------------Version 1.0.10.0Beta2 : August 24th, 2009
--------------------------------------------------------------------------- This version includes Microsoft TestSigned CAT Files.
Note: If this driver package is used on x64 Windows Vista/7,
need to set the following command.
>bcdedit -set TESTSIGNING ON
- This installer package is generated with the InstallShield2010.
If the previous driver package (v0.X.X.X , v1.0.1.0 or v1.0.7.0) is installed,
please uninstall the previous driver package and install the new package.
- Installer Wizard Messages, "nusb3mon.exe" and "nusb3utl.exe" support
the following languages.
LCID
404
407
409
40A
40C
410
411
:
:
:
:
:
:
:
:
Language
Traditional Chinese
German
English
Spanish
French
Italian
Japanese
412
413
804
816
:
:
:
:
Korean
Dutch
Simplified Chinese
Portuguese(Standard)

1. Some hub devices are not detected after resuming Sleep and Hibernate.
2. Bluescreen occurs after resuming Sleep and Hibernate.
- Known issue. This issue will be fixed in the next version.
1. Bluescreen sometimes occurs when starting WebCam application.
--------------------------------------------------------------------------Version 1.0.7.0Beta : July 17th, 2009
--------------------------------------------------------------------------- The following bugs are fixed.
1. USB Devices are not detected after resuming from Sleep and Hibernate.
2. Bluescreen occurs after resuming from Sleep and Hibernate.
3. USB-VGA Devices do not work correctly.
4. The message that bandwidth is getting low might not be indicated.
-The following function is Added
1. Add a Vendor Defined Command.
--------------------------------------------------------------------------Version 1.0.1.0Beta : June 15th, 2009
--------------------------------------------------------------------------- This package includes the following applications.
1. nusb3mon.exe
This application provides the following function.
USB3.0 Specificatin Section 11.1 describes the following function.
To address the situation where a USB 3.0 device is connected to a
USB 2.0-only port on a USB 3.0- capable host, after establishing a
USB 2.0 high-speed connection with the device, it is recommended
that the host inform the user that the device will support
SuperSpeed operation if it is moved to a USB 3.0-capable port on the
same host. If a USB 3.0 device is connected to a USB 3.0- capable
host via a USB 2.0 hub, it is recommended that the host inform the
user that the device will support SuperSpeed operation if it is
moved to an appropriate host port or if the hub is replaced with a
USB 3.0 hub.
2. nusb3utl.exe
This application provides functions that show Driver Version
and Firmware Version.
1. Function driver is not unloaded after resuming from Sleep and Hibernate.
2. USB Remote wake up function does not work correctly.
3. Bluescreen occurs upon repeated hot-plug of FS-Speaker Device
that is connected to the USB 3.0 HC through an HS Hub.
--------------------------------------------------------------------------Version 0.9.12.0Beta : May 29th, 2009

--------------------------------------------------------------------------- Changed installer package configuration.
1. EXE type
*All files are included in the EXE file.
*Combined x86 and x64 in one package.
2. ZIP type
*Composed of 3 items: setup.exe, x86 folder and x64 folder.
*All files for x86 are in x86 folder.
*All files for x64 are in x64 folder.
*Setup.exe installs drivers automatically.
--------------------------------------------------------------------------Version 0.9.12.0Beta : May 27th, 2009
1. Function driver is not unloaded after resuming from Sleep and Hibernate.
2. While repeatedly hot-plugging a USB2.0 device, the device is not detected.
3. When connecting two USB Devices and then resuming from Sleep and Hibernate,
neither device is detected.
4. Bluescreen occurred when USB-VGA device is running.
5. Dual Display mode of a USB-VGA device can't operate.
--------------------------------------------------------------------------Version 0.9.4.0Beta : March 27th, 2009
--------------------------------------------------------------------------- Support for Super Speed Transactions
--------------------------------------------------------------------------Version 0.9.3.0Beta : March 9th, 2009
1. If the system is booted up with a USB device already present on the USB
port, the USB port is inoperative and cannot recover even if the
USB device is unplugged and then plugged back in.
--------------------------------------------------------------------------Version 0.9.0.0Beta : February 9th, 2009
--------------------------------------------------------------------------- First Beta Version Release

Release Note XHCI DR WIN

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Release Note XHCI DR WIN

Încărcat de

Drepturi de autor:

Formate disponibile

****************************************************************************

** D720200 & D720200A Design Resources Release *

7) Disable the Dynamic U1/U2 state control function

Open the "control panel".

Version 2.1.28.0 : November 7, 2011

- Windows Logo Information

U1 Timeout value was big in ver 2.1.19.0,

--------------------------------------------------------------------------- Windows Logo Information

- The following issues were fixed.

to a USB 3.0 port, there is a possibility that it will not be correctly

1. When a USB3.0 ExpressCard is reconnected while the USB3.0 Host Controller

- Windows Logo Information

- Supported the Selective Suspend function for an External Hub.

The Drivers in this package are certified with WLK1.5.

Qualification Level: Signature Only - Microsoft Windows XP family, x86 - Uncla

1. If the USB Device has multiple Endpoints with same EndpointAddress,

- The following bugs are fixed.

- The following bugs are fixed.

--------------------------------------------------------------------------Version 0.9.12.0Beta : May 29th, 2009

S-ar putea să vă placă și