Access problem of gmsl camera from Xavier A

I have a problem to access the gmsl camera from XavierA in my AGX Pegasus.
I can access gmsl camera from XavierB using sample_camera_gmsl_raw, but met an error on XavierA side.

I get the following error:

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_camera_gmsl_raw
[18-09-2019 09:53:32] Platform: Detected DDPX - Tegra A
[18-09-2019 09:53:32] Initialize DriveWorks SDK v2.0.2081
[18-09-2019 09:53:32] Release build with GNU 4.9.4 from heads/buildbrain-branch-0-g36b127f against Drive PDK v5.1.0.2
[18-09-2019 09:53:32] TimeSource: monotonic epoch time offset is 1568764756806178
[18-09-2019 09:53:32] PTP Time is available from NVPPS Driver
[18-09-2019 09:53:32] Platform: number of GPU devices detected 2
[18-09-2019 09:53:32] Platform: currently selected GPU device discrete ID 0
[18-09-2019 09:53:32] SDK: Resources mounted from /usr/local/driveworks-2.0/data/
[18-09-2019 09:53:32] SDK: Create NvMediaDevice
[18-09-2019 09:53:32] SDK: use EGL display as provided
[18-09-2019 09:53:32] Initialize DriveWorks VisualizationSDK v2.0.2081
[18-09-2019 09:53:32] Initialize DriveWorksGL SDK v2.0.2081
[18-09-2019 09:53:32] SensorFactory::createSensor() -> camera.gmsl, output-format=raw+data,camera-type=ar0231-rccb-bae-sf3324,camera-group=a,format=raw,fifo-size=3,slave=0
[18-09-2019 09:53:32] CameraGMSL: Create NvMediaIPPManager
[18-09-2019 09:53:32] CameraGMSL: required FPS = 30, resolution = 1920x1208
nvmedia isc: IscPwrCtrlInit: 939: Camera power control library: NVCCP
receive_from: Timeout Error.
Please check Ethernet ip configuration or
Update Aurix firmware version by the following command

sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update

receive_from: Timeout Error.
Please check Ethernet ip configuration or
Update Aurix firmware version by the following command

sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update

nvmedia isc: NvccpCamPowerControl: 534: NVCCP command failed with ret NVCCP_REQ_TIMEOUT
iscRootDevOpen: Failed to request ownership
NvMediaISCRootDeviceCreate: Unable to open root device
nvmedia: ERROR: Init: Failed to create NvMedia ISC root device
[18-09-2019 09:53:42] Driveworks exception thrown: DW_SAL_CANNOT_CREATE_SENSOR: CameraGMSL: cannot connect to camera

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2019-09-18 09:53:42] DW Error DW_SAL_CANNOT_CREATE_SENSOR executing DW function:
dwSAL_createSensor(&m_camera, params, m_sal)
at /dvs/git/dirty/gitlab-master_av/dw/sdk/samples/sensors/camera/camera_gmsl_raw/main.cpp:178
Aborted (core dumped)

I tried to run ‘sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update’ but I get the following error.

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update
starting Aurix FW checking…
Checking arguments…
No_Response_From_Aurix

!!! IMPORTANT INFORMATION BELOW REGARDING Aurix FW (PLEASE READ) !!!

No response from Aurix FW. It seems
vlan iface not configured properly
Please check your nv_tacp_init systemd service

THIS MESSAGE WILL CONTINUE TO BE SHOWN UNTIL ACTION MENTIONED IS TAKEN
With action taken, this script will be muted and not shown again

I also use minicom to connect to aurix via usb cable, and get the following version information:

shell> version
Info: Executing cmd: version, argc: 0, args:
SW Version: DRIVE-V5.1.0-E3550-EB-Aurix-ForHyperion-3.02.07
Compilation date: Apr 2 2019, 14:40:07
Command Executed

I’m not sure where the problem is and how to solve it.

Best Regards,
Liang

