I’m working on the sipl system with MAX96712 connected to MAX9295 and IMX490, Jetpack 7.2.1, and I have a question regarding exposure and would like to ask for some advice.
The ‘SetExposure’ function in the sensor driver is only invoked during initialization. Why is this function called only once? And how do we set exposure updates afterwards? I’m wondering if there is another way to configure exposure. Many thanks if anyone can help answer this question!
SIPL supports runtime exposure updates through the auto-control pipeline. In your Camera HAL/UDDF path, sensor settings reach SetSensorControls(), which calls the driver’s
SetExposure(). Updates occur when AE/AWB produces new sensor settings; SetExposure() does not necessarily run for every frame. See the SIPL notification documentation (https:// Camera SIPL Notifications — NVIDIA Jetson Linux Developer Guide ).
Your log shows one SetSensorControls() → SetExposure() call requesting 0.010000 seconds. Afterwards, embedded-data parsing reports:
ParseExposure: shs1:10000, vmax:2000, … exposureTimePrev[0]:0.250000
Bad exp0 value: 0.250000
ParseExposure failed
Failed to parse embedded data
SIPLParseTopEmbDataInfo failed. nvmStatus: 7
This suggests the frame metadata/control feedback path is failing. Please check that the exposure-to-register conversion in SetExposure() and the register-to-exposure conversion
in ParseExposure() match the IMX490 mode, timing, register units, and embedded-data layout. The requested 10 ms and parsed 250 ms warrant investigation.
The log also reports Unsupported IMX490 revision 0x00 detected; please verify the sensor identification read and supported revision handling.
Please share the complete nvsipl_camera command, selected plugin/NITO, and relevant SetSensorControls(), SetExposure(), and ParseExposure() implementations so we can narrow down
the cause.
With prolonged continuous frame output, SetExposure gets invoked only once. It seems that AE is not generating new parameters, or AE is not taking effect at all.