you’re still working with JetPack release drivers (i.e. CSI, VI) no matter sensor types.
please also check Camera Architecture Stack, you’ll also need ISP support if the [Camera Core] is involved.
suggest you could also access Tutorials page, to expand the [Developer Tools] session and check the [Develop a V4L2 Sensor Driver] training video for the overview of camera software architecture.
if you’re working with CSI bayer sensor, you’ll need de-bayer process.
- if you’re going through “Direct V4L2 Interface”, VI driver handle the de-bayer process. you might also have raw dump with v4l2 standard controls. here’s sample commands for your reference.
$v4l2-ctl -d /dev/video0 --set-fmt-video=width=2592,height=1944,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=1 --stream-to=test.raw
- if you’re going through [Camera Core], then ISP handle the de-bayer process. the hardware encode/decode components were also necessary in the same pipeline as ISP outputs.
$ gst-launch-1.0 nvarguscamerasrc num-buffers=1 ! 'video/x-raw(memory:NVMM), width=2592, height=1944' ! nvjpegenc ! filesink location=sample.jpg