TUSB9261: Connectivity Problem

Hi Jayanthan,

Is the device showing up on the Flash Burner or device manager at all? Do you have an EEPROM for this device.

I will review the schematic as well, one thing I noticed right away though is 100nF caps on the USB RX lines. Typically for these lines, there should be either 330nF or no caps, as this can cause the USB3 signal to violate the USB spec.

I will let you know if I find anything else in the schematic.

Thanks,

Ryan

HI Ryan,

Sorry for the delayed response. 

Device isn't showing up on Flash Burner. I have assembled the EEPROM Ref 'U6'.

I tried changing the caps to 330nF & also shorting the caps pad. But still, there is no response.

Thanks,

Jayanthan V

Hi Jayanthan,

Another thing I've noticed is that it seems like you have the USB3RX net connected to the TX pins, and the USB3TX net connected to the RX pins. Could you send the portion of the schematic that contains the USB3 connector? I would like to verify the connection there.

The TX pins of the connector should connect to the TX of the TUSB9261, while the RX pins of the connector should connect to the RX pins of the TUSB9261.

Thanks,

Ryan

Hi Ryan,

I'm trying to connect as USB2.0. But the device isn't deducted. I have gone through the Implementation guide. there it shows the device will show atleast as unknown device. But, in my case that also not showing.

FYI, I'm attaching the other part of schematic.

Thanks,

Jayanthan V

Hi Jayanthan,

Can you use something else, like USBTreeView, and see if that detects anything either? We have sometimes seen that program detect a connection while device manager will not.

Also, can you monitor the USB2 lines if possible and see if there is activity on the lines there? If there is a connection, one of the line should be pulled up. If there is no connection, then it is possible the TUSB9261 is not powered or functional.

Additionally, please ensure the power-up timing requirement is being met: 

Thanks,

Ryan

Hi Ryan,

I will try using USBTreeView & check the USB lines.

Power seems to be Okay.

Thanks,

Jayanthan V

Hi Jayanthan,

Okay, got it. Please let me know what you find.

Thanks,

Ryan

Hi Ryan,

Device isn't deducted even in USBTreeView software.

I'm unable to check USB LInes.

Meanwhile have you found any hardware error in the schematic?

Thanks,

Jayanthan V

Hi Jayanthan,

Is this a crystal or an oscillator? If this is a crystal, then VSSOSC should not be pulled down to the PCB ground, and should instead be left floating.

What is the sequencing for powering this device? Per the errata for this device, VDD(1.1V) needs to be powered before the VDD33 rail, or else there will be issues in the power-up sequence.

For the GRSTZ pin, in our EVM, we have this pulled down to ground via a 220nF capacitor in order to delay the pin asserting, per the datasheet:

I see it only pulled-up here with no capacitor, that may be affecting it as well I believe.

I will keep looking to see if I see any other potential causes.

Thanks,

Ryan

Hi Ryan,

There is no activity on USB lines, since connection isn't established. Following changes are done,

1. VSSOSC made to float & made sure 1.1V is powered ON before 3.3V suuply.

2.  22uF capacitor added at reset section. But link up isn't happening.

Thanks,

Jayanthan V 

Hi Ryan,

There is an update, I removed FB11 at USB Connector.

TUSB9261 is deducted as unknown USB device. How to proceed further?

Thanks,

Jayanthan V

Uploaded the image for clear view

Hi Jayanthan,

Have you already installed the TUSB9261 Flash burner? I believe that should come with a driver for the TUSB9261 which typically helps with unknown device issues.

Can you monitor the USB lines again to see if there is any change in activity, I.E one line is just pulled up, or if there is activity?

Also, it may be good to look at treeview again and see what info is said there, (PID, VID).

Jayanthan V said:

There is an update, I removed FB11 at USB Connector.

Strange that removing the ferrite bead at the connector fixes this. Was the voltage or current being heavily affected by it?

The unknown device error could also be due to signal integrity. Is the total length of the system and USB cable used a decent length?

Thanks,

Ryan

Hi Ryan,

I guess TUSB9261 doesn't provide descriptor response. That's why it showing as unknown device.

In treeview, PID - 0002, VID - 0000

Thanks,

Jayanthan V

Hi Jayanthan,

The driver is not changing anything on the PID/VID side? If you right-click "Unknown USB Device" in device manager, what does the device status say under the general tab? What code does it return?

