The Jetson AGX Orin can’t use Argus to capture images with the IMX219 on version R39.2.
The device I’m using is the Orin developer kit.
Using the latest R39.2 system version.
Use the official nv_imx219.ko driver.
I can normally capture raw images using v4l2, but I can’t get the processed images with the system-supported argus. Does the official version have ISP files for IMX219 on Orin? Could you share the ISP file if possible?
The ISP file that worked fine on R36.5.0 can’t be used on R39.2.
Please help take a look at this problem, thanks.
Hello @744159057!
Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.
If this was an incorrect assessment, please send me a direct message.
Disclaimer: this moderation suggestion and message were generated with AI assistance.
hello 744159057,
may I double check which Jetson platform you’re working with.
and.. are you using Raspberry PI IMX219? it should works with Orin Nano/NX instead of AGX Orin.
besides, please share the failure logs for reference.
hello JerryChang,
I’m using the Orin development kit and made an adapter board that can connect to the IMX219 MIPI camera. It works fine on version R36.5.0, which means the camera, the link, and the adapter board are all working properly, but on the latest R39.2 version, I can’t use Argus to capture images.
The ISP file I’m using works fine for lighting up the camera on R36.5. Could you provide the ISP file for the IMX219 on R39.2 or any related info?
Thanks for the clarification on your setup. Since v4l2 raw capture works on R39.2 but Argus fails, the issue is likely in the Argus daemon or ISP configuration layer rather than the driver itself.
To help narrow this down, please provide:
-
The exact error message or failure output when Argus attempts to capture on R39.2 (e.g., timeout, permission denied, ISP initialization error, etc.)
-
Complete Argus daemon logs from a capture attempt. You can collect these by:
sudo pkill nvargus-daemon
export enableCamScfLogs=5
nvargus-daemon 2>&1 | tee argus-output.log
Then run your capture application and share the log output.
-
ISP file comparison: Have you checked whether the ISP tuning files differ between R36.5.0 and R39.2? The file that worked on R36.5.0 may need adjustments for R39.2’s Argus version.
Once we have the logs and error details, we can identify whether this is an ISP tuning issue, a version incompatibility, or a configuration mismatch.
hello carolyuu
This is the ISP file I’m using and the log after running the command.
Camera_overrides.tar.gz (12.5 KB)
argus-output.log (30.4 KB)
Hi @744159057,
How are you setting the badge property in the camera module device tree?
On JetPack 7, I have noticed that the module part number must correctly match the one embedded in the NITO file. NITO files are usually located in: /var/nvidia/nvcam/settings/
According to the NVIDIA module properties documentation, the expected format is: CAMERA_BOARD_ID_POSITION_PART_NUMBER
You can try explicitly loading the NITO file:
sudo systemctl stop nvargus-daemon
sudo -i
export NVCAMERA_NITO_PATH=/var/nvidia/nvcam/settings/<file>.nito
nvargus-daemon
Keep that terminal running and test the Argus application from another terminal.
If you do not have a NITO file, you can try the legacy/default configuration:
export NVCAMERA_NITO_PATH=CONFIG
nvargus-daemon
If you have a NITO file but do not know its part number, this command may help identify it:
strings /var/nvidia/nvcam/settings/<file>.nito | head -n 3
Regards,
Kimberly Carvajal
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com
hello kimberly.carvajal
Thanks, after specifying this environment variable, I can see the images now.