Getting Started with Zephyr

1.1 Preparing Zephyr Environment

This video walks you through the essential steps to get your Zephyr development environment up and running on a Windows operating system using Visual Studio Code (VS Code) and the MCUXpresso extension.

This presentation aims to make setup quick and easy, so you can start developing your application now without getting bogged down in the details.

1. Download and Install VS Code
   Get the latest version of VS Code for Windows.
2. Install the MCUXpresso extension for VS Code
   Add NXP’s official extension to enable embedded development features
3. Run the MCUXpresso installer
   Use the installer to set up the software development kit (SDK), toolchain and environment
4. Install the Zephyr Repository
   Clone and configure the Zephyr repo to complete your setup
5. Install MCUXpresso Config Tools
   Pin tool support for Zephyr is available for version 25.03 and higher
6. Install MCUXpresso Secure Provisioning Tool

1.2 Install Your Toolchain

NXP offers a complimentary extension for VSCode called MCUXpresso for VS Code.

Download VS Code to access the extension library.

Get VS Code

Learn how to install VS Code for your host PC with the following tutorial

1.3 Jump Start Your Design with Zephyr Developer

The MCUXpresso Installer includes an option called the 'Zephyr Developer', allowing you to download all necessary components, tools and dependencies needed in addition to the Zephyr SDK. The Zephyr SDK contains toolchains for each of Zephyr its supported architectures, which include a compiler, assembler, linker and other programs required to build Zephyr applications.

Find the MCUXpresso Installer inside the "Quickstart Panel" of the MCUXpresso for VSCode

1.4 MCUXpresso Config Tools

The MCUXpresso Config Tool is an integrated suite of configuration tools that guides users in creating new MCUXpresso SDK project it also includes pin and clock tools to generate initialization C code for custom board support. The Pins Tool has a Graphic User Interface (GUI) to help select all the desired signals used by the application, and configure the PinMux and pin settings. Starting with release v25.03, the Config Tool can generate Zephyr board pinctrl files for the i.MX RT1xxx and MCX devices. Zephyr uses pinctrl to configure the pins and PinMux settings of an system on chip (SOC).

Click the Get MCUXpresso Config Tools button below to get the Config Tools installer.

Get MCUXpresso Config Tools

1.5 Programming and Provisioning Tools

The MCUXpresso Secure Provisioning (SEC) Tool is a GUI-based application provided to simplify the generation and provisioning of bootable executables on NXP microcontroller unit (MCU) devices. We recommend all users to begin with the MCUXpresso SEC tool for trial run and mass production use. It supports secure programming and device provisioning on NXP's microcontrollers at the production stage. After downloading the tool, you can find the user guide under the ‘Help’ tab. Follow the instructions for your board in the ‘Processor-specific workflow’ chapter.

Download SEC

Note: For advanced users who need a more customizable set-up, we also offer a command-line tool that is useful when interfacing with a custom or partner programming tool. The Secure Provisioning Software Development Kit (SPSDK) is open source and cand be found on GitHub  and PyP.

1.6 Get Familiar with MCUXpresso for VS Code

Key Features to Know in MCUXpresso for VS Code

When getting started with MCUXpresso for VS Code, it helps to be aware of a few key features and tools that can streamline your development experience. This section gives you a high-level overview — rather than a deep dive—so you can get oriented quickly.

Quickstart Panel

The quickstart panel is your launchpad for creating, importing and managing projects. It provides shortcuts to common tasks. Here, the most commonly shortcuts are "Import Example from Repository" and "Open MCUXpresso Installer".

Projects View

This is where your workspace and project files are organized. Understanding how the Zephyr projects are structured will help you navigate and manage your code more effectively.

Device Tree

The device tree describes the hardware layout and configuration. After compiling the Zephyr Project and refreshing the DEVICE TREE view, it will be populated with a tree-like view of the project hardware hierarchy. You also can inspect the nodes and their associated values.

Pristine Build

Pristine build is used to clean and rebuild your project from scratch. It’s especially useful when switching configurations or resolving build issues.

Debug

MCUXpresso for VSCode integrates with various debuggers. With it you can learn how to set breakpoints, step through code and inspect variables to troubleshoot effectively.

Terminal and Serial Monitor

The terminal is designed to enable command-line interactions with the imported repositories. The serial terminal allows you to interact with your board via UART. This is great for logging, debugging and real-time communication.

1.7 Preparing the Hardware

This steps guides will walk you through how to get started with Zephyr using the FRDM-MCXN947 board as an example. However, you can follow the same general process with the different evaluation board of your choice.

Note: This guide does not cover custom hardware. For advanced topics and custom board support, please refer to the resources available on the Getting Started Support Page.

1. Choose Your Evaluation Board

   While this guide uses the FRDM-MCXN947, you may substitute it with another supported board, but make sure to:

   • Confirm Zephyr support for your board
   • Check for any board-specific setup instructions
2. Update On-Board Debugger Firmware

   Most evaluation boards come with an on-board debugger. To ensure compatibility and stability: Verify that your board’s debugger firmware is up to date.

   Download the latest firmware from the LinkServer firmware page. Choose the appropriate firmware type:

   • Cortex Microcontroller Software Interface Stardard-Debug Access Port (CMSIS-DAP)
   • Segger J-Link

   If your board does not have an on-board debugger, connect an external debugger to your target board.

3. Powering the Board

   You’ll need to power your board during development. Common methods include:

   • USB cable (most common)
   • Barrel jack connector (for some boards)
4. Plug in Your Board