Quick Start

Note

The Workspace and Tools Setup, Import Application, and Create New Application panels support both West and bare-metal CMake/SDK projects. The Workspace and Tools Setup wizard detects the project type from the selected source and adapts its steps accordingly. You can also open an existing project folder via File → Open Folder and configure it with the Configure Settings panel (onsemi Studio Activity Bar → Configuration → Configure Settings) or by editing .vscode/settings.json directly.

Workspace and Tools Setup

Open the Command Palette (Ctrl+Shift+P) and run:

onsemi: Workspace and Tools Setup

Alternatively, open the Quick Start View in the onsemi Studio Activity Bar and click Development Environment Setup.

Quick Start View in the onsemi Studio Activity Bar with Development Environment Setup, Import Application, and Create New Application entries

Fig. 1 Quick Start View in the onsemi Studio Activity Bar

This opens the interactive setup panel with two operation modes:

  • Express Mode - Fully automated installation (recommended for first-time users)

  • Advanced Mode - Granular control over individual tool selection and installation

Import Application

Open the Command Palette (Ctrl+Shift+P) and run:

onsemi: Import Application

Alternatively, click Import Application in the Quick Start View (onsemi Studio Activity Bar).

The import panel guides you through:

  • Select SDK/Repository: Choose from configured SDKs/Repositories or browse for local folders/archives

  • Choose Toolchain: Select an existing toolchain or browse for toolchain installation path

  • Select Board Vendor and Target Board (West only): Choose the board vendor, then select the specific target board from the available options

  • Select Application(s): Pick one or more samples from the chosen SDK/Repository. Both CMake / bare-metal SDK and West sources support selecting multiple samples in a single import; failure on an individual sample does not abort the rest of the batch. For West imports, every selected sample is paired with the board chosen in the previous step.

    Zephyr only — toggle the “Repo samples only” checkbox above the sample list to hide upstream Zephyr samples and show only samples discovered under the selected repository’s samples/ folder. Uncheck it to also see upstream Zephyr samples. A sample is recognized whenever its directory contains a CMakeLists.txt (a sample.yaml is no longer required).

    West only — (experimental) when a board is selected, the sample picker reads each sample’s twister manifest (sample.yaml or the newer tests.yaml) plus the samples/boards/<vendor>/<board>/ path convention and offers a Compatible / All toggle. This feature is experimental and relies on support being declared in the sample’s twister manifest (tests.yaml) or the board’s <board>_<soc>.yaml:

    • Compatible hides samples that cannot build for the selected board. Samples with no twister manifest are hidden in this mode (except board-specific samples under samples/boards/<vendor>/<board>/).

    • All shows every sample and adds a green Recommended badge when the board is in the sample’s integration platforms.

    The board’s architecture is resolved from its platform file (<board>.yaml / <board>_<soc>.yaml) and its toolchain variant from the selected SDK, so arch_allow / arch_exclude and toolchain_allow / toolchain_exclude are applied along with depends_on hardware features. Samples whose support depends on an unevaluable devicetree filter stay visible in Compatible mode without a badge.

After import, the project is added to your VS Code workspace with:

  • Configured build settings in .vscode/settings.json

  • Selected toolchain and board

Import Application panel showing workspace and sample selection

Fig. 5 Import Application panel showing workspace and sample selection

Tip

Copy Sample Option: When importing, you can enable the “Copy Sample” option to copy the sample to a different directory. This helps avoid long path issues on Windows and provides better organization.

Create New Application

Open the Command Palette (Ctrl+Shift+P) and run:

onsemi: Create New Application

Alternatively, click Create New Application in the Quick Start View (onsemi Studio Activity Bar).

Create a new application from scratch:

  • Select SDK/Repository: Choose the sdk/repository for the new application

  • Choose Template: Select whether to create an empty application or start from an existing sample (the “From Sample” tab is active by default)

Create New Application panel showing template selection

