Documentation FreeMASTER Documentation    This training currently covers the following areas: Getting started - Variables, communication with target, and project configuration Gui Guider integration   Other resources NXP Community - FreeMASTER 

RTOS DETAILS View The RTOS DETAILS view shows various information about RTOS Tasks/Threads. The view appears in the bottom pane, once a debug session is started, and disappears after debugging ends. The view is independent of the debug probe being used, as it only uses GDB commands to receive information from the target. The supported RTOSes are: FreeRTOS  Zephyr    FreeRTOS Usage The RTOS DETAILS view will display the following for FreeRTOS projects. However, the project must be configured properly. TCB#: Task Control Block.  configUSE_TRACE_FACILITY  needs to be set to 1. Task Name: Name of task.  configMAX_TASK_NAME_LEN  needs to be greater than 1. Task Handle: Address of the task handle. Task State: Current task state. Rows are also colored based on the state. Priority: Task actual priority and task base priority. Stack Usage: Graphical view of current stack usage, peak usage and total size for the task. Hovering over the cell reveals more information about the stack.  configRECORD_STACK_HIGH_ADDRESS  needs to be set to 1. Runtime: Task runtime with percentage value.  configGENERATE_RUN_TIME_STATS  needs to be set to 1. Note: The Runtime view needs a patch to FreeRTOS to access runtime counters. See Erich Styger's blog for explanation and patch.     For the FreeRTOS portion of this article, I'll be working with the frdmrw612_freertos_sem example project obtained from the FRDMRW612 SDK. To configure the settings on this project, open the FreeRTOSConfig_Gen.h file. In the FreeRTOSConfig_Gen.h file, use Ctrl+F to quickly find and set the defines highlighted in red above. Save the file.   Once the settings have been configured, build the example and flash the board. The RTOS DETAILS View is available in the bottom pane. To view the data, suspend the target and the view will detect the RTOS type and read information about the tasks/threads. Every time the target stops (suspended or stepped), the RTOS DETAILS view will refresh with updated information.   RTOS DETAILS view has the following capabilities: Resize columns by dragging their edges. Sort columns by clicking on them. Hover over each cell and header to get more information. Color rows by task/thread state. Display warning icons when missing certain RTOS configurations. The warning icons can be hovered for more help on how to solve the issue.     Zephyr Usage The RTOS DETAILS view will display the following for Zephyr projects. Name: Name of the thread.  CONFIG_THREAD_NAME  needs to be enabled. Handle: Address of the thread handle. Priority: Priority of the thread. State: Current task state. Rows are also colored based on the state. Stack Usage: Graphical view of the stack delta offset, current usage and total size for the thread. Hovering over the cell reveals more information about the stack.  CONFIG_THREAD_STACK_INFO  needs to be enabled.   For the Zephyr portion of this article, I'll be working with the philosophers example project obtained from the Zephyr 4.1.0 SDK. To configure the settings on this project, open the prj.conf file. Add the highlighted items above and save the file.   Next, build the project and flash the board. The RTOS DETAILS view will appear on the bottom pane during a debug session as it did for the FreeRTOS example. Expect the behavior to be similar with only a change in the columns.

This guide covers: How to create a basic gui for your FreeMASTER project using Gui Guider Connection to FreeMASTER How to import FreeMASTER project file How sync the FreeMASTER project variables into a gui

The following video demonstrates how to import a GUI Guider project to VS Code:

Kconfig Usage You can interact with Kconfig via graphical menu interface. Once you have completed the CMake configuration process, you can invoke the Kconfig gui with the following command:   west build -t guiconfig   In this interface, the user selects the options and features desired, and saves a configuration file, which is then used as an input to the build process.   Kconfig Example In this exercise, we will use the simple freertos Hello_World example to demonstrate how to launch and interact with the Kconfig gui. Build the project on the CLI using West       Launch the Kconfig gui by running:        The previous command launches the following gui:       Use the dropdown menus or the Jump to... button to find components   Select a component and click Save to update   Once you have finalized changes to any components, simply rebuild the project.

