Server / Chipsets / Ingenic T31

CameraStack on the
Ingenic T31.

Ready-made camera software for the T31: capture, hardware H.264 and H.265, RTSP streaming and a standards-compliant ONVIF interface, with overlays, motion events and person detection, integrated directly against Ingenic's IMP media SDK.

Available reference platform Class / Camera SoC

The silicon

Inside the
T31.

A compact camera SoC: a single MIPS application core with SIMD instructions, Ingenic's ISP, hardware H.264 and H.265 encoders and a JPEG encoder, with the DRAM in the package.

CPU
XBurst MIPS32r2
single core, with SIMD
ISP
Ingenic ISP
sensor input, statistics for motion
Video encode
H.264 & H.265
two hardware encoders, plus JPEG
Memory
128 MB DRAM
T31X reference, 64 MB Linux + 64 MB media

On this silicon

What runs today.

  • 01 Sensor capture through the T31's ISP and hardware encoders
  • 02 Multi-profile hardware encode, H.264 or H.265 Main: 2496x1440, 1080p or 720p and 640x360, at 25 fps
  • 03 Up to four ONVIF profiles sharing the two hardware encoders
  • 04 The full RTSP transport family: TCP, UDP, HTTP tunnelling, WebSocket and multicast
  • 05 ONVIF Device, DeviceIO, Media, Media2, Events, Imaging, Analytics and Advanced Security services
  • 06 TLS: HTTPS management and snapshots, RTSP over HTTPS, secure WebSocket, rtsps:// streaming and SRTP over UDP and TCP, with camera-held certificates managed through the ONVIF TLS Configuration Add-on
  • 07 Imaging control wired to the ISP: brightness, contrast, saturation, sharpness, exposure, gain, white balance and backlight compensation
  • 08 Polygon motion detection: ONVIF MotionRegionDetector rules on an ISP statistics grid
  • 09 Person detection on the CPU with tracked ONVIF scene metadata
  • 10 Hardware JPEG snapshots and four-slot text and date/time OSD, shared with the snapshot path
  • 11 Live encoder control: bitrate changes mid-stream, codec and resolution changes without stopping the other stream
  • 12 Metadata streaming and events, including the ONVIF ImageTooDark tampering event

How this port works

The reference port runs on the T31X, the 128 MB member of Ingenic’s T31 family. Other T31 variants use the same IMP SDK; their memory sizes and sensor choices set the starting point for a product integration.

The T31’s sensor, ISP and encoders are reached through Ingenic’s IMP media SDK. CameraStack handles platforms like this with a C producer: a compact native adapter, written in C against the IMP libraries, that drives the vendor media pipeline from sensor to hardware encoder and passes encoded video, motion events and object observations to the portable core. There is no GStreamer dependency on the device. ONVIF request handling, authentication, profile management, events and RTSP delivery are the same portable core used on every other platform. On the T31X, the whole stack runs on the single MIPS core in the 64 MB of its 128 MB that is left to Linux, with the other 64 MB reserved for the media pipeline.

Video profiles

The T31 has two hardware encoders, a main stream and a substream, and each can use H.264 Main or H.265 Main independently:

EncoderResolutionFrame rateBitrate
Main2496x1440, 1920x1080 or 1280x72025 fps512 to 4096 kbit/s
Substream640x36025 fps256 to 1024 kbit/s

Up to four ONVIF profiles share these two encoders, so a client can create extra profiles without needing more hardware encoding channels. Profiles attached to the same encoder use the same video settings.

Bitrate changes apply to the running encoder. A codec or resolution change rebuilds only the selected encoding channel, while the sensor, ISP and the other stream keep running.

Imaging, snapshots and OSD

The Imaging service operates the running ISP: brightness, contrast, saturation and sharpness, automatic or manual exposure and gain, automatic or manual white balance, and backlight compensation.

JPEG snapshots come from the hardware JPEG encoder at the selected profile’s resolution. The OSD has four slots for text and date/time, composed into both video streams and the snapshots, so they always match.

Motion and person analytics

The Analytics service runs up to four ONVIF MotionRegionDetector polygons over the ISP’s statistics grid, with named region events and an aggregate motion alarm. The same statistics, together with the exposure settings, drive the ONVIF ImageTooDark tampering event.

Person detection runs on the CPU’s SIMD instructions through Ingenic’s JZDL runtime, at one or two inferences per second, using images from the existing substream. Detected people are tracked with stable IDs by the shared tracker and published as ONVIF scene metadata. The model package is optional: a product can leave it out and keep video and motion events.

Built on the Ingenic IMP SDK

The producer builds against Ingenic’s IMP media SDK and the matching sensor driver. The ISP, the two video encoders and the JPEG encoder are driven directly through IMP, and the producer builds on the same shared common core as CameraStack’s other custom-SDK platforms. Bringing up another T31 product starts from its silicon variant, sensor, SDK version and memory layout.

Field note

A full camera stack in 64 MB.

The T31X leaves 64 MB of memory and a single MIPS core for Linux. That is enough for the same CameraStack Server that runs on the larger platforms, with ONVIF, every RTSP transport, TLS, events, motion analytics and person detection.

Read the port story

Build on it

Designing a
T31 camera?

The port work is already done, at the level of the Ingenic IMP 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 Ingenic T31