Xavier USB issue on R32.1 BSP

Hi
Our Carried board have USB can not working issue on R32.1 .
Test processor:

  1. Power on Xavier system and plug-in USB 3.1 SSD(USB device is working ).
  2. Power off system(USB SSD lock on system)
  3. Power on Xavier system and can not find USB SSD(if unplug USB device again and same as fail result) .
  4. remove USB device then power on system.
  5. Plug-in USB device when system ready. USB SSD can be working.

Hi bill_tu,

Is this device able to work well on devkit? Do you have any special design on custom carrier board?
For example, always-on vbus.

dear WWWW.

Yes, USB device can be working on devkit. OUr carried board design please see block diagram and not any special designal .

Bill

block diagram.jpg

Could you share the log with us? Please share the working log and the NG log. Thanks.

dear WWWW.

We had try to use Devkit and find same as issue . So we load fail log from devkit.
BTW, the sytem show time out information(see log) on reboot statn when issue happen.

Bill
fail.log (96.9 KB)

I don’t even see the xusb firmware is up. Could you see the working log to check if below line shows up?

[    8.468300] tegra-xusb 3610000.xhci: Direct firmware load for tegra19x_xusb_firmware failed with error -2
[    8.477954] tegra-xusb 3610000.xhci: Falling back to user helper
[   10.347277] tegra-xusb 3610000.xhci: cannot find firmware....retry after 1 second
[   11.357041] tegra-xusb 3610000.xhci: Firmware timestamp: 2018-03-29 14:24:42 UTC, Version: 60.05 release
[   11.357083] tegra-xusb 3610000.xhci: xHCI Host Controller
[   11.357104] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[   11.357922] tegra-xusb 3610000.xhci: hcc params 0x0184ff25 hci version 0x110 quirks 0x00050810
[   11.357954] tegra-xusb 3610000.xhci: irq 472, io mem 0x03610000

Could you also share the result of lsusb -t when NG case?

Dear WWW.

attach file is USB working state logo file (power on then plug in USB device). lsusb -t connamd show none any USB device on fail state . 

Bill
pass.log (79.7 KB)


Hi bill_tu,

Are you sure this “pass.log” is the successful log? I don’t see any usb device that has been detected in dmesg.

Your issue sounds like another issue we just met.
https://devtalk.nvidia.com/default/topic/1056193/

Could you take as a reference and check your vbus?

dear WWW.

For this issue, we try to use USB flash and USB external Box(PCIE SSD to USB box) .For USB flash have working on reboot state but USB external box haven't working on reboot . have different of those USB device? 

BTW, our current carried board use USB hub(TUSB8020B) and ths hub chip fail siganl when plug USB 2.0 device have you recommand USB hub chip can be working on Xavier?
USB external box
https://24h.pchome.com.tw/prod/DRAH6S-A9009C3PL?fq=/S/DRAH6S

If this issue can be reproduced on devkit, I would think it is another issue instead of the vbus issue. Would you mind sharing the failure log (bootloader + kernel log)?

Hi bill_tu,

Have you clarified the cause and resolved the problem?
Any result can be shard?

Thanks

KayCCC.
No, the problem was open. we was check external USB box and find use same JMS583 chip (PCIE to USB3). This is keep point for it?

Bill

If this is still an issue, could you help re-summarize the case here? It has been almost a month w/o any update.

dear WayneWWW.

We have use M.2 NVME external SSD to running USB3.1(10G) speed and it is working fine. But USB device was not working and wasn't find it after reboot system. We had try to use USB type C and Type A port as smae issue.

M.2NVME SSD box :https://www.pcstore.com.tw/digifusion/M44980763.htm

Bill

Hi,

Then when did it come to work? You need to hotplug the usb device?

Could you share the dmesg of failure case? Is it on devkit?

WayneWWWW.

 we try to use on devkit and same as issue . When issue happen , we remove USB ddevice and reboot again then plug in USB device . It is working fine  .

Bill

Hi Bill,

Why do you need “reboot” to make device back? Does the system hang? Could you share the failure log?

WayneWWW.

Beacuse our manfaceture function test need to reboot state while all device plug in state.
pass.log (79.7 KB)
fail.log (96.9 KB)

Hi Bill,

Beacuse our manfaceture function test need to reboot state while all device plug in state.

Could you elaborate more about when is your device working and when is not?
It sounds that this issue is sometimes reproducible and sometimes not.

I mean, how do you make your device work? You said it has failure after reboot. Then, how do you make it work? Hotplug the device?