Jetson TX2 NX & SC233HGS

自主机器 Jetson 开发者专区
1

body

Hello,

I am using a Jetson TX2 NX with JetPack 4.6.6 (L4T R32.7.x — exact build from /etc/nv_tegra_release if needed). I have a custom SC233 camera module with an in-tree driver (sc233hgs / tegracam-style) connected over CSI. Capture is stable via V4L2 on /dev/video0.

What works today

  • Pixel format: 8-bit Bayer (BA81 / SBGGR8), resolutions such as 1920×1080 and 1920×1200 depending on mode.
  • Controls: exposure, gain, sensor mode, and other Camera class controls exposed through the tegracam path.
  • No application-side issues for RAW capture.

What I checked

  • v4l2-ctl -d /dev/video0 --list-ctrls shows no ARGUS_* / user_argus_* style controls.
  • v4l2-ctl -d /dev/video0 --list-formats-ext shows BA81 only (RAW), not NV12/NV16.

So this node looks like a direct VI RAW path, not the V4L2 NV Extensions + Argus path described in the Jetson Linux API documentation for some camera devices.

What I want to know

  1. For Jetson TX2 and L4T 32.x (JetPack 4.6), is access to the Tegra hardware ISP through libargus / nvarguscamerasrc effectively limited to NVIDIA-supported camera modules that are fully integrated in the BSP? For a custom Bayer sensor that only exposes RAW on /dev/video*, is there any documented, supported way to route that sensor through Argus and get ISP-processed YUV (e.g. NV12) without a full ODM-style bring-up?
  2. If Argus / HW ISP is not realistically available for this sensor without NVIDIA camera-stack integration, does NVIDIA still recommend V4L2 RAW + GPU (CUDA/NPP/OpenCV CUDA) or VPI for non-catalog sensors on this platform?
  3. Are there official references (for JP 4.6 / R32.7) that clearly distinguish “ISP inside the sensor module” vs “ISP on Tegra / Argus” for developers bringing up RAW sensors?

I understand that full stack bring-up (device tree, camera firmware/configuration, ISP tuning) may require a partner engagement. I am mainly looking for official guidance on whether HW ISP via Argus is ever in scope for user-developed tegracam drivers on TX2 + JP 4.6, or whether we should plan on GPU/CPU ISP only.

I can provide nv_tegra_release, media-ctl -p, and v4l2-ctl --list-ctrls / --list-formats-ext output if that helps.

Thank you.