Zephyr RTOS on FRDM-MCXN947: A Practical Bring-Up Guide

Introduction

What is Zephyr RTOS??

Zephyr RTOS is a scalable, open-source real-time operating system designed for resource-constrained embedded systems. It is maintained under the Linux Foundation and supports multiple architectures including ARM Cortex-M, RISC-V, and x86.

Zephyr provides:

• Deterministic real-time scheduling
• Modular kernel architecture
• Device driver framework
• Networking and Bluetooth stacks
• Secure firmware support
• Device Tree-based hardware abstraction

Unlike traditional bare-metal firmware, Zephyr introduces a structured RTOS environment that enables multitasking, synchronization, and better system organization. It is widely used in IoT, wearable devices, industrial automation, and edge computing applications.

Why RTOS is Important in Embedded Systems??

In modern embedded systems, applications are no longer limited to blinking LEDs or reading a single sensor. Systems today often require:

• Handling multiple sensors simultaneously
• Managing communication stacks (BLE, UART, SPI, I2C)
• Running background tasks
• Meeting strict timing constraints

Maintaining responsiveness a Real-Time Operating System (RTOS) ensures that critical tasks execute within defined timing boundaries. It provides Task scheduling, Interrupt handling, Inter-process communication, Resource management.

Without an RTOS, managing concurrency and timing in complex systems becomes difficult and error prone. Using Zephyr helps structure firmware in a scalable and maintainable way, especially as system complexity increases.

Why the MCX Series is Interesting??

The FRDM-MCXN947, developed by NXP Semiconductors, is based on the new MCX series of microcontrollers featuring dual Cortex-M33 cores.

What makes this platform interesting:

• Dual-core ARM Cortex-M33 architecture
• Modern security and Trust Zone support
• High-performance peripherals
• Advanced power management
• Scalable architecture for industrial and IoT applications

The MCX series represents a new generation of microcontrollers aimed at performance, security, and real-time control applications. Bringing up Zephyr on this board is not just about running an example — it is about understanding how a modern RTOS interacts with a next-generation MCU platform.

Development Environment Setup for Zephyr on FRDM-MCXN947:

To build and run the Blinky application on the FRDM-MCXN947 using the Zephyr ProjectRTOS, a complete cross-compilation environment must be configured. Zephyr follows a modular build architecture that integrates multiple tools working together to transform application source code into executable firmware for the target microcontroller. The environment consists of Python, West, CMake, Ninja, and the Zephyr SDK. Each component plays a specific role in the build and deployment pipeline.

Python Installation:Python (version 3.10 or newer) is required because Zephyr’s tooling infrastructure is built around Python-based scripts. The west meta-tool, build configuration utilities, device tree processing, and Kconfig system rely on Python execution.After installation, the version can be verified using:

python --version

Python does not execute firmware code on the microcontroller; rather, it enables the host-side build system.

CMake Installation:CMake functions as the build configuration engine. It reads project metadata such CMakeLists.txt, board definitions, and configuration files, and generates low-level build instructions.Installation can be verified with:

cmake --version

CMake determines what components are compiled, which drivers are enabled, and how the selected board is configured. It does not perform compilation itself but prepares instructions for Ninja.

Ninja Installation:Ninja serves as the build executor. Once CMake generates build files, Ninja processes those instructions and performs the actual compilation and linking steps. Ninja compiles source files into object files and links them into firmware such as.elf,.bin, and.hex.Verification command:

ninja --version

Zephyr SDK Installation:The Zephyr SDK provides the cross-compilation toolchain required to build firmware for ARM Cortex-M processors. Since the FRDM-MCXN947 contains a Cortex-M33 MCU, an ARM cross-compiler is necessary. The SDK includes ARM GCC compiler (arm-zephyr-eabi-gcc), Linker, Binary utilities, Debugging support tools. The SDK enables compilation on a host machine (Windows/Linux/macOS) targeting an embedded ARM architecture.Workspace Initialization Using West:West is the meta-tool developed by the Zephyr Project to manage repositories and builds.A new Zephyr workspace is initialized using:

west init zephyrproject

This command creates a workspace structure prepared to host the Zephyr source tree.All required repositories and modules are then downloaded using:

cd zephyrproject
west update

The Zephyr kernel, Hardware abstraction layers (including NXP support), Board definitions for FRDM-MCXN947, External modules required for compilation. Without executing west update, the Zephyr environment remains incomplete.Building the Blinky Application:After entering the Zephyr source directory:

cd zephyr

The Blinky sample application can be built using the following commands in the terminal:

west build -b frdm_mcxn947/mcxn947/cpu0 samples/basic/blinky

Parameter Description

• -b frdm_mcxn947/mcxn947/cpu0 Specifies the target board and CPU core. The MCXN947 microcontroller supports multiple cores; explicit core selection ensures correct firmware targeting.
• samples/basic/blinkyIdentifies the application source directory.

here the command initiates the following sequence :Firstly west invokes CMake for configuration, the CMake processes board definitions, device tree files, and Kconfig settings.Ninja executes compilation and linking using the Zephyr SDK toolchain and finally as a result firmware artifacts are generated in the build/zephyr/ directory.Firmware Deployment:

Open OCD is not supported for this board in Zephyr. The default and supported flashing tool is NXP Link Server. As Link server is the default runner for this board, and supports the factory default MCU-Link firmware.Link Server should be downloaded from NXP website and installed locally. The installation directory should be added to the Windows system PATH variable(since the host machine used is windows). Default path of link server is

C:\NXP\LinkServer_25.12.83

and also confirmed with version by

LinkServer.exe --version

with the target board connected via USB,

firmware programming is performed using the command :

west flash

This command transfers the compiled binary to the microcontroller’s flash memory using the board’s supported flashing interface. Successful execution results in periodic toggling of the onboard LED, confirming:

• Correct toolchain configuration
• Functional board support package
• Proper GPIO driver initialization
• Operational Zephyr kernel scheduling

Conclusion:

This project demonstrated a complete Zephyr RTOS bring-up on the FRDM-MCXN947, from environment setup to successful firmware execution. It reinforced the importance of structured build systems, proper board configuration, and understanding RTOS-based development workflows.

With Zephyr running reliably on hardware, this foundation enables the development of more advanced real-time embedded applications.