You could also try updating the driver of the device manually via device manager to the see if you can update the driver to the TUSB920 Flash Burner Driver.

Thanks,

Ryan

HI Ryan,

PID VID Obtained from TreeView is okay? Does IC is works fine? 

Thanks,

Jayanthan V

Hi Jayanthan,

The PID/VID we see right now on treeview is the one typically associated with an unknown device. That's why I would like to confirm whether or not the driver changes the PID/VID to the expected value per the flash burner guide: https://www.ti.com/lit/ug/sllu125d/sllu125d.pdf?ts=1746480043866&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FTUSB9261

I would like to see if the driver for this device can be updated via device manager to the TUSB9260 Flash Burner Driver, and see if that improves the VID/PID.

Additionally, the device status and code displayed in device manager would be nice as well.

Thanks,

Ryan

Hi Ryan,

USBTreeView

Device Manager General Tab

TUSB926x Burner Software. I tried all methods given in Flash Burner Guide. 

If IC provides the descriptor, It will either show as Mass storage Device or Direct TUSB9261. 

Here in my case it shows as unknown device, which is due to descriptor failure. 

Thanks,

Jayanthan V

Hi Jayanthan,

Jayanthan V said:

 

I was looking back through the schematic, and noticed that it looks like the USB2 DP/DM lines split between three different locations, the AM572x, the Micro-b connector, and the TUSB9261. Are these lines all connected together at the same time? splitting the USB2 lines can cause issues with signal integrity, or if there is activity on the lines from two different devices at the same time, I.E The AM part and the TUSB9261 going to that micro-b connector, that could potentially cause issues as well. Please confirm how all these are communicating via USB2, a block diagram may help.

You mentioned removing a FB on the Micro-b helped show the device appear on device manager. I see multiple FB's on these schematics, could you try removing those to ensure they are not harming the power supplies/rails performance?

Have you tested with different USB cable lengths for communicating with the TUSB9261 to ensure signal integrity due to cable length is not an issue? Is it being communicated to via the Micro-B port?

If possible, could you test with a TUSB9261 demo board and confirm whether the performance you see there is different?

Thanks,

Ryan

Hi Ryan,

DP/DM lines are connected between TUSB9261 & USB Connector. Even, I suspected the FBs, I removed all & tried to provide required voltage from external source. 

I tried with shorter length cables. Still facing the issue.

TUSB9261DEMO is working fine.

Descriptor failed in my custom Board. 

Thanks,

Jayanthan V

Hi Jayanthan,

Jayanthan V said:

DP/DM lines are connected between TUSB9261 & USB Connector. Even, I suspected the FBs, I removed all & tried to provide required voltage from external source. 

On the schematic, specifically the picture above, it looks like the USB2 signal is broken out. Are one of these resistors depop-ed so that there is only a connection between the connector and the TUSB9261?

Is it possible to use a protocol analyzer and see if you see any attempt at communication with that, or maybe use an oscilloscope and see if there is any communication/packets there? Even being able to see if there is a pull-up on DP or DM may be good.

Thanks,

Ryan

Hi Ryan,

At a time, either 1-2 are populated or 1-3 are populated. 

Do you want to me to pull up DP/DM lines? If yes, provide resistor value & pull up to which voltage?

Thanks,

Jayanthan V

Hi Jayanthan,

Jayanthan V said:

Do you want to me to pull up DP/DM lines? If yes, provide resistor value & pull up to which voltage?

You do not need to pull up DP/DM. DP or DM should automatically be pulled up in the scenario where there is a valid USB connection, so I would like to see if either have been pulled-up so that we can confirm whether can connection is being made or not.

And with an oscilloscope trace or protocol analyzer trace, we can see if any attempt at communication is being made, or if there is no activity.

Thanks,

Ryan

Hi Ryan,

I checked with oscilloscope, DP/DM lines aren't pulled up.

Since descriptor is failed, how the connection will be made? 

Please provide, solution for descriptor failure.

Thanks,

Jayanthan V

Hi Jayanthan,

Jayanthan V said:

I checked with oscilloscope, DP/DM lines aren't pulled up.

Sounds like there is no USB connection then, the PC must just detect a connection due to VBUS. Could you monitor VBUS at the connector, TUSB9261 and PC to ensure it is 5V?

I will continue looking through the resources we have and let you know what suggestions or solutions I have by EOD tomorrow, 5/13.

Thanks,

Ryan

Hi Ryan,

I checked VBUS from PC. It is stable. 

