Part Number: TUSB7340
Hi team,
We are using TUSB7340 in Robotics application.
- Hardware Configuration: SoC -> PCIe -> TI USB host -> 3 USB cameras.
- Upon system startup, a stress test involving continuous video streaming from the three USB cameras was conducted. After approximately 18 hours (the exact duration is unconfirmed, but the issue appears to manifest only after prolonged stress testing), the camera connected to port USB 2-2 stopped outputting frames. Please refer to the logs for kernel error messages. Details of the various test scenarios are attached. Currently, the USB 2-2 port on the TI USB host is suspected to be the cause.
- Test details are as follows:
- Test 1: Three cameras streamed simultaneously; after over two days of stress testing, the camera on port USB 2-2 reported an error (Kernel error: `WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state`) and the FPS dropped to 0.
Analysis: The root cause was unclear; the stress test was repeated. - Test 2: Three cameras streamed simultaneously; after over two days of stress testing, the camera on port USB 2-2 reported an error (Kernel error: `WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state`) and the FPS dropped to 0.
Analysis: The "left camera" failed with 0 FPS in both instances, raising suspicions about the camera itself. Test 3 was conducted. - Test 3: The cameras connected to USB 2-2 and USB 2-3 were swapped, along with their USB cables. After approximately two days of stress testing, the camera on port USB 2-2 again reported an error (Kernel error: `WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state`) and the FPS dropped to 0.
Analysis: Camera and USB cable issues were ruled out. Suspicion shifted to the USB 2-2 port or the PCB circuitry. Since the issue only appears after a long duration, it may be temperature-related. - Test 4: The "MA" board was replaced with an "MB" board (mainboard replacement), while all other conditions remained unchanged. After 14 hours of stress testing, the camera on port USB 2-2 again reported an error (Kernel error: `WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state`) and the FPS dropped to 0.
Relevant kernel log: (kernelMB_6.9.log)
- Test 1: Three cameras streamed simultaneously; after over two days of stress testing, the camera on port USB 2-2 reported an error (Kernel error: `WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state`) and the FPS dropped to 0.
4,49695,51211548032,-;xhci_hcd 0000:02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
SUBSYSTEM=pci
DEVICE=+pci:0000:02:00.0
4,49696,51211549136,-;xhci_hcd 0000:02:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
SUBSYSTEM=pci
DEVICE=+pci:0000:02:00.0
6,49697,51211751735,-;usb 2-2: reset SuperSpeed USB device number 3 using xhci_hcd
SUBSYSTEM=usb
DEVICE=c189:130
6,49698,51211781284,-;uvcvideo 2-2:1.1: Unknown video format 20343159-0000-0010-8000-00aa00389b71
SUBSYSTEM=usb
DEVICE=+usb:2-2:1.1
6,49699,51211781296,-;usb 2-2: Found UVC 1.10 device Orbbec Gemini 215 (2bc5:0808)
SUBSYSTEM=usb
DEVICE=c189:130
6,49700,51211785583,-;usb 2-2: Found UVC 1.10 device Orbbec Gemini 215 (2bc5:0808)
SUBSYSTEM=usb
DEVICE=c189:130
6,49701,51211792801,-;usb 2-2: Found UVC 1.10 device Orbbec Gemini 215 (2bc5:0808)
SUBSYSTEM=usb
DEVICE=c189:130
Test 5: Stress testing the MB (Board 124) using the original three cameras. An issue occurred after approximately 50 hours of stress testing, specifically affecting the camera on usb2-2. (Relevant log: 124_issue/xhci_rootcause_20260608_152520)
Log:
