Developer Docs
Portal Login Get Started

Hardware groups

How groups bind platform, display, boot config, and devices inside a project.

What is a group?

A hardware group (or just “group”) is a bucket inside a project. All devices in the group share:

  • Platform (SoM) — which computer module / silicon family.
  • Display integration — which licensed screen pipeline (resolution, interface, timing profile).
  • Default GraphLab Boot Config (optional) — custom splash, boot UI, and initstub.bin for early boot.
  • Device license product — inherited from the parent project environment (GraphLab Boot or GraphLab Boot - Development).

Use separate groups when hardware differs — e.g. one group for 7" LVDS panels and another for 10" HDMI on the same project.

Where groups live in the UI

  1. Projects → open a project → Hardware Groups table.
  2. Click a group name for Group Overview.
  3. New group creates a group in the current project only.

Creating a group

  1. On the project page, click New group.
  2. Enter Name and optional Description.
  3. Select Platform (SoM) — options depend on the project environment (development projects may use evaluation or commercial platforms; production projects require commercial only).
  4. Select Display integration — filtered by platform and the same tier rules as platform.
  5. Click Save.

If Save is disabled or dropdowns are empty, order and activate licenses in Shop first (Licensing overview).

Group overview page

Each group has four main areas:

1. CLI provision token

For developer workflows, you can generate a one-time provision token per group. The CLI uses it to register a device and download its license in a single step (see CLI Provisioning).

  • Generate token — creates a secret shown once; copy it immediately.
  • Rotate token — replaces the active token (old token stops working).
  • Revoke — disables CLI provisioning until you generate a new token.

2. Hardware

Read-only summary of the group's platform and display integration, including license tier badge and display path (controller + interface). If hardware is missing, use Edit group to set it.

3. GraphLab Boot Config

Shows the group default boot config (if assigned) and how many compatible configs exist in your company library.

  • Only configs built for this group's platform + display can be selected.
  • Configs without a built firmware show (not built) — finish the VPS build on the Boot Config Editor page first.
  • Devices use the group default unless they have a device-level boot override.

4. Devices

Lists devices registered into this group. Use Add device to open device registration (Devices guide).

Editing a group

Edit group lets you change:

  • Name and description
  • Platform and display integration
  • Default GraphLab Boot Config — dropdown filtered to matching hardware; choose None to clear the default

Changing platform or display may invalidate the current boot config selection. Pick a config that matches the new hardware or create one via GraphLab Boot Configs.

Devices and license slots

When you register a device into a group:

  • The device inherits the group's platform, display, and default boot config.
  • One project license slot is consumed immediately (see Projects).
  • The group must belong to a project with free allocation slots.
  • When license enforcement is enabled, the group needs platform, display, and boot config set before registration succeeds.

After registration, open the device page and Provision to generate the per-device license.bin.

Evaluation workspace groups

Groups under the onboarding evaluation workspace are development-environment groups. They use GraphLab Boot - Development device slots and may bind evaluation or commercial platform and display licenses. Behavior matches other development projects; the evaluation workspace label helps you separate trial work from production rollouts.

Deleting a group

From the project’s group table, Delete removes the group. You cannot delete a group that still has devices — remove or reassign devices first.

Relationship diagram

Company
 └── Device license pool (GraphLab Boot / GraphLab Boot - Development)
      └── Project (environment + license allocation: N slots)
           └── Group (platform + display + boot config)
                └── Device (UUID + provisioned license)

Troubleshooting

Issue What to check
No platforms in create form Order and activate a platform license in Shop
Display dropdown empty Order a display integration for the selected platform in Shop
Group shows “Not configured” Edit group and set platform + display
No boot configs in dropdown Create a boot config for this display; wait for VPS build to finish
Platform or display missing for production project Production projects require commercial platform and display licenses — upgrade in Shop or use a development project for evaluation hardware
Cannot add device to group Project allocation full, wrong device license product, or group missing required hardware/boot config
CLI token does not work Token revoked or rotated — generate a new one; use token only once if docs say so

See also

← Projects Devices →