Thanks,

Jayanthan V

Hi Jayanthan :

   Ryan is out of office and will be back on Monday.

Best

Brian

Hi Ryan & Brian,

Is there any update on my query?

Regards,

Jayanthan V

Hi Jayanthan,

Sorry for the long delay on this.

I took a look a little more at your schematic, and I noticed that there are no load capacitors on your crystal, as per what is recommended on the data sheet and EVM:

This may be affecting the reference clock for this device, which could in turn affect the overall performance of the TUSB9261. If possible, I would recommend adjusting your board to mirror this implementation.

Additionally, I did notice that the GRST pin on our EVM also has a capacitor connected to ground, which would help delay the start-up of this device and allow VDD to ramp up. Maybe that could be implemented to see if that improves performance:

Thanks,

Ryan

Hi Ryan,

I have provided reference clock externally using function generator & also added caps at reset pin.

PID & VID remains the same.

Regards,

Jayanthan V 

Hi Jayanthan,

Just to confirm, the clock you generated was 40MHz and going into the XI pin, and you left XO floating and VSSOSC pulled down to PCB ground, correct?

Another thing you could also test is removing R710 and R711, which connecting to the SPI_DATA_IN/OUT lanes. By removing these, it should disconnect the EEPROM, and we can see if the TUSB9261 embedded memory/boot loader is able to enumerate correctly.

Thanks,

Ryan

Hi Ryan,

Yes, while providing 40MHz clock externally, I made XO pin to float & pulled VSSOSC to ground.

Now, I'll check removing the SPI Lines of EEPROM. 

Thanks,

Jayanthan V

Hi Ryan,

Thanks, TUSB9261 is deducted after removing R710,R711. But I'm unable load the ti hex file file using TUSB Burner.

Thanks,

Jayanthan V

Hi Ryan,

Device was programmed after going through 'sllu125d'. Now SATA isn't detected. 

