NvRos testing

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.6.0.8170
other

Host Machine Version
native Ubuntu 18.04
other

I went through the NvRos document but when trying the test applications I found many errors.

For the first test (test_nvros_sipl)

image
image729×347 57.9 KB

image
image725×343 66.5 KB

I can’t find further information about these errors in the documentation. what am I doing wrong?

3

Hi @jber4282,

I didn’t see the error messages. Below is what I ran after installed the prerequisite packages. FYI.

  • In one shell:

nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated/bin$ cd /opt/nvidia/nvros/install_isolated
nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated$ source setup.bash
nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated$ roscore &
[1] 10366
nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated$ … logging to /home/nvidia/.ros/log/7b5c448a-10e7-11ec-8d06-00044ba4e4d1/roslaunch-tegra-ubuntu-10366.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://tegra-ubuntu:45261/
ros_comm version 1.14.3

SUMMARY

PARAMETERS

  • /rosdistro: melodic
  • /rosversion: 1.14.3

NODES

auto-starting new master
process[master]: started with pid [10376]
ROS_MASTER_URI=http://tegra-ubuntu:11311/

setting /run_id to 7b5c448a-10e7-11ec-8d06-00044ba4e4d1
process[rosout-1]: started with pid [10389]
started core service [/rosout]

nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated$ test_nvros_egl_utils_consumer -d 0 -w 0 -s /tmp/nvros_cam_0
[ INFO] [1631134963.358544192]: Display Id : 0

[ INFO] [1631134963.358732352]: Window Id : 0

[ INFO] [1631134963.358770688]: EGLStream socket_path : /tmp/nvros_cam_0

[ INFO] [1631134963.473601120]: EGLStreamSendfd: sock_fd: 30

[ INFO] [1631134963.476410656]: Waiting for EGL stream producer

[ INFO] [1631135051.488148832]: EGL Stream consumer - Latency: 16000 usec

[ INFO] [1631135051.488284512]: EGL Stream consumer - Timeout: 16000 usec

  • In another shell:

nvidia@tegra-ubuntu:~$ cd /opt/nvidia/nvros/install_isolated
nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated$ source setup.bash
nvidia@tegra-ubuntu:/opt/nvidia/nvros/install_isolated$ test_nvros_sipl
[ INFO] [1631135051.359700704]: EGLStreamReceivefd: listen_fd: 29

MAX96712: Revision 2 detected
MAX96712: Enable periodic AEQ on Link 0
MAX96705: Pre-emphasis set to 0xaa
MAX96705: Revision 1 detected!
Sensor AR0231 RCCB Rev7 detected!
Module_id 22 Severity 6 : NvMediaICPCreateEx 76
Module_id 22 Severity 6 : T19x VI version 0x000019

4

Hi @VickNV

I re-flashed the machine and I had the same output. I’m having trouble with gdm3 as I can’t see anything on the screen. But when running those commands I could see the camera image on the connected monitor. I went through the documentation I’d think some parts are missing e.g. what’s the expected output for each of the commands, what’s the meaning of the input arguments, etc.

5

Is the origin problem clarified?
The source code is available in the installed directory. You may take a look at it to understand the applications included.

6

I still sometimes can see the error shown in the first post. what’s the meaning of this error?

9

It’s due to too many timeouts from retrying NvMediaEglStreamProducerGetImage() call.
You have source access so you can check it to know the detail.

10

Hi @VickNV

The original error only appears when I have gdm3 running, otherwise the screen would show the camera image, is there anyway to display the camera image when gdm3 is running?

11

Maybe you can stop it temporarily.

sudo service gdm3 stop
<run sample>
sudo service gdm3 start

12

Hi @VickNV , it doesn’t solve the issue

13

Dear @jber4282,

That means, you had no issue before installing gdm3 for setting up monitor display? After enabling monitor display, you see the issue? Could you double check the gdm3/display status after running above commands?

14

Hi @SivaRamaKrishnaNV , After stopping gdm3 as suggested I still can see the display I tried
sudo systemctl stop gdm3 but the display is still on.

nvidia@tegra-ubuntu:~$ systemctl status display-manager
��ᗏ gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabl
   Active: inactive (dead) since Thu 2021-09-23 16:01:42 AEST; 3min 59s ago
  Process: 1215 ExecStart=/usr/sbin/gdm3 (code=exited, status=0/SUCCESS)
 Main PID: 1215 (code=exited, status=0/SUCCESS)

Sep 22 17:03:30 tegra-ubuntu systemd[1]: Starting GNOME Display Manager...
Sep 22 17:03:30 tegra-ubuntu systemd[1]: Started GNOME Display Manager.
Sep 22 17:03:30 tegra-ubuntu gdm-autologin][1333]: gkr-pam: no password is avail
Sep 22 17:03:30 tegra-ubuntu gdm-autologin][1333]: pam_unix(gdm-autologin:sessio
Sep 23 16:01:42 tegra-ubuntu systemd[1]: Stopping GNOME Display Manager...
Sep 23 16:01:42 tegra-ubuntu gdm3[1215]: GLib: g_hash_table_find: assertion 'ver
Sep 23 16:01:42 tegra-ubuntu systemd[1]: Stopped GNOME Display Manager.