GraphLab Boot Configs

Your company's library of boot configurations — splash, boot UI, and built initstub.bin firmware.

What is a boot config?

A GraphLab Boot Config defines early-boot visuals and timing for a specific platform + display license pair. The portal builds an initstub.bin that devices download via the boot config API.

Configs are company-wide. You assign them as group defaults or device overrides — see Groups and Devices.

Configs page (`/initstub`)

Open Configs in the navigation (after onboarding). The index lists every boot config in your workspace with platform, display, build status, and revision.

Create Config — starts the four-step editor (requires active display license and at least one registered device).
Platform & display licenses — shortcuts to Shop and Hardware if hardware is not unlocked yet.
Edit — reopen the editor for an existing config.
Download — fetch the latest built initstub.bin when the VPS build succeeded.

Prerequisites

Active display license for your target hardware — order in Shop; confirm under Licenses.
At least one registered device — the portal uses this gate before first config creation.
A group with matching platform and display when assigning defaults.

If the create button routes you to license requests or device registration, complete those steps first.

Build lifecycle

Save configuration in the editor — a build job is queued on the VPS.
Poll until status is Ready (revision and download enabled).
Assign the config to a group or device.
Devices poll the boot config API and download updates when revision changes.

Configs marked (not built) in dropdowns cannot be deployed until the build finishes. Deep editor documentation: Boot Config Editor.

Hardware binding rules

Each config is tied to one platform and one display integration license.
Resolution, refresh, interface, and porch timings come from the display integration license.
On commercial integrations, porch timings are locked — edit them on evaluation via Hardware before upgrading in Shop.
Only matching configs appear when editing groups or devices.
Changing a group's platform or display may require picking a different config.

Troubleshooting

Issue	What to check
No Configs menu	Internal developer company flag; onboarding complete
Cannot create config	Display license inactive — order in Shop; register a device first
Build stuck / failed	Re-save in editor; check VPS worker; contact support if persistent
Config missing in group dropdown	Platform/display mismatch; or build not finished
Device shows "update available"	New revision built — device will fetch on next API poll