Hands On In this lab we will first import the MCUXpresso for Visual Studio Code SDK for the MCX W23 Freedom board into the MCUXpresso extension for Visual Studio Code and then we will build, flash and debug the hello world project to make sure the environment is set for the following Labs. Hardware Requirements Personal Computer FRDM-MCXW23 Board Type C USB Cable Software Requirements IDE: Visual Studio Code 1.91.1 Extension: MCUXpresso for VS Code v25.06.97 or newer SDK: SDK next gen v25.06.00 or newer Windows OS (Windows 11 was used for this hands-on) Serial Terminal program, like PuTTY or Tera Term Note: In order to make downloads in NXP website, it is necessary to have an account. Please, register and log-in for moving forward. MCUXpresso for Visual Studio Code MCUXpresso for Visual Studio Code (VS Code) provides an optimized embedded developer experience for code editing and development. The extension enables NXP developers to use one of the most popular embedded editor tools and provides an easy and fast way to create, build and debug applications based on MCUXpresso SDK or Zephyr projects.               Install it following the next steps: Download Visual Studio Code from Microsoft Store or visual studio code web page Download Visual Studio Code - Mac, Linux, Windows Access to vscode for MCUX wiki and download MCUXpresso Installer  Dependency Installation · nxp-mcuxpresso/vscode-for-mcux Wiki · GitHub Run MCUXpresso Installer and for this Hands On install at least MCUXpresso SDK Developer Arm GNU Toolchain PEmicro   Installing the FRDM-MCXW23 SDK v 25.06.00. Each MCU has its own SDK that includes driver, examples, middleware, docs and other components. To get and build the demo, let’s install the SDK into VS Code:        Once MCUXpresso for Visual Studio Code is installed open VS Code. Go to MCUXpresso for VS Code extension that is on the tools column at the left. Look for INSTALLED REPOSITORIES option and press ‘+’. Detail steps are described in                                                                                                            Use the steps for import a remote Git repository wiki page. Working with MCUXpresso SDK · nxp-mcuxpresso/vscode-for-mcux Wiki · GitHub Search for Revision v25.06.00 or newer and complete installation. Lab Section . Run Hello World Demo Open VSCode Go to MCUXpresso for VS Code extension that is on the tools column at the left.     Go to PROJECTS section and select “Import Example Application from and Installed Repository”                                                                                                                                                                        Select “frdmmcxw23_hello_world” project as freestanding as shown in the next image and create the project                                                                                                                                                     Now you should have the “frdmmcxw23_hello_world” in your workspace. Before moving to the building and testing phase of the project, we want to do a small modification, go to line 39 of the hello_world.c file and change the line PRINTF("hello world.\r\n"); to PRINTF("hello world, this is MCXW23 from NXP Semiconductors.\r\n"); 7.Build the projects clicking “Build Selected” icon to make sure the build process succeeds with zero errors and warnings or you can right click on the project’s name and press “Build Project button”.   The build project process starts, follow its progress in the Console tab located in the bottom center of the window. If the build process will successfully end you will see something like “build finished successfully” in the Terminal window:   To start the debug session, connect the FRDM-MCXW23 board debugger port to your host PC, using the USB A to USB C cable provided with the FRDM board as per the picture below on MCU-Link USB port and then the other end to a free USB port on the host PC.                                                                                   Open a Serial terminal on PC for the serial device with these settings on the two boards: - 115200 baud rate - No parity - One stop bit - No flow control To identify the appropriate COM, open the Device Manager and look for MCU-Link VCom Port   To start debugging, simply click on Debug icon or you can right click on projects name and press “Debug” Button.   All is set to start debugging the project, click on “Continue” button or press “F5” key on your keyboard to continue running the downloaded program on device.   The execution of the example starts and “hello world, this is MCXW23 from NXP Semiconductors.” is printed in the Terminal window as per the below picture:   Enter any character + <enter> to see the examples echoes every character that is entered through the terminal. Click on the Stop button (red square) to end the debug session. Congratulations you have successfully completed the hello world lab.

