I can capture raw images using the command v4l2-ctl --set-ctrl bypass_mode=0 --stream-mmap --stream-count=1 --stream-to=imx477.raw -d /dev/video2, but cannot do so using the argus_camera tool.
The attachment is my execution：
sudo su
service nvargus-daemon stop
export enableCamScfLogs=5
nvargus-daemon 2>&1 | tee log.txt
The log obtained afterwards, could you please help analyze it?log.txt ([en.number.human.storage_units.format])
What’s the argus_camera log?
First, I execute sudo su
service nvargus-daemon stop
export enableCamScfLogs=5
nvargus-daemon 2>&1 | tee log.txt, then open another window to execute ./argus_camera to obtain the log
Can you understand what I mean?
It’s the log obtained by executing the command nvargus-daemon 2>&1 | tee log.txt after I run the argus_camera tool.
Please check if Argus detect any camera sensor by below command.
nvargus_nvraw --lps
video2 is in raw10 format.
Modify the device tree to leave only one sensor to try.
And get the log without enableCamScfLogs=5
Currently, there are only sensors in my device tree.
May I ask if I still need to execute
sudo su,
service nvargus-daemon stop,
and nvargus-daemon 2>&1 | tee log.txt
to obtain the log?
This is the log obtained after executing sudo su, service nvargus-daemon stop, and nvargus-daemon 2>&1 | tee log.txt, then executing argus_camera in another window.
log.txt (7.0 KB)
Try nvargus_nvraw to capture.
nvargus_nvraw --format "jpg" --file test.jpg --skipframes 30
This is the result of the execution
I noticed that there are only modules0 to modules2 in my dts, but when I check /proc/device-tree/tegra-camera-platform/modules, I found 3 more modules. I wonder if this will affect image output?
Make sure by nvargus_nvraw –lps
Hi ShaneCCC
argus_camera can already be turned on and display images. Thank you very much for your support.
It’s the modules that have an impact.
I will remove the parts that may be affected, and then add a status attribute to each node, which will be fine.
Thank you very much for your support, which has helped me find a direction to solve the problem.
Best Regard.
But I found another problem. My sensor has two modes, but when I click on mode 0 and 1 in the Sensor mode index of the Argus_camera tool, the driver always prints 0. What is the reason for this?
This is the log I added in the driver’s set_mode function. I found that when I click on mode 1, it still prints 0.
It has been solved. Thank you very much.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
