Quickstart
Flash the evaluation image from the GraphLab Portal, customize your splash/spinner/status text, and verify the seamless boot experience.
1. Get the evaluation image
Open the GraphLab Portal and download the evaluation image for your supported hardware. The portal also provides the recommended flashing method for your platform.
2. Flash the image
Choose one of the supported flashing paths:
Option A — Online Flash Loader
The browser-based Online Flash Loader is not enabled on this portal instance. Use one of the manual flashing options below.
Option A — Toradex Easy Installer (Verdin showcase platform)
If you are using the GraphLab showcase platform based on the Toradex Verdin module, you can flash the image using Toradex Easy Installer .
- Download the evaluation image from the GraphLab Portal
- Copy the image to the TEZI media or network source
- Boot the device into Toradex Easy Installer
- Select the GraphLab evaluation image
- Start the installation and wait for completion
3. Customize splash, spinner, and status text
The GraphLab Portal is the easiest way to customize early boot visuals. After you have an active display license, open GraphLab Boot Configs and:
- Select the platform and display license the config is built for.
- Customize splash image (placement on the licensed screen), boot UI settings (colors and spinner), and status text in the four-step editor.
- Save to the library and assign the config to a project with matching hardware.
Screen resolution and refresh rate are taken from the display license. You do not configure display timings separately in the boot config editor. See the Boot Config Editor guide for section-by-section details and the GSET JSON schema.
Deploy the built initstub.bin to the device boot partition or use the portal revision API
if your integration polls the boot config endpoint.
4. Power-cycle test
- Remove power from the board completely
- Reconnect power
- Observe the display — your splash should appear immediately
- Confirm the transition to the Linux UI is smooth (no flicker, no black frame)
5. What “good” looks like
- Instant first pixel from power-on (display active immediately)
- Continuous visuals through SPL and kernel boot (no visible reset)
- Seamless handover when the Linux UI starts rendering
- Consistent behavior across cold boot, warm boot, and watchdog reset
Next: Read Prerequisites for production integration requirements (BSP assumptions, display pipeline constraints, and handover rules).