zed-ros-wrapper: ZED not working after boot but replugging it helps on J120 TX2
I have a TX2+J120 carrier board with Logitech USB Camera connected to OTG Micro USB, LTE USB Modem connected to USB3 and ZED connected to the second USB3. Everything work but ZED camera requires me to remove and plug again after every reboot. Do you know what may be the cause of this?
Error before replugging: CAMERA DETECTION ISSUE
Full dmesg log: https://gist.github.com/ArkadiuszNiemiec/88a0116fc53319efc49b205a77b166e3 At around 120 seconds you can see me replugging the ZED camera.
Device found after reboot:
[ 7.858892] usb 1-2: New USB device found, idVendor=2b03, idProduct=f681
[ 7.866362] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.874230] usb 1-2: Product: ZED-M Hid Device
[ 7.879310] usb 1-2: Manufacturer: STEREOLABS
[ 7.884322] usb 1-2: SerialNumber: 10025962
[ 7.889787] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
[ 7.898718] hid-generic 0003:2B03:F681.0001: hidraw0: USB HID v1.11 Device [STEREOLABS ZED-M Hid Device] on usb-3530000.xhci-2/input0
Replugging:
[ 117.945273] usb 1-2: USB disconnect, device number 2
[ 120.021599] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 4
[ 120.028642] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work ignore firmware MBOX_CMD_INC_SSPI_CLOCK request
[ 120.130313] usb 1-2: new full-speed USB device number 6 using xhci-tegra
[ 120.258795] usb 2-1: new SuperSpeed USB device number 2 using xhci-tegra
[ 120.268201] usb 1-2: New USB device found, idVendor=2b03, idProduct=f681
[ 120.274926] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 120.282143] usb 1-2: Product: ZED-M Hid Device
[ 120.286674] usb 1-2: Manufacturer: STEREOLABS
[ 120.291188] usb 1-2: SerialNumber: 10025962
[ 120.296587] usb 2-1: New USB device found, idVendor=2b03, idProduct=f682
[ 120.303389] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 120.310677] usb 2-1: Product: ZED-M
[ 120.314418] usb 2-1: Manufacturer: Technologies, Inc.
[ 120.320239] hid-generic 0003:2B03:F681.0002: hidraw0: USB HID v1.11 Device [STEREOLABS ZED-M Hid Device] on usb-3530000.xhci-2/input0
[ 120.332746] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6
[ 120.343917] uvcvideo: Found UVC 1.10 device ZED-M (2b03:f682)
[ 120.355831] input: ZED-M as /devices/3530000.xhci/usb2/2-1/2-1:1.0/input/input5
So after boot there’s only ZED-M Hid Device. Restarting it did not help:
sudo usb_modeswitch -R -v 2b03 -p f681
or
echo -n "1-2:1.0" > /sys/bus/usb/drivers/usbhid/unbind
echo -n "1-2:1.0" > /sys/bus/usb/drivers/usbhid/bind
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 49 (18 by maintainers)
The fix for the ZED-M detection has been integrated by NVIDIA into the new JetPack 4.2. The TX2 can now reboot with the ZED-M plugged in and it will be detected, like the ZED.
A compatible ZED SDK installer has been released for the TX2.
Since no official fix (or even updates on the issue) has been released I had success with a workaround that involves re building the TX2 kernel, decompiling/recompiling the device tree, removing the vbus regulator and triggering a script with a serviced to turn off and on the USB port on boot up.
For anyone interested on the rough steps, this is the thread on the Nvidia forum USB Power Control
I’m having this issue with the ZED Mini and Jetpack 4.6.
@ArkadiuszNiemiec https://github.com/stereolabs/zed-ros-wrapper/issues/249#issuecomment-453387119
Yes, it comes back after replugging, no problem after. For development it’s OK, we just cannot apply it in production devices.