Unable to access system after disabling gdm for nvsipl_camera

Please provide the following info (tick the boxes after creating this topic):
Software Version
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
1.9.3.10904
[*] 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

Hi,
I am trying to interface the camera sensor Entron F008A120RM0A with my Orin system and referring the steps mentioned in the link “Camera Setup”.
As soon as I executed the below commands the display connected with the system got terminated. I am unable to access X Terminals using CTRL+FX keys as well.

systemctl disable gdm 
systemctl stop gdm

Dear @PA_GN ,
I am assuming you want to run nvsipl_camera . Could you check launching nvsipl_camera from an ssh session and see if it works?
If you want GUI back, can you check start/enable gdm from ssh session. Also, see if rebooting fixes the issue.

Hi SivaRamaKrishnaNV,

Yes it works by logging from an ssh session.

Now for camera streaming I followed the instructions mentioned in the links Camera Setup but face errors like -
nvsipl_camera: ERROR: NvSIPLCamera Init failed

nvsipl_camera: ERROR: Master initialization failed. status: 10
Attaching the complete logs for reference.
Camera Model is - F008A120RM0A and connect on PORT A
**
camera_sensor_error_logs.txt (40.8 KB)
**

Dear @PA_GN,
Could you check changing command to use 0001/0010/0100/1000 indexes for port A in link-enable-masks to confirm if it is not an issue with camera connection. Also, could you first try without display(d) parameter.

Hi @SivaRamaKrishnaNV ,

I tried changing the commands as you suggested but still see the same error. Attaching logs for commands with d param and without d param.
Commands tried :

a) sudo ./nvsipl_camera --platform-config “F008A120RM0AV2_CPHY_x4” --link-enable-masks “0x0001 0x0000 0x0000 0x0000” -d 1 -v 4
b) sudo ./nvsipl_camera --platform-config “F008A120RM0AV2_CPHY_x4” --link-enable-masks “0x0001 0x0010 0x0100 0x1000” -v 4 -d 1
c) sudo ./nvsipl_camera --platform-config “F008A120RM0AV2_CPHY_x4” --link-enable-masks “0x0001 0x0010 0x0100 0x1000” -v 4

camera_sensor_error_logs_with_d_param.txt (89.2 KB)
camera_sensor_error_logs_without_d_param.txt (83.2 KB)

Dear @PA_GN,
Is it connected on A0? May I know how you have confirmed it?
I have suggested to use link-enable-masks “0x0001 0x0000 0x0000 0x0000 (maps A0) link-enable-masks “0x0010 0x0000 0x0000 0x0000(maps A1) link-enable-masks “0x0100 0x0000 0x0000 0x0000(maps A2)
link-enable-masks “0x1000 0x0000 0x0000 0x0000(maps A3)`.

Can you share the camera module picture and camera port connection pictures to confirm.

Hi @SivaRamaKrishnaNV,

Yes it is connected on A0. We tried to connect on other ports like A1, A2 and A3 but still observe the same error output.
We referred to this connection diagram to confirm connected on A0.

image

We tried to connect on port C3 and still observe the issue.

Dear @PA_GN,
As asked, could you share the camera module picture to confirm? Also, is there any reason to use DRIVE OS 6.0.6 instead of DRIVE OS 6.0.8.1?

Let me check internally on this issue and get back to you.

Hi @SivaRamaKrishnaNV,

As the SDK Manager was easily available to install in comparison to Docker containers for 6.0.8 we used 6.0.6 over 6.0.8. Is it required to upgrade to 6.0.8 or the issue is fixed in 6.0.8?

Hi @SivaRamaKrishnaNV,

I tried with 6.0.8 SDK but still see the same issue. Attaching the logs for reference.
camera_sensor_error_logs_6_0_8_port_c3_with_d_param.txt (51.1 KB)

Also, it is observed that in 6.0.8 wifi is not able to connect; seems to be due to wifi support disabled as I get No Wi-Fi Adapter Found in Settings page on Orin Board. Just wanted to confirm is the WiFi support disabled in default image of 6.0.8?

Yes. Wifi is not supported

Hi @SivaRamaKrishnaNV ,

Is there any update on the camera module issue?

Dear @PA_GN,
The camera module is expected to work. The error indicates, camera is not failed to initialize. It could be either be not connected properly or some other reason. Could you restart the target(either poweroff/poweron from aurix or common_if_testapp -mcureset ) and check running sudo ./nvsipl_camera -c F008A120RM0AV2_CPHY_x4 -m "0x0001 0 0 0" --showfps -d 1 .

If you notice issues, please share the application log and syslog.

Also, just confirming if the camera ever worked? Just make sure the link label on connector maps to correct link in the port.
In port A, top left link is mapped to A0.
Do you have any other camera module to confirm if the issue is specific to this camera.

Also, what’s is the board type and part number. We noticed camera issues when wrong board type is selected during flashing. Please check DRIVE Platform Supported Boards | NVIDIA Docs .

Did you flash the board with docker or sdkmanager. Please check if the board type matches in flashing logs.

Please update us about the above suggestions to narrow down the issue.

Hi @SivaRamaKrishnaNV,

The camera module worked now. It seems to be due to loose connection.
Thanks a lot for your support.

My part number from the invoice I know is 940-63710-0010-100 for platform p3710.
Can you please help me with below details :
a) Is there any command to identify the part number apart from looking the details embossed on the system. As the details are not viewable so just want to confirm.
b) Is there any command to capture the camera frames in encoded / YUV / RAW format?

Dear @PA_GN,
Glad to see the route cause is identified.
See DRIVE Platform Supported Boards | NVIDIA Docs to identify board number. There is no command.
A table is given at DRIVE Platform Supported Boards | NVIDIA Docs to map P/N to board variant.

Please check the needed commandline paramters from Command Line Switches | NVIDIA Docs. Please see the usage of -f , enableRawOutput and disableISP0Output

Please file a new topic to avoid cluttering of topics as the original issue is addressed.

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