Camera issues

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
,
1

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
[**] NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
[**] Linux
QNX
other

Hardware Platform
[**] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
[**] 1.5.0.7774
other

Host Machine Version
[**] native Ubuntu 18.04
other

Hello everyone,

I am here today because I’m facing a problem with my camera.
When I start the box after hours the camera is functional, I can run the scripts to retrieve the values of the driveix programs.

But when I restart or shutdown the box and then power again after a few minutes I have problems with AURIX and my camera cannot be found.

In addition, my aurix console does not work as requested in other topics that I have read.

It’s pretty annoying, does anyone have any idea how to fix this?

2

capt3
capt34032×3024 2.76 MB

3

Dear @nida.rahman1 ,
Do you see any issue with DW camera samples? Could you share output of any DW camera sample?
When did you buy this target? Where and how(office or car) it was used before you hit this issue? Could you check the AUrix FW version via minicom?

5

@SivaRamaKrishnaNV I buy this target few weeks ago, I’m using it in the office not in the car yet.

Well, I tried “sudo minicom -D /dev/ttyUSB1” to open the minicom but I don’t have the shell… so I can’t write any command

6

image
image1139×101 4.6 KB

I tried this command but this is what I got:

capt4
capt44032×1803 2.84 MB

7

I’m actually on TegraB so I only have the executables of drive IX and not of DW. So I tried the ClientSample.cpp and this is what I had:

capt5
capt54032×3024 2.97 MB

8

Dear @nida.rahman1,
Could you please login to Tegra A and check running DW samples. Or you may cross compile DW sample and run on Tegra B as well. This help to understand the status of the board. Please check connecting /dev/ttyUSB3 using minicom?

9

Dear @SivaRamaKrishnaNV when I connected /dev/ttyUSB3 it works! and when I write “version” I got this message:

SW Version: DRIVE-V5.1.6-E3550-EB-Aurix-With3LSS-ForHyperion-StepA-3.05.04

10

Dear @nida.rahman1 ,
So now you are able to access Aurix console. Also, you have right Aurix version. As I said, could you check running DW samples to know if issue with camera module or board. Please share the output to investigate the issue furthur.

1 Like
11

Dear @SivaRamaKrishnaNV
This is what I got when I try to run some DW samples:

capt6
capt64032×3024 3.78 MB

12

Dear @SivaRamaKrishnaNV , maybe it’s more lisible like this:

nvidia@tegra-ubuntu:~$ cd /usr/local/driveworks/bin
nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ ./sample_drivenet --input-type=camera
[18-05-2021 12:41:49] Platform: Detected DDPX - Tegra A
[18-05-2021 12:41:49] TimeSource: monotonic epoch time offset is 1621334414827861
[18-05-2021 12:41:49] PTP Time is available from NVPPS Driver
[18-05-2021 12:41:49] Platform: number of GPU devices detected 1
[18-05-2021 12:41:49] Platform: currently selected GPU device integrated ID 0
[18-05-2021 12:41:49] SDK: Resources mounted from …/./data/
[18-05-2021 12:41:49] SDK: Create NvMediaDevice
[18-05-2021 12:41:49] SDK: use EGL display as provided
[18-05-2021 12:41:50] TimeSource: monotonic epoch time offset is 1621334414827861
[18-05-2021 12:41:50] PTP Time is available from NVPPS Driver
[18-05-2021 12:41:50] Initialize DriveWorks SDK v2.2.3136
[18-05-2021 12:41:50] Release build with GNU 7.3.1 from heads/buildbrain-branch-0-gca7b4b26e65 against Drive PDK v5.1.6.1
[18-05-2021 12:41:50] Initialize DriveWorks VisualizationSDK v2.2.3136
[18-05-2021 12:41:50] Initialize DriveWorksGL SDK v2.2.3136
[18-05-2021 12:41:50] SensorFactory::createSensor() → camera.gmsl, camera-type=ar0231-rccb-bae-sf3324,camera-group=a,slave=0,serialize=false,output-format=raw,camera-count=4,camera-mask=0001
[18-05-2021 12:41:50] CameraGMSL: Couldn’t set CameraGMSL setup thread sched params!
[18-05-2021 12:41:50] CameraGMSL: Create NvMediaIPPManager
[18-05-2021 12:41:50] CameraGMSL: required FPS = 30, resolution = 1920x1208
nvmedia isc: GetCameraPowerControlLevel: 936: 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: 535: 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-05-2021 12:42:10] Driveworks exception thrown: DW_SAL_CANNOT_CREATE_SENSOR: CameraGMSL: cannot connect to camera