This article will give a brief introduction of FRDM-IMX91S software release. FRDM-IMX Yocto BSP Release i.MX FRDM Development software release contains prebuilt images, documentation, and i.MX FRDM Yocto layer for FRDM-IMX boards. It also includes support for Matter.  Based on i.MX SW 2024 Q3 BSP release Linux kernel: 6.6.36_2.1.0 u-boot: 2024.04 i.MX FRDM Yocto layer source: https://github.com/nxp-imx-support/meta-imx-frdm For more details, please check i.MX FRDM Software User Guide. FRDM-IMX91S accessories and corresponding dtb: 5-inch Tianma LCD: imx91-11x11-frdm-imx91s-tianma-wvgapanel. dtb RPI-CAM-INTB: imx91-11x11-frdm-imx91s-mt9m114.dtb MX93AUD-HAT: imx91-11x11-frdm-imx91s-aud-hat.dtb 8MIC-RPI-MX8: imx91-11x11-frdm-imx91s-8mic.dtb Build FRDM-IMX91S SD boot image: Download i.MX SW 2024 Q3 Release: $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync Integrate meta-imx-frdm layer into Yocto code base: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git Yocto Project Setup: $ cd ${MY_YOCTO} $ MACHINE=imx91frdmimx91s DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-setup.sh -b frdm-imx91s Build images: $ bitbake imx-image-full Flash SD card image using dd: $ zstdcat imx-image-full-imx91frdmimx91s.rootfs.wic.zst | sudo dd of=/dev/sdx bs=1M && sync Or use uuu to burn image to SD card: $ uuu -b sd_all imx-image-full-imx91frdmimx91s.rootfs.wic.zst Build FRDM-IMX91S NAND boot image: Download i.MX SW 2024 Q3 Release: $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync Integrate meta-imx-frdm layer into Yocto code base: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git Yocto Project Setup: $ cd ${MY_YOCTO} $ MACHINE=imx91frdmimx91s DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-setup.sh -b frdm-imx91s Configure U-Boot to nand boot: $ echo "UBOOT_CONFIG = \"nand\"" >> conf/local.conf Build base rootfs: $ bitbake imx-image-base Build initramfs: $ bitbake fsl-image-mfgtool-initramfs Use uuu script to flash nand boot image:  $ sudo uuu example_kernel_nand.uuu FRDM-IMX91S Matter support  Based on i.MX Matter 2024 Q3. To include Matter support, please follow below steps to include Matter layer into Yocto build. Download i.MX SW 2024 Q3 BSP Release: $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync Download i.MX Matter Yocto layer: $ cd ${MY_YOCTO}/sources/meta-nxp-connectivity $ git remote update $ git checkout imx_matter_2024_q3 Integrate meta-imx-frdm layer into Yocto code base: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git Yocto Project Setup: $ cd ${MY_YOCTO} $ MACHINE=imx91frdmimx91s-iwxxx-matter DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-matter-setup.sh bld-xwayland-frdmimx91s Build images:  $ bitbake imx-image-multimedia Related Documentation i.MX FRDM Software User Guide More information about i.MX productions can be found at(http://www.nxp.com/imxlinux) i.MX Yocto Project User’s Guide​ i.MX Linux User’s Guide​ i.MX Linux Reference Manual​ i.MX Porting Guide

