GraphLab Splash · Branded startup
Use GraphLab Splash to replace the black startup interval with approved branding. It keeps your logo or artwork visible from power-on until the Linux UI is ready.
Scope at a glance
Splash is deliberately focused. Provide the known display timings in the GraphLab Portal, and it creates the project-specific configuration, including the required device-tree settings. Your approved branding then stays visible until the accepted Linux frame is ready.
Your existing Linux application stays in place.Included in Splash
Turn the agreed panel timings into a validated, project-specific setup.
Show your approved logo or artwork as soon as the display becomes active.
Keep the physical display path stable while Linux starts in parallel.
Reveal the accepted Linux framebuffer at the agreed readiness point.
A U-Boot logo or Plymouth splash can be sufficient when the surrounding display transitions already meet your requirements. If kernel or compositor initialization blanks the panel, preserving artwork alone cannot guarantee continuity. GraphLab retains physical display authority on the real-time core for the assessed integration.
Compare boot splash and display handover approachesIllustrative GraphLab startup sequence
One illustrative mobility example for an architecture intended for industrial displays, instruments, and mobility products. Three early experiences. The real-time core retains display authority while Linux starts in parallel.
Turn the key to ON to play the illustrative sequence.
Starting motorcycle system
Dashboard application restarting
Defined real-time display fallbackReal hardware proof
The GraphLab Boot reference on Toradex Verdin iMX8M Plus reaches its first visible pixel in approximately 800 ms. That result belongs to the validated Boot setup and is not a performance promise for Splash on another configuration.
Read the platform proofProduct comparison
| Capability | SplashBranded startup | BootStatus and fallback | ProReal-time GUI library |
|---|---|---|---|
| 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 |
| Library for customer-developed early interfaces | No | No | Yes |
GraphLab Splash Technical Articles
Diagnose black frames, flicker, and visible resets across the bootloader, Linux DRM, compositor, and embedded application startup path.
Read articleA boot splash can cover waiting time, but it does not by itself preserve panel and display-controller state through the Linux graphics transition.
Read articleKeep early display output stable until the Qt application has a complete frame, without confusing visual continuity with faster application startup.
Read articleHow GraphLab Splash, Boot, and Pro retain display authority while Linux renders, illustrated by the measured GraphLab Boot reference on Toradex Verdin iMX8M Plus with Torizon.
Read articleGraphLab Splash Product Studies
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
Keep an operator-facing status visible while Linux or the main system applies an update.
Read product study
Let the real-time core maintain a controlled display while application cores sleep, then request a wake-up when needed.
Read product study
Keep charging progress and battery warnings visible from the real-time side, then allow an A-core start only after the agreed power conditions are met.
Read product studyFree technical fit check
Share your target platform and display requirements. A GraphLab engineer will review compatibility and outline the next steps for integration.
