ADAS Display Pipeline Capabilities
Camera Overlay Pipeline
Sparklet accepts a decoded camera frame buffer from the platform ISP and assigns it to a dedicated hardware rendering layer. On NXP i.MX 8 with Vivante GPU and on Renesas RA8D1 with Mali-Limav, compositing is performed entirely in hardware — zero CPU involvement in the pixel blend. Parking guidelines, proximity warning bars, object detection bounding boxes, and lane departure indicators are rendered as vector elements in the overlay layer, updated at 60 fps even when the camera feed runs at 30 fps. The overlay layer is configured in Flint UI Designer and exported as standard C code.
Hardware Layer Composition
Sparklet's multi-layer rendering engine composites the camera feed layer, the GUI overlay layer, and the safety warning layer independently — each on dedicated hardware planes. On platforms with a hardware compositor (i.MX 8, RA8D1, RH850 D/AVE2D), GPU blending replaces all software compositing. This architecture means the camera feed and the warning overlay are never rendered in the same software pass — a safety warning icon can be drawn to its layer by a priority interrupt handler without waiting for the camera frame decode to complete. See the hardware acceleration page for GPU layer details.
Low-Latency Rendering
Hardware layer compositing on NXP i.MX 8 Vivante GPU and Renesas RA8D1 Mali GPU achieves sub-50 ms end-to-end camera-to-overlay latency — keeping object detection annotations accurately aligned with moving objects. Sparklet's compositing step itself adds less than one display frame (under 16 ms at 60 fps refresh) to the total pipeline latency. For surround-view systems, Sparklet's 3DView widget renders a real-time 3D bowl projection of four camera feeds around a vehicle model on i.MX 8 — updated frame-synchronously with camera capture. See the 3D graphics page for pipeline details.