terminate called after throwing an instance of ‘std::runtime_error’
what(): [2021-05-18 12:42:10] DW Error DW_SAL_CANNOT_CREATE_SENSOR executing DW function:
dwSAL_createSensor(&m_sensor, params, m_sal)
at /dvs/git/dirty/gitlab-master_av/dw/sdk/samples/framework/SimpleCamera.cpp:107
Aborted (core dumped)
nvidia@tegra-ubuntu:/usr/local/driveworks/bin$

13

Dear @nida.rahman1,
I notice SF3324 camera flag and camera-count as 4 in log. Are you using SF3324 camera module? If not, please use the right flags

14

I will try thanks @SivaRamaKrishnaNV

15

Dear @SivaRamaKrishnaNV ,

I changed the flag to SF3325 because I am not using a SF3324, but still have the issue:

nvidia@tegra-ubuntu:/usr/local/driveix/bin$ ./driveIX --gmsl
using runtime config
machine: e3550_t194b
using internal ip address 10.42.0.29
DriveIX stand-alone mode
Got input of gmsl camera
Initializing governor!
visionfaceID: no process found
sdkParams.dataPath: …/models
PROTOCOL: camera.gmsl
PARAMETERS: camera-group=a,camera-count=4,camera-mask=0001,host=127.0.0.1,port=35565,output-format=raw,camera-type=ar0231-rccb-bae-sf3325,fifo-size=3,mode=mailbox,siblingIndex=0
nvmedia isc: GetCameraPowerControlLevel: 936: 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: 535: 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
dwStatus: ‘dwSAL_createSensor(&m_dwSesnor, params, m_dwSal)’ = DW_SAL_CANNOT_CREATE_SENSOR in createCameraSensors @ GmslCameraGroup.cpp:73
==== exception backtrace ====
[0]: (null) (0x4ecbf8)
[1]: GmslCameraGroup::createCameraSensors(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) (0x4ed628)
[2]: RawGmslCameraGroup::RawGmslCameraGroup(int, unsigned long, std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::__cxx11::basic_string<char, std::char_traits, std::allocator >, dwSALObject*, dwContextObject*) (0x4f1ce4)
[3]: GmslCamera::createCamera(unsigned long, dwContextObject*) (0x4ebbf4)
[4]: Governor::initCameraFrameReaders() (0x5099f0)
[5]: Governor::initFrameReaders() (0x50c810)
[6]: Governor::start(InputType, char const*, FrameDumpInfo const&) (0x50d26c)
[7]: driveix::IXMainPipeline::main(int, char**) (0x4e1770)
[8]: driveix::IXMainPipeline::runMode(int, char const**) (0x502508)
[9]: dsw::framework::services::ServiceSync::loop(bool, int, char const**, bool) (0x79321c)
[10]: main (0x4e27bc)
[11]: __libc_start_main (0x7f880e4720)
[12]: (null) (0x4e6628)

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: 535: 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
dwStatus: ‘dwSAL_releaseSensor(m_dwSesnor)’ = DW_INVALID_HANDLE in ~GmslCameraGroup @ GmslCameraGroup.cpp:109
==== exception backtrace ====
[0]: (null) (0x4ecbf8)
[1]: GmslCameraGroup::~GmslCameraGroup() (0x4ed0f8)
[2]: RawGmslCameraGroup::RawGmslCameraGroup(int, unsigned long, std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::__cxx11::basic_string<char, std::char_traits, std::allocator >, dwSALObject*, dwContextObject*) (0x4f1e2c)
[3]: GmslCamera::createCamera(unsigned long, dwContextObject*) (0x4ebbf4)
[4]: Governor::initCameraFrameReaders() (0x5099f0)
[5]: Governor::initFrameReaders() (0x50c810)
[6]: Governor::start(InputType, char const*, FrameDumpInfo const&) (0x50d26c)
[7]: driveix::IXMainPipeline::main(int, char**) (0x4e1770)
[8]: driveix::IXMainPipeline::runMode(int, char const**) (0x502508)
[9]: dsw::framework::services::ServiceSync::loop(bool, int, char const**, bool) (0x79321c)
[10]: main (0x4e27bc)
[11]: __libc_start_main (0x7f880e4720)
[12]: (null) (0x4e6628)

