What Embedded GUI Runs on NXP i.MX RT and i.MX 8?

Sparklet is a production-ready embedded GUI library for NXP i.MX RT and i.MX 8 platforms. On the i.MX RT1170, Sparklet uses the on-chip PXP (Pixel Pipeline) accelerator for hardware 2D scaling, rotation, alpha blending, and LCDC compositing — the exact operations that define smooth instrument cluster animations and responsive industrial touch panels. On the i.MX 8, Sparklet runs under embedded Linux using the Mali GPU via OpenGL ES 2.0, enabling 3D UI elements, live camera feed integration, and CarPlay or Android Auto screen mirroring.

NXP's portfolio spans a wide performance range. Sparklet is architected to scale across it: the same widget codebase, the same Flint design files, and the same application logic compile on both the i.MX RT1170 MCU and the i.MX 8 MPU. Moving a product up the performance ladder is a toolchain change and a HAL swap — not a UI rewrite. See the full platform support list for all 9 supported hardware families.

NXP Platform Support

i.MX RT1170 — Crossover MCU

NXP i.MX RT1170 — Dual-Core Crossover MCU with PXP Acceleration

The NXP i.MX RT1170 combines a Cortex-M7 at 1 GHz and a Cortex-M4 co-processor with 2 MB of on-chip SRAM and an integrated PXP (Pixel Pipeline) accelerator. The PXP performs 2D scaling, rotation, alpha blending, colour space conversion, and rectangle fill in hardware.

Sparklet's i.MX RT1170 HAL uses the PXP for all blit operations:

Widget blit — Pre-rendered widget regions copied to framebuffer by PXP, not the CPU.
Alpha-blended overlays — Transparent panels, modal dialogs, and notification badges composite in hardware.
Rotate and scale — Image widgets and rotary displays transform without CPU-bound loops.
Dual framebuffer swap — PXP writes to back buffer while LCDIF scans out front buffer — tear-free 60 fps.

The i.MX RT1170 also supports dual display output from a single MCU — a primary cluster display plus a secondary driver information panel — using separate LCDIF instances and Sparklet's multi-screen API. The 2 MB on-chip SRAM is sufficient for a single framebuffer at lower resolutions, avoiding external SDRAM cost in many designs.

i.MX 8 — Linux MPU

NXP i.MX 8 — Linux Application Processor with Mali GPU

The NXP i.MX 8 family combines Cortex-A application cores with a Cortex-M real-time co-processor and a Mali GPU (G52 or G57) supporting OpenGL ES 2.0 and Vulkan on select variants. The standard platform for automotive infotainment, ADAS display head units, and premium HMI running embedded Linux.

Sparklet on i.MX 8 supports two rendering backends:

OpenGL ES 2.0 backend — Full GPU-accelerated rendering via the Mali driver. Enables Sparklet's 3D widget set, hardware layer compositing, and shader-based visual effects.
Linux framebuffer backend (DRM/KMS) — Direct framebuffer write for lighter applications where GPU driver complexity must be minimised.

CarPlay and Android Auto support is available via Sparklet's screen mirroring protocol integration. ADAS camera feed integration is supported via hardware video capture (ISP or CSI-2) — Sparklet renders the camera feed as a background layer and composites the widget overlay in hardware. See ADAS display GUI for architecture details.

PXP & VGLite Accelerators

NXP Hardware Accelerators — PXP, VGLite, and LCDIF

NXP's hardware accelerator ecosystem for embedded GUI applications spans several components that Sparklet integrates with:

PXP (Pixel Pipeline) — Present on i.MX RT family. Handles 2D blit, scale, rotate, alpha blend, and colour conversion in hardware. Sparklet's RT1170 HAL uses PXP for all compositing operations.
VGLite / VGLITE GPU — Available on select i.MX RT variants. Vector graphics acceleration for smooth curves, paths, and anti-aliased rendering without full OpenGL ES stack.
LCDIF (LCD Interface) — Integrated on i.MX RT1170. Drives RGB parallel displays directly, with hardware timing generation and double-buffer support.
Mali GPU (i.MX 8) — Full OpenGL ES 2.0 / Vulkan GPU. Used for 3D widgets, shader effects, and high-throughput compositing on MPU targets under embedded Linux.

