Project fit check

GraphLab Pro · Real-time GUI library

Build your own embedded GUI before Linux is ready.

GraphLab Pro includes Boot and the real-time graphics library for developing your own early GUI. Connect your interface to data and controls available on the real-time core, then transition to your Linux application.

Discuss your Pro integrationSee how it works

What you receive

A library for your early interface. Support for the integration.

01 / BUILD

Real-time graphics library

Develop your own screens and visual states on the real-time core. Your team owns the GUI implementation and application behavior.

02 / INHERIT

Everything in Boot

Start with a continuously active display path, observed status and progress, custom startup text, and defined fallback.

03 / INTEGRATE

Project-specific support

GraphLab provides the library and supports the assessed hardware and display integration. Peripheral integration scope is agreed per project.

Need help creating the interface itself? Custom GUI implementation by GraphLab is available as an optional service.

How it works

Your early GUI and Linux share one display path.

Your product data and inputsMeasurements and controls available independently of Linux
↓ Data and input paths agreed for your project
REAL-TIME CORE

Your early GUI code

Custom screens and application behavior

GraphLab graphics library

GraphLab Core retains display authority.

APPLICATION CORES

Your Linux application

The full application starts in parallel, with its existing UI stack.

Accepted Linux framebuffer

Selected when the agreed readiness point is reached.

↓ Early GUI or accepted Linux frame
One continuously active display pathControlled frame selection without rebuilding the active panel path on the validated configuration

Connect what is ready early

Early interaction requires the relevant data and control backend to be available independently of Linux. Your application connects those functions to the GUI through the project-defined integration.

Define what returns during recovery

Configure and validate the early screen that returns during an application restart or recovery. State continuity and available controls depend on the agreed data paths and application behavior.

Illustrative GraphLab startup sequence

See your motorcycle’s state while Linux starts.

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.

Your brand, throughout startup

Turn the key to ON to play the illustrative sequence.

Where Pro can fit

Build around a function your operator needs early.

Potential applications to assess with your team, rather than claimed customer deployments.

Industrial HMI

Early: show controller readings and expose agreed basic settings through an independent controller.

Linux: add recipes, trends, and production history.

Measurement instruments

Early: show a measurement and a basic action such as zeroing when the measurement backend is available.

Linux: add analysis, reports, and connectivity.

Equipment recovery

Early or fallback: show current equipment status and agreed controls while the main application reconnects.

Linux: restore detailed diagnostics and configuration.

Choose the capability you need

Branding. Status. Your own early GUI.

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

Underlying display architecture

Boot reference evidence.

The GraphLab Boot reference on Toradex Verdin iMX8M Plus reaches its first visible pixel in approximately 800 ms. That measured result belongs to the validated Boot setup and is not a Pro performance promise. Pro availability is assessed with your actual screens, data paths, hardware, and rendering workload. Linux application readiness remains unchanged.

Read the platform proof
GraphLab Boot on the validated reference. Linux application readiness time is unchanged.

Common questions

Before you build.

Who writes the early GUI?

Your team develops the GUI with the real-time graphics library. GraphLab supports the assessed library and display integration. Custom GUI implementation by GraphLab is an optional service.

What can work before Linux is ready?

Functions whose measurements, input paths, and control backend are available independently of Linux. The available interfaces and peripheral integration scope are assessed per project.

What happens to our Linux application?

It remains your complete product application and starts in parallel. GraphLab selects its accepted framebuffer at the agreed readiness point while retaining physical display authority.

Which hardware configurations are supported?

Start with an assessment of your NXP i.MX device, carrier, display, and software stack. The published Boot reference is a specific validated configuration; it does not establish universal Pro compatibility.

How are library access and integration quoted?

We provide a custom quote after agreeing your configuration, library delivery, and integration responsibilities. Licensing and support terms are defined in the project offer.

How quickly will our early GUI be available?

Availability is assessed and validated with your hardware, screens, data paths, and rendering workload. The Boot reference timing is not a Pro performance promise.

Technical articles

Explore the architecture.

Product studies

Explore potential applications.

Free technical fit check

Ready to bring your chosen product to your device?

Share your target platform and display requirements. A GraphLab engineer will review compatibility and outline the next steps for integration.

  • No confidential design files required
  • Platform and integration review
  • Reply within one business day

Check my project fit