Fail to test GMSL camera on PX2

Autonomous Vehicles DRIVE PX 2 DriveWorks
1

Hi,

I used the samples in driveworks-0.1.2, which was preinstalled on PX2, to test an ov10635 camera, but failed.
The camera was connected to A0 input, and I tried the following sample:

./sample_camera_gmsl --camera-type=ov10635

Output logs are as below:

Program Arguments:
–camera-type=ov10635
–csi-port=ab
–offscreen=0
–serialize=false
–serialize-bitrate=8000000
–serialize-framerate=30
–serialize-type=h264
–slave=0
–write-file=

Initialize DriveWorks SDK v0.1.2 (47dcf3d4d12e5646ec971f4b54817f16213755ba)
Create NvMediaDevice
SDK: use EGL display as provided
SAL: identified board as DrivePX2-TegraA
SensorFactory::createSensor() → camera.gmsl, camera-type=ov10635,csi-port=ab,offscreen=0,serialize=false,serialize-bitrate=8000000,serialize-framerate=30,serialize-type=h264,slave=0,write-file=
***** aurix state *****
CAM_PWR_ON: 0x0
TEGRA_GMSL: TEGRA B
TEGRA_FPDL: TEGRA B
TEGRA_A_HDMI: MXM
TEGRA_B_HDMI: MXM
TEGRA_PCI: TEGRA B
FAN_STATE: UNKNOWN

***** aurix state *****
CAM_PWR_ON: 0x1
TEGRA_GMSL: UNKNOWN
TEGRA_FPDL: UNKNOWN
TEGRA_A_HDMI: UNKNOWN
TEGRA_B_HDMI: UNKNOWN
TEGRA_PCI: UNKNOWN
FAN_STATE: UNKNOWN

nvmedia: ERROR: SetupVideoLink: Can’t detect config link(0)
nvmedia: ERROR: Init: Failed to setup video link

What should I do to make this sample run correctly? Thank you!

2

Hello Wanghao,

Could you please check AURIX_IP_ADDRESS ip on Aurix shell?
If AURIX_IP_ADDRESS=10.42.0.73, please modify tacp.cfg file.
AURIX_IP_ADDRESS=10.42.0.73 => AURIX_IP_ADDRESS=10.42.0.33
Then export DRIVEPX2_AURIX_IP_ADDRESS=10.42.0.33 on DPX2.

However we’ve post DrivePX2 PDK Beta 1.0 on NVONLINE.
If possible, could you please use new one instead of old one? Thanks.

3

Hi Mania,

I changed the aurix ip address to 10.42.0.33, this error still exists. I upgrade the DrivePX2 PDK Beta 1.0, still the same error. Is there any other point I should check with? Thank you!

4

Hello Wanghao,
Did you upgrade Aurix F/W version 1.03?
If you still encounter same issue, could you please file a bug on NVONLINE. Thanks.

5

Hello I followed all these your answers and instraction to on the gmsl camera but yet i am not able to run any single camera on px2. in following you can see my terminal output corresponding input additionally I dont have any file as tacp.cfg . PLEASE HELP THANK YOU

$ sudo /etc/systemd/scripts/nv_aurix_check_fw.sh
[sudo] password for nvidia:

starting Aurix FW checking…
Checking arguments…
Rootfs EB FW version is 2.02.04.0
Flashed EB FW version is 2.02.04.00
Aurix is booted with Latest EB FW
Rootfs UPDATE FW version is 0.16.00.0
Flashed UPDATE FW version is 0.16.00.00
Aurix is booted with Latest UPDATE FW

$ ./x11/nvmipp_raw -cf e2379a_c01.conf -c dvp-c-ov10640-b1-raw12-1280x1080-ab -d 0 --nvplugin

receive_from: Timeout Error.
Please check Ethernet ip configuration or
check Aurix firmware version
iscRootDevOpen: Failed to power on camera(s)
NvMediaISCRootDeviceCreate: Unable to open root device
nvmedia: ERROR: Init: Failed to create NvMedia ISC root device
nvmedia: ERROR: IPPInit: Failed to initialize ISC devices
nvmedia: ERROR: IPPInit: Failed
[NvMediaIPPManagerDestroy:189] Bad parameter
nvmedia: ERROR: main: Error in IPPInit

in minicom terminal
shell>>status
IP add: TegraA 10.42.0.28
IP add: Tegrab 10.42.0.29
IP add: aurix 10.42.0.73

6

Dear mehmed.yueksel,

Can I know you are using PDK version and Aurix version?
If not, please update PDK and Aurix.

Regarding ./x11/nvmipp_raw -cf e2379a_c01.conf -c dvp-c-ov10640-b1-raw12-1280x1080-ab -d 0 --nvplugin
Please check camera type and connection. Thanks.

7

Dear Steve
Thank you for reply
I solved the problem with changing IP address of Aurix in tacp.cfg file.
Best