Fig. 6 Create New Application panel showing template selection

  • Configure Project: Enter the Application Name and Save Location for your new application

  • Environment Configuration:

    • Toolchain: Select the toolchain for building

    • Board Vendor: Choose the board vendor (West)

    • Target Board: Select the target board (West)

  • Click Create Application to create your new application

Create New Application panel showing Configure Project and Environment Configuration

Fig. 7 Create New Application panel showing Configure Project and Environment Configuration

Working with Projects

Once you have projects in your workspace, you can:

From Explorer and onsemi Studio Activity Bar:

Right-click on project folders to access:

  • Build, Clean, Rebuild

  • Configure (CMake projects)

  • Flash (West projects)

  • Debug (Start debugging with active ELF)

  • Stop Task (cancels the in-flight build / configure / clean / flash for that project)

  • Memory Reports (West projects)

  • KConfig (menuconfig / guiconfig) for West projects and for CMake projects that expose menuconfig / guiconfig targets

  • Debug Files submenu: - Select Active ELF - Clear Active ELF - Rescan ELFs

  • Open in onsemi Studio Terminal (Opens terminal with proper environment)

Application View

After importing or creating projects, they appear in the Application View with an organized structure:

  • Configuration

    • Active Configuration: Quick selector for build configurations

    • Board: Change target board (West Projects)

    • Toolchain: Switch between registered toolchains

  • Actions

    • Build: Compile the project

    • Clean: Remove build artifacts

    • Clean and Rebuild: Clean then build

    • Flash: Load firmware to the board (West Projects)

    • Configure: Configure the project (Bare-metal CMake Projects)

    • Debug: Open Debug Configuration Panel

    • Stop Task: Cancel a running build / configure / clean / flash (visible only while a task is running)

    • KConfig Config: Run menuconfig or guiconfig (West projects, and CMake projects with menuconfig / guiconfig targets)

  • Documentation: Text, RST, and MD files

  • Header Files: All .h files

  • Source Files: All .c files

  • Output Files: Build outputs (*.elf, *.map, *.dts, .config)

  • Components: All source files compiled into the final output

  • Configuration: Kconfig and DeviceTree files (West Projects)

Application view showing project structure and actions

Fig. 8 Application view showing project structure and actions

Switching the Active Configuration

The Active Configuration determines which build configuration (board, args, environment, preset) is used when you Build, Clean, Configure, Flash, or Debug a project.

To change it from the Application View:

  1. Expand Projects → <your application name> → Configuration → Active Configuration.

  2. Click Active Configuration. A Quick Pick menu appears listing all configurations defined under onsemi.build.configurations in the project’s .vscode/settings.json.

  3. Select the desired configuration. The Application View updates to reflect the new active configuration, and subsequent project actions use it.

You can also change the active configuration from the Configure Settings panel:

  1. Expand Projects → <your application name> → Configuration → Configure Settings.

  2. In the panel, under Build Configurations, toggle the Active switch (or radio button) on the desired configuration.

  3. Click Save at the top of the panel.

Important

Changes made in the Configure Settings panel are not applied until you click Save. Unsaved changes are kept only in the panel.

Pristine Build Mode (West)

For West build configurations, each entry under onsemi.build.configurations accepts a pristine property that controls whether west build re-runs CMake from scratch:

  • "auto" (default) — Re-run CMake only when inputs (board, overlays, prj.conf, etc.) change. Fastest for incremental development.

  • "always" — Always wipe the build directory before configuring. Use this when you have changed something CMake’s auto-detection cannot see (for example, you moved or renamed the project on disk and the build directory’s cached source path is now stale).

  • "never" — Never wipe; reuse the existing build directory unconditionally.

You can change pristine from the Configure Settings panel (per build configuration) or by editing .vscode/settings.json directly.

Project Terminal

Open an integrated terminal with your project’s environment already configured:

Command: Right-click project folder → “Open Terminal”

