# Perfect images with v4l2src, but green images with nvargus **URL:** \ **Category:** Jetson Orin NX\ **Tags:** camera\ **Created:** [February 5, 2024, 10:19am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822 "2024-02-05T10:19:10Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 5, 2024, 10:19am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/1 "2024-02-05T10:19:10Z")
Hello, I have recently switched from jp511 to jp512. With jp511, v4l2src and nvarguscamerasrc images were perfect, but with jp512 the images captured by nvargus are always pure green. Images captured using v4l2 are perfect. Maybe I forgot something in the update, but I don’t find what it is. Here are the log of nvargus-daemon, with enableCamScfLogs=5 and enableCamPclLogs=5, and the relevant parts of the DT. The DT excerpts are identical to the ones with jp511. [nad.log](https://forums.developer.nvidia.com/uploads/short-url/bpm72eqW5eM7efN8eRct43nbsbu.log) (581.2 KB) [sensors.txt](https://forums.developer.nvidia.com/uploads/short-url/a2CaVZ3vfdfoZb0oRw7Q0DDQIEz.txt) (4.5 KB) [module.txt](https://forums.developer.nvidia.com/uploads/short-url/yoOFD3oPm546oHSXTEMoXncBxk9.txt) (850 Bytes) I get no error message from the nvargus clients , nvarguscamerasrc or nvargus\_nraw, and it’s difficult to distinguish what nvargus-daemon is complaining about. e.g. ```auto loadSubType: Sensor type missing in DT, 206 ``` or ```auto [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. ``` or ```auto LSC:patch width less than 12 ``` Any idea ? ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 8, 2024, 8:41pm UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/3 "2024-02-08T20:41:52Z")
Are the above error messages important to explain the problem ? How should they be fixed ? Is there another way to add debugging to the work of the ISP ? ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 15, 2024, 7:16am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/4 "2024-02-15T07:16:44Z")
Remove the \*.isp file at /var/nvidia/nvcam/settings/ if have it. Thanks ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 20, 2024, 3:57pm UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/5 "2024-02-20T15:57:04Z")
> [@ShaneCCC](#): > > Remove the \*.isp file at /var/nvidia/nvcam/settings/ if have it. I have done that. It does not solve the problem. More info : - with “gst-launch-1.0 v4l2src” or “v4l2-ctl --stream-mmap”, the images are perfect - with “nvargus\_nvraw --format jpg”, the images are solid green - with “gst-launch-1.0 nvarguscamerasrc ! nvjpegenc” the images are solid black I test also with the pattern generator of the sensor, so exposure and gain do not matter. Do the error or log messages of nvargus-daemon point at some error in my DT or driver ? My parts in the DT and my driver have not changed since jp511, where I had perfect images using argus. Are the sources of nvargus-daemon available (jetpack-5.1.2 version) ? ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 21, 2024, 5:49am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/6 "2024-02-21T05:49:37Z")
Try to add below to /var/nvidia/nvcam/settings/camera\_overrides.isp lensShading.correction\_type.enableLSC = FALSE; sudo chmod 664 /var/nvidia/nvcam/settings/camera\_overrides.isp ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 21, 2024, 9:40am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/7 "2024-02-21T09:40:37Z")
Thank you ShaneCCC, but that does not improve the behaviour. I still get solid green or black images using argus. Here are the messages from nvargus-daemon : ```auto === NVIDIA Libargus Camera Service (0.99.33)=== Listening for connections...=== nvargus_nvraw[3249]: Connection established (FFFF9F739900)OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module0 OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module1 NvPclHwGetModuleList: No module data found NvPclHwGetModuleList: No module data found OFParserGetVirtualDevice: NVIDIA Camera virtual enumerator not found in proc device-tree ---- imager: Found override file [/var/nvidia/nvcam/settings/camera_overrides.isp]. ---- [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. Config Error: sensor load cfg: 1, cfg check: 0 ---- imager: Found override file [/var/nvidia/nvcam/settings/camera_overrides.isp]. ---- [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. Config Error: sensor load cfg: 1, cfg check: 0 === nvargus_nvraw[3249]: CameraProvider initialized (0xffff98713000)SCF: Error BadValue: NvPHSSendThroughputHints (in src/common/CameraPowerHint.cpp, function sendCameraPowerHint(), line 56) [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. Config Error: sensor load cfg: 1, cfg check: 0 LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12LSC:patch width less than 12PowerServiceCore:handleRequests: timePassed = 746 === nvargus_nvraw[3249]: CameraProvider destroyed (0xffff98713000)=== nvargus_nvraw[3249]: Connection closed (FFFF9F739900)=== nvargus_nvraw[3249]: Connection cleaned up (FFFF9F739900) ``` Please notice ```auto [IspConfigCheckNR] Error: both NR v8 and v6 are enabled ``` and ```auto LSC:patch width less than 12 ``` What do those messages mean ? ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 22, 2024, 5:08am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/8 "2024-02-22T05:08:11Z")
Please dump the device tree to check. ```auto sudo dtc -I fs -O dts -o extracted_proc.dts /proc/device-tree ``` ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 22, 2024, 7:18am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/9 "2024-02-22T07:18:31Z")
Here you are [dt512.txt](https://forums.developer.nvidia.com/uploads/short-url/1RcBfxO2TjeZwExQRIe5uJpURmt.txt) (253.0 KB) The only changes compared to the jp511 DT are in the nvidia-provided parts. Where are the sources of nvargus-daemon (jp512 version) ? ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 22, 2024, 5:26pm UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/10 "2024-02-22T17:26:45Z")
Could you attached the picture to tell the problem more clear. Thanks ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 22, 2024, 7:40pm UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/11 "2024-02-22T19:40:39Z")
Here you are. The same source, configured using the pattern generator of the image sensor. Using ```auto gst-launch-1.0 v4l2src device=/dev/video1 num-buffers=1 ! video/x-raw,format=GRAY8 ! jpegenc ! filesink location=imx1-111.jpg ``` ![imx1-111](https://global.discourse-cdn.com/nvidia/original/4X/f/8/5/f8580c911fb51e14ca320bb2d84da8168350e43e.jpeg) and then using ```auto nvargus_nvraw --format jpg --c 1 --file byargus_nraw-1.jpg ``` ![byargus_nraw-1](https://global.discourse-cdn.com/nvidia/original/4X/2/d/9/2d9c6419e0b7de17bb8878386e737f2de244a3ee.jpeg) or using ```auto gst-launch-1.0 -v nvarguscamerasrc sensor-id=1 ! "video/x-raw(memory:NVMM)" ! \ nvjpegenc ! multifilesink location=argus%02d.jpg max-files=2 ``` ![argus90](https://global.discourse-cdn.com/nvidia/original/4X/a/f/e/afeedbbf287ad374878eaeb8a9a1f37260725912.jpeg) The exact same problem happens with the other (smaller) sensor. ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 23, 2024, 7:43am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/12 "2024-02-23T07:43:55Z")
What’s below command shows. ```auto v4l2-ctl --list-formats-ext ``` ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 23, 2024, 7:48am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/13 "2024-02-23T07:48:24Z")
> [@ShaneCCC](#): > > `v4l2-ctl --list-formats-ext` ```auto ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'RG12' (12-bit Bayer RGRG/GBGB) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [1]: 'BA12' (12-bit Bayer GRGR/BGBG) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [2]: 'GB12' (12-bit Bayer GBGB/RGRG) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [3]: 'BG12' (12-bit Bayer BGBG/GRGR) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [4]: 'Y16 ' (16-bit Greyscale) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [5]: 'GREY' (8-bit Greyscale) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) ``` ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 23, 2024, 8:05am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/14 "2024-02-23T08:05:25Z")
Looks like the sensor mode doesn’t like v4l2-ctl query. 1. The size in the device tree is 2472x2064 but sensor driver report 4128x3008 2. Remove all pixel format only report RG12 by sensor driver. ```auto mode0 { discontinuous_clk = "no"; readout_orientation = [30 00]; exposure_factor = "1000000"; mclk_khz = "37125"; phy_mode = "DPHY"; dpcm_enable = "false"; max_gain_val = "48"; framerate_factor = "1000000"; min_hdr_ratio = [31 00]; num_lanes = [34 00]; pixel_t = "bayer_bggr12"; max_framerate = "67200000"; min_gain_val = [30 00]; pixel_phase = "bggr"; mode_type = "bayer"; pix_clk_hz = "396000000"; cil_settletime = [30 00]; gain_step_pitch = "0.1"; active_h = "2064"; max_exp_time = "165770"; dynamic_pixel_bit_depth = "12"; lane_polarity = [36 00]; active_w = "2472"; min_exp_time = "16.165"; max_hdr_ratio = "64"; min_framerate = "1000000"; default_framerate = "67200000"; csi_pixel_bit_depth = "12"; inherent_gain = [31 00]; embedded_metadata_height = [31 00]; line_length = "2472"; tegra_sinterface = "serial_a"; gain_factor = [31 00]; }; ``` ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 23, 2024, 8:15am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/15 "2024-02-23T08:15:42Z")
> [@ShaneCCC](#): > > Looks like the sensor mode doesn’t like v4l2-ctl query. > > 1. The size in the device tree is 2472x2064 but sensor driver report 4128x3008 > > 2. Remove all pixel format only report RG12 by sensor driver. I have two sensors, one is 2472x2064, the other one is 4128x3008. That’s not the problem. The answer I posted is from sensor 1, to match the images in the previous post. I work with L4T since jetpack 3.0.0, and my driver has always reported all those formats, to ease testing and to support monochrome and bayer sensors with different orientations, using the HREVERSE/VREVERSE settings in the sensor. This worked up to with jetpack-5.1.1. Nevertheless I will try and let you know. ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 23, 2024, 8:30am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/16 "2024-02-23T08:30:54Z")
First result (disappointing) : ```auto qcam5@ubuntu:~$ v4l2-ctl --list-formats-ext -d1 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'RG12' (12-bit Bayer RGRG/GBGB) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [1]: 'Y16 ' (16-bit Greyscale) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [2]: 'GREY' (8-bit Greyscale) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) qcam5@ubuntu:~$ nvargus_nvraw --format jpg --c 1 --file /tmp/byargus_nraw-1.jpg nvargus_nvraw version 1.14.0 ("nvargus_nvraw") Error BadParameter (0x04): No events in queue (in capture_nvraw/src/mobile/ArgusNvRawCapture.cpp, func captureRequest(), line 700) ("nvargus_nvraw") Error BadParameter (0x04): (propagating from capture_nvraw/src/mobile/ArgusNvRawCapture.cpp, func capture(), line 810) ("nvargus_nvraw") Error BadParameter (0x04): Unable to capture (propagating from capture_nvraw/src/mobile/main.cpp, func main(), line 97) qcam5@ubuntu:~$ ``` and here are the messages from nvargus-daemon ```auto Connection established (FFFF8F194900)OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module0 OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module1 NvPclHwGetModuleList: No module data found NvPclHwGetModuleList: No module data found OFParserGetVirtualDevice: NVIDIA Camera virtual enumerator not found in proc device-tree ---- imager: Found override file [/var/nvidia/nvcam/settings/camera_overrides.isp]. ---- [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. Config Error: sensor load cfg: 1, cfg check: 0 ---- imager: Found override file [/var/nvidia/nvcam/settings/camera_overrides.isp]. ---- [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. Config Error: sensor load cfg: 1, cfg check: 0 socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running? socket connection /var/lib/nvphs/nvphsd.ctl to PHS failed: No such file or directory D/ libnvphs:socket: Warning: connecting to Power Hinting Service failed. Is PHS running? queue_or_send() failed CameraProvider initialized (0xffff886e7c20)SCF: Error BadValue: NvPHSSendThroughputHints (in src/common/CameraPowerHint.cpp, function sendCameraPowerHint(), line 56) [IspConfigCheckNR] Error: both NR v8 and v6 are enabled. Config Error: sensor load cfg: 1, cfg check: 0 LSC:patch width less than 12LSC:patch width less than 12(NvCamV4l2) Error BadParameter: 0x32314742 pixelFormat not found under current active buffer type (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function setActivePixelFormat(), line 1457) (NvOdmDevice) Error BadParameter: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function enableStreamingConfiguration(), line 2343) (NvOdmDevice) Error BadParameter: enableStreamingConfiguration FAILED (in dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorBase.cpp, function writeMode(), line 328) (NvOdmDevice) Error BadParameter: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 218) (NvCamV4l2) Error InvalidState: Invalid active Mode Size (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function streamControl(), line 1655) (NvOdmDevice) Error InvalidState: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 277) (NvCamV4l2) Error BadParameter: 0x32314742 pixelFormat not found under current active buffer type (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function setActivePixelFormat(), line 1457) (NvOdmDevice) Error BadParameter: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function enableStreamingConfiguration(), line 2343) (NvOdmDevice) Error BadParameter: enableStreamingConfiguration FAILED (in dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorBase.cpp, function writeMode(), line 328) (NvOdmDevice) Error BadParameter: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 218) (NvCamV4l2) Error InvalidState: Invalid active Mode Size (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function streamControl(), line 1655) (NvOdmDevice) Error InvalidState: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 277) (NvCamV4l2) Error InvalidState: Invalid active Mode Size (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function streamControl(), line 1655) (NvOdmDevice) Error InvalidState: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 277) (NvCamV4l2) Error InvalidState: Invalid active Mode Size (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function streamControl(), line 1655) (NvOdmDevice) Error InvalidState: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 277) Module_id 30 Severity 2 : (fusa) Error: Timeout propagating from:/capture/src/fusaViHandler.cpp 776 SCF: Error InvalidState: Sensor 1 already in same state (in src/services/capture/CaptureServiceDeviceSensor.cpp, function setErrorState(), line 100) SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 0 draining session frameEnd events 3 (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 635) SCF: Error InvalidState: Sensor 1 already in same state (in src/services/capture/CaptureServiceDeviceSensor.cpp, function setErrorState(), line 100) SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 1 draining session frameEnd events 2 (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 635) SCF: Error InvalidState: Sensor 1 already in same state (in src/services/capture/CaptureServiceDeviceSensor.cpp, function setErrorState(), line 100) SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 2 draining session frameEnd events 1 (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 635) SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 1 draining session frameStart events 2 (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameStart(), line 532) LSC:patch width less than 12SCF: Error Timeout: Sending critical error event for Session 1 (in src/api/Session.cpp, function sendErrorEvent(), line 1039) (NvCamV4l2) Error InvalidState: Invalid active Mode Size (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function streamControl(), line 1655) (NvOdmDevice) Error InvalidState: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 277) PowerServiceCore:handleRequests: timePassed = 2505 (NvCamV4l2) Error BadParameter: 0x32314742 pixelFormat not found under current active buffer type (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function setActivePixelFormat(), line 1457) (NvOdmDevice) Error BadParameter: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function enableStreamingConfiguration(), line 2343) (NvOdmDevice) Error BadParameter: enableStreamingConfiguration FAILED (in dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorBase.cpp, function writeMode(), line 328) (NvOdmDevice) Error BadParameter: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 218) (NvCamV4l2) Error InvalidState: Invalid active Mode Size (in /dvs/git/dirty/git-master_linux/camera/utils/nvcamv4l2/v4l2_device.cpp, function streamControl(), line 1655) (NvOdmDevice) Error InvalidState: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function apply(), line 277) SCF: Error Timeout: (propagating from src/services/capture/CaptureServiceDeviceViCsi.cpp, function waitCompletion(), line 368) SCF: Error Timeout: (propagating from src/services/capture/CaptureServiceDevice.cpp, function pause(), line 1034) SCF: Error Timeout: During capture abort, syncpoint wait timeout waiting for current frame to finish (in src/services/capture/CaptureServiceDevice.cpp, function handleCancelSourceRequests(), line 1129) Module_id 30 Severity 2 : (fusa) Error: Timeout propagating from:/capture/src/fusaViHandler.cpp 776 SCF: Error InvalidState: Sensor 1 already in same state (in src/services/capture/CaptureServiceDeviceSensor.cpp, function setErrorState(), line 100) SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 3 draining session frameEnd events 1 (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 635) SCF: Error BadParameter: CC has already been disposed (in src/components/CaptureContainerManager.cpp, function dispose(), line 161) SCF: Error BadParameter: CC has already been disposed (in src/components/CaptureContainerManager.cpp, function dispose(), line 161) SCF: Error InvalidState: Timeout!! Skipping requests on sensor GUID 1, capture sequence ID = 3 draining session frameStart events 1 (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameStart(), line 532) SCF: Error Timeout: NvRmSyncWait failed (in src/api/Buffer.cpp, function cpuWaitFences(), line 622) SCF: Error Timeout: (propagating from src/api/Buffer.cpp, function cpuWaitInputFences(), line 543) SCF: Error Timeout: (propagating from src/api/Buffer.cpp, function acquire(), line 680) SCF: Error Timeout: (propagating from src/api/Buffer.cpp, function ScopedBufferLock(), line 657) SCF: Error Timeout: NvRmSyncWait failed (in src/api/Buffer.cpp, function cpuWaitFences(), line 622) SCF: Error Timeout: (propagating from src/api/Buffer.cpp, function cpuWaitInputFences(), line 543) SCF: Error Timeout: (propagating from src/api/Buffer.cpp, function acquire(), line 680) SCF: Error Timeout: (propagating from src/api/Buffer.cpp, function ScopedBufferLock(), line 657) PowerServiceCore:handleRequests: timePassed = 16806 CameraProvider destroyed (0xffff886e7c20)(NvOdmDevice) Error FileOperationFailed: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/HotplugMonitor.cpp, function close(), line 153) (NvOdmDevice) Error FileOperationFailed: Failure in HotplugMonitor::close() (in dvs/git/dirty/git-master_linux/camera-partner/imager/src/HotplugMonitor.cpp, function removeHotplugCallback(), line 830) ``` I see that nvargus-daemon is looking for 0x32314742, that’s actually BG12, not RG12. ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 23, 2024, 8:44am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/17 "2024-02-23T08:44:19Z")
Second attempt, this time with only BG12 : ```auto qcam5@ubuntu:~$ v4l2-ctl --list-formats-ext -d1 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'BG12' (12-bit Bayer BGBG/GRGR) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [1]: 'Y16 ' (16-bit Greyscale) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) [2]: 'GREY' (8-bit Greyscale) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) qcam5@ubuntu:~$ nvargus_nvraw --format jpg --c 1 --file /tmp/byargus_nraw-1.jpg nvargus_nvraw version 1.14.0 capture: Total captured frame count 90 writeToFile_Jpeg: file /tmp/byargus_nraw-1.jpg is successfully created qcam5@ubuntu:~$ ``` No error message this time, but the image is again solid green. ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 23, 2024, 8:50am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/18 "2024-02-23T08:50:05Z")
Please remove Y16 and GREY to get the image by v4l2-ctl and argus to check. Thanks ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 23, 2024, 9:32am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/19 "2024-02-23T09:32:44Z")
Here you are ```auto qcam5@ubuntu:~$ v4l2-ctl --list-formats-ext -d1 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'BG12' (12-bit Bayer BGBG/GRGR) Size: Discrete 4128x3008 Interval: Continuous 0.034s - 22.934s (0.044-29.200 fps) qcam5@ubuntu:~$ v4l2-ctl -d1 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=1 --stream-to=/tmp/v4l2.raw < qcam5@ubuntu:~$ ls -l /tmp/v4l2.raw -rw-rw-r-- 1 qcam5 qcam5 24834048 Feb 23 10:20 /tmp/v4l2.raw qcam5@ubuntu:~$ expr 24834048 / 3008 / 2 4128 qcam5@ubuntu:~$ rawtopgm -bpp 2 -maxval 65535 -littleendian 4128 3008 < /tmp/v4l2.raw | pnmtopng > /tmp/v4l2.png ``` ![v4l2](https://global.discourse-cdn.com/nvidia/original/4X/2/1/4/214434056ac0aa17c402bd8f2014cda3515ed1ca.png) ```auto qcam5@ubuntu:~$ nvargus_nvraw --format jpg --c 1 --file /tmp/byargus_nraw-1.jpg nvargus_nvraw version 1.14.0 capture: Total captured frame count 90 writeToFile_Jpeg: file /tmp/byargus_nraw-1.jpg is successfully created qcam5@ubuntu:~$ ``` ![byargus_nraw-1](https://global.discourse-cdn.com/nvidia/original/4X/2/d/9/2d9c6419e0b7de17bb8878386e737f2de244a3ee.jpeg) nvargus deamon keeps complaining about ‘[IspConfigCheckNR] Error: both NR v8 and v6 are enabled.’ and 90 times ‘LSC:patch width less than 12’ The ‘both NR v8 and v6 are enabled’ message comes from /usr/lib/aarch64-linux-gnu/tegra/libnvscf.so. What is tested there ? Are the sources of that library available for me or for you to understand the meaning of that cryptic message ? ---
**Author:** ![ShaneCCC](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/shaneccc/32/14043_2.png) [@ShaneCCC](https://forums.developer.nvidia.com/u/ShaneCCC)\ **Post date:** [February 26, 2024, 8:18am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/20 "2024-02-26T08:18:12Z")
NR v6 shouldn’t enable. Did you confirm remove the \*.isp files at /var/nvidia/nvcam/settings/? Please remove all the \*.isp and bin file and reboot the system to check if the message still shows. Thanks ---
**Author:** ![phdm](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@phdm](https://forums.developer.nvidia.com/u/phdm)\ **Post date:** [February 26, 2024, 8:55am UTC](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822/22 "2024-02-26T08:55:33Z")
> [@ShaneCCC](#): > > /var/nvidia/nvcam/settings/ Here is the current situation. The camera\_overrides.isp file is the one you told me to add. With that situation, I get the error message ‘[IspConfigCheckNR] Error: both NR v8 and v6 are enabled.’ ```auto root@ubuntu:/home/qcam5# ls -la /var/nvidia/nvcam/settings/ total 16 drwxr-xr-x 2 root root 4096 Feb 21 09:45 . drwxr-xr-x 6 root root 4096 Nov 15 16:01 .. -rw-rw-r-- 1 root root 48 Feb 21 09:45 camera_overrides.isp -rw-r--r-- 1 root root 102 Aug 1 2023 README.txt root@ubuntu:/home/qcam5# cat /var/nvidia/nvcam/settings/camera_overrides.isp lensShading.correction_type.enableLSC = FALSE; root@ubuntu:/home/qcam5# ``` later … I have now removed the .isp file : ```auto qcam5@ubuntu:~$ sudo ls -la /var/nvidia/nvcam/settings total 12 drwxr-xr-x 2 root root 4096 Feb 26 09:43 . drwxr-xr-x 6 root root 4096 Nov 15 16:01 .. -rw-r--r-- 1 root root 102 Aug 1 2023 README.txt qcam5@ubuntu:~$ ``` and rebooted the board. The error message is again present, and the resulting image again green :( What is ‘NR v6’ ??? [Next page](https://forums.developer.nvidia.com/t/perfect-images-with-v4l2src-but-green-images-with-nvargus/281822.md?page=2)