Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
[*] DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
[*] Linux
QNX
other
Hardware Platform
[*] DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
[*] native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Issue Description
in ref Testing run_cgf_demo on target - #42 by ashwin.nanda specific to Testing run_cgf_demo on target - #46 by SivaRamaKrishnaNV :::
I switched bootchain to B, and tried running the CGF demo samples after installing the .deb files and proceeded with the custom node steps, however, the display was still not accessible.
we powered off/on through the Board’s switch, and as by default it switched to bootchain A.
Now when trying to switch bootchain back to B, I faced the following error string:
Error String
pomo@tegra-ubuntu:/usr/local/driveworks$ common_if_testapp -set_next_bootchain x1 B
DU_MCC_InitResources: Failed to open NvSciIpc endpoint. err is: 0x1100
Failed to initialize IPC resource
Failed to initialize DU MCC
pomo@tegra-ubuntu:/usr/local/driveworks$ common_if_testapp -tegrareset x1
DU_MCC_InitResources: Failed to open NvSciIpc endpoint. err is: 0x1100
Failed to initialize IPC resource
Failed to initialize DU MCC
pomo@tegra-ubuntu:/usr/local/driveworks$
**
When tried to flash the Board again I faced that the Tegra A isnt going to recovery mode:
Flashing DriveOS 6.0.8.1 driveinstaller.log:
driveinstaller.log (105.2 KB)
Tried puitting Tegra A manually in recovery via NvShell, and flashed again, however flashing fails with same logs as above.
Tegra A accessible through ttyACM0
dear @SivaRamaKrishnaNV please note this is important because x11vnc cant detect dispaly as well now:
output from starting x11vnc from ttyACM0
27/11/2024 11:49:01 x11vnc version: 0.9.16 lastmod: 2019-01-05 pid: 2387
27/11/2024 11:49:01 XOpenDisplay("") failed.
27/11/2024 11:49:01 Trying again with XAUTHLOCALHOSTNAME=localhost ...
27/11/2024 11:49:01
27/11/2024 11:49:01 *** XOpenDisplay failed. No -display or DISPLAY.
27/11/2024 11:49:01 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort.
27/11/2024 11:49:01 *** 1 2 3 4
27/11/2024 11:49:05 XOpenDisplay(":0") failed.
27/11/2024 11:49:05 Trying again with XAUTHLOCALHOSTNAME=localhost ...
27/11/2024 11:49:05 XOpenDisplay(":0") failed.
27/11/2024 11:49:05 Trying again with unset XAUTHLOCALHOSTNAME ...
27/11/2024 11:49:05
27/11/2024 11:49:05 ***************************************
27/11/2024 11:49:05 *** XOpenDisplay failed (:0)
*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.
also
pomo@tegra-ubuntu:~$ echo $DISPLAY
pomo@tegra-ubuntu:~$