CameraStack on the
Axera AX630C.

Ready-made camera software for the AX630C: capture, hardware encode, RTSP streaming and a standards-compliant ONVIF interface, integrated directly against Axera's vendor SDK.

Available reference platform Class / Camera SoC

The silicon

Inside the
AX630C.

An edge-AI vision SoC built for smart cameras: a dual-core application processor, a high-TOPS neural engine, and a 4K-capable AI-ISP and hardware video pipeline on a single die.

CPU: Dual-core Cortex-A53; up to 1.2 GHz
AI engine: 12.8 TOPS; INT4 (3.2 TOPS INT8)
ISP: AI-ISP, up to 4K; 2-frame HDR, 3DNR
Video encode: H.264 & H.265; up to 4K @ 30fps
Memory: LPDDR4x; up to 4 GB

On this silicon

What runs today.

01 Sensor capture through the AX630C's ISP pipeline
02 Multi-profile hardware encode, H.264 and H.265
03 RTSP streaming
04 ONVIF services
05 Runtime encoder control through ONVIF, including resolution, bitrate, GOP and on-demand keyframes

How this port works

The AX630C has no vendor GStreamer stack; its camera and encoder are reached through Axera’s native SDK. CameraStack handles platforms like this with a producer plugin: a small native component that owns the vendor media pipeline, sensor through ISP, scaler and hardware encoder, and hands encoded video to the portable core. From there the core takes care of the rest, RTSP streaming to clients and the ONVIF services, as a single static binary, unchanged from every other platform.

Control flows the other way too. Because the producer owns the encoder, settings changed through ONVIF are applied live through the vendor API, and synchronisation-point requests map to on-demand keyframes: clients get a camera they can genuinely configure, not just watch.

The integration sits at the level of the SDK that ships with the chip’s BSP, the same surface any custom AX630C board design already has, and it carries across the Axera chips that share the same SDK.

Built on the Axera SDK

The port builds against the V3.0.0 Axera MSP SDK tree, with a pinned GNU AArch64 toolchain so builds stay reproducible. The producer links Axera’s runtime libraries directly: libax_sys for system and memory management, libax_ivps for the image and video processing subsystem, libax_venc for the hardware encoder, and libax_ae and libax_awb for the ISP’s auto-exposure and auto-white-balance control.

ax630c / live stream probe

$ ffprobe rtsp://<user>:<pass>@ax630c.lan:8554/onvif/Profile_1
ffprobe version 7.1.1-1ubuntu4.2 Copyright (c) 2007-2025 the FFmpeg developers
  ...
Input #0, rtsp, from 'rtsp://<user>:<pass>@ax630c.lan:8554/onvif/Profile_1':
  Metadata:
    title           : CameraStack Server (AX630C)
  Duration: N/A, start: 0.138167, bitrate: N/A
  Stream #0:0: Video: h264 (Main), yuvj420p(pc, bt470bg/bt470bg/bt709, progressive), 2688x1520, 30 fps, 30 tbr, 90k tbn
  Stream #0:1: Data: none

The main profile runs at 2688x1520. The probe's second track is the ONVIF metadata stream, carrying analytics and events alongside the video.

Build on it

Designing an
AX630C product?

The port work is already done, at the level of the SDK your board already has. Use CameraStack Server as your complete camera stack, or as a drop-in ONVIF interface for a pipeline you already have. Evaluation builds are available to teams building real products.

Talk to us about the AX630C