See hardware acceleration for a full breakdown of how Sparklet abstracts each accelerator type through the GDI layer.

Variant	Core	GPU / Accelerator	On-Chip RAM	Target Use	OS / RTOS
i.MX RT1170	Dual Cortex-M7/M4 @1GHz	PXP 2D + LCDIF	2 MB SRAM	Instrument clusters, industrial HMI, dual display	FreeRTOS, Zephyr, bare metal
i.MX 8 / 8M	Cortex-A + Cortex-M	Mali GPU (OpenGL ES 2.0)	External LPDDR4	IVI, ADAS display, premium HMI, 3D UI	Embedded Linux, Android AOSP

Why Choose Sparklet Over Other NXP GUI Frameworks?

NXP developers evaluating GUI frameworks typically compare Sparklet against LVGL (open source), Qt for MCUs (commercial), and TouchGFX (STM32-specific but sometimes evaluated for NXP). The key differentiators for NXP targets:

PXP and Mali Integration is Built In

Sparklet's NXP HAL uses the PXP accelerator out of the box on i.MX RT. LVGL requires custom accelerator driver work that falls on the developer's team. Qt for MCUs adds significant Flash and RAM overhead on i.MX RT targets and charges per-unit royalties at volume.

Pure C, No C++ Dependency

i.MX RT projects in automotive and industrial segments often mandate C-only application code. Sparklet's entire widget stack is pure C, unlike Qt for MCUs and TouchGFX which require C++ toolchain support.

Scales from MCU to MPU

The same Flint design file and the same C screen code compile on i.MX RT1170 and i.MX 8. No parallel UI codebase for MCU and Linux variants of the same product family. This is Sparklet's most impactful advantage for NXP product teams managing multiple product tiers.

Royalty-Free at Any Volume

No per-unit fees. Qt for MCUs charges per-unit royalties at volume — Sparklet uses a developer-seat model with zero runtime cost. For a detailed comparison, see Sparklet vs Qt for MCUs and Sparklet vs LVGL.

NXP-Specific Capabilities

Key features Sparklet delivers on NXP hardware that hardware-locked frameworks cannot match.

Dual Display from One MCU

i.MX RT1170 supports two independent LCDIF instances. Sparklet drives separate screen content on each — primary cluster plus secondary infopanel from a single MCU.

CarPlay & Android Auto on i.MX 8

Screen mirroring protocol integration on i.MX 8. Hardware video decode and multi-channel display output make it the reference platform for IVI systems.

Yocto Layer for i.MX 8

Sparklet provides Yocto layer recipes for clean integration into the NXP BSP build. GStreamer multimedia pipeline integration supported for video playback widgets.

MISRA C Compliant Source

MISRA C compliance on i.MX RT matters for automotive NXP projects. Sparklet provides compliance documentation on request for integration into safety artefacts.

Frequently Asked Questions — Sparklet for NXP

What embedded GUI runs on NXP i.MX RT?

Sparklet is a production-ready embedded GUI library for NXP i.MX RT targets, particularly the i.MX RT1170. It uses the PXP Pixel Pipeline accelerator for hardware 2D blitting, scaling, and alpha blending. The library runs on FreeRTOS, Zephyr, or bare metal and generates code via Flint UI Designer from a visual design environment.

Does Sparklet support NXP i.MX 8?

How does Sparklet use the NXP PXP on i.MX RT1170?

Can Sparklet drive two displays on NXP i.MX RT1170?

Is Sparklet royalty-free on NXP platforms?

What toolchains does Sparklet support for NXP targets?

NXP Embedded GUI Library — i.MX RT1170 and i.MX 8