Hi, I’m trying to install the Arducam driver on my Jetson Nano but it keeps failing. When I run the install script it just spits out something like “Cannoot find the corresponding deb package, please send the following information to support@arducam” and then stops. Not sure what I’m doing wrong here, any help would be great.
Hey, sure, let’s figure this out. Can you post your setup details so I can check compatibility?
Specifically:
- Which Arducam camera model are you using?
- Which Jetson board / carrier board are you running?
- The output of
uname -rfor the kernel version.
Also paste the exact error text the script prints, that message usually gets followed by the detected kernel and Jetson type.
Camera is the Arducam 12MP IMX477 Motorized Focus camera.
Board is a yahboom Jetson NANO 4GB Board Developer Kit(SUB).
Kernel version: 4.9.140-tegra-32.4.3-20200924161615
Jetson type: Nano
And yes the script printed exactly:
Cannoot find the corresponding deb package, please send the following information to support@arducam
Kernel version: 4.9.140-tegra-32.4.3-20200924161615
Jetson type: Nano
Thanks, that’s helpful. So the installer builds a package name from your exact kernel version and Jetson type, then looks for a matching prebuilt .deb in its repo. If there’s no matching entry, it bails with that “cannot find the corresponding deb package” message instead of building one. Basically it couldn’t find a driver package for your specific combination.
Can you run these so we can confirm what it’s actually seeing?
uname -r
cat /etc/nv_tegra_release
Also, which install script/package did you download, and can you paste the full terminal output from running it (not just the final lines)?
Here you go:
$ uname -r
4.9.140-tegra-32.4.3-20200924161615
$ cat /etc/nv_tegra_release
# R32 (release), REVISION: 4.3, GCID: 22002642, BOARD: t210ref, EABI: aarch64, DATE: Fri Jul 31 05:06:27 UTC 2020
I used the Arducam IMX477 install script from the product page. The full output is pretty much just:
Cannoot find the corresponding deb package, please send the following information to support@arducam
Kernel version: 4.9.140-tegra-32.4.3-20200924161615
Jetson type: Nano
I tried re-running it a couple of times and also rebooted, same result every time.
OK. Your kernel string lines up with a stock L4T R32.4.3 Nano kernel, so that part looks normal. But the installer is matching against the board too, not just the L4T version.
Your board is a yahboom Jetson NANO 4GB Board Developer Kit(SUB) — that’s a third-party carrier board, not an official NVIDIA developer kit. The Arducam driver packages are built and published for the official NVIDIA dev kit only. When your board reports as a non-official one, the script won’t find a corresponding .deb for that combination, which is exactly the error you’re hitting.
So this isn’t a command you typed wrong or a corrupted download — it’s a compatibility limit on the driver side.
Ah, I see. So the yahboom board is the problem? I assumed any Nano-based board would work the same. Is there anything I can do to get it running, or is it just not supported?
Right — the carrier board is the issue. Arducam only supports the official NVIDIA development kit for this driver, and non-official carrier boards like the yahboom one aren’t covered, so there’s no matching deb package for it.
What you’d need to do is make sure your carrier board is an official one. If it is, the installer should find the right package. With a third-party board, the install will keep failing the same way no matter how many times you re-run it.
Got it. So to confirm: if I switch to an official Jetson Nano dev kit with the same kernel, the IMX477 install should work, and the yahboom board is just out of luck for now?
Yep, that’s the summary:
- The error “cannot find the corresponding deb package” comes from the installer not finding a driver package that matches your board + kernel + Jetson type combo.
- The root cause is that your carrier board is a third-party yahboom board, and Arducam driver support currently only covers the official NVIDIA development kit.
- First step is to make sure you’re on an official carrier board / dev kit — only the official development kit is supported right now.
So it’s not something on your end you can patch around; it’s a support-scope limitation on the driver. If you move to an official Nano dev kit with that same R32.4.3 setup, the installer should find the matching package.