Documentation Open-CMSIS-Packs Documentation    This training currently covers the following areas: Getting started - Installation and environment setup Build, Flash, and Debug Using partner packs - EmSA walkthrough Using partner packs - Crank Software walkthrough 

Overview MCUXpresso SDK 24.12 introduced enhanced support for custom manifests, enabling developers to define precisely which components, drivers, middleware, and board support packages are included in their workspace. This feature is especially valuable in modern embedded workflows where minimalism, reproducibility, and CI/CD integration are key. Customization of the MCUXpresso SDK is enabled by West. The West tool is used to manage multi-repository projects. By leveraging custom west.yml files, developers can: Reduce SDK footprint by excluding unused components. Accelerate build times and simplify dependency management. Align SDK content with specific hardware targets or application domains. Improve collaboration across teams by standardizing SDK configurations. This guide walks through the process of creating and using a custom manifest to tailor your MCUXpresso SDK setup, ensuring your development environment is optimized for performance and maintainability. This guide has the following components: Cloning the MCUXpresso SDK manifests Creating a custom manifest file Initializing the West workspace Completing the import with West Test and build a project   Cloning the MCUXpresso SDK manifests - Ensure that Git is installed and available in the system path - Open a terminal - Navigate to or create a directory to store the SDK - Run:  git clone https://github.com/nxp-mcuxpresso/mcuxsdk-manifests.git Output:   - Navigate to the mcuxsdk-manifests directory. We will modify the west.yml file in the next step     Creating a custom manifest file - Open the file in an editor (e.g VS Code).   - Make a copy of the west.yml file. Give the copy a relevant name: mcuxpresso_sdk_custom_mcx.yml. - The following items contain component-specific manifests that can be explicitly included in the import relevant to a particular use case. Devices. Explore /submanifests/devices. The list of manifest files are ALL imported if NOT specifically listed. Middleware. Explore /submanifests/middleware. The list of manifest files are ALL imported if NOT specifically listed. RTOS. Currently there is only 1 manifest file. Future updates may offer alternate RTOS manifests. In this guide, we will replace the devices and middleware lines with an explicit submanifest. Replace the devices and middleware lines with a specific submanifest that includes only the components you need. To further reduce the amount of content imported, remove the rtos and internal components. import: - submanifests/base.yml - submanifests/devices/MCX.yml - submanifests/middleware/eIQ.yml   - Save the modified mcuxpresso_sdk_custom_mcx.yml file. The file should now contain:      Initializing the West workspace - In your terminal, navigate to the mcuxsdk-manifests directory - Create a West workspace in the current directory using the updated manifest file run: west init -l --mf mcuxpresso_sdk_custom_mcx.yml  *Note: -l : Stands for "local" --mf : Specifies a custom manifest file to use instead of the default file west.yml. Output:     Completing the import with West After initializing the West workspace, we are now ready to import. - Run: west update Output: *This image is concatenated to show that the import process has begun.   Test import and build a project At this point the custom MCUXpresso SDK manifest is ready for use. To test, import an example project into MCUXpresso for VS Code and build it. - Import the custom SDK into MCUXpresso for VS Code.   - Import an example from the custom MCUXpresso SDK   - Build the project.   Output: **Note: This step assumes that the user has already installed dependencies (e.g toolchain, CMake, etc). Follow the steps below to install dependencies with the MCUXpresso Installer if not yet done so.   - Open the MCUXpresso Installer.   - Select MCUXpresso Developer. Click install.  

This video demonstrates how to quickly get started with Open-CMSIS-Packs  

This guide covers: How to import example projects from standalone SDKs How to build, flash and debug How to use the serial monitor

This getting started guide covers: Preparation of project variables for visualization with FreeMASTER FreeMASTER communication with target Importing symbol files Adding variables to the FreeMASTER Variable Watch Creating visual components to visualize data for variables

