Vision Components cameras on Torizon

Hey Community!

I am trying to use mipi cameras from Vision Components (VK000514) on my Toradex board together with Torizon OS. Looks like OS doesn’t have any drivers by default. Does anybody have experience where to get and how to integrate them?

tdx-info:

Software summary

Bootloader: U-BootKernel version: 6.6.101-7.4.0-g557af2783d91 #1-Torizon SMP PREEMPT Thu Sep 25 07:49:28 UTC 2025Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/f3a4c0d28279618ce1a13ed03824ad923d19df32c7a6a7097a35bdde21420134/0Distro name: NAME=“Torizon OS”Distro version: VERSION_ID=7.4.0-build.28Distro variant: VARIANT=“Docker”Hostname: verdin-imx8mp-15637947

Hardware info

HW model: Toradex Verdin iMX8M Plus on Verdin Development BoardToradex version: 0063 V1.1BSerial number: 15637947Processor arch: aarch64

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


MIPI Camera Integration with Torizon OS

Based on your hardware setup (Verdin iMX8M Plus on Verdin Development Board with Torizon OS 7.4.0), you’re working with a well-supported platform for camera integration(1).

General Camera Integration Approach

For MIPI cameras that don’t have built-in drivers in Torizon OS, you’ll need to use TorizonCore Builder to create a custom image with the required camera drivers(1)(2). This is the standard approach for integrating third-party camera modules.

Required Steps

  1. Device Tree Overlay Creation: You’ll need to create device tree overlays specific to your Vision Components VK000514 camera(2)

  2. Driver Integration: Use TorizonCore Builder to add the camera driver source code to your custom Torizon OS image(2)

  3. Container Setup: Configure containers for camera usage with proper hardware access(1)

Hardware Access Requirements

When working with cameras in containers, you need specific bind mounts and device access(1):

  • /dev: Mount for device access(1)
  • /tmp: For Weston GUI interaction(1)
  • /sys: Kernel subsystem access(1)
  • /var/run/dbus: System services access(1)

Building Process

The process involves(2):

  1. Installing TorizonCore Builder(2)
  2. Cloning the torizon-samples repository(2)
  3. Creating a tcbuild.yaml configuration file(2)
  4. Building the custom image with your camera drivers(2)

Container Requirements

You’ll typically need three containers(2):

  • Weston container for display(2)
  • Camera driver container (custom for your Vision Components camera)(2)
  • GStreamer container for video pipeline(2)

Recommendation

Since Vision Components cameras require specific drivers not included in standard Torizon OS, I recommend checking with Vision Components directly for:

  • Device tree overlay examples for their VK000514 camera
  • Driver source code compatible with kernel 6.6.101
  • Integration documentation specific to their MIPI camera modules

The integration process follows the same pattern as other third-party cameras like the Framos FSM:GO series documented in our guides(2).

Best regards, Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

Hello @svt,

Vision Components usually supplies the needed drivers in a Yocto Layer.
You can find it here: Vision Components MIPI CSI-2 driver for NXP SoMs
Using Yocto would be the most straight-forward way to integrate the driver, as it is the method supplied by the vendor.
However, using TorizonCore Builder may be possible as well, by adding an external module.

Do you know which sensor is used on the VK000514?
I have supported one of your colleagues before with Vision Components cameras, but maybe you are using a different sensor.

Best Regards,
Bruno