Cross-platform embedded GUI from Sparklet means the same widget codebase, the same Flint design files, and the same application logic deploy across 9 hardware families — with only the HAL layer changed. Renesas RH850, NXP i.MX RT1170, STM32H7, Infineon TRAVEO T2G, Rockchip RK3506G2, and more. One royalty-free licence, zero per-unit fees.
A cross-platform embedded GUI library is a software framework that allows developers to build a graphical user interface once and deploy it on multiple hardware targets without rewriting the UI logic. Sparklet achieves this through a 7-layer architecture where the Hardware Abstraction Layer (HAL) encapsulates all hardware-specific code — display drivers, GPU commands, touch input, and DMA calls — while the widget layer, rendering engine, and application logic remain unchanged across platforms.
This matters in real projects because silicon availability changes, product families span multiple performance tiers, and customers frequently ask for ports to new hardware years after the initial launch. Sparklet lets your team make that change at the HAL layer only, leaving every screen, animation, and state machine intact.
Supported platforms include MCUs from Renesas, NXP, STMicroelectronics, Nuvoton, and Infineon, plus MPUs from NXP and Rockchip, and PC simulators on Windows x86 and Linux SDL2 for development and testing. Total: 9 hardware platform families, covering automotive, industrial, consumer electronics, medical, and wearable applications.
Five Microcontroller Families — from Automotive to IoT
Sparklet targets five MCU families with dedicated HAL implementations that expose each chip's hardware accelerator:
Two Linux-Capable Application Processors
For applications requiring embedded Linux, Android, or full 3D OpenGL ES rendering, Sparklet scales to MPU platforms. The same Flint-generated C code compiles and runs on MPUs — only the HAL is swapped.
Both MPU targets support Sparklet's 3D widget and OpenGL ES pipeline. The Yocto Linux build environment is the standard integration path. Framebuffer (DRM/KMS) and OpenGL ES 2.0 backends are both available.
OS-Agnostic by Design — Bare Metal to Linux
Sparklet runs as a single dedicated task or as the main bare-metal loop. All supported operating environments:
For full RTOS integration details, see the RTOS support page.
| Platform | Vendor | Type | Min RAM | GPU / Accelerator | RTOS Support |
|---|---|---|---|---|---|
| Renesas RH850 D1M1A | Renesas | MCU | 16 KB | D/AVE2D 2D GPU | Bare metal, AUTOSAR |
| Renesas RA8D1 | Renesas | MCU | 16 KB | Mali-Limav GPU | FreeRTOS, Azure RTOS |
| Renesas RA6M3 | Renesas | MCU | 16 KB | 2D HW assist | FreeRTOS, Azure RTOS |
| NXP i.MX RT1170 | NXP | MCU | 16 KB | PXP 2D accelerator | FreeRTOS, Zephyr |
| NXP i.MX 8 | NXP | MPU | 32 KB | Mali GPU (OpenGL ES) | Embedded Linux, Android |
| STM32 F4 / H7 / U5 | STMicro | MCU | 16 KB | DMA2D Chrom-ART | FreeRTOS, Azure RTOS |
| Nuvoton Gerda-ZWEI | Nuvoton | MCU | 16 KB | Integrated display ctrl | FreeRTOS, bare metal |
| Infineon TRAVEO T2G | Infineon | MCU | 16 KB | 2D graphics engine | AUTOSAR, FreeRTOS |
| Rockchip RK3506G2 | Rockchip | MPU | 32 KB | SW + 2D | Embedded Linux |
Sparklet's Hardware Abstraction Layer (HAL) is the boundary between portable UI code and hardware-specific implementation. The HAL exposes a fixed set of function signatures — draw pixel, blit region, fill rectangle, wait for vsync, read touch point — and each platform provides its own implementation of those functions using the chip's native drivers and accelerator APIs.
Above the HAL, every component is hardware-independent: all 36+ widgets, the rendering pipeline, the state machine executor, Flint-generated screen code, fonts, images, and animation keyframes. When moving from one supported platform to another, the porting scope is typically under 500 lines of C code — exclusively in the HAL directory.
For custom or unlisted hardware, Embien provides platform porting services covering BSP bring-up, HAL implementation, display driver optimisation, and touch integration. Most engagements complete in 2–4 weeks depending on hardware complexity. See the performance benchmarks page for RAM footprint, FPS, and Flash usage figures per platform.
Sparklet ships with two PC simulators that support the full widget catalogue, state machine execution, multi-language fonts, and animation playback. Development teams routinely complete 80% of UI work on the Windows x86 simulator or Linux SDL2 simulator before first hardware boot — removing the compile-flash-test bottleneck from the UI development cycle.

The same Flint-generated C screen files compile on all 9 supported platforms. No conditional compilation blocks, no platform-specific widget code.

Changing target hardware requires modifying only the HAL layer — under 500 lines of C for most certified platform moves. Every widget, screen, and animation stays untouched.

One developer seat licence covers all 9 platforms. Ship on Renesas one year and NXP the next — no new licence, no per-unit fees, zero royalties at any production volume.

Each platform HAL is tuned to the chip's native accelerator: D/AVE2D on RH850, Mali on RA8D1, PXP on i.MX RT, DMA2D on STM32. No generic fallback, no wasted cycles.
Sparklet supports Renesas RH850, RA8D1, and RA6M3; NXP i.MX RT1170 and i.MX 8; STM32 (F4, H7, U5); Nuvoton Gerda-ZWEI; and Infineon TRAVEO T2G as MCU/MPU targets. Windows x86 and Linux SDL2 simulators are also included for development.
Download the Sparklet evaluation binary and Flint UI Designer, then build and run on your evaluation kit. Evaluation packages are available for all 9 supported platforms. Embien's engineering team provides free technical assistance during evaluation.