This guide covers: How to launch Config Tools for projects in MCUXpresso for VS Code. How to modify and update code from Config Tools. Note: The warning at 1:43 is due to an older version of Config Tools. Note: The dialogue at 2:13 refers to simultaneously route the Wakeup Unit Peripheral that is not needed for this example.

Documentation LinkServer Integration with MCUXpresso IDE   This training currently covers the following areas: General Usage Getting Started with LinkFlash: A GUI-Based Flash Programming Utility - NXP Community NXP LinkServer 24.9.75: New GUI for Flash Programming | MCU on Eclipse

GOAL Learn how to import CMSIS packs into existing projects. In this particular project, CMSIS packs from EmSA will be used alongside the lpcxpresso55s16_mcan_interrupt_transfer example obtained from the LPCXpresso55s16 SDK.   ENVIRONMENT This guide requires MCUXpresso IDE v11.9.1 or latest.   PROCEDURE 1. Import the lpcxpresso55s16_mcan_interrupt_transfer example into the workspace. In this example, SDK drivers, startup and board interface files are readily available. CAN pins are already routed and enabled.     2. Launch Config Tools to configure the clock for the CAN peripheral     3. Configure the clock for the CAN peripheral. I. Set up the main clock so that it is generated from crystal or oscillator, and it is evenly dividable by 40 MHz.   II. Change the PLL configuration an even multiple of 40 MHz   III. Set the CAN divider to get a 40 MHz clock.   4. Update the code.   5. Add Open-CMSIS Packs to the project.   6. Project set-up I. Add the watchdog driver.   II. Exclude the fsl_mcan.c module from the build. A dedicated version is included in the EmSA packs.   III. Add the main.c module from CMSIS template   IV. Exclude or remove the original main source code mcan_interrupt_transfer.c file.   7. Save and build the project.          

Open-CMSIS-Pack project  This is a link to the Open-CMSIS-Pack project website. This resource provides all the technical details behind CMSIS-Packs.   Working with Open-CMSIS-Packs  This is a link to documentation for MCUXpresso for VS Code that shows the user how to get started with Open-CMSIS-Packs.      

The NXP MCUXpresso SDK team is developing West Extension commands to help customers utilize the SDK.  In 25.06.00 SDK release on GitHub, the team introduced west explore command.  A user can gain access to the command with the following instructions.  Also demonstrated in the video below. Install Visual Studio Code Install the MCUXpresso for VS Code extension from the Marketplace Use MCUXpresso Installer to properly set up work environment with tool dependencies. Import the MCUXpresso SDK from GitHub.  Use Import Repositories wizard in VS Code   Select "24.12 or newer" Remote tab Select Version = 25.06.00 or newer Import repository.  It will clone the manifest repository, then run west update to import the repositories associated with the SDK. Open a terminal.  In Terminal Tab select "MCUXpresso Terminal" Select to open Terminal in MCUXpresso SDK mode Select target of GitHub SDK installed in step 4 Change folder to the root of the /mcuxsdk.  There will be several SDK folders including /examples Type command 'west explore' Use keywords and drop down options to filter thousands of SDK Examples Select and copy a single command from the bottom of the GUI. Paste and run the command.   MCUXpresso SDK Project will build and run for the filtered example you selected. NOTE: You can add "-d /pathname_example" to have the example stored in a unique folder

This guide covers how to work with example projects obtained from an Open-CMSIS-Pack.

FreeMASTER User Guide  This document provides in-depth information about FreeMASTER'S features and usage.    

Documentation MCUXpresso Config Tools | Software Development for NXP Microcontrollers (MCUs) | NXP Semiconductors This training currently covers the following areas: MCUXpresso Config Tools: How-Tos MCUXpresso Config Tools: Zephyr Pins Setup System Manager configuration via Config tools for i.MX