Why does system often update on AGX platform automatically ? and then the camera cannot be launched.

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

I found a strange phenomenon on AGX platforrm.
After flashing AGX diver I can luanch camera by type “./sample_camera_gmsl”,
but after typing “sudo apt-get update” and reboot system,camera cannot be launched!
It printed the following log:

Driveworks exception thrown :DW_NVMEDIA_ERROR: CameraGMSL:Cannot setup pipeling:7

I think that library updating influnce camera launching,so I flashed AGX driver again,
But I found that as long as connect network and then reboot system, the camera cannot be launched.
even I closed update options in Software&Updates,but I still cannot avoid the problem.
Who can help me?

webwxgetmsgimg.jpeg
webwxgetmsgimg.jpeg1080×1440 221 KB

2

Hi,

Did you only do an update or also an upgrade? The update should not change anything…

Perhaps you can also provide us with dmesg outputs.

Thanks.

Fabian

3

Hi

I have captured dmesg outputs and uploaded it,please check it from attachments.

In addition I found that after updating and reboot the current user become ubuntu,not nvidia,I don’t know why.

I think that the bellowing log might be important for you, so I pasted it,please checkit.

nvidia@tegra-ubuntu:/usr/local/driveworks-1.5/bin$ ./sample_camera_gmsl
[06-06-2019 02:30:58] Platform: Detected DDPX - Tegra A
[06-06-2019 02:30:58] Initialize DriveWorks SDK v1.5.3584
[06-06-2019 02:30:58] Release build with GNU 4.9.4 from heads/buildbrain-branch-0-g38b3a75 against Drive PDK v5.0.13.2
[06-06-2019 02:30:58] TimeSource: monotonic epoch time offset is 1559786109654792
[06-06-2019 02:30:58] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[06-06-2019 02:30:58] PTP Time is available from Eth Driver
[06-06-2019 02:30:58] Platform: number of GPU devices detected 1
[06-06-2019 02:30:58] Platform: currently selected GPU device integrated ID 0
[06-06-2019 02:30:58] SDK: Resources mounted from …/./data/resources
[06-06-2019 02:30:58] SDK: Create NvMediaDevice
[06-06-2019 02:30:58] SDK: use EGL display as provided
[06-06-2019 02:30:58] SensorFactory::createSensor() → camera.gmsl, output-format=yuv,fifo-size=3,camera-type=ar0231-rccb-bae-sf3324,camera-group=a,slave=0
[06-06-2019 02:30:58] CameraGMSL: Create NvMediaIPPManager
[06-06-2019 02:30:58] CameraGMSL: required FPS = 30, resolution = 1920x1208
Max96712 Rev 2 detected!
Sensor AR0231 RCCB Rev7 detected!
(NvCapture) Error IoctlFailed: capture setup ioctl failed: Device or resource busy (in /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture_hw_linux.c, function NvCaptureLinuxChannelOpen(), line 140)
(NvCapture) Error IoctlFailed: (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureChannelHwBackendOpen(), line 1130)
(NvCapture) Error IoctlFailed: (propagating from /dvs/git/dirty/git-master_linux/camera/capture/nvcapture/capture.c, function NvCaptureChannelSetAttribute(), line 1230)
CaptureInit: failed to set channel source attribute
ICPCreate: captureCreate failed
nvmICPCreate: failed for create ICP instance 0
[IppIcpExComponentCreateNew:625] Failed to create ICP
[NvMediaIPPComponentCreateNew:807] Failed to create NVMEDIA_IPP_COMPONENT_ICP_EX component
[06-06-2019 02:30:59] Driveworks exception thrown: DW_NVMEDIA_ERROR: CameraGMSL: Cannot setup pipeline : 7

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2019-06-06 02:30:59] DW Error DW_NVMEDIA_ERROR executing DW function:
dwSAL_createSensor(&m_camera, params, m_sal)
at /dvs/git/dirty/gitlab-master_av/dw/sdk/samples/sensors/camera_gmsl/main.cpp:158
Aborted (core dumped)

dmesg_before_update.txt (86.9 KB)
dmesg_after_update.txt (80.1 KB)

4

Hi Fabian

After many experiments, I found out solution to solve the issue:

1,shutdown
2,disconnect power
3,connect power,waiting system reboot

5

Hi,

Thanks for the information and glad that you found a solution for it. I will mark it as solved w.r.t. your answer.

Best regards,
Fabian

6

Hi Fabian

Although I’ve found a solution, I don’t know why camera cannot be launched after updating,
also I think it is not the best solution.
So I hope you find the reason and get a better solution.
Thank you!

7

Hi,

You are using the following cameras:

Max96712 Rev 2 detected!
Sensor AR0231 RCCB Rev7 detected!

Are you actually using one of our supported cameras and did you try disconnecting one and then the other?

Also we have a camera tutorial right here, so please follow this up and see if you perhaps connected them wrong. (see https://developer.nvidia.com/drive/learn/tutorial-camera)

First, we need to exclude some more basic issues before digging even deeper.

Thanks.

Fabian

8

HI,

I’m sure the camera is supported by AGX platform. I don’t think the camera have some fault,because I can launch the camera after flashing AGX device.

As an engineer, I think it’s necessary for you to repeat my steps to reproduce this issue.
Thanks.

9

Hi,

Which exact camera are you using?

For repro it would make sense to use the same camera, if supported.

Fabian