The terminal automatically configures:

  • PATH Environment: Starts from the system/user PATH inherited by VS Code, with the active project’s repository tools (registered under onsemi.repositories) prepended. The terminal uses a strict environment, so tool entries from other repositories registered in your settings do not leak into this terminal’s PATH. This guarantees the project sees the exact tool versions configured for its own repository (e.g. its own CMake, Ninja, and toolchain), while system-wide tools (Git, Python, etc.) remain available.

  • Python Virtual Environment: Auto-activated for projects (if configured in .vscode/settings.json)

  • Project Environment Variables: All project-specific variables from settings

  • Working Directory: Set to your project root

Configure Project Settings

For more control over project settings:

  1. Expand your project in the Application View

  2. Under Configuration, click “Configure Settings”

  3. The Configure Project Settings Panel opens

Configure Project Settings panel

Fig. 9 Configure Project Settings panel

The panel provides:

  • Root Project Path: Points to the root project directory

  • Toolchain Path: Path to your toolchain installation

  • Python Environment Path: Path to the virtual environment folder

  • Build Configurations: Manage multiple build configurations

    • Add new configurations using the “+” button

    • Clone existing configurations using the “Clone” button

    • Toggle Active switch to set the active configuration

    • Configure build-specific settings (board, sysbuild, pristine mode, args, environment variables)

    • (West) Select Snippets to apply from the multi-select — available snippets are discovered from the sibling Zephyr tree (<west-dir>/zephyr/snippets) and the repository’s own snippets/ folder, and are passed to west build as repeated -S <name> flags

Configure Settings panel showing the West Snippets multi-select

Fig. 10 West Snippets multi-select in the Configure Settings panel

  • Save Changes: Click the “Save” button after making changes

Repository Tools Panel

The Repository Tools panel lists every registered repository that still exists on disk (from onsemi.repositories) grouped with its configured tool installations. Open it from the Command Palette (onsemi: Repository Tools) or from the title-bar action on the Application view. The panel is only available when at least one repository is registered (onsemi.hasRepositories context key).

For each tool the panel shows:

  • Its parsed version and source (managed / system)

  • Toolchain and duplicate-entry badges where applicable

  • Whether the tool’s install path exists on disk

  • A west badge for West-based projects

You can edit a tool’s install path inline or via a folder picker, add new tools per repository, and remove tools — all changes are written back to onsemi.repositories.

Repository Tools panel listing repositories with their configured tools, versions, and badges

Fig. 11 Repository Tools panel

NVM Image Tool Panel

The NVM Image Tool panel mirrors the SK5 NVM plugin options, generates the full nvmi command line, and launches nvmi.exe directly from VS Code. Open it with the onsemi: NVM Image Tool command.

Note

The panel is only surfaced when a registered SDK declares NVM support (isNVMSupport: true in its sdk.json); the onsemi.panel.nvm command is gated behind the onsemi.nvmSupported context key.

NVM Image Tool panel showing NVM options and the generated nvmi command line

Fig. 12 NVM Image Tool panel

Debugging Your Application

Prerequisites

  • J-Link debugger connected to your target board

  • J-Link GDB Server (JLinkGDBServerCL.exe) must be in system PATH or manually specified

Note

J-Link version check — When you start a J-Link debug session or run west flash, onsemi Studio warns (once per window session, non-blocking) if J-Link is missing or older than the version the active SDK recommends via minJLinkVersion in its sdk.json, and offers a shortcut to the SEGGER download page. The Debug Configuration panel also shows a non-blocking banner and highlights the GDB Server input when the configured J-Link is missing or outdated. Saving and debugging are never blocked, and SDKs that do not declare minJLinkVersion produce no warning.

Debug Configuration panel showing the non-blocking J-Link version warning banner

Fig. 13 Non-blocking J-Link version warning banner in the Debug Configuration panel

Quick Start Debugging

  1. Build your project first to generate the ELF file

  2. Select Active ELF (automatic or manual):

    • Automatic: The extension auto-detects and selects the ELF file from your build directory

    • Manual: Right-click project → Debug Files → Select Active ELF

  3. Run the Debug command to open the Debug Configuration Panel:

    • Right-click project folder → onsemi: Project: Debug

The panel provides:

  • Configuration management (create, edit, duplicate, delete)

  • Visual editors for general settings, target configuration, runtime options, command customization, UART settings, and peripheral inspector

  • Real-time JSON preview

  • Task integration