Dear Liang,
Could you please check the following.

  • Check if camera connected to A0 port and verify if the camera has any issue by connecting to other board
  • Hard reboot of system and check if the symtom persists
  • Check aurixreset on aurix console and hardreboot the board and share ifconfig output if it did not help

Thanks so much for the reply.
My problem is fixed by aurixreset on aurix console.

It seems that this symtom occurs after I connected the external internet LAN cable to Dongle channel A of front panel 1GbE/100MbE Port3&4.

When I remove the external internet LAN cable and restart, it will be fixed.

Is it because of wrong network settings? I used the default settings after flash.

Dear Liang_Qi,
Could you check if the issue reproduces now. If so, please share ifconfig outputs before the issue and after the issue occurs.

Dear Liang_Qi,
I do not see any issue when I connected LAN to Dongle channel A of front panel 1GbE/100MbE Port3&4.

Sorry for my late reply. I couldn’t access the internet from my Xavier.
The ifconfig outputs are as followings:

Before the issue (LAN cable is not connected)

nvidia@tegra-ubuntu:~$ ifconfig
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:106

can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:512 (512.0 B) TX bytes:0 (0.0 B)
Interrupt:107

enp4s0 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:1b
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet6 addr: fe80::204:4bff:fecb:ce18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:364 errors:0 dropped:0 overruns:0 frame:0
TX packets:827 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:27109 (27.1 KB) TX bytes:63894 (63.8 KB)
Interrupt:82

eth0:400 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:82

eth0:900 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:10.1.0.81 Bcast:10.1.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:82

eth0.200 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:10.42.0.28 Bcast:10.42.0.255 Mask:255.255.255.0
inet6 addr: fe80::204:4bff:fecb:ce18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:164 errors:0 dropped:0 overruns:0 frame:0
TX packets:220 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11371 (11.3 KB) TX bytes:16299 (16.2 KB)

hv0 Link encap:Ethernet HWaddr 0a:86:4c:f8:e8:00
inet addr:192.168.10.4 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::886:4cff:fef8:e800/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:292 (292.0 B) TX bytes:7192 (7.1 KB)
Interrupt:11

hv1 Link encap:Ethernet HWaddr 0a:86:4c:f8:e9:00
inet addr:192.168.12.4 Bcast:192.168.12.255 Mask:255.255.255.0
inet6 addr: fe80::886:4cff:fef8:e900/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:292 (292.0 B) TX bytes:6992 (6.9 KB)
Interrupt:12

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:8468 (8.4 KB) TX bytes:8468 (8.4 KB)

After the issue (LAN cable is connected)

nvidia@tegra-ubuntu:~$ ifconfig
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:106

can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:342 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:2736 (2.7 KB) TX bytes:0 (0.0 B)
Interrupt:107

enp4s0 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:1b
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:172.25.6.73 Bcast:172.25.7.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
RX packets:4921 errors:0 dropped:268 overruns:0 frame:0
TX packets:2875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:330674 (330.6 KB) TX bytes:212513 (212.5 KB)
Interrupt:82

eth0:400 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
Interrupt:82

eth0:900 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:10.1.0.81 Bcast:10.1.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
Interrupt:82

eth0.200 Link encap:Ethernet HWaddr 00:04:4b:cb:ce:18
inet addr:10.42.0.28 Bcast:10.42.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
RX packets:291 errors:0 dropped:0 overruns:0 frame:0
TX packets:362 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17481 (17.4 KB) TX bytes:26213 (26.2 KB)

hv0 Link encap:Ethernet HWaddr 0a:86:4c:f8:e8:00
inet addr:192.168.10.4 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::886:4cff:fef8:e800/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:292 (292.0 B) TX bytes:10658 (10.6 KB)
Interrupt:11