FRDM-IMX91S Hardware Introduction The FRDM i.MX 91S Development Board is a cost-effective, compact platform built around the i.MX 91 applications processor, optimized for embedded Linux development. It integrates the NXP IW610 wireless module, enabling robust Wi-Fi 6 + Bluetooth LE 5.4 / 802.15.4 connectivity for Industrial and IoT applications. Designed for rapid prototyping, the board supports GoPoint for i.MX Applications Processors, providing a suite of pre-integrated demos and reference implementations. The FRDM i.MX 91S features integrated 256MB NAND flash memory supporting direct boot (NAND boot). This includes a deeply trimmed, lightweight file system optimized for reliability and minimal resource consumption. Its small footprint maximizes usable storage while ensuring efficient operation. This file system serves as an ideal starting point – its modular design is fully customizable, allowing you to tailor it further to your specific application needs and optimize performance. Get to know FRDM-IMX91S Development Boaard Specifications i.MX 91 applications processor with 1x Arm® Cortex®-A55 LPDDR4 16-bit 512MB QSPI NAND Flash, 256MB Power Management IC (PMIC) MicroSD 3.0 card slot One USB 2.0 Type-C connector One USB 2.0 Type-C for debug One USB 2.0 Type-A connector One USB Type-C PD only Onboard Wi-Fi® 6 + Bluetooth® LE 5.4/802.15.4 module One 2x5 Pin NXP custom interface with: One CAN port Two channels for ADC I2C/I3C expansion One 1 Gbps Ethernet (ETER) External RTC with coin cell connector 40 pin (2 x 20) expansion I/O Feature FRDM-IMX91S SoC Package 11 x 11 NVM NAND flash 256 MB DRAM NANYA 512 MB PMIC PF9453 WiFi Module u-blox MAYA-W476 on-board USB TYPE C Type-C+Type-A ENET 1xGbe Display (Parallel RGB LCD) 2x20 EXPI Camera (Parallel Camera) 2x20 EXPI 2x20 Expansion Interface Y CAN BUS Y MicroSD Y UART Y Audio MQS Power Connector Type-C PCB layers 6 Base Board DIM 6.5 x 9.5 cm   NXP Devices On-board PMIC PF9453 Real time clock/calendar PCF2131 WIFI/BLE/802.15.4 Tri-Radio IW610 in u-blox module CAN Transceiver TJA1051T/3 IIC Extends GPIO PCAL6524   Expansion Boards ​8MIC-RPI-MX8: 8-microphone array proto board for voice enablement MX93AUD-HAT: Audio expansion board with multiple features Useful Links −i.MX Yocto Project User’s Guide​ −i.MX Linux User’s Guide ​−i.MX Linux Reference Manual​ −i.MX Porting Guide -i.MX Debian Linux SDK User Guide

This project implements a configurable secure encrypted Ethernet communication node with the transmission of a large data image.

This document is intended to guide you in the installation of the tools and let you know the material required for the FRDM-MCXW72 Channel Sounding Hands On 