Configuring Debug Settings

Target Tab

  1. Device Name: Enter your target device name (e.g., Cortex-M0+)

  2. GDB Server Path: Verify the path to JLinkGDBServerCL.exe

    • Default: Should be auto-detected if J-Link is in PATH

    • If not found, click Browse to locate it

  3. Connection Settings:

    • Host: localhost (default)

    • Port: 2331 (default)

Debug Configuration Panel - Target Configuration

Fig. 14 Debug Configuration Panel - Target Configuration

Initialization Tab

Configure initialization settings for your target device:

  1. Reset Command: Command sent to reset the target device

    • Reset Timing: Controls when the target device is reset during programming

      • Before Programming: Reset before loading program

      • After Programming: Reset after loading program

      • Always: Reset before and after programming

      • Never: No automatic reset

    Important

    Use “Never” when running code from RAM or when reset interferes with debug session.

  2. Initialization Commands: Commands executed after connecting to target but before running

    • Command Generation Options: Automatic generation of common GDB commands

      • Include Load Command: Load program load to target

      • Enable Semihosting: Emits monitor semihosting enable so target-side printf / file I/O is routed through the debugger. When enabled, choose a Console Routing target:

        • Telnet (port 2333) — output sent over the J-Link telnet port

        • GDB target output stream — output sent to GDB’s target output stream

        • GDB stdio (Debug Console) (recommended) — output appears directly in the VS Code Debug Console

      • Set Program Counter: Set CPU program counter to specific address or symbol (e.g., Reset_Handler, main, or 0x08000000)

      • Set temporary breakpoint: Set temporary breakpoint tbreak at a function name (e.g., main)

      • Output display format: Controls how GDB displays numeric values (addresses, register contents, etc.)

    • Generated Commands Preview: Shows the actual GDB commands that will be executed

    • Additional Commands: Enter custom GDB commands to execute after the generated commands

  3. Pre-Run Commands: Commands executed after loading the program but before start of execution

    • Additional Commands: Enter the actual GDB commands to send

  4. Custom Reset Commands: Enter custom reset commands when standard reset is insufficient

Debug Configuration Panel - Initialization Commands

Fig. 15 Debug Configuration Panel - Initialization Commands

GDB Settings Tab

  1. Debugger Executable: Verify path to GDB executable

    • Should point to your toolchain’s GDB (e.g., arm-zephyr-eabi-gdb.exe, arm-none-eabi-gdb.exe)

    • Click Browse if you need to change it

Debug Configuration Panel - GDB Settings

Fig. 16 Debug Configuration Panel - GDB Settings

Peripheral Tab

Configure SVD (System View Description) file for viewing and debugging microcontroller peripheral registers during debug sessions:

  1. SVD File Path: Browse and select the SVD file for your target device

    • SVD files provide detailed register layouts and bit field descriptions

    • Enables viewing and modifying peripheral registers in real-time during debugging

Debug Configuration Panel - Peripheral Inspector

Fig. 17 Debug Configuration Panel - Peripheral Inspector

Starting the Debug Session

  • Program Path: The extension automatically resolves the active ELF file path. You can use the variable ${command:onsemi.getActiveElfPath} or specify a workspace-relative path using ${workspaceFolder}.

  • Click “Start Debugging” to debug the program (with breakpoints)

  • Click “Run Program” to flash the program without debugging

Note

Selecting Active ELF File: When multiple ELF files are present in your project, use the bottom status bar to select the active ELF file for debugging. If the Debug Configuration panel is already open when you change the active ELF in the status bar, you must save the Debug Configuration for the panel to display the updated ELF path.

Start debugging

Fig. 18 Start debugging

Troubleshooting Debug Issues

If program fails to load:

  1. Verify GDB Server Path points to correct JLinkGDBServerCL.exe

  2. Check Debugger Executable in the GDB Settings Tab points to the correct GDB

  3. Ensure your J-Link debugger is connected and detected

  4. Try debugging again