Hi,
We set it in the device tree before. But it still not work.
hello alexigu01x,
it looks part of your v4l command-line has truncated, please note you should specify width/height as same as your mode definition in the v4l command-line.
When we used nvgstcapture to get frames, if we didn’t enable the aelock parameter, we got the same errors as before, and the stream would crash, if we enabled the aelock, the stream wouldn’t crash.
It’s the journalctl log:
log.txt (12.9 KB)
hello alexigu01x,
it has some Error BadParameter failures reported, which might be incorrect ISP tuning parameters were used.
if issue gone by removing the ISP file, it should be an issue with parameter settings.
for quick testing, please try reproduce this again by removing the ISP file and cache files,
for instance,
/var/nvidia/nvcam/settings/camera_overrides.isp
/var/nvidia/nvcam/settings/nvcam_cache_0.bin
We removed the ISP, and it worked well. Do you know any possible reasons why our sensor worked well with the ISP file when we enabled the aelock?
hello alexigu01x,
as mentioned, it should be an issue with parameter settings.
please review those ISP settings, especially the AE related parameters.
hello alexigu01x,
BTW, this discussion thread is a little bit too long.
the issue you met currently is not the same as original description.
in order to avoid confusion, and, for better supports. (since the streaming issue has addressed with workarounds),
please submit another new topic for following-up.
thanks
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.