search

NVIDIA-ISAAC-ROS / isaac_ros_common

Common utilities, packages, scripts, Dockerfiles, and testing infrastructure for Isaac ROS packages.
https://developer.nvidia.com/isaac-ros-gems
Other
168 stars 113 forks source link

ZED_Depth_Viewer crashes on Jetson Orin NX (16GB) #123

Open prakharg01 opened 2 months ago

prakharg01 commented 2 months ago

Issue: Encountering crashes when running tools from the ZED SDK within the Nvidia Isaac ROS Docker environment. Suspected mismatch between ZED SDK versions in Dockerfile and required version for ZED Box Orin NX (16GB).

Description: Attempting to set up ZEDX with Nvidia Isaac ROS Docker following the provided documentation (https://nvidia-isaac-ros.github.io/getting_started/hardware_setup/sensors/zed_setup.html). ZEDX driver is functional, but when executing tools from the SDK, consistent crashes occur. Suspected cause may be a discrepancy between the ZED SDK version specified in the Dockerfile (found at https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_common/blob/main/docker/scripts/install-zed-aarch64.sh) and the required version for my hardware (ZED Box Orin NX (16GB)).

Action Needed:

Confirm compatibility between ZED SDK versions specified in Dockerfile and required version for ZED Box Orin NX. If mismatch is confirmed, update Dockerfile to include the required ZED SDK version (ZED SDK for JetPack 5.1.1 (L4T 35.3), version 4.1).

Any help or comments will be appreciated.

prakharg01 commented 2 months ago

Update:

Successfully updated the Dockerfile with the correct SDK version, resolving the previous issue. Added the line wget -q --no-check-certificate -O ZED_SDK_Linux.run https://download.stereolabs.com/zedsdk/4.1/l4t35.3/jetsons to fetch the required SDK version.

However, a warning persists:

[ZED-X][Warning] Failed to connect to zed_x_daemon.
[ZED-X][Warning] Failed to verify the match between the L4T version of the host and the container. If you are indeed in a container, be sure to run the same L4T version on both.

When checking cat /etc/nv_tegra_release within the container, it returns "not found," while in the host, it returns:

# R35 (release), REVISION: 3.1, GCID: 32827747, BOARD: t186ref, EABI: aarch64, DATE: Sun Mar 19 15:19:21 UTC 2023

Despite the successful operation of the tools, the warning persists. Is this something that needs to be addressed?

I ran the ZED_Diagnostic tool, it reports: "No GMSL drivers detected, USB devices wont be affected". My ZEDX uses GMSL, but on the host there is no issue. also L4T version in container is unknown, what could be the issue?