NXP i.MX8M Plus
Published GraphLab Boot reference on Toradex Verdin with LVDS and Torizon OS.
Embedded display authority
Control what your product shows before Linux is ready.
GraphLab creates a deliberate display experience from power-on to the existing Linux UI. Start with branding, add observed status and fallback, or build a bespoke early interface.
Keep your Linux UIBuilt for NXP i.MXValidated per project
System services starting
One display ownerLinux joins the active path as a renderer at the agreed readiness point.
Approximately 800 msFirst visible pixel on the validated Boot reference
3 product levelsBranding, observed states, or a bespoke GUI
2 tested referencesVerdin iMX8M Plus and Colibri iMX8QXP
Your Linux stackQt, Embedded Wizard, Crank Storyboard, and more
Illustrative GraphLab Splash sequence
Keep the display controlled until the Linux UI is ready.
- 1
Bootloader loads and starts the real-time firmware
- 2
The real-time core initializes and retains the display path while output begins black
- 3
Approved branding stays visible while Linux renders into the active display path in parallel
- 4
The accepted Linux-rendered framebuffer becomes visible
No display-ownership handover. Linux joins the active display path as a renderer. GraphLab Splash does not make Linux or the application ready sooner. The measured approximately 800 ms result below belongs only to the validated GraphLab Boot reference.
Your brandGraphLab SplashReal-time display owner
WelcomeYour Linux-rendered framebuffer is selected.
Ready. Press the power button on the display.
Three levels of control
Choose the visible outcome your product needs.
Every product keeps the existing Linux application. The difference is what the real-time side presents while Linux starts.
01Branded startup
GraphLab Splash
Provide the known display timings in the GraphLab Portal. It creates the project-specific configuration, including the required device-tree settings, while GraphLab Splash keeps your branding visible as Linux starts.
- Project configuration from known timings
- Approved early branding
- Persistent real-time display authority
From €2,999Per assessed project
Explore Splash 02Status and fallback
GraphLab Boot
Add observed status, meaningful progress, approved custom text, and defined fallback to a continuously active display path.
- Everything in Splash
- Status and progress tied to observed milestones
- Approved custom status text
From €4,999Per assessed project
Explore Boot 03Bespoke early GUI
GraphLab Pro
GraphLab Pro designs a project-specific GUI on the real-time core, connects it to the agreed product peripherals, and targets availability in under one second while Linux starts in parallel.
- Functional GUI connected to project peripherals
- Under-one-second availability as an agreed design target
- Custom screens, states, copy, and artwork
Custom quoteTailored engineering engagement
Explore Pro 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.
| Capability | SplashBranded startup | BootStatus and fallback | ProBespoke early GUI |
|---|---|---|---|
| Project configuration from known timings | Yes | Yes | Yes |
| Persistent display authority | Yes | Yes | Yes |
| Approved branding | Yes | Yes | Yes |
| Observed status and progress | No | Yes | Yes |
| Defined fallback | No | Yes | Yes |
| Functional early GUI with peripheral I/O | No | No | Yes |
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.
- 01Start the display early
Bootloader loads GraphLab Core and the real-time core initializes the active path.
- 02Let Linux start in parallel
The existing Linux stack renders without visibly rebuilding the panel path.
- 03Select the accepted frame
The product switches to the Linux-rendered UI at a defined readiness point.
Standard Torizon compared with GraphLab Boot on the validated Toradex Verdin iMX8M Plus reference. Linux application readiness time is unchanged.
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.
NXP i.MX8QXP
GraphLab Boot has also been tested on the Toradex Colibri reference platform.
Technical Articles
Understand the display path before changing it.
Why Embedded Linux Displays Flicker During Boot
Diagnose black frames, flicker, and visible resets across the bootloader, Linux DRM, compositor, and embedded application startup path.
Read articleWhy a Boot Splash Does Not Solve Display Handover
A boot splash can cover waiting time, but it does not by itself preserve panel and display-controller state through the Linux graphics transition.
Read articleSeamless Boot-to-Qt Without Display Reinitialization
Keep early display output stable until the Qt application has a complete frame, without confusing visual continuity with faster application startup.
Read articleProduct Studies
Explore system behaviors, not generic feature lists.
Add a persistent splash to your Torizon product
Enter the known display timings in the GraphLab Portal, add the generated GraphLab Splash configuration to your Torizon build, and keep a branded screen visible until the Linux UI is ready.
Read product study
Visible OTA update status
Keep an operator-facing status visible while Linux or the main system applies an update.
Read product study
Instant mobility instrument cluster
Show keyless state, essential system information, and urgent warnings immediately on motorcycle, marine, and other mobility displays.
Read product studyFree 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