GMSL Sekonix camera problem

Autonomous Vehicles DRIVE PX 2 DRIVE Hardware
1

Hi.

We purchased a sekonix GMSL cameras SF3326-101 N2.0 RGB
We are having trouble to start this camera in RGB mode:

./sample_camera_gmsl --csi-port=ab --camera-type=ar0231
Program Arguments:
--camera-type=ar0231
--csi-port=ab
--fifo-size=3
--serialize-bitrate=8000000
--serialize-framerate=30
--serialize-type=h264
--slave=0
--write-file=
nvrm_gpu: Bug 200215060 workaround enabled.
Initialize DriveWorks SDK v0.6.54
Release build with GNU 4.9.2 from v0.6.0-rc5-0-g3f25786 against Vibrante PDK v5.0.5.0
TimeSource: monotonic epoch time offset is 1522843702720123
TimeSource: PTP ioctl returned error. Synchronized time will not be available.
TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
SDK: Resources mounted from /usr/local/driveworks-0.6/data/resources
SDK: Create NvMediaDevice
SDK: use EGL display as provided
SDK: Default GPU Device set to device number 0. Total number of devices detected: 2
SAL: identified board as DrivePX2-TegraA
SensorFactory::createSensor() -> camera.gmsl, camera-type=ar0231,csi-port=ab,fifo-size=3,serialize-bitrate=8000000,serialize-framerate=30,serialize-type=h264,slave=0,write-file=,output-format=yuv
CameraGMSL: required FPS = 30, resolution = 1920x1208
***** 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: RGGB mode for this sensor version is not supported
nvmedia: ERROR: SetupVideoLink: Image sensor(0) device is not present
nvmedia: ERROR: Init: Failed to setup video link
***** aurix state *****
CAM_PWR_ON: 0x0
TEGRA_GMSL: UNKNOWN
TEGRA_FPDL: UNKNOWN
TEGRA_A_HDMI: UNKNOWN
TEGRA_B_HDMI: UNKNOWN
TEGRA_PCI: UNKNOWN
FAN_STATE: UNKNOWN
***********************
Driveworks exception thrown: DW_SAL_CANNOT_CREATE_SENSOR: CameraGMSL: cannot connect to camera
Cannot create driver: camera.gmsl with params: camera-type=ar0231,csi-port=ab,fifo-size=3,serialize-bitrate=8000000,serialize-framerate=30,serialize-type=h264,slave=0,write-file=,output-format=yuv
Error: DW_SAL_CANNOT_CREATE_SENSOR

But in the RCCB mode this camera works, but of course the image is overexposed.
Have any ideas?
Thanks.

2

Dear zhukov,

We are checking the symptom in RGB mode.

Regarding overexposure in RCCB mode, could you please file a bug for this topic?
Please login to https://developer.nvidia.com/drive with your credentials.
And check MyAccount->MyBugs->Submit a new bug to file bug.
Please share ID here to follow up. Thanks.

3

Hi everyone!

we are facing also problems with a Sekonix camera. We are using the SF3326-100 N2.0 RCCB and we are also having problems to start the camera:

./sample_camera_multiple_gmsl --selector-mask=1000
    Program Arguments:
    --cross-csi-sync=0
    --fifo-size=3
    --selector-mask=1000
    --slave=0
    --type-ab=ar0231-rccb
    --type-ab=ar0231-rccb
    --type-ab=ar0231-rccb

    nvrm_gpu: Bug 200215060 workaround enabled.
    Initialize DriveWorks SDK v0.6.54
    Release build with GNU 4.9.2 from v0.6.0-rc5-0-g3f25786 against Vibrante PDK v5.0.5.0
    TimeSource: monotonic epoch time offset is 1518711405241233
    TimeSource: PTP ioctl returned error. Synchronized time will not be available.
    TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
    SDK: Resources mounted from /usr/local/driveworks-0.6/data/resources
    SDK: Create NvMediaDevice
    SDK: use EGL display as provided
    SDK: Default GPU Device set to device number 0. Total number of devices detected: 2
    SAL: identified board as DrivePX2-TegraA
    SensorFactory::createSensor() -> camera.gmsl, csi-port=ab,camera-type=ar0231-rccb,camera-count=4,camera-mask=1000,slave=0,cross-csi-sync=0,fifo-size=3
    CameraGMSL: required FPS = 30, resolution = 1920x1208
    ***** 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
    ***********************
    Sensor AR0231 RCCB Rev7 detected!
    nvmEglStProducerCreateCommon: Entered
    readFrameNvMedia: DW_NOT_READY
    ***** aurix state *****
    CAM_PWR_ON: 0x0
    TEGRA_GMSL: UNKNOWN
    TEGRA_FPDL: UNKNOWN
    TEGRA_A_HDMI: UNKNOWN
    TEGRA_B_HDMI: UNKNOWN
    TEGRA_PCI: UNKNOWN
    FAN_STATE: UNKNOWN
    ***********************

We tried it with other cameras like the SF3324-100 or SF3325-100 and had no problems.
Do you have any ideas on that?
Thank you!

4

Dear stefan.bogenrieder,

Can I know the SF3324-100 camera revision? Thanks.

5

Dear SteveNV,

we have two versions of the SF3324-100 camera, Rev06 and N2.0. It worked with both of them.

6

Dear SteveNV,
I submitted a new bug (2106337).

7

Dear zhukov,

Thank you for filing a bug for this symptom.
We will look into the issue. Thanks.

8

Dear zhukov,

Could you please update DPX2 PDK(5.0.13.0) and DriveWorks1.2 via SDK manager?
And please refer to the below link for sample_camera_gmsl application.
/usr/local/driveworks-1.2/doc/nvdwx_html/camera_mainsection.html on DPX2. Thanks.

9

hi, is this problem solved? I am going to purchase a sekonix 3326 but I am not sure if it is compatible with drive px2. could you confirm? Thanks.

10

Dear sarveshd,

Unfortunately Sekonix 3326 camera is not in DriveWorks supported camera list. Thanks.

11

Any fish eye GMSL camera I can use for Drive PX2?

I only find this one LI-AR0231-GMSL-xxxH (FOVH 60 / 120 200):
https://leopardimaging.com/product/li-ar0231-gmsl/

In the webpage it says “Support Nvidia Drive PX2”

12

Dear sarveshd,

Could you please refer to below link for your topic? Thanks.