Choose a branded startup, observed status and fallback, or a bespoke early interface. GraphLab Splash, Boot, and Pro keep your existing Linux UI while giving the visible startup experience a clear owner.
Splash looks finishedKeep approved branding visible until the Linux UI appears.
Boot stays understandableShow observed status, progress, and fallback states.
Pro becomes useful earlyPresent a product-specific GUI before Linux is ready.
Every project is assessed for its NXP device, display path, BSP, Linux UI stack, and agreed acceptance evidence.
The real-time core keeps an approved logo visible while Linux renders into the already active display path.
Product win: the device looks finished from power-on.
Boot uses the same persistent real-time display authority and adds state-driven status, progress, and fallback behavior.
Product win: the operator always knows what the system is doing.
GraphLab designs and implements the agreed early interface on the real-time core.
Product win: the product becomes useful before Linux is ready.
Press once to see the intended visible sequence. Timing and the exact presentation-switch behavior are validated separately for every customer configuration.
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.
Ready. Press the power button on the display.
This comparison uses a Toradex Verdin iMX8M Plus, LVDS, Torizon OS reference image, and the standard Linux graphics path. Linux application readiness time remains unchanged.
Standard Torizon path compared with GraphLab Boot on the validated reference setup.
Representative product studies
These project-specific studies show where observed status, fallback, and a bespoke early interface can create a concrete product outcome. They are product studies, not claimed customer deployments.
Keep an operator-facing status visible while Linux or the main system applies an update.
Read the product study
Return the display to a defined real-time state when Linux stops meeting the agreed health contract.
Read the product study
Show keyless state, essential system information, and urgent warnings immediately on motorcycle, marine, and other mobility displays.
Read the product studyWe assess GraphLab Splash, Boot, and Pro for the specific device, display path, firmware, BSP, and Linux UI stack in each project.
You do not need to choose the perfect product or send confidential design files at this stage.
Not sure whether you need Splash, Boot, or Pro? Select “Not sure” as the product path and we will route the request.
A few details are enough for the first conversation.
No. Your existing Linux application remains the complete product UI. The real-time core remains display authority, and the accepted Linux-rendered framebuffer becomes visible at the selected readiness point.
No. They improve what users see while Linux and the application start. The validated Boot reference reaches its first visible pixel in approximately 800 ms, but Linux application readiness time remains unchanged.
All three keep display authority on the real-time core while Linux joins as a renderer. Splash provides the branded early experience. Boot adds observed status, progress, custom text, and fallback. Pro adds a bespoke GraphLab-designed early GUI.
We work with NXP i.MX projects. The published Boot reference uses Toradex Verdin iMX8M Plus with Torizon, and GraphLab Boot has also been tested on i.MX8QXP. Every customer configuration requires a separate assessment.
Tell us your company, NXP platform, preferred product path, and visible display requirement. Please do not send confidential design files or source code with the first request.
Ask us to identify whether GraphLab Splash, Boot, or Pro fits your NXP i.MX project.
