I am running the nvsipl_camera sample on my DRIVE AGX Xavier with a Sony IMX390 camera. This is the command line I use to start it:
./nvsipl_camera --platform-config "IMX390RGGBE5_200FOV_RGGB_CPHY_x2" --link-enable-masks "0x0001 0x0000 0x0000 0x0000" -d 0 -w 1 --icrop "0+1216" --disableISP1Output --nvsci
Sometimes, everything works just fine. My latency measurement setup shows 65ms on average (glass-to-glass), which is expected for that setup and the display I am using.
However, most of the time, I observe the following two problems:
- frames are displayed “out of order”. I have some LED set up that blink in regular intervals, so it is easy to observe it with the naked eye. Also when objects move through the field of view, there is some “rubberbanding” when the out-of-order frames are displayed.
- the latency goes up to over 200ms.
- this only EVER happened with the --nvsci flag. Without that flag, I never saw that behavior.
- I tried to mess with NUM_PACKETS and replace all
#define NUM_PACKETS (6U)with
#define NUM_PACKETS (3U). If I understand it correctly, that should NOT solve the problem. However, it looks like the problem is less “severe” with NUM_PACKETS=3. I do not understand why.
Is there a known issue in the --nvsci variant of the nvsipl_camera sample?
DRIVE OS Linux 5.2.6
Target Operating System
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
SDK Manager Version
Host Machine Version
native Ubuntu 18.04