Embedded display authority

Control what your product shows before Linux is ready.

Show your brand, report system status, or offer an early interface while Linux starts. Keep your existing Linux UI.

Keep your Linux UIBuilt for NXP i.MXDisplay control from power-on

From power-on to your Linux UI

Power onBootloader starts GraphLab Core
  • GraphLab SplashApproved brand display
  • GraphLab BootBrand + observed status and progress
  • GraphLab ProBoot + a product-specific early interface
Your Linux UI appearsAccepted frame becomes visible

Linux starts in parallel across all three paths.

Real-time core retains display authority throughout

Illustrative GraphLab startup sequence

See your motorcycle’s state while Linux starts.

One electric motorcycle. Three early experiences. The real-time core retains display authority while Linux starts in parallel.

Your brand, throughout startup

Turn the key to ON to play the illustrative sequence.

Turn the key to ON
About this demo

Simulated vehicle signals and illustrative timing. Early information depends on project-specific integration. Linux startup time is unchanged.

The real-time core retains display authority. Vehicle controllers determine operating permissions.

A different display architecture

Linux renders. The real-time core remains display authority.

GraphLab starts and retains the display path on the real-time core. Linux renders into shared framebuffers and becomes visible only when the agreed frame is ready.

  1. 01
    Start the display early

    Bootloader loads GraphLab Core and the real-time core initializes the active path.

  2. 02
    Let Linux start in parallel

    The existing Linux stack renders without visibly rebuilding the panel path.

  3. 03
    Select the accepted frame

    The product switches to the Linux-rendered UI at a defined readiness point.

Read the platform proof
Standard Torizon compared with GraphLab Boot on the validated Toradex Verdin iMX8M Plus reference. Linux application readiness time is unchanged.
Approximately 800 msFirst visible pixel on the validated Boot reference
3 product levelsBranding, observed states, or a product-specific interface
Validated on NXP i.MXVerdin iMX8M Plus and Colibri iMX8QXP
Your Linux stackQt, Embedded Wizard, Crank Storyboard, and more

Three levels of control

Choose the visible outcome your product needs.

Capability comparison

Move up only when the requirement demands it.

Select a product name to explore its complete scope, proof, studies, and project fit check.

CapabilitySplashBranded startupBootStatus and fallbackProReal-time GUI library
Project configuration from known timingsYesYesYes
Persistent display authorityYesYesYes
Approved brandingYesYesYes
Observed status and progressNoYesYes
Defined fallbackNoYesYes
Library for customer-developed early interfacesNoNoYes

Not sure which level fits your product?

Project fit check

Validated hardware

Start with the platform you already use.

Support and performance are validated for the agreed device, carrier, panel, BSP, display stack, and application.

Toradex Verdin iMX8M Plus module

NXP i.MX8M Plus

GraphLab Boot tested on Toradex Verdin with LVDS and Torizon OS.

Toradex Colibri iMX8QXP module

NXP i.MX8QXP

GraphLab Boot tested on the Toradex Colibri i.MX8QXP platform.

Validated software

Keep the software you already use.

GraphLab is validated with these UI frameworks. Support and performance depend on the agreed hardware, display stack, and application.

Qt logo

Qt

Cross-platform UI framework for rich embedded applications with C++ and QML.

Crank Storyboard logo

Crank Storyboard

Design-driven GUI development that separates visuals from application logic.

Slint logo

Slint

Declarative UI toolkit for native interfaces with Rust, C++, and JavaScript.

LVGL logo

LVGL

Lightweight, open-source graphics library for embedded displays.

Embedded Wizard logo

Embedded Wizard

Visual GUI development with generated C code for embedded devices.

Free project fit check

Tell us what the display must do before Linux is ready.

A GraphLab engineer will review your NXP i.MX display path and identify whether Splash, Boot, or Pro is the practical next step.

  • No confidential design files required
  • Product-focused technical review
  • Reply within one business day

Check my project fit

Technical Articles

Understand the display path before changing it.

Browse Technical Articles

Product Studies

Explore system behaviors, not generic feature lists.

Browse all Product Studies