Cannot find deb package for OV5647 driver on Jetson Orin Nano during install_full.sh

Nvidia Jetson Cameras
1

Hi all, I’m trying to get an OV5647 camera module working on my Jetson Orin Nano Dev Kit. I ran the install_full.sh script to set up the camera drivers but it keeps failing with this error:

cannot find a corresponding deb package

Not really sure what’s going on here. Has anyone else run into this? The camera is connected properly as far as I can tell, and the system sees it on the CSI interface. Any pointers would be appreciated.

2

Can you share a bit more about your setup? Specifically:

  • Which Jetson module and carrier board are you using?
  • What’s the output of uname -r?
  • And just to confirm, you’re using the OV5647 sensor, correct?

I have a suspicion about what might be happening here but want to check your environment first.

3

Sure, here you go:

  • Platform: NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super
  • Kernel: 5.15.148-tegra-36.4.7-20250918154033
  • Camera sensor: OV5647

Yeah, it’s definitely the OV5647 module. I had it lying around from an old Raspberry Pi project and figured I’d repurpose it. Is that a problem?

4

That explains it. Unfortunately, the OV5647 sensor does not have camera driver support on the Jetson platform — and this isn’t a configuration issue or a bug with the install script. It’s expected behaviour.

On the Jetson Orin Nano (and Jetson platforms in general), only certain camera sensors have driver packages available. When install_full.sh runs, it looks for a pre-built deb package matching your sensor and kernel combination. Since no such package exists for the OV5647, you get the “cannot find a corresponding deb package” error.

The supported sensors on this platform include the IMX219 and IMX477. You’d need to swap the OV5647 out for one of those. Once you do, the install script should detect the sensor and pull the correct driver package without any issues.

5

Ah, that makes sense. I had a feeling it might be something like that since I pulled it from an old Pi setup. Bit of a bummer but at least I know it’s not something I messed up on my end. Ok, thank you for your help — I’ll grab an IMX219 and give that a try instead.