Caught exception: dwStatus: ‘dwSAL_createSensor(&m_dwSesnor, params, m_dwSal)’ = DW_SAL_CANNOT_CREATE_SENSOR in createCameraSensors @ GmslCameraGroup.cpp:75
==== exception backtrace ====
[0]: (null) (0x4ed3d0)
[1]: GmslCameraGroup::createCameraSensors(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) (0x4ed714)
[2]: RawGmslCameraGroup::RawGmslCameraGroup(int, unsigned long, std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::__cxx11::basic_string<char, std::char_traits, std::allocator >, dwSALObject*, dwContextObject*) (0x4f1ce4)
[3]: GmslCamera::createCamera(unsigned long, dwContextObject*) (0x4ebbf4)
[4]: Governor::initCameraFrameReaders() (0x5099f0)
[5]: Governor::initFrameReaders() (0x50c810)
[6]: Governor::start(InputType, char const*, FrameDumpInfo const&) (0x50d26c)
[7]: driveix::IXMainPipeline::main(int, char**) (0x4e1770)
[8]: driveix::IXMainPipeline::runMode(int, char const**) (0x502508)
[9]: dsw::framework::services::ServiceSync::loop(bool, int, char const**, bool) (0x79321c)
[10]: main (0x4e27bc)
[11]: __libc_start_main (0x7f880e4720)
[12]: (null) (0x4e6628)

Please read config/cameras.ini to check your camera setup.
If you are using slave protocol, please check camera server connection.
Destroying Governor

16

I am having this problem from the beginning, when I start my Nvidia drive agx after few hours everything works well I dont have any issue, but once I restart it could not connect to camera, ping the aurix is unreachable …

Does anyone know why?

17

Dear @nida.rahman1 ,
It seems driveIX requires GazeT AR0144 OnSemi module (Please see prerequisites section in DRIVE IX documentation at /path/to/DRIVE_SW_10.0_References/DRIVE_Software/index.html#page/DRIVE%20IX/drIX_Getting_started.html#wwpID0E4HA).

when I start my Nvidia drive agx after few hours everything works well I dont have any issue,

Do you see driveIX is working with SF3325 camera after booting?

May I know which camera module you are using while testing DW sample?

1 Like
18

I am using the same camera module :SF3325 Sekonix for DW and also for Drive IX.

Yes driveIX is working with SF3325 even DW when I boot after few hours ( it was powered off all the night), but if I restart or reboot then I have the issue I talked about above…

19

Dear @nida.rahman1 ,
Please see if the issue persists when you turn on board more than 20secs after turning it off. If so, could you confirm if re-flashing help to fix it?

20

yes the issue persists, well I have tried flashing during 2weeks I can’t take the risk to reflash now I have a project to finish!!

21

Dear @nida.rahman1,
Could you please connect only one SF3325 camera module to A0 port and share the output of ./sample_camera_gmsl --camera-type=ar0231-rccb-bae-sf3325 on Tegra A.