-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZED not working after boot but replugging it helps on J120 TX2 #249
Comments
Porblem was solved for me after message "CAMERA DETECTION ISSUE" by flipping the usb -C connector 180degree and plugging it in again. BUT YOU DEFINITELY SHOULD FIX THAT IN THE FIMRWARE OR SOMEWERE OR AT LEAST GIVE CLEAR INSTRUCTIONS. FOund it only accidentially in the zed diagnotics tool where it says "flip or use usb3.0 port" |
I have the exact same issue on a Jetson tx2, on boot up the camera does not work, but re connecting it solves the problem, however some time it takes more than one try. |
@plieningerweb it's true but it's also not the problem I described. |
@ArkadiuszNiemiec I am using a Jetson TX2 Developer Kit. |
@molinadavid thanks, I was worried that it is the problem of my J120 carrier board. |
@ArkadiuszNiemiec I can also confirm that is not a specific board, I have 7 different kits all present the same problem, also can confirm that this problem is only on the ZED-mini, I have also ZED normal type (the big one) and this problem does not happen. |
This problem occurs too in a regular windows pc. Have tried both firmware 14xx & 15xx, but still, no camera detected and replugging the camera sometimes fixes it. |
Ok, so this is a general problem with ZED Mini, I will forward this issue to their tech support email. |
We were able to consistently reproduce the issue on Jetson and are looking for a software solution. |
@nesnes Good news, thank you! Please keep us updated if you will find a fix. |
@ArkadiuszNiemiec Removing the power cord from the hub the problem remains. That is a good USB3 HUB for ZED because it has a very short USB cable |
@nesnes However, we appreciate your efforts on it, and are waiting for a real fix. |
Hi @Myzhar, Is there any update on this issue ? I also managed to reproduce it (jetson tx2 dev kit + ZED-M, classical ZED works fine at boot) and unfortunately the powered usb 3.0 is not a working solution for me :( ! |
@Wagdi-Benyaala the HW team is working on it. Stay tuned to further information |
Thanks a lot for the fast answer ! |
We found we were able to adjust the "USB Power Delay" BIOS setting on our mini-ITX motherboard to 5 seconds to solve some of these issues. |
@Myzhar |
@jonpol01 We are discussing with the Nvidia Embedded department to find a solution for this problem (maybe a kernel patch). We will update as soon as possible |
@Myzhar any updates? |
The bug is in process in NVIDIA since this is related to the Jetpack boot configuration. Sorry for the inconvenience but we don't have the full control on the Jetpack. |
@obraun-sl @Myzhar |
@jonpol01 I can confirm what you wrote. Ubuntu 18.04 on Mi Notebook Pro 15" - same problem but solving it on TX2 will be enough for me. Edit: missclicked 😞 |
Yes, it comes back after replugging, no problem after. For development it's OK, we just cannot apply it in production devices. |
Thanks @ArkadiuszNiemiec. Big relief to know that 👍 |
Any update on this issue? |
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 fond that launching the Zed Explorer (which doesn't require CUDA) will fix this problem without disconnecting and reconnecting. I'm using Ubuntu 16.04, on an X86_64 pc. #!/bin/bash |
The fix for the ZED-M detection has been integrated by NVIDIA into the new JetPack 4.2. A compatible ZED SDK installer has been released for the TX2. |
I wouldnt consider it a fix, since Jetpack 4.2 reflashes your tx2 system into ubuntu 18.04. However we did a workaround with the help from Nvidia guys on the developer forums to fix this ugly Zed mini hardware fault. btw, stereolabs developers sucks on support and addressing this issue publicly. We are considering lawsuits for this false advertising. "that it works on Ubuntu linux(jetpack and Zed sdk version from summer 2018 to this date) without doing workarounds on the dtb(which we solved for you guys)" |
@jonpol1 can you post a link to forums, where the problem was discussed? |
@jonpol01 I understand you're not happy that the fix requires you to update your Jetson to the new Jetpack 4.2 (which is based on Ubuntu 18). Nvidia will also backport the fix to JetPack 3.X, so that it does not require to rebuild the Jetpack. |
Can someone test it so I can close this issue? My TX2 is currently without a carrier board. |
I have tested the current Jetpack 3.3 and can confirm that Jetpack 3.3 as of today, May 3rd 2019, does not fix this bug. |
You can try to add a rule in your system |
@tomcattigerkkk
this fix did not work for me. i also tried the following variations: with reboot each time in between the changes. is there anything that i might've missed? ubuntu@tegra-ubuntu:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2b03:f681
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub |
@rhklite |
Is there any news of this being backported to earlier Jetpack versions? Will it be necessary to reflash the TX2 or can the fix be applied through a software upgrade? |
@cosama if the fix has been backported to older Jetpack versions a reflash is anyway required |
there is a workaround for this issue: use an external supplied usb cable (hope this information is useful for somebody) |
I'm having this issue with the ZED Mini and Jetpack 4.6. |
Same here ZED mini Jetpack 4.6 need to replug it everytime to get it working is there a workaround for this ? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment otherwise it will be automatically closed in 5 days |
Issue observed on Xavier NX on Auvidea JNX30 carrier board with Jetpack 5.0.1 and ZEDSDK 3.7 |
Also observed for the Seeedstudio A206 carrier with Jetpack 5.0.2 and ZEDSDK 3.8. |
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:
Replugging:
So after boot there's only
ZED-M Hid Device
. Restarting it did not help:or
The text was updated successfully, but these errors were encountered: