Nvgetty udev issues between ZED SDK and UART GPS how to resolve?

[linuxdev]

@FGR_Mike

[ 3689.277206] tegra-xusb-padctl 7009f000.xusb_padctl: power down UTMI pad 1
[ 3689.277229] usb 1-2: USB disconnect, device number 7
[ 3689.277233] usb 1-2.2: USB disconnect, device number 8
[ 3689.279333] soctherm: OC ALARM 0x00000001
[ 3690.018903] usb 2-1: USB disconnect, device number 3
[ 3690.202932] usb usb2: usb_suspend_both: status 0
[ 3702.529899] tegra-xusb-padctl 7009f000.xusb_padctl: power on UTMI pads 1

Was the above purely from plugin? I’m wondering if using an externally powered HUB might help.

What do you see from the verbose lsusb listing (this logs)?
sudo lsusb -vvv -d 2b03:f881 2>&1 | tee log_lsusb_2b03-f881.txt
(note that log files are superior because I can see the entire log on the monitor without a horizontal scrollbar)

That is only part of the device, and so this is the other part (devices f881 and f880 are independent, but use the same USB cable)
sudo lsusb -vvv -d 2b03:f880 2>&1 | tee log_lsusb_2b03-f880.txt

I see at least part is UVC (a standard video driver which comes with USB, but is really just a camera driver despite it being associated with USB). I also see this include HID, which is no doubt part of the control. Camera and control would be separate programs even though they work together. Each could work or fail independently. It is the camera part which consumes a lot of power and is why an externally powered HUB is a good test (in addition to padctl logs as a reason).

As far as I can tell this works, with the exception of overcurrent (OC). I think the bus can’t supply enough power. Not being able to connect could be a result of insufficient power shutting something down. The diagnostic software “Camera not detected” log, in combination with the device showing up initially in lsusb, tends to say it is likely a power delivery issue.

[FGR_Mike]

There is no powered hub, the ZED is powered by the Jetson, which is powered by a 5V 3A regulator.

The log files are attached:
log_lsusb_2b03-f881.txt (14.8 KB)
log_lsusb_2b03-f880.txt (10.5 KB)

I am not sure I can tell anything wrong from these log files.

According to the ZED2i data sheet

It only requires 380mA at 5V. And the Jetson is capable of supplying a max of 1A via the USB 3.0 connector.

So it seems perhaps, power is not the issue?

[linuxdev]

@FGR_Mike

There is no powered hub, the ZED is powered by the Jetson, which is powered by a 5V 3A regulator.

Can you test with an externally powered USB HUB? Even if the camera does not use “a lot” of power the previous logs do make me wonder if power is an issue, and it is perhaps the easiest of all tests. Not using a “lot” of power won’t be enough to say for sure when bus powered since other parts also consume power from the same bus (it is cumulative).

The logs of verbose lsusb indicate no issue with USB. It seems there is no “direct” software issue for the USB part of this. This leads me back to wanting to try the externally powered HUB since power issues are common, especially with cameras.

[FGR_Mike]

Hi @linuxdev ,

The problem was that the bluez 5.48 was using the same interface as the Zed and upgrading bluez to 5.52 my manually making it resolved this issue. We have tested for days and it is stable, there are no power issues with the Zed2i plugged directly into the USB3 of the Jetson nano.