hv1 Link encap:Ethernet HWaddr 0a:86:4c:f8:e9:00
inet addr:192.168.12.4 Bcast:192.168.12.255 Mask:255.255.255.0
inet6 addr: fe80::886:4cff:fef8:e900/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:292 (292.0 B) TX bytes:10458 (10.4 KB)
Interrupt:12

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:151 errors:0 dropped:0 overruns:0 frame:0
TX packets:151 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:12772 (12.7 KB) TX bytes:12772 (12.7 KB)

Dear Liang_Qi,
If internet is not working, could you check running sudo service network-manager restart

Dear Liang_Qi,
ANy update on the issue?

After restart, the issue still exists.

  1. I tried the following commands from XavierA, but none of them got some response.
  2. Then I excecute [sudo service network-manager restart] without LAN cable connection, still none of them got some response.
  3. Then I shutdown Pegasus, and Power on without LAN cable connection. This time I can get response with following ping commands.

ping 10.42.0.146
ping 10.42.0.29
ping 192.168.1.203
ping 10.1.0.82

Dear Linag_Qi,
It is confusing. Do you have issue with network connectivity or camera?
I have flashed my board with DRIVE SW 9.0 and the external internet LAN cable to Dongle channel A of front panel 1GbE/100MbE Port3&4. I don’t see any issue with internet and able to ping like you said.

When Xavier is connected to the LAN from Port3&4, I cannot connect to internet, and can not use the camera. The error message is posted at the top of this topic.

I tried on another Drive AGX Xavier, and met the same issue.

Dear Laing_Qi,
So as I understand, you are not able to connect to internet using LAN cable to Dongle. Did you notice the same issue on another board?
When you do not connect dongle, you are able to use camera. But when you connect dongle, you are encountering NvccpCamPowerControl: 534: NVCCP command failed with ret NVCCP_REQ_TIMEOUT error. You noticed the same on another board.
As I said, the above error indicate aurix tegra communication issue. In comment #3, You said it is fixed via aurixreset. So it came back when you connected dongle again?

Do you see this issue since beginning after flashing DRIVE SW 9.0? or It came after few days?

On my board, with default setting after flashing, I am able to use cameras even after connecting external internet LAN cable to Dongle channel A of front panel 1GbE/100MbE Port3&4.

Could you check flashing the board again?

Hi Liang_Qi,

Have you managed to get issue resolved or still an issue to support?
Any result can be shared?

I still have this issue.

As the Xavier PC is shared with my collegues, I haven’t try a flash.

Is there any other possible solution?

Hi Liang_Qi,

Please refer to our previous comments#12, and see if can get it works after flashing the board again?

Thanks

I have tried to flash it again.
The same issue occurs since the begining after flashing DRIVE SW 9.0.

A possible problem might be the network update during the flashing.
In our LAN network, I have to modify the proxy settings to access the internet,
but modifying the settings on Xavier during the flashing is impossible.
So although I did connect the LAN cable to Dongle channel A of front panel 1GbE/100MbE Port3&4,
the network should not work.

This lead to some errors from ‘connect to ubuntu.com XXX’ in the final part of installation on Xavier.
This part might be some update, is it important or relate to my issue?
If it is important, how to fix it?
Is there any way to modify proxy settings during installation?
or is there any way to re-run this final installation part again?

Dear Liang_Qi,
Did you check setting proxy in SDKManager(https://docs.nvidia.com/sdk-manager/sdkm-settings/index.html). We have DRIVE SW 10.0 included in latest SDkManager now. Could you check flashing that?

I did the proxy setting in SDKManager and there is no problem about downloading in the SDKManager.
But I think this proxy setting won’t be available on Xavier until the installation finished.
Would you tell me whether this will affect the installation or not? and how to solve this problem?

Even flashing Drive SW 10.0, this proxy problem still exists,
so would you provide some advice for this problem before trying to flash?

The problem is sovled by connect the channel A of port3&4 to a network which can access internat without proxy server.
It seems that the proxy setting on Xavier or the network with proxy server blocks the connection between Xavier A/B and Aurix.

Thank so much for providing me the advices!