Objectives In this lab, you will learn: How to use the MCUXpresso Installer to obtain NXP Software (FreeMASTER) How to use Application Code Hub to import an example into the VS Code workspace How to build, clean, debug, and run the example. How to connect the Serial Monitor for UART console How FreeMASTER can be used as a real-time debug monitor and data visualization tool Hardware Requirements Personal Computer FRDM-MCXA153 Board Heart Rate 4 CLICK Module (MIKROE 5547) USB type-C cable   Software Requirements MCUXpresso for VS Code FreeMASTER v3.2 or latest FRDM-MCXA153 SDK Application Code Hub The Application Code Hub (ACH) repository enables engineers to easily find microcontroller software examples, code snippets, application software packs and demos developed by NXP in-house experts. This space provides a quick, easy and consistent way to find microcontroller applications. Find more information at www.nxp.com/ach.   Installing Prerequisites - Launch MCUXpresso for VS Code - Launch the MCUXpresso Installer from the QUICKSTART PANEL   - Install MCUXpresso SDK Developer, LinkServer, and FreeMASTER   Heart Rate Monitor Lab The NXP Application Code Hub provides a complete example of how to use the MCXA-153 microcontroller in a Heart Rate and SPO2 monitor application. This lab will walk through the steps to import, build, program and debug the example. The final section of the lab shows how to use FreeMASTER as a data-visualization tool for the acquired sensor data on the FRDM-MCXA153 development board. 1. Go to the Quick Start Panel 2. Select Application Code Hub 3. Filter Visible Examples (MCX + Sensors) - Go to the filter section next to the Search bar and select two filters. - Select MCX in the Device Families Section and Sensor in the Categories section of the filters   4. Search for Keywords in Examples - Search for the keyword 'heart rate'. - Select the demo "frdm mcxa153 freemaster heart rate". 5. Read Overview of Heart Rate Demo The Application Code Hub provides a consistent Readme Overview for every project. The FreeMASTER Heart Rate demo overview is previewed after clicking on the application card. Scroll through the readme to become familiar with the available contents like required hardware, software and setup instructions. 6. Select Destination for Project The wizard automatically provides a prompt to browse to a desired destination folder. Create the destination C:\NXP_ACH to store the project here. Or you can specify a custom location. 7. Import Project into Workspace Select Import Project(s) after entering the desired location. If a valid project is not available, the wizard only displays Import Repository, to allow a code repo, without a project, to be added to workspace. 8. Select Detected Project(s) The import wizard will scan the example repo and list valid projects that were discovered. This allows the user to select only the projects they want created. Select the mcuxpresso project listed at the top of the VS Code window. 9. Associate a Toolchain The last selection is to identify the Compiler toolchain to be used for the project. GCC will be used for this project. Select Arm GNU Toolchain 12.3.Rel1 (Or latest version available from MCUXpresso Installer prework) The scan may locate Compilers associated with MCUXPresso IDE. Verify the path and version between listed compilers. At this time the wizard will complete the project import. A Successful Conversion notification is displayed at the bottom of the screen. It is important to recognize that the selected Heart Rate example is a working project within the MCUXpresso IDE (Eclipse based). The VS Code extension has the ability to convert an existing MCUXpresso IDE projects for development in VS Code. 10. Navigating a Project in VS Code The MCUXpresso for VS Code extension includes a PROJECTS section to help users access useful project information. Users can review and modify project information with the following steps. Review Project Details Project details are shown in the Dropdown menu of the Projects Section in the MCUXpresso Extension Navigation Pane. • Settings: Workspace settings specific to the project • MCU: Targeted device. • Build Configurations: Select build configuration from available list (i.e. Debug or Release). • Debug Configurations: • Repository Information • Project Files 11. Working with Source Files There are two ways to view and modify the project's files: • Click on the Explorer Icon at the top of the VS Code left navigation pane.  • Expand the Project Files section from the PROJECTS view 12. Build the application The MCXA153 FreeMASTER Heart Rate project needs to build the application image. After the code builds without any errors, the application can be run on the FRDM board. The following steps require that you return to the MCUXpresso perspective by clicking the MCUXpresso for VS Code X icon in the Activity bar Build the project by clicking the Build Selected icon. After a successful build, the Terminal console displays the memory usage (or compiler errors if any). 13. Connect Serial Monitor to the board To use the Serial Monitor integrated into VS Code: - Connect the USB-C cable to J15 to power the FRDM board. The onboard debugger provides a USBUART bridge to interface with the Serial monitor. - Click on the SERIAL MONITOR found as a tab in the Terminal window at the Bottom of VS Code Window. NOTE: The default COM settings are valid for NXP eval boards: "115200, None..." - Click Start Monitoring to connect the monitor to the FRDM board’s auto-detected COM port. VS Code in light theme 14. Flash/Debug the Application This section uses the on-board debugger to connect to the MCU, and program the flash. LinkServer from NXP manages the GDB server for communicating with the NXP MCULink on-board debug probe. It includes support for flash programming. - Click the play icon to Debug the application: The application is flashed to the FRDM board and VS Code switches to the Debug perspective. Return to the SERIAL MONITOR tab under the Terminals. It switches to the OUTPUT terminal when a Debug session is started.  VS Code in light theme - The execution will be paused on a breakpoint. Click Continue/Play icon to continue execution. The application will advance to the start of main().   - Click Continue/Play icon a 2nd time for the Heart Rate application to launch inside main(). 15. View Heart Rate Values in Serial Terminal The Heart Rate application using the serial port to display information. The following should be displayed in the SERIAL MONITOR tab after main() starts. Place a finger on the sensor near the Heart silkscreened on Heart Rate 4 click board. The following should be displayed in the SERIAL MONITOR tab after a finger is placed on the sensor: A heart rate value will be calculated and displayed after 16. FreeMASTER Data Visualization FreeMASTER is a standalone application provided by NXP to help developers visualize, monitor and manipulate data available from their projects. The Heart Rate example includes a /freemaster folder that helps users get started using the tool. The settings in the Application Code Hub were established for an MCUXpresso IDE based project. There are a few changes that need to be made after the project is converted to a VS Code project. The following steps will properly configure FreeMASTER to work with the Heart Rate example project: Launch FreeMASTER Application There are two options for launching FreeMASTER. • Click on the heart_rate.pmpx using File Explorer. The FreeMASTER application should be associated with .pmpx file extensions. This will also automatically load the included project settings.   • Launch FreeMASTER by searching Windows Applications. • This will not load project settings. You will be required to Open Project using the FreeMaster menu as shown. Open the .pmpx project file. • Verify Project Options FreeMASTER has a few key settings to verify once a project is opened. A user should verify they are correctly set for the type of Debug Probe and location of the project output files. - Click Project -> Options from the menu bar. - Verify that the correct method is set for communicating with the board. The on-board Debug Probe for the FRDM-MCXA153 is by default shipped with NXP CMSIS-DAP firmware. Select FreeMASTER CMSIS-DAP Communication Plug-in found under the Comm tab, for Plug-in module:   - Verify that the correct Default symbol file is targeted for the VS Code project. The symbol file in VS Code projects is output under an /armgcc folder. Select the /armgcc folder within VS Code project MAP Files tab. The window will autodetect the Binary ELF File, and display this under File format:   - Visualize Data From Heart Rate Project The NXP software team has included a default visualization for the Heart Rate project. The demonstration showcases the different styles for project data to be shown. The following visualization settings are preset for the Heart Rate project: Welcome HTML Page: The HTML Pages (Under Options) points to welcome.html file. This provides structured web view for displaying elements. Beyond scope of this lab, but .html file can be reviewed to see how target values/charts are referenced in html. Oscilloscope Visual: View plots the values of a project variable. The plot axis are configured for scale and color. Heart Rate, SPO2 and ECG are configured. Variable Watch Table: After variables are configured to be tracked, they can be added to this table view.   Make sure that the debug probe is not in an active debug session in the IDE or VS Code. Click GO icon on the menu bar to initiate the project data visualization! The following points are highlighted for the FreeMASTER output. 1. Clicking on the elements listed under the Project Tree changes the view to the specific Oscilloscope Visual. 2. View the captured values for the variables in a Table view. 3. Visualization of data organized based on the layout defined in the Welcome.html.  

