No Display while running Custom_CGF

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

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

SDK Manager Version
2.1.0
[*] 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
While running the custom_cgf which is made according to Testing run_cgf_demo on target - #20 by SivaRamaKrishnaNV we are facing the issue of Display. There is Black Screen while running the script and it doesn’t come out of it(i.e. we have to poweroff the target board as it becomes inaccessible)

Logs
We have attached the log of the issue over here
LogFolder.zip (115.2 KB)

2

We’ve also tried the same process with adding --offscreen=1 in the run_cgf_demo.sh script and the launcher exit status code is 0 in that case. I have attached that Log file in this post
LogFolder.tar.gz (2.3 MB)

4

Dear @prit.shah,
So, you notice the same display issue on both the bootchains with VNC and physical display as well? As mentioned earlier, I don’t see any issue with VNC. I will check with physical display next week and update you my observation.

5

Dear @SivaRamaKrishnaNV ,

Thanks for working with physical display we will look forward hearing from you.

We have checked on both bootchains with the physical display and the result is same (no display). We have checked with VNC on bootchain A but not with B. We are not looking to check with display i.e. we will running cgf script by adding --offscreen =1 line in script until the issue of display is solved.

6

@SivaRamaKrishnaNV Please look at this DRIVE OS 6.0.8.1 Linux Release Notes

Does the bellow help us understand the issue?

image
image864×797 71.2 KB

7

Dear @SivaRamaKrishnaNV ,
Could you please provide an update on your observations with the physical display?

8

Dear @SivaRamaKrishnaNV ,

Can we have an update on this?

10

Dear @SivaRamaKrishnaNV ,

Can we have any update on this please?

11

Dear @prit.shah ,
I also notice blank screen and launcher exit status : 33 when running CGF with customer nodes. This looks like a bug. Unfortunately, this app is not maintained in next release(DRIVE OS 6.0.10 onwards).

1 Like
12

Hi @SivaRamaKrishnaNV thank you so much confirming this, this helps a lot. When you say this app is not supported in the next release, do you want us to test running the custom nodes on the new sample CGF application on Driveworks 5.20?

If I reckon, we did try moving to 5.20, but couldnt run the CGF sample itself.
wrt to your reply we had moved to 5.14 :
ref : Testing run_cgf_demo on target - #16 by SivaRamaKrishnaNV

please do let me know how we create a custom pipeline then? (with display)

13

Dear @prit.shah ,
Please try adding custom nodes to minipipeline application.

15

Dear @SivaRamaKrishnaNV ,

We are facing the issues when we are running minipipeline script by adding custom nodes to it .

sudo ./run_mini_pipeline.sh
20250106_145314
20250106_145314
DW_TOP_PATH=/usr/local/driveworks
SAMPLE_TOP_PATH=/usr/local/driveworks/apps/minipipeline
CGF_SYS_PATH=
SMP_LOG_PATH=/usr/local/driveworks/apps/minipipeline/LogFolder
DATA_PATH=/usr/local/driveworks/data/samples/minipipeline/dataset
Current DISPLAY is :1
|--> Tuning message queue
|--> Tuning network stack
LD_LIBRARY_PATH: :/usr/local/driveworks/lib
/usr/local/driveworks/apps/minipipeline/LogFolder dir exists
total 72
drwxr-xr-x. 6 root root  4096 Jan  6 14:52 .
drwxr-xr-x. 5 root root  4096 Nov 28 14:01 ..
drwxr-xr-x. 2 root root  4096 Jan  6 14:20 LogFolder
-r-xr-xr-x. 1 root root 33190 Jan  6 14:08 MiniPipeline__standardSchedule.stm
-r-xr-xr-x. 1 root root 11532 Jan  6 14:08 MiniPipeline__standardSchedule.yaml
drwxr-xr-x. 2 root root  4096 Jan  6 14:49 applications
drwxr-xr-x. 2 root root  4096 Jan  6 14:50 graphlets
drwxr-xr-x. 2 root root  4096 Jan  6 14:04 nodes
Running command: /usr/local/driveworks/bin//launcher --binPath=/usr/local/driveworks/bin/ --spec=/usr/local/driveworks/apps/minipipeline/applications/MiniPipeline.app.json --logPath=/usr/local/drivework>
Check if reset NetworkStack needed
Restore LD_LIBRARY_PATH to
=======================================================================
launcher exit status: 217

Please find the Logfolder and files for your reference
LogFolderMini.tar.gz (49.5 KB)
minipipeline.tar.gz (169.9 KB)

NOTE: we are running this script by --offscreen=1 in it.

16

Dear @prit.shah ,
Can you please file a new topic for minipipeline sample?

19

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.