Hey everyone, I’m pulling my hair out trying to get an Arducam Mini IMX477 working on a Jetson Orin Nano. I’ve been searching everywhere but I can’t find the right deb package for the camera driver.
My kernel version is: 5.15.148-tegra-36.4.7-20250918154033
The Jetson type shows up as UNKNOWN when I check. I tried installing the drivers I could find but keep getting an error — basically no matching deb package exists for this kernel version.
Does anyone have a link to a driver that’s actually compatible with this kernel? I’m stuck until I can get the right package.
Thanks for the detailed kernel info — that helps narrow things down.
You’re running kernel 5.15.148-tegra-36.4.7 on the Orin Nano, and the issue is that the Arducam IMX477 driver deb for that specific kernel revision simply wasn’t publicly available yet. That’s why none of the existing packages matched.
Good news though — a new build has just been released that targets your exact kernel. I’ve sent you the download link and the .deb package via private message. Check your inbox here on the forum.
That did the trick — the driver installed without any errors and both cameras are now detected. Thanks for that!
But now I’ve got a new problem and it’s driving me nuts: the image quality is really bad. There’s this weird tearing and artifacts at the bottom of every frame, like the lower portion of the image is corrupted or out of sync. It’s happening identically on both cameras, so I don’t think it’s a hardware defect.
Here’s what it looks like — there’s just this band of garbage/tearing at the bottom of every frame.
My guess is this is some kind of software or configuration issue rather than the cameras themselves. Any ideas on what could cause this kind of video tearing and how to fix it?
Interesting — the fact that both cameras show the exact same tearing pattern strongly points to a system-level configuration issue rather than faulty sensors. My suspicion is it might be related to the carrier board or how the camera pipeline is set up.
Let’s diagnose this in two steps:
Step 1 — Identify your carrier board
Can you share a clear photo of your Jetson setup? I’d like to confirm the exact carrier board model you’re using. Some boards have known quirks with certain camera configurations and there might be a compatibility flag we need to set.
Step 2 — Test with the native IMX477 driver
This is the more important test. We need to rule out whether the issue is specific to the Arducam driver stack. Let’s enable the native NVIDIA IMX477 driver temporarily and see if the tearing goes away:
That’ll let you enable the native IMX477 driver. Once it’s active, test the camera feed again and let me know if the tearing disappears. That’ll tell us whether the root cause is in the Arducam driver or somewhere deeper in the pipeline.
Okay, so I went ahead and re-ran the jetson-io configuration — I’d actually already enabled the native IMX477 driver through that tool a while back but I figured it was worth going through the process again.
And… that fixed it. Completely. No more tearing, no artifacts, clean image across the entire frame on both cameras.
I’m not 100% sure what happened under the hood — maybe installing the Arducam deb package overwrote or clashed with some of the device tree settings from the earlier jetson-io config? Either way, re-running jetson-io and re-enabling the native IMX477 driver sorted everything out.