Regarding the difference in exposure value of Jetson NANO and NX cameras equipped with IMX327 sensor

[mszeta]

Hello, @JerryChang

1. you having exactly same driver between Xavier and Nano?
   yes

2. could you please dump the settings of each frame to compare the difference

############################################################

xavier nx

cat i2c@3180000/rbpcv2_veye327_a@3b/mode0/default_exp_time
33334

cat i2c@3180000/rbpcv2_veye327_a@3b/mode0/max_exp_time
660000

cat i2c@3180000/rbpcv2_veye327_a@3b/mode0/min_exp_time
30

############################################################

nano

cat /proc/device-tree/host1x/i2c@546c0000/imx327_a@1a/mode0/default_exp_time
33334

cat /proc/device-tree/host1x/i2c@546c0000/imx327_a@1a/mode0/max_exp_time
660000

cat /proc/device-tree/host1x/i2c@546c0000/imx327_a@1a/mode0/min_exp_time
30

v4l2-ctl -L says like below.

Xavier NX imx327

manager@manager-desktop:~$ v4l2-ctl -L

Camera Controls

                     group_hold 0x009a2003 (bool)   : default=0 value=0 flags=execute-on-write
                    sensor_mode 0x009a2008 (int64)  : min=0 max=1 step=1 default=0 value=0 flags=slider
                           gain 0x009a2009 (int64)  : min=0 max=714 step=3 default=0 value=15 flags=slider
                       exposure 0x009a200a (int64)  : min=30 max=660000 step=1 default=33334 value=9999 flags=slider
                     frame_rate 0x009a200b (int64)  : min=2000000 max=33000000 step=1 default=30000000 value=21000000 flags=slider

Nano imx327:

type or paste code hermanager@manager-desktop:~$ v4l2-ctl -L

Camera Controls

                     group_hold 0x009a2003 (bool)   : default=0 value=0 flags=execute-on-write
                    sensor_mode 0x009a2008 (int64)  : min=0 max=2 step=1 default=0 value=0 flags=slider
                           gain 0x009a2009 (int64)  : min=0 max=714 step=3 default=0 value=9 flags=slider
                       exposure 0x009a200a (int64)  : min=30 max=660000 step=1 default=33334 value=2433 flags=slidere

Thank you.

[JerryChang]

hello mszeta,

sorry, I don’t meant check via sysnodes, or v4l to parse these static values.
that should be identical since it’s checking by driver side.

I doubt the lux value isn’t meet the requirement, or the AE region is target some dark area.
so, please enable Argus daemon logs,
for example,

$ sudo su 
# pkill nvargus-daemon
# export enableCamCoreLogs=5
# nvargus-daemon 2>&1 | tee argus-output.log

this will configure debug flag of camera stack, you may expect lots of logs pop-up.
we’ll need to look into debug prints to understand why Nano series to keep increasing the exposure. please attach log files for reference.
thanks

[mszeta]

Hello, @JerryChang

Here is argus-output.log

nano_argus-output.log (39.6 MB)
nx_argus-output.log (4.0 MB)

I captured the nano argus-output log longer.
If you need additional logs, please request them.

Thank you.

[JerryChang]

hello mszeta,

as you can see. all of them has converged, convergenceStatus: 2 it means the specific algorithm is in a converged state.
for example,
Nano
runBreakDownAlgorithm output ---: convergenceStatus: 2, framerate 21.00000, requiredCain 0.00388 totalAchievedCGains 0.00388 with AA 0.17361 {step 0, f-Number 2.40000}, ET 0.02234, AG 1.00000, ISPDG 1.00000

Xavier NX
runBreakDownAlgorithm output ---: convergenceStatus: 2, framerate 21.00000, requiredCain 0.01983 totalAchievedCGains 0.01983 with AA 0.17361 {step 0, f-Number 2.40000}, ET 0.04000, AG 2.85617, ISPDG 1.00000

that’s interesting.
Nano using exposure-time (0.02234) and also analog-gain (1.00000) that’s lower than Xavier NX. that’s not reasonable you see overexposure capture results on Nano.

please check your kernel driver layer, is it program the correct value to camera driver?