TUSB8041: BOS Descripter of HUB can not recognize

Hello,
Are you using tUSB8041 evaluation boards? If not. please share your schematic for review.
What is the operating system?
Regards

Hi,　Villegas-san

Thank you for your immediate support.

Because circuit information can not be disclosed in general,
I'd like to send it to your personal e-mail address, please tell me the sending address.

Best regards
Cafain

Hello Villegas-san

It is not EVM. It is a board designed by the user.

The OS is Windows 7 / Linux (details unknown).

I will send the circuit diagram, but please tell me your e-mail address.

Best Regards

You can send it to elias.villegas@ti.com
Regards

Hi,

I sent a circuit diagram to the mail address I taught.

If there is any other information request, please mail.

best regards

Cafain

Hello,
I reviewed the schematic and have some comments:

1) You are using the same GRSTz signal to reset several devices, I would like to see a scope capture of the power-up sequence showing GRSTz, USB_VBUS, VDD33 and VDD11.

2) I see you are using re-drivers, does the issue happens with both USB3.0 and USB2.0 downstream devices?

3) I don't clearly understand what do you mean by "HUB1 and HUB2" do you have tiered hubs? That is not shown on the schematic.

4) How many inches of PCB trace do you have on both sides of the USB3.0 re-driver?

You can email me the scope captures to the same address.

Regards

Hello, Villegas san

Thank you for your support

I confirmed that BOS is supported if the value of bcdUSB is 0x0210 or more in USB2.0 Device Descriptor.
As a result, since the value of bcdUSB is 0x300, we recognize that it is operating on USB3.0.
We have confirmed that access speed faster than USB2.0 is using USB3.0 compatible memory.

Also, regarding this, it is additional information.
Depending on the cable length between PC and HUB, the BOS becomes invisible.
0.5 m: BOS can be recognized
1.0 m: BOS can be recognized
2.0 m: BOS can be recognized
3.0 m: BOS can not be recognized

Attached is the Device Description list of the USB3.0 hub for each cable length.

We will re-experiment and send the result at a later date.

best regards

CafainTUSB8041 DeviceDescription.zip

Hello, Villegas san

I got the power sequencing waveform and PCB layout information requested by e2e, so I will send it to e-mail.

 

1) You are using the same GRSTz signal to reset several devices, I would like to see a scope capture of the power-up sequence showing GRSTz, USB_VBUS, VDD33 and VDD11.

 

    Please look at the attached BMP file. (to e-mail)

 

2) I see you are using re-drivers, does the issue happens with both USB3.0 and USB2.0 downstream devices?

 

    We are checking the problem with the USB 3.0 downstream devices.

    In the USB 2.0 downstream devices, we have not confirmed. (USB 2.0 is not used)

 

3) I don't clearly understand what do you mean by "HUB1 and HUB2" do you have tiered hubs? That is not shown on the schematic.

 

    HUB 1 and HUB 2 are independent HUB boards and are the same HUB board.

    The circuit diagram I sent is a circuit diagram of one HUB board.

 

4) How many inches of PCB trace do you have on both sides of the USB3.0 re-driver?

 

    Please look at the attached Excel file.(to e-mail)

 

best regards.

Hello Cafain, please see below feedback from the Team.

Regards

"It looks like the hub may be dropping into low power mode before the host sends the BOS descriptor request when a 3M cable is used.  The host is not waking the hub to send the command.  If a USB 3.0 device is connected to a downstream port of the hub when it is connected with a 3M cable, that would keep it out of low power mode for longer.  It would be a good test to see if the BOS descriptor can be read in that case."

Hi, Villegas san

Hoping for support from the team, I will wait.
Sorry to trouble you, but please do so.

best regards

cafain

Hello villegas -san

The reason why I ask about BOS Descriptor is because the USB3.0 device does not work when I connect a USB3.0 device (not a USB memory) to a USB3.0 hub (prototyped at our company).

If you connect another USB3.0 hub with a USB3.0 device (not a USB memory), it works normally.

Other USB3.0 hubs:
· Use hub chips not made by TI.
· ReDriver IC is not used.

Compared with other USB3.0 hubs, what I found is as follows.
· You can read the BOS Descriptor of other USB3.0 hubs.
· You can not read the BOS Descriptor of the USB3.0 hub (prototyped at our company).
· The BOS Descriptor of the connected USB 3.0 device can be read regardless of the difference of the hub.

From the above results, I inquired about the inability to read the BOS Descriptor.

※ When connecting a USB memory (USB3.0 compatible) to a USB3.0 hub (prototype at our company), it works without problems.

Hello,
We need a USB protocol trace taken between the Host and the TUSB8041 for further debug.
What is the failure rate?
Have you tried other USB Host?
Can you ship your platform to USA for debug?
Regards

Hello villegas -san

 

We appreciate your support to solve this problem.

 

Confirm that you can send the product designed by the user to you.

Please wait a little more.

 

Best regards

cafain