How to restart recording with Libargus in case of error

[sarperyurttas36]

Hi Everyone,

I have an application with 2 IMX477 cameras being recorded at the same time and running on Jetson Orin NX 16 GB/Jetpack 5.1.1/L4T r35.3.1.

After a couple of hours of running, argus crashes and I restart the application and nvargus daemon with another application and continue recording however it gives a huge load of additional workload to the workflow of my application.

I tried to disable multiprocessing and restart the recording without restarting the application but it hangs on the line cameraProvider.reset() so I cannot recover the error from there without restarting the application.

Libargus handling of bad camera packets

I was doing outage various error tests today with the 09_camera_jpeg_capture example, and I seem to be able to recover from Argus::STATUS_TIMEOUT errors most of the time by going into software standby, waiting a few seconds, and then going back into streaming mode, but was wondering if there are any other types that libargus should be able to recover from. If so, do you have any ways that I can easily and reliably simulate these types of errors? Also, does libargus have the capability of reset…

Argus errors on some boots

hello haensler, there’s Argus error recovery mechanism with the Jetpack-4.6 release version, it’s software approach, once there’s timeout failure from camera pipeline. Argus will report it via error flag, EVENT_TYPE_ERROR, and the application has to shutdown. you may see-also Argus/public/samples/userAutoExposure for reference. however, what exactly the failure is before sending images via CSI?

In these two entries, moderators mentioned that the application needs to shut down if an error happens however I think it should be possible.

I cannot reproduce the errors as it’s happening on the cameras and currently, I’m stopping and starting the application again to replicate errors. Is there a better way to do that?

/sys/kernel/debug/camera-video0/streaming file node doesn’t exist so I cannot use it to trigger an error.

[ShaneCCC]

I would suggest upgrade to latest release like JP6 r36.4.3 or JP5 r35.6

Thanks

[sarperyurttas36]

Hi,

I cannot upgrade to the latest version since the devices in production are in this version.

[ShaneCCC]

You can check the patches from the link.

[Argus] camera stability and error resiliency bug fixes

JP5.1 nvarguscamera doesn't recover from single NVCSI failure

hello casperlyngesen.mogensen, here’s pre-built update, Topic243051_Jun05.7z (1.8 MB) could you please based-on JetPack-5.1.1/l4t-r35.3.1 to update the binaries with attachment, you may preform a warm-reboot, i.e. $ sudo reboot after replace the binary files.

[Argus] pre-built update to resolve memory corruption within libnvargus.so

Argus pipeline randomly gets error

hello pepijn.vanheiningen, we normally not back-port changes. anyways, please give it a try with this attachment on JP-5.1.1 Topic268519_Oct11.7z (267.7 KB)

[Argus] Extend timeout values to avoid socket timeout errors reported by Argus

Argus Error OverFlow

hello angel.corrales, there’re some dependency, this failure might due to my unclean code-base, I’ve check-out entire tree to r35.3.1 for builting those binary files, please kindly test again for verification. for instance, Topic278999_Jan31_v2.7z (2.3 MB)

[sarperyurttas36]

Hi,

Thanks for the update. I will give those patches a try but I have some questions first.

1- The last patch is on the 31st of January so this means it has all the other patches I assume. Is this correct?

2- Even if the patches don’t solve my issue, would it be okay to keep updated libraries or revert back to the original libraries?

[ShaneCCC]

1. Sorry I can’t confirm that why I suggest update to latest release.
2. You can save the original .so file and restore it.