nvmipp_raw/nvmimg_cc on Tegra B

Autonomous Vehicles DRIVE PX2 DRIVE - Linux
#1

Hello,

I am trying to run the nvmipp_raw on the Tegra B with Seknoics SF3324-100 (AR0231 sensor). In the documentation the following is mentioned :

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

https://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520DRIVE%2520Linux%2520SDK%2520Development%2520Guide%2FConfiguration%2Fcamera_setup_dpx.html%23

In the latest Drive SDK the following configs are avaliable

drive-ax.conf  
drive-px2-a.conf  
drive-px2-autocruise.conf  
drive-px2-b.conf  
p2382_t186.conf

I tried the following :

./nvmipp_raw -cf drive-px2-b.conf -c dvp-ar0231-raw12-1920x1208-ab

However, I get the following error :

***** 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
***********************
nvmedia: ERROR: IPPInit: Failed to initialize ISC devices
nvmedia: ERROR: main: Error in IPPInit
[NvMediaIPPManagerDestroy:181] Bad parameter

Also what is the Deserializer I2C Address and Serializer I2C Address from Tegra B?

#2

Dear Puneeth,

Please refer to Simultaneous Capture with MAX96799 Aggregator part in https://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%20DRIVE%20Linux%20SDK%20Development%20Guide%2FConfiguration%2Fcamera_setup_dpx.html%23

I connected one camera to B group and could run the sample like below without any error.
sudo ./nvmipp_raw -cf …/drive-px2-b.conf -c dvp-ar0231-rccb-raw12-1920x1208-cd -d 0 --aggregate 1 --plugin

#3

Hi Steve,

Thanks for the reply. Changing the configuration to rccb helped.

I am also trying to run the nvmimg_cc from Tegra B.

But there is only configuration for Tegra A (drive-px2-a/dvp_o_ar0231_raw12_hdr_1920x1236_ab_ta_rccb_v7_b.script).

Is there a configuration for Tegra B?

I guess the following needs to be changed (Took this from the ipp_raw Tegra B configuration)

; Interface: csi-ab
; Input Format: raw12
; Resolution: 1920x1208
; CSI Lanes: 4
; I2C Device: 7
; Sensor Address: 0x20
; Deserializer Address: 0x90
; Pixel Order: GRBG

to

; Interface: csi-ab
; Input Format: raw12
; Resolution: 1920x1236 #1920x1208, +24 top emb, +4 bottom emb
; CSI Lanes: 4
; I2C Device: 7
; Sensor Address: 0x10
; Deserializer Address: 0x6A
; Pixel Order: GRBG
; Serializer Address: 0x40

Also change the addresses on rest of the lines.

And looks something like this:

; Interface: csi-ab
; Input Format: raw12
; Resolution: 1920x1236 #1920x1208, +24 top emb, +4 bottom emb
; CSI Lanes: 4
; I2C Device: 7
; Sensor Address: 0x10
; Deserializer Address: 0x6A
; Pixel Order: GRBG
; Serializer Address: 0x40

6A 3F 4F
; Delay 2ms
6A 3B 1E
; Delay 2ms
6A 0A FF
40 04 43
; Delay 5ms
40 08 01
40 97 5F
; Delay 2ms
6A 3B 19
; Delay 2ms

6A 15 03
6A 12 F7    #DBL=1, CSI_DBL=1
6A 01 00    #frame sync on, manual
6A 00 EF
..
..

However, I get a timeout error with this. Any idea regarding this?

#4

Dear Puneeth,

I will check it.
BTW is there any reason to run nvmedia sample application on TegraB only? Thanks.

#5

Hi Steve,

Tegra A is stuck in recovery mode, there is another thread on Drive Hardware waiting for a resolution.

Because of this I am using the Tegra B.

#6

Hi Steve,

Any update on this?

#7

Hi Puneeth,
Could you please upgrade to latest PDK(https://developer.nvidia.com/nvidia-drive-downloads).
SF3324 camera modules are supported on latest PDK. However, if you want to stick onto this current due to any reason, can you please attach complete config here. We will look into it.

#8

Hi Siva,

Thanks for the reply. I have not tried the new PDK. But does new PDK have a different nvmimg_cc program on it?

#9

Dear punith,
There can be minor changes in the code. You can check installing latest PDK on host to compare the codes. But we hav added separate configuration for sf3324 camera module.

#10

Dear punith,

Did you solve TegraA issue?
If still use TegraB, there is no configuration folder for drive-px2-b on TegraB now.
So if fix TegraA issue, please run the application on TegraA. Thanks.

#11

Guys,

Thanks for the reply.

Yes the Tegra A issue is still open. Alright, I will wait for the issue to be solved.