[ 9643.287313] usb 1-2: new high-speed USB device number 52 using xhci_hcd
[ 9644.243360] usb 1-2: device descriptor read/64, error -71
[ 9645.171328] usb 1-2: device descriptor read/64, error -71
[ 9645.407393] usb 1-2: new high-speed USB device number 53 using xhci_hcd
[ 9646.099191] usb 1-2: device descriptor read/64, error -71
[ 9647.027422] usb 1-2: device descriptor read/64, error -71
[ 9647.135493] usb usb1-port2: attempt power cycle
[ 9647.963295] usb 1-2: new high-speed USB device number 54 using xhci_hcd
[ 9648.272546] usb 1-2: Device not responding to setup address.
[ 9648.479429] usb 1-2: Device not responding to setup address.
[ 9648.687305] usb 1-2: device not accepting address 54, error -71
[ 9649.023266] usb 1-2: new high-speed USB device number 55 using xhci_hcd
[ 9649.200624] usb 1-2: Device not responding to setup address.
[ 9649.407344] usb 1-2: Device not responding to setup address.
[ 9649.615122] usb 1-2: device not accepting address 55, error -71
[ 9649.615262] usb usb1-port2: unable to enumerate USB device
[ 9649.887252] usb 1-2: new high-speed USB device number 56 using xhci_hcd
[ 9650.739294] usb 1-2: device descriptor read/64, error -71
[ 9651.667157] usb 1-2: device descriptor read/64, error -71
[ 9651.903252] usb 1-2: new high-speed USB device number 57 using xhci_hcd
[ 9652.595288] usb 1-2: device descriptor read/64, error -71
[ 9653.523281] usb 1-2: device descriptor read/64, error -71
[ 9653.631377] usb usb1-port2: attempt power cycle
[ 9654.459346] usb 1-2: new high-speed USB device number 58 using xhci_hcd
[ 9654.769565] usb 1-2: Device not responding to setup address.
[ 9654.975396] usb 1-2: Device not responding to setup address.
[ 9655.183197] usb 1-2: device not accepting address 58, error -71
[ 9655.519104] usb 1-2: new high-speed USB device number 59 using xhci_hcd
[ 9655.697941] usb 1-2: Device not responding to setup address.
[ 9655.903361] usb 1-2: Device not responding to setup address.
[ 9656.111334] usb 1-2: device not accepting address 59, error -71
[ 9656.111477] usb usb1-port2: unable to enumerate USB device
[ 9656.383225] usb 1-2: new high-speed USB device number 60 using xhci_hcd
[ 9657.235077] usb 1-2: device descriptor read/64, error -71
[ 9658.163264] usb 1-2: device descriptor read/64, error -71
[ 9658.399100] usb 1-2: new high-speed USB device number 61 using xhci_hcd
[ 9659.091343] usb 1-2: device descriptor read/64, error -71
[ 9660.019098] usb 1-2: device descriptor read/64, error -71
[ 9660.127335] usb usb1-port2: attempt power cycle
[ 9660.955196] usb 1-2: new high-speed USB device number 62 using xhci_hcd
[ 9661.266768] usb 1-2: Device not responding to setup address.
[ 9661.471255] usb 1-2: Device not responding to setup address.
[ 9661.679189] usb 1-2: device not accepting address 62, error -71
[ 9662.019068] usb 1-2: new high-speed USB device number 63 using xhci_hcd
[ 9662.195197] usb 1-2: Device not responding to setup address.
[ 9662.403240] usb 1-2: Device not responding to setup address.
[ 9662.611288] usb 1-2: device not accepting address 63, error -71
[ 9662.611442] usb usb1-port2: unable to enumerate USB device
[ 9662.883302] usb 1-2: new high-speed USB device number 64 using xhci_hcd
[ 9663.735073] usb 1-2: device descriptor read/64, error -71
[ 9664.663216] usb 1-2: device descriptor read/64, error -71
[ 9664.899182] usb 1-2: new high-speed USB device number 65 using xhci_hcd
[ 9665.591211] usb 1-2: device descriptor read/64, error -71
[ 9666.519060] usb 1-2: device descriptor read/64, error -71
[ 9666.627398] usb usb1-port2: attempt power cycle
[ 9667.455164] usb 1-2: new high-speed USB device number 66 using xhci_hcd
[ 9667.764308] usb 1-2: Device not responding to setup address.
[ 9667.971236] usb 1-2: Device not responding to setup address.
[ 9668.179231] usb 1-2: device not accepting address 66, error -71
[ 9668.515174] usb 1-2: new high-speed USB device number 67 using xhci_hcd
[ 9668.692459] usb 1-2: Device not responding to setup address.
[ 9668.899233] usb 1-2: Device not responding to setup address.
[ 9669.107144] usb 1-2: device not accepting address 67, error -71
[ 9669.107296] usb usb1-port2: unable to enumerate USB device
[ 9669.379041] usb 1-2: new high-speed USB device number 68 using xhci_hcd
[ 9670.231284] usb 1-2: device descriptor read/64, error -71
[ 9671.159272] usb 1-2: device descriptor read/64, error -71
[ 9671.395144] usb 1-2: new high-speed USB device number 69 using xhci_hcd
[ 9672.087175] usb 1-2: device descriptor read/64, error -71
[ 9673.015184] usb 1-2: device descriptor read/64, error -71
[ 9673.123359] usb usb1-port2: attempt power cycle
[ 9673.951014] usb 1-2: new high-speed USB device number 70 using xhci_hcd
[ 9674.261566] usb 1-2: Device not responding to setup address.
[ 9674.467037] usb 1-2: Device not responding to setup address.
[ 9674.675133] usb 1-2: device not accepting address 70, error -71
[ 9675.011224] usb 1-2: new high-speed USB device number 71 using xhci_hcd
[ 9675.189699] usb 1-2: Device not responding to setup address.
[ 9675.395030] usb 1-2: Device not responding to setup address.
[ 9675.602992] usb 1-2: device not accepting address 71, error -71
[ 9675.603138] usb usb1-port2: unable to enumerate USB device
[ 9675.875139] usb 1-2: new high-speed USB device number 72 using xhci_hcd
[ 9676.731134] usb 1-2: device descriptor read/64, error -71
[ 9677.655003] usb 1-2: device descriptor read/64, error -71
[ 9677.891127] usb 1-2: new high-speed USB device number 73 using xhci_hcd
[ 9678.590903] usb 1-2: device descriptor read/64, error -71
[ 9679.511233] usb 1-2: device descriptor read/64, error -71
[ 9679.619244] usb usb1-port2: attempt power cycle
[ 9680.447191] usb 1-2: new high-speed USB device number 74 using xhci_hcd
[ 9680.758562] usb 1-2: Device not responding to setup address.
[ 9680.963134] usb 1-2: Device not responding to setup address.
[ 9681.171085] usb 1-2: device not accepting address 74, error -71
[ 9681.511008] usb 1-2: new high-speed USB device number 75 using xhci_hcd
[ 9681.686842] usb 1-2: Device not responding to setup address.
[ 9681.895130] usb 1-2: Device not responding to setup address.
[ 9682.103074] usb 1-2: device not accepting address 75, error -71
[ 9682.103221] usb usb1-port2: unable to enumerate USB device
[ 9682.378939] usb 1-2: new high-speed USB device number 76 using xhci_hcd
[ 9683.231116] usb 1-2: device descriptor read/64, error -71
[ 9684.154952] usb 1-2: device descriptor read/64, error -71
[ 9684.391065] usb 1-2: new high-speed USB device number 77 using xhci_hcd
[ 9685.082905] usb 1-2: device descriptor read/64, error -71
[ 9686.015121] usb 1-2: device descriptor read/64, error -71
[ 9686.123187] usb usb1-port2: attempt power cycle
[ 9686.950929] usb 1-2: new high-speed USB device number 78 using xhci_hcd
[ 9687.255830] usb 1-2: Device not responding to setup address.
[ 9687.463101] usb 1-2: Device not responding to setup address.
[ 9687.671063] usb 1-2: device not accepting address 78, error -71
[ 9688.006916] usb 1-2: new high-speed USB device number 79 using xhci_hcd
[ 9688.183907] usb 1-2: Device not responding to setup address.
[ 9688.394956] usb 1-2: Device not responding to setup address.
[ 9688.602923] usb 1-2: device not accepting address 79, error -71
[ 9688.602984] usb usb1-port2: unable to enumerate USB device
[ 9688.875144] usb 1-2: new high-speed USB device number 80 using xhci_hcd
[ 9689.726878] usb 1-2: device descriptor read/64, error -71
[ 9690.650918] usb 1-2: device descriptor read/64, error -71
[ 9690.887032] usb 1-2: new high-speed USB device number 81 using xhci_hcd
[ 9691.579094] usb 1-2: device descriptor read/64, error -71
[ 9692.510916] usb 1-2: device descriptor read/64, error -71
[ 9692.619145] usb usb1-port2: attempt power cycle
[ 9693.446891] usb 1-2: new high-speed USB device number 82 using xhci_hcd
[ 9693.753202] usb 1-2: Device not responding to setup address.
[ 9693.959179] usb 1-2: Device not responding to setup address.
[ 9694.166822] usb 1-2: device not accepting address 82, error -71
[ 9694.506967] usb 1-2: new high-speed USB device number 83 using xhci_hcd
[ 9694.681346] usb 1-2: Device not responding to setup address.
[ 9694.887063] usb 1-2: Device not responding to setup address.
[ 9695.095076] usb 1-2: device not accepting address 83, error -71
[ 9695.095219] usb usb1-port2: unable to enumerate USB device
[ 9695.370880] usb 1-2: new high-speed USB device number 84 using xhci_hcd
[ 9696.219024] usb 1-2: device descriptor read/64, error -71
[ 9697.147016] usb 1-2: device descriptor read/64, error -71
[ 9697.382829] usb 1-2: new high-speed USB device number 85 using xhci_hcd
[ 9698.078982] usb 1-2: device descriptor read/64, error -71
[ 9699.002826] usb 1-2: device descriptor read/64, error -71
[ 9699.111117] usb usb1-port2: attempt power cycle
[ 9699.947004] usb 1-2: new high-speed USB device number 86 using xhci_hcd
[ 9700.250297] usb 1-2: Device not responding to setup address.
[ 9700.454838] usb 1-2: Device not responding to setup address.

Hi Jayanthan,

Got it, sounds like EEPROM may be an issue then. 

What HEX/BIN are you using to flash the TUSB9261? The firmware that is provided on TI.com? On the TUSB926X flash burner, how does the TUSB9261 appear on there? How does the TUSB9261 appear on TreeView, I.E PID/VID, data speed.

Is there any activity on PWM0 or PWM1?

Thanks,

Ryan

Hi Ryan,

I'm extremely sorry for the delay.

It is working now. R710 need to be removed initially, board was turned on, TUSB was detected in PC, at this time, we shorted R710 manually & dumped the code. after that power was disconnected, 0 ohms assembled at R710 & when board turned ON , TUSB firmware runs from EEPROM. 

Thanks for your support in debugging the issue.

Thanks & Regards,

Jayanthan V