Hi ShaneCCC,
Indeed, it’s sensor dependent.
To give you a bit more context, we’ve asked Leopard Imaging to develop our sensor driver, they’ve succeeded to get a working streaming on our sensor board plugged on one of your evaluation board kits. We are now in the process of testing this sensor board on one of our own carrier board. This is where we get the nvgstcapture-1.0 to crash.
So to resume, the sensor board is working with the following params on the EVK but not on our carrier board:
line_length = "6524";
pix_clk_hz = "840000000";
active_w = "1936";
active_h = "1080";
On both systems, EVK and our own carrier board, the v4l2-ctl command shows us intermediary black frames even though there’s a working colour streaming on the EVK. As the streaming works on EVK, I don’t understand how come v4l2-ctl still gives black frames as you suggested that it should first perfectly work.
Can you show the result by the v4l2-ctl --list-formats-ext
nvidia@tegra-ubuntu:~$ v4l2-ctl --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Index : 0
Type : Video Capture
Pixel Format: 'RGGB'
Name : 8-bit Bayer RGRG/GBGB
Size: Discrete 2464x2048
Interval: Discrete 0.033s (30.000 fps)
Index : 1
Type : Video Capture
Pixel Format: 'RG10'
Name : 10-bit Bayer RGRG/GBGB
Size: Discrete 2464x2048
Interval: Discrete 0.033s (30.000 fps)
Index : 2
Type : Video Capture
Pixel Format: 'BG10'
Name : 10-bit Bayer BGBG/GRGR
Size: Discrete 2464x2048
Interval: Discrete 0.033s (30.000 fps)
Index : 3
Type : Video Capture
Pixel Format: 'XBGP'
Name : 10-bit Bayer BGGR(10-10-10-2)
Index : 4
Type : Video Capture
Pixel Format: 'XRGP'
Name : 10-bit Bayer RGGB(10-10-10-2)
Size: Discrete 2464x2048
Interval: Discrete 0.033s (30.000 fps)
Index : 5
Type : Video Capture
Pixel Format: 'RG12'
Name : 12-bit Bayer RGRG/GBGB
Size: Discrete 2464x2048
Interval: Discrete 0.033s (30.000 fps)
What’s the BSP version?
Does the size correct?
28.1 for TX1
Size is correct: 2464x2048
That confuse! Then why the active_w/active_h is different with that.
active_w = "1936";
active_h = "1080";
Ask Leopard Imaging.
I’ve changed it to
active_w = "1936";
active_h = "1096";
and it still works on the EVK.
I don’t think the kernel driver report 2464x2048 but DT report 1936x1096 are working.
Please working with Leopard to dump the DT from the system to make sure the setting is correct.