Error running gst-launch-1.0 pipeline with Arducam IMX477 quad camera on Jetson

Hi, I’m trying to set up an Arducam 12MP*4 IMX 477 quad camera on a Jetson Nano, and I keep getting an error when I run the gst-launch-1.0 pipeline from the docs. Installation went fine, but as soon as I run this command it fails and shows an error (screenshot attached):

FRAMERATE=13 # Framerate can go from 2 to 13 for 4032x3040 mode

gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! “video/x-raw(memory:NVMM),width=4032,height=3040,framerate=$FRAMERATE/1” ! nvvidconv ! “video/x-raw(memory:NVMM),width=1432,height=1080,framerate=$FRAMERATE/1” ! nvoverlaysink

I’m following the Arducam quick-start for the multi-camera CamArray. Any idea what’s going wrong?

Thanks for the details. Before I dig into the pipeline error, can you reboot the device and then run this diagnostic so I can see the full state of the system? Run these in order:

wget -O arducam-camera-bug-report-nvidia https://github.com/ketai-dhr/arducam-camera-bug-report/releases/download/tools/arducam-camera-bug-report-nvidia
chmod +x ./arducam-camera-bug-report-nvidia
./arducam-camera-bug-report-nvidia

It will produce arducam-bug-report.txt in the current directory. Attach that here and I’ll take a look.

Done. I rebooted and ran the script, and I’m attaching arducam-bug-report.txt as requested.

Thanks, I’ve gone through the report. I’d like to take a closer look at this live on your Nano. I’ve sent you the remote support details via private message - please check your messages and install the remote tool on the Jetson Nano.

Okay, I installed the remote tool on the Nano and I’ve sent the access details back through private message. Let me know when you want to connect.

Got it. During the session we went over the setup and one thing I suggested was updating the system to 32.7.3. Can you go ahead with that update, then reboot and try the camera again?

I updated to 32.7.3 as suggested, but now the Nano doesn’t detect the camera at all. I restarted the Nano and even moved the camera to a different port, but it still doesn’t show up. Screenshot attached.

Let’s separate the detection problem from the original gst-launch issue. Can you check whether the sensor is visible at the driver level? Try:

ls /dev/video*

and also run nvgstcapture-1.0 to see if it can open the camera. That will tell us if this is a detection problem or just the pipeline.

Okay, I got the detection sorted out. The camera shows up again and I can actually take pictures with nvgstcapture-1.0 now. But the original gst-launch-1.0 pipeline still fails with the same error.

Thanks for the update. To summarize where we are: after the 32.7.3 upgrade we hit a detection regression, but that’s now resolved and nvgstcapture-1.0 can capture images, so the sensor itself is working. The remaining problem is the gst-launch-1.0 pipeline using nvarguscamerasrc at 4032x3040 converted to 1432x1080 with nvoverlaysink, which still fails. As a workaround you can use nvgstcapture-1.0 for capturing, but I still need to investigate why the gst-launch pipeline is failing. I’ll follow up once I’ve reproduced it.