Skip to main content

BSP Launcher — User Guide

BSP Launcher is Advantech’s GUI-driven automation tool for downloading validated images, building BSPs, and flashing targets without memorising Yocto workflows. It streamlines customer evaluation, production validation, and field recovery for NXP, Qualcomm, NVIDIA Jetson, and MediaTek platforms.

Latest Download

Download BSP Launcher (v1.0.8)

The Azure Blob link above always hosts the most recent BSP Launcher build—bookmark it to pick up future updates as soon as they drop.

Latest Release Notes​

New Features​

  • Support Ubuntu 24.04 out of the box.

Enhancements​

  • Build environment now uses libwebkit2gtk-4.1-dev (previously libwebkit2gtk-4.0-dev) so the same package set works on both Ubuntu 24.04 and Ubuntu 22.04 (Bug #44189).

Bug Fixes​

  • Resolved an intermittent hang that occurred right after a successful BSP compilation and prevented the post-build steps from running.
  • Fixed Rockchip flash detection by downloading all required tool scripts during the detection phase, ensuring that flashing starts reliably every time.

Click the button above or run the following command to download the latest build:

wget 'https://riscsw.blob.core.windows.net/bsp-launcher-app/BSP_Launcher_v1.0.8.zip' -k -O 'BSP_Launcher_v1.0.8.zip'

1. At-a-Glance​

  • All-in-one console: download official prebuilt images or trigger full BSP builds from the same dashboard.
  • Profile-aware builds: each project remembers the manifest, machine, and image recipe, so engineers can reproduce releases with one click.
  • Integrated flashing: once an image is ready, the launcher guides you through recovery-mode wiring and flashes the media automatically.
  • Traceable artifacts: build logs, SBOM data, and packaged images are stored with the project for audits and regression testing.

2. Why Teams Use BSP Launcher​

Traditional challengeBSP Launcher approach
Host dependencies and mismatched Python/toolchain versionsProvides curated Docker environments and switches profiles automatically
Error-prone CLI flows (repo, bitbake, manual SDK install)Encapsulates repo sync, build scripts, and SDK export with validated presets
Multiple products sharing one workstationProject drawer isolates configs, logs, and generated images
Manual flashing steps and inconsistent recovery instructionsGuided flash tasks with inline checklists and hardware diagrams
Limited log visibilityReal-time terminal pane with searchable output and downloadable archives

3. Guided Workflow​

Step 1 – Download a Prebuilt Image​

Step 1 action selection

  1. Choose Download image and flash when you only need a validated release for lab bring-up.
  2. In Specify Environment, confirm platform, chipset, board name, and release filters.
  3. Click Continue to start the download; progress, checksum validation, and extraction appear in the log pane.
  4. Completed images land inside the project’s folder and stay ready for flashing.

Step 2 – Download BSP Sources and Build​

Step 2 specify environment

Step 3 download resources

Step 3 build progress

  1. Select Build BSP and flash to pull the correct manifest, sync layers, and run the Advantech release script.
  2. Define the platform profile (e.g., NVIDIA / AGX-THOR / AIMB294A1) plus distro, RAM, and workspace path.
  3. Use the Download Resources view to monitor repo sync progress, throughput, and checksum checks.
  4. When prompted, confirm Docker availability and the host capability assessment before continuing the build.
  5. The Build BSP Image tab streams logs (bitbake tasks, package installs, kernel compilation) and exposes download/export buttons for audit sharing.
  6. After Build Completed!, the final artifact path prints in the log, and the packaged image is registered for flashing.

Step 3 – Flash a Prebuilt Image or Image built from BSP​

Step 4 flash

  1. Open the Flash on Device tab and choose either the downloaded image (*_download) or the newly built package (*_build).
  2. Connect the target hardware via USB and enter recovery mode; the launcher confirms detection before enabling Flash.
  3. Pick the storage target (NVMe or USB) when prompted so the correct vendor script runs.
  4. Flash logs mirror the flash_bsp_* scripts and surface progress percentages, retries, and timestamps.
  5. A green Flash on device successfully banner signals completion; logs remain under the project directory for audits.

4. Comparing CLI vs. BSP Launcher​

AspectTerminal workflowBSP Launcher workflow
Environment prepInstall packages, set env vars, source setup scriptsLaunches curated container/Docker profile automatically
Manifest updatesManual repo init / repo syncManaged through project metadata, one click to resync
Build monitoringtail -f tmp/logStructured log pane with color-coded errors and download button
FlashingRemember board-specific scripts and switchesWizard with diagrams, recovery instructions, and logging
Knowledge transferTribal knowledge, wikisProjects act as executable documentation

5. Enterprise Benefits​

  • Faster onboarding: new engineers can ship images in minutes instead of days of Yocto training.
  • Consistent release cadence: one tool handles download, build, flash, and documentation, reducing handoffs.
  • Audit-ready artifacts: logs, SBOMs, and packaged images stay with each project for future investigations.
  • Field support acceleration: FAEs can reproduce customer issues by replaying the same project profile.

6. Conclusion​

BSP Launcher converts a traditionally manual BSP workflow into a predictable, traceable, and user-friendly experience. Whether you are testing a prebuilt image, rebuilding the BSP from source, or flashing dozens of systems on a manufacturing line, the launcher enforces the same process every time—reducing mistakes and accelerating delivery.