Why Argus in Jetson 35.2.1 and 35.3.1 produce very fuzzy image?

The attached sharp image was taken with Jetson 35.1.0, but fuzzy with 35.3.1
Camera registers are the same, camera portion of .dts the same.
I used the same command each time:
nvargus_nvraw --c 0 --mode 0 --exp0 “0.016666,1” --file test --format “raw,jpg”
and the resulting .raw image is very similar, but .jpg produced by 35.2.1 or 35.3.1
is so fuzzy, it is unusable.
How to restore the old sharp image behavior of 35.1.0?
Thank you

What’s the sensor module?

It is a custom omnivision sensor board 800x800 pixels

Could you share the badge info of this sensor and check if any ISP override file at /var/nvidia/nvcam/settings/ for both version.


		modules {

			module1 {
				badge = "ecam_hexcu130-2";
				position = "rear2";
				orientation = [31 00];
				phandle = <0x49f>;

				drivernode0 {
					devname = "e-CAM130A_CUXVR-2";
					proc-device-tree = "/proc/device-tree/i2c@3180000/tca9548@70/i2c@2/ar1335_c@42";
					pcl_id = "v4l2_sensor";
					status = "disabled";
					phandle = <0x4a0>;

Originally we made our testcam dts from imx274 with some modifications, which worked OK on Jetson 35.1.0:
module10 {
status = “okay”;
badge = “testcam_bottom_A6V26”;
position = “bottom”;
orientation = “1”;

drivernode0 {
    status = "okay";
    pcl_id = "v4l2_sensor";
    devname = "testcam 30-0036";
    proc-device-tree = "/proc/device-tree/i2c@3180000/tca9546@70/i2c@0/testcam_a@36";

In /var/nvidia/nvcam/settings I only see nvcam_cache_0.bin, nvcam_cache_1.bin, serial_no_0.bin and serial_no_1.bin,
but they can be deleted without any difference. Same on 35.1.0 and 35.3.1

I also verified that if I use syncStereoRawReprocess sample app from 35.3.1 on .raw file recorded on 35.1.0 then it also produces fuzzy image.
So, the problem is definitely not with sensor, but with Argus ISP processing.
I attached the raw file in case you want to test it yourself. Size is 800x800 bggr16.
send_nvidia_35.1.0_good.raw (1.2 MB)

Please modify the “A6V26” in badge info to avoid duplicate with reference sensor to load incorrect ISP configure.
Please check the image both on 35.1.0 and 35.3.1 to check if any image different.

OK, I renamed badge to “testcam_bottom_TEST” and now the image looks completely different from what it was before, however there is no difference anymore between 35.1.0 and 35.3.1 and both are sharp.
The documentation only says that third part of the badge name has to be unique, but it does not say that some keywords have some special treatment by ISP. Is it possible to get a list of badge IDs, which receive special treatment, like A6V26?
Is it possible to use Argus ISP API to restore the image to look like what it was when we used badge “A6V26”?
Thank you

I would suggest to create new badge info instead of modify from any reference dts to avoid it.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.