This document is intended to guide you in the installation of the necessary tools and repository for start running matter examples and development. Matter (previously known as Project CHIP) is a single, unified, application-layer connectivity standard designed to enable developers to connect and build reliable, secure IoT ecosystems and increase compatibility among Smart Home and Building devices. Backed by major brands and developed through collaboration within the Connectivity Standards Alliance (previously known as the Zigbee Alliance), Matter is an open-source royalty-free connectivity standard built with market-proven technologies using Internet Protocol (IP) and compatible with Thread and Wi-Fi network transports. Building solutions and leading standards efforts, NXP provides scalable, flexible and secure platforms for the variety of use cases Matter addresses – from end nodes to gateways – so device manufacturers can focus on their product innovation. NXP’s Matter solutions go beyond just the connectivity with comprehensive capabilities for the compute and security requirements for IoT devices.

Goal of this lab is to show the SDK example implementing the Bluetooth LE Ranging profile, how to flash it and run it, as well as looking into the code to extract meaningful information for applications that use ranging Guide

This document is intended to guide you in the installation of the necessary tools and repository for start running Zephyr examples and development. Zephyr is a lightweight, open-source real-time operating system (RTOS) designed specifically for microcontrollers (MCUs) and other resource-constrained embedded devices. Unlike general-purpose operating systems, Zephyr is built to run on systems with limited memory, low power consumption, and strict real-time requirements. It provides the core software foundation that allows an MCU to run multiple tasks reliably, respond to events on time, and interact with hardware in a structured way.

Unlike MCXW 71 MCU, MCXW 72 supports an Open NBU. This means that NBU firmware source code is exposed to user. On MCXW 71 MCU, NBU firmware is NXP proprietary; it is not user customizable.

This hands-on describes how to run the Low Power Reference Design demo on FRDM-MCXW72. Two low-power reference design applications are provided in the reference_design folder: Low power peripheral application, demonstrating the low power feature on an advertiser peripheral Bluetooth LE device. Low power central application, demonstrating the low power feature on a scanner central Bluetooth LE device. These applications aim at providing: A reference design application for low power/timing optimization on a Bluetooth Low Energy application. These can be used in first intent for porting a new application on low power. A way for measuring the power consumption, wake-up time, and active time in various power modes. The default low-power mode used in different modes are shown as follows: Default power mode App core Radio core Advertise mode Power Down mode Deep sleep mode Connected mode Deep Sleep mode Deep Sleep mode Scanning mode Deep Sleep mode WFI or Deep Sleep mode For complete documentation please visit: reference_design — MCUXpresso SDK Documentation

Goal of this lab is to show the SDK example implementing the wireless UART profile and we will move forward in making some meaningful modifications to the example itself with the goal to show where in the code the end user should enter the relevant application software for the application. Run Wireless UART IoT Toolbox Demo

The MCX W72 family features a 96 MHz Arm® Cortex®-M33 core coupled with a multiprotocol radio subsystem also called Narrow Band Unit (NBU) supporting Matter, Thread, Zigbee and Bluetooth LE. The independent radio subsystem, with a dedicated core and memory, offloads the main CPU, preserving it for the primary application and allowing firmware updates to support future wireless standards. On MCXW72, only boot ROM has access to the NBU flash. The ROM bootloader provides an in-system programming (ISP) utility that operates over a serial connection on the microcontroller units (MCUs) The objective in this hands-on, is to learn how to recognize when the NBU firmware does not match with the SDK version.

The MCX W72 family features a 96 MHz Arm® Cortex®-M33 core coupled with a multiprotocol radio subsystem also called Narrow Band Unit (NBU) supporting Matter, Thread, Zigbee and Bluetooth LE. The independent radio subsystem, with a dedicated core and memory, offloads the main CPU, preserving it for the primary application and allowing firmware updates to support future wireless standards.   The ROM bootloader provides an in-system programming (ISP) utility that operates over a serial connection on the microcontroller units (MCUs)  This hands-on describes how to update the code in NBU and the User firmware using the ISP.  

In this lab we make some experience with the FRDM-MCXW72 board using the SDK project to implement a simple LED blinking. Once we will get familiar with the example project, we will integrate simple modifications

In this lab we will first import the MCUXpresso SDK for the MCX W72 Freedom board into MCUXpresso IDE and then we will build, flash and debug the hello world project to make sure the environment is set for the following Labs  

Introduction This document is intended to guide you in the installation of the tools and let you know the material required for the FRDM-MCXW72 Hands On.  Required Materials The material and the software requirements will depend on the hand on, but the next is what it is required in most of them. Hardware Requirements FRDM-MCXW72 Board Personal Computer Type C USB Cable Software Requirements IDE: Visual Studio Code 1.107.1 or later SDK: v25.12.00 MCUXpresso extension for VS Code version v25.12.48 BLHost Tool or LinkFlash tool (Linkflash is included with LinkServer installation) Windows OS (It was used Windows 11 for this hands-on) NXP IoT Toolbox (For an Android or iOS device) Serial Terminal program, like PuTTY or Tera Term Environment Setup Note: In order to make downloads in NXP website, it is necessary to have an account. Register and log-in for moving forward. MCUXpresso for Visual Studio Code                                                                                                                                                                         MCUXpresso for Visual Studio Code (VS Code) provides an optimized embedded developer experience for code editing and development. The extension enables NXP developers to use one of the most popular embedded editor tools and provides an easy and fast way to create, build and debug applications based on MCUXpresso SDK or Zephyr projects.   Install it following the next steps: Download Visual Studio Code from Microsoft Store or visual studio code web page Download Visual Studio Code - Mac, Linux, Windows Access to vscode for MCUX wiki and download MCUXpresso Installer  Dependency Installation · nxp-mcuxpresso/vscode-for-mcux Wiki · GitHub Run MCUXpresso Installer and for MCXW72 Hands On install at least MCUXpresso SDK Developer Matter Developer Arm GNU Toolchain Standalone Toolchain Add ons Linkserver PEmicro Installing the FRDM-MCXW72 SDK V25.12.00   Each MCU has its own SDK that includes driver, examples, middleware, docs and other components. To get and build the demo, let’s install the SDK into VS Code. Install the NXP’s GitHub SDK: Once MCUXpresso for Visual Studio Code is installed, open VS Code. Go to MCUXpresso for VS Code extension that is on the tools column at the left.    Look for INSTALLED REPOSITORIES option and press ‘+’ (Detail steps are described in wiki page. Working with MCUXpresso SDK · nxp-mcuxpresso/vscode-for-mcux Wiki · GitHub).                                               Search for the remote option of the Import Repository window. Select the MCUXpresso SDK in the repository option to download the GitHub SDK, then in the Revision tab you can select either the “main” revision (which corresponds to the latest version available) or to select an specific version (we’ll be using version v25.12.00 for these series of labs), optionally you can change the repository name and location.     Finally click on the “Import” button. Blhost Installation The blhost application is used on a host computer to issue commands to an NXP platform running an implementation of the MCU bootloader. The blhost application with the MCU bootloader, allows a user to program a firmware application onto the MCU device without a programming tool. Please go an download the tool in the next path and make sure to placed in a known location. BLHost Download page.