Failed to re-enumerate USB3.0 plug
Collapse
X
-
Seems unlikely that the same problem fixed in 2016 would be back.
We have made a new firmware update, to fix an issues from another customer (to do with the precise timings of training sequences).
It should be released next Monday 14th on this page.
https://www.passmark.com/products/us...k/download.php
So try that next week. There is some chance it might also fix your issue, but can't be sure.
Leave a comment:
-
Hi David (PassMark),
Thanks for your support.
We found below history in the readme file of USB3.0 loopback FW.
Actually our platform does have TI TUSB8041 on board.
After doing some cross checks, the error of "Failed to re-enumerate USB3.0 plug" can only happen when the loopback is on the downstream ports of TUSB8041.
If we plug loopback on other ports only, it can run over 24 hours without errors.
Is it possible that this bug occurred before could reappear in Burn in v10.2 1010 (64-bit) with loopback FW 2.7?
v2.1 31/August/2016
- Fixed a re-enumeration issue with Cypress CY4609, Texas Instruments TUSB8041 and Microchip USB5534B hubsLeave a comment:
-
Hi David,
We have used the latest driver from intel.
Thanks for your update.
1. Have you seen this kind of error on any USB hub design?
2. Is there a workaround (i.e. some settings in the burn in program) to avoid this error?
3. Is it possible that we can get an older FW or driver of USB3.0 plugs to try if it can have a different result?
Thanks a lot.Last edited by Mark_Huang; Apr-04-2025, 11:58 AM.Leave a comment:
-
The CPU doesn't contain the USB host controller. It is part of the motherboard chipset, or when a lot of ports are required, or higher speed ports, a separate controller chip on the motherboard is used. (For Intel this is sometimes called the PCH, Platform Controller Hub chipset)
We are not aware of any problems with Windows Server 2019.
Update: Xeon D are system on a chip CPUs, so they do contain some of the PCH functionality. So might be worth checking if there is a device driver update available.
Update 2: We had a report last week of a host controller that was very sensitive to the link training sequence start delay and duration. (i.e. didn't enumerate due to the timings being wrong by a number of milliseconds). We are still looking into this.Leave a comment:
-
We are using this CPU Intel® Xeon® D-1746TER Processor as the USB3.0 host.
Unfortunately we don't have an USB protocol analyzer to debug.
Does the loopback driver support Win Server 2019? (I can't see it in the supported list.)Leave a comment:
-
USB 3.0 enumeration is the process where a host discovers and configures a newly connected USB device. The key steps include:- Device connection detection via VBUS power and differential pair connection
- Reset and speed negotiation (SuperSpeed uses separate differential pairs). Part of this step is link training sequences.
- Device descriptor request to identify basic information
- Address assignment to uniquely identify the device
- Configuration descriptor request to understand device capabilities
- Configuration selection by the host
- Interface and endpoint setup for data transfer
The really get to the bottom of it a protocol trace on the USB bus would normally be required.
What USB host controller are you using?
Leave a comment:
-
Failed to re-enumerate USB3.0 plug
Hi
We are running a restart test. The periodic procedure is as below.
1. boot into Windows OS
2. auto-run BurnInTest for 5 minutes, then stop and exit.
3. shutdown the system and then boot up
= Test environment =
OS: Win Server 2019 64bit
Test Program: BurnInTest 10.2 1010 (64-bit)
USB Plug: Firmware 2.7, Driver 1.2.3
Duty Cycle: 50%
Test items: CPU, RAM, USB
After running hours(could be 1 hour or 8 hours), it shows the error message (Failed to re-enumerate USB3.0 plug) for a few times.
I can't find the description for this error in the manual.
Would you advise what does this error mean?
Thanks a lot.Tags: None
Leave a comment: