Introduction to BSP Development

A Board Support Package (BSP) is the foundational software layer that enables Linux to run on specific hardware. For vision systems, BSP development requires expertise in bootloaders, kernel drivers, and multimedia frameworks.

BSP Architecture Overview

A complete BSP for vision systems consists of the following layers:

Bootloader: U-Boot with secure boot support
Linux Kernel: Mainline or vendor-specific with drivers
Device Tree: Hardware description for the kernel
Root Filesystem: Busybox or systemd-based
Multimedia Framework: V4L2, GStreamer, hardware codecs
AI Runtime: TensorFlow Lite, ONNX Runtime, vendor SDK

Bootloader Development

U-Boot Configuration

U-Boot serves as the primary bootloader for ARM-based vision systems. Key configuration steps:

bash

# Clone U-Boot source
git clone https://github.com/u-boot/u-boot.git
cd u-boot

# Configure for target board
make CROSS_COMPILE=aarch64-linux-gnu- vision_board_defconfig

# Build
make CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc)

Secure Boot Implementation

Secure boot ensures only authenticated firmware runs on the device:

Generate RSA-2048 or RSA-4096 signing keys
Configure U-Boot with FIT image verification
Sign kernel and device tree with private key
Program public key hash into OTP/eFuse
Enable secure boot in hardware security module

Store signing keys in a Hardware Security Module (HSM). Compromised keys cannot be revoked in devices with OTP-programmed key hashes.

Kernel Development

Kernel Configuration

Vision system kernels require specific subsystem configurations:

text

# Essential kernel options for vision systems
CONFIG_VIDEO_V4L2=y
CONFIG_MEDIA_SUPPORT=y
CONFIG_VIDEOBUF2_DMA_CONTIG=y
CONFIG_VIDEO_MEM2MEM_DEINTERLACE=y
CONFIG_DRM=y
CONFIG_DRM_PANEL=y
CONFIG_FB=y
CONFIG_FB_SIMPLE=y

Camera Driver Development

Implementing a V4L2 camera sensor driver involves:

Implement v4l2_subdev_ops for sensor control
Define supported formats and resolutions
Implement streaming start/stop callbacks
Handle I2C register configuration
Integrate with ISP driver if applicable

Device Tree Configuration

Device Tree describes hardware to the kernel:

dts

/ {
    camera@0 {
        compatible = "secutronic,vision-sensor";
        reg = <0x36>;
        clocks = <&csi_clk>;
        clock-names = "xclk";
        
        port {
            sensor_out: endpoint {
                remote-endpoint = <&csi_in>;
                data-lanes = <1 2 3 4>;
                clock-lanes = <0>;
            };
        };
    };
};

Multimedia Framework

V4L2 Subsystem

Video4Linux2 provides the standard Linux API for video capture and processing. Key components:

Component	Function
v4l2-ctl	Command-line control utility
media-ctl	Media controller configuration
v4l2-dbg	Debug and register access
v4l2-compliance	Driver conformance testing

Hardware Codec Integration

Vision SoCs include hardware video encoders/decoders. Integration steps:

Implement V4L2 M2M (memory-to-memory) driver
Support stateful codec API for H.264/H.265
Configure DMA buffer management
Integrate with GStreamer via v4l2videoenc/dec
Implement rate control and GOP configuration

Build System

We recommend Yocto Project for reproducible BSP builds: