AVerMedia integrates JetPack 7.2 vision stack

AVerMedia Technologies and Stereolabs have added NVIDIA JetPack 7.2 support across ZED X GMSL cameras and AVerMedia Jetson carrier boards, coordinating the board support, device tree and camera driver work required to move embedded vision systems into production.

The collaboration covers boards using NVIDIA Jetson Orin and Jetson Thor modules. Stereolabs maintains its ZED X camera driver architecture, firmware and ZED software development kit, while AVerMedia handles the integration needed for its carrier boards. That division allows each company to update its part of the platform without requiring the customer to rebuild the connection between the two from scratch after every hardware or software change.

A Jetson module does not define the complete embedded system. The carrier board determines power delivery, external interfaces, camera connections and much of the physical I/O around the processor. Linux also needs an accurate description of those resources through the device tree, while the camera driver has to match the kernel, interface and software release running on the chosen board.

Changes in any one layer can affect the others. A new JetPack version can alter the Linux kernel or supporting libraries, while a board revision may change how an interface is exposed to the operating system. A camera release can introduce another driver requirement. Without a controlled integration process, manufacturers can end up maintaining several slightly different software combinations across prototypes and production machines.

Under the joint workflow, AVerMedia can adapt the device tree for its hardware and generate drivers for the JetPack and Jetson Linux versions required by the customer. Stereolabs can continue developing its camera firmware, image signal processing and ZED software independently. The partners say this allows the two development paths to proceed in parallel rather than waiting for successive integration cycles.

JetPack 7.2 also adds Jetson agent skills intended to optimise memory use across the software stack. NVIDIA’s embedded modules have to divide available memory between the operating system, camera buffers, perception models and the application itself. With several image streams and AI workloads operating simultaneously, memory reserved unnecessarily by one part of the stack reduces the capacity left for inference or image processing.

The integration supports adjustments to bootloader allocations, kernel memory reservations, user space services and inference memory use. Those changes do not increase the physical memory fitted to the module, but they can reduce resources consumed by the underlying software environment. The practical gain depends on the customer workload and the amount of memory already committed to camera and model processing.

Reproducible Debian packages record the driver, device tree, installation flow and kernel code used in a deployed configuration. JetPack 7.2 also brings official Yocto support, giving manufacturers another route to create controlled Linux images rather than relying on manually assembled development installations.

Long service lives make that traceability important when a field update introduces a security fix, new JetPack release or revised camera driver without changing the hardware. Engineers need to know which board definition and software components were used in the original system before they can assess whether an update changes device behaviour.

ZED X cameras use GMSL connections aimed at robotics and machine vision systems where cameras may be positioned away from the compute module. Stereo camera systems also place sustained bandwidth and processing demands on the Jetson platform because multiple image streams feed depth and perception workloads. Driver and memory behaviour can therefore affect whether a configuration that works in development remains stable when several cameras and AI models operate together.

JetPack 7.2 support uses existing Jetson processors and ZED X camera hardware; the change is in the maintained software boundary between camera drivers and production carrier boards. AVerMedia’s support pages already list JetPack 7.2 software for Jetson Thor and Orin hardware, providing a deployment route for the integrated stack.

Maintaining that software combination as a reproducible production configuration removes one recurring integration task without changing the underlying vision algorithm. The camera, carrier board and Jetson module still have to meet processing, thermal and mechanical requirements, while the managed driver and device tree combination provides a controlled baseline for production and later updates.