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

Whether you're a student, hobbyist, or professional developer, the FRDM Development Platform by NXP is your gateway to building powerful embedded applications—quickly and affordably. In this beginner-friendly guide, you’ll learn: What FRDM boards are and how they compare to other NXP evaluation kits Who the platform is designed for How to buy and get started with your first board What’s new in the latest FRDM series featuring MCX microcontrollers and i.MX processors How the FRDM ecosystem supports your development with modular hardware, software tools, and ready-to-use code examples

Customer may want to debug FRDM-IMX93 with the SWD interface of Jtag. This doc give an introduction about how to do that. Hardware: FRDM-IMX93,J-link. 1.Rework FRDM-IMX93 board and get the VREF(1.8V) from TP707 for SWD, show as the following picture.     2. Remove the  R3017 and R3018 in the following picture.     3.Connect FRDM-IMX93 and PC through J-link as the following pictures.     4.Switch the sw1 to 1001 to the serial download of the M33, then run the J-link commander.   The command is as following: J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect   The full log is as following: SEGGER J-Link Commander V8.10 (Compiled Sep 26 2024 08:38:41) DLL version V8.10, compiled Sep 26 2024 08:37:48 Connecting to J-Link via USB...O.K. Firmware: J-Link V10 compiled Jan 30 2023 11:28:07 Hardware version: V10.10 J-Link uptime (since boot): N/A (Not supported by this model) S/N: 600109556 License(s): RDI, FlashBP, FlashDL, JFlash, GDB VTref=1.800V Type "connect" to establish a target connection, '?' for help J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect Device "MIMX9352_M33" selected. Connecting to target via SWD ConfigTargetSettings() start ConfigTargetSettings() end - Took 12us InitTarget() start InitTarget() end - Took 2.53ms Found SW-DP with ID 0x5BA02477 DPIDR: 0x5BA02477 CoreSight SoC-400 or earlier AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[1]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: Core found AP[3]: AHB-AP ROM base: 0xE00FF000 CPUID register: 0x411FD210. Implementer code: 0x41 (ARM) Feature set: Mainline Cache: No cache Found Cortex-M33 r1p0, Little endian. Cortex-M (ARMv8-M and later): The connected J-Link (S/N 600109556) uses an old firmware module that does not handle I/D-cache correctly. Proper debugging functionality cannot be guaranteed if cache is enabled FPUnit: 8 code (BP) slots and 0 literal slots Security extension: implemented Secure debug: enabled CoreSight components: ROMTbl[0] @ E00FF000 [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33 [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI Memory zones: Zone: "Default" Description: Default access mode Cortex-M33 identified. J-Link>   5.You can also switch the sw1 to 0011 boot the A55 and stop at U-boot, then run the J-link commander The following is the command: J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect   The following is the full log: SEGGER J-Link Commander V8.10 (Compiled Sep 26 2024 08:38:41) DLL version V8.10, compiled Sep 26 2024 08:37:48 Connecting to J-Link via USB...O.K. Firmware: J-Link V10 compiled Jan 30 2023 11:28:07 Hardware version: V10.10 J-Link uptime (since boot): N/A (Not supported by this model) S/N: 600109556 License(s): RDI, FlashBP, FlashDL, JFlash, GDB VTref=1.806V Type "connect" to establish a target connection, '?' for help J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect Device "MIMX9352_M33" selected. Connecting to target via SWD ConfigTargetSettings() start ConfigTargetSettings() end - Took 27us InitTarget() start InitTarget() end - Took 3.89ms Found SW-DP with ID 0x5BA02477 DPIDR: 0x5BA02477 CoreSight SoC-400 or earlier AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[1]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: Core found AP[3]: AHB-AP ROM base: 0xE00FF000 CPUID register: 0x411FD210. Implementer code: 0x41 (ARM) Feature set: Mainline Cache: No cache Found Cortex-M33 r1p0, Little endian. Cortex-M (ARMv8-M and later): The connected J-Link (S/N 600109556) uses an old firmware module that does not handle I/D-cache correctly. Proper debugging functionality cannot be guaranteed if cache is enabled FPUnit: 8 code (BP) slots and 0 literal slots Security extension: implemented Secure debug: enabled CoreSight components: ROMTbl[0] @ E00FF000 [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33 [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI Memory zones: Zone: "Default" Description: Default access mode Cortex-M33 identified. J-Link>device MIMX9352_A55_0 Disconnecting from J-Link...O.K. Device "MIMX9352_A55_0" selected. Connecting to target via SWD ConfigTargetSettings() start ConfigTargetSettings() end - Took 19us Found SW-DP with ID 0x5BA02477 DPIDR: 0x5BA02477 CoreSight SoC-400 or earlier AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[1]: APB-AP (IDR: Not set, ADDR: 0x00000000) AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000) Using preconfigured AP[1] as APB-AP AP[1]: APB-AP found DebugRegs + CTI manually specified. ROM table scan skipped. Cortex-A55 @ 0x80810000 (configured) CoreCTI @ 0x80820000 (configured) Debug architecture: ARMv8.2 6 code breakpoints, 4 data breakpoints Processor features: EL0 support: AArch64 + AArch32 EL1 support: AArch64 + AArch32 EL2 support: AArch64 + AArch32 EL3 support: AArch64 + AArch32 FPU support: Single + Double + Conversion + single arithmetic ARMv8-A/R: The connected J-Link (S/N 600109556) uses an old firmware module V0 with known problems / limitations. Add. info (CPU temp. halted) Current exception level: EL2 Exception level AArch usage: EL0: AArch32 EL1: AArch32 EL2: AArch64 EL3: AArch64 Non-secure status: Non-secure Cache info: Inner cache boundary: none LoU Uniprocessor: 0 LoC: 0 LoU Inner Shareable: 0 VMSAv8-64: Supports 48-bit VAs Memory zones: Zone: "Default" Description: Default access mode Zone: "AP0" Description: MEM-AP (AHB-AP) Zone: "AP1" Description: MEM-AP (APB-AP) Zone: "AP3" Description: MEM-AP (AHB-AP) Cortex-A55 identified. Memory zones: Zone: "Default" Description: Default access mode Zone: "AP0" Description: MEM-AP (AHB-AP) Zone: "AP1" Description: MEM-AP (APB-AP) Zone: "AP3" Description: MEM-AP (AHB-AP) J-Link>  

In this lab, you will learn how to: Bring up Wi-Fi interfaces. Run basic Wi-Fi scan Configure and bring up Wi-Fi STA mode using WPA_SUPPLICANT. Configure and bring up UDHCP server for dynamic IP assignment for associated client devices. Run UDHCP client to get dynamic IP address. Configure and bring up Wi-Fi AP mode using hostapd. Connect STA to external AP Connect AP to external STA Start ping  Wi-Fi Basic Hands-on Demo Guide  Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

FRDM Training and Resources This article provide a guide of available resources for FRDM Development boards to help you to find and use available resources (Boards, Guides, Hands-On Trainings and more)

GoPoint   GoPoint is a user-friendly application that allows the user to launch preselected demonstrations included in the NXP provided BSP and follows the quarterly release roadmap for BSP How to launch GoPoint     GoPoint Demo On FRDM-IMX93 Board Since FRDM-IMX93 board’s BSP is based on standard BSP release, GoPoint is included in FRDM-IMX93 Yocto build by default. List of 9 demos available on FRDM-IMX93 Board: Image Classification Object Detection Selfie Segmenter i.MX Smart Fitness DMS (Driver Monitor System) ML Benchmark Video Test i.MX Smart Kitchen i.MX E-Bike VIT   Image Classification Demo Image classification is a ML task that attempts to comprehend an entire image as a whole. The goal is to classify the image by assigning it to a specific label. Typically, it refers to images in which only one object appears and is analyzed. This example is using NNStreamer.            Object Detection Demo Object detection is the ML task that detects instances of objects of a certain class within an image. A bounding box and a class label are found for each detected object. This example is using NNStreamer.        Selfie Segmenter Demo Selfie Segmenter showcases the ML capabilities of i.MX 93 by using the NPU to accelerate an instance segmentation model. This model lets you segment the portrait of a person and can be used to replace or modify the background of an image. This example is using NNStreamer.         i.MX Smart Fitness Demo i.MX Smart Fitness showcases the i.MX' Machine Learning capabilities by using an NPU to accelerate two Deep Learning vision-based models. Together, these models detect a person present in the scene and predict 33 3D-keypoints to generate a complete body landmark, known as pose estimation. From the pose estimation, the application tracks the 'squats' fitness exercise.          DMS (Driver Monitor System) Demo This application showcases the capability of implementing DMS on i.MX 93 platform, and the performance boost brought by Neural Processing Unit (NPU). DMS uses four ML models in total to achieve face detection, capturing face landmark and iris landmark, smoking detection and calling detection.         ML Benchmark Demo This example is based on benchmark_model tool in Tensorflow Lite framework, which allows to easily compare the performance of TensorFlow Lite models running on CPU (Cortex-A) and NPU.   Video Test Demo This is a simple demo that allows users to play back video captured on a camera or a test source. It’s based on gstreamer pipeline.            i.MX Smart Kitchen Demo i.MX Smart Kitchen showcases the Multimedia capabilities of i.MX to emulate an interactive kitchen through a GUI controlled by voice commands. The GUI is based on LVGL (Little Versatile Graphic Library) and NXP's Voice Intelligent Technology (VIT) supports the voice commands. Usage: Keyword + command       i.MX E-Bike VIT Demo i.MX E-Bike VIT showcases the Multimedia capabilities of i.MX to emulate an interactive ebike through a GUI controlled by voice commands. The GUI is based on LVGL (Little Versatile Graphic Library) and NXP's Voice Intelligent Technology (VIT) supports the voice commands. Usage: Keyword + command         Useful Link GoPoint User Guide: https://www.nxp.com/webapp/Download?colCode=GPNTUG GoPoint repo: https://github.com/nxp-imx-support/nxp-demo-experience-demos-list/tree/lf-6.6.36_2.1.0 (Including source code of demo: Selfie Segmenter, DMS, ML benchmark, Video test) Image Classification/Object Detection: https://github.com/nxp-imx/eiq-example/tree/lf-6.6.36_2.1.0 i.MX Smart Fitness: https://github.com/nxp-imx-support/imx-smart-fitness i.MX Smart Kitchen: https://github.com/nxp-imx-support/smart-kitchen i.MX E-Bike VIT: https://github.com/nxp-imx-support/imx-ebike-vit

FRDM-IMX93 Yocto Release - BSP  Based on i.MX SW 2024 Q3 release Linux kernel: 6.6.36_2.1.0 u-boot: 2024.04 Source: https://github.com/nxp-imx-support/meta-imx-frdm FRDM-IMX93 BSP changes: U-boot: Add basic support for FRDM-IMX93 Kernel: Add basic support for FRDM-IMX93 and add support for kinds of accessories GoPoint: Add FRDM-IMX93 support FRDM-IMX93 Yocto layer: Add Yocto layer for FRDM-IMX93 and integrate u-boot/kernel/GoPoint patches    FRDM-IMX93 accessories 7 inch Waveshare LCD: imx93-11x11-frdm-dsi.dtb 5 inch Tianma LCD: imx93-11x11-frdm-tianma-wvga-panel.dtb RPi-CAM-MIPI: imx93-11x11-frdm.dtb RPI-CAM-INTB: imx93-11x11-frdm-mt9m114.dtb MX93AUD-HAT or MX93AUD-HAT + 8MIC-RPI-MX8: imx93-11x11-frdm-aud-hat.dtb 8MIC-RPI-MX8: imx93-11x11-frdm-8mic.dtb   LCD Panel Vender Interface Size Resolution Support Touch Purchase Link dtb T050RDH03-HC Tianma 24 bit Parallel 5" 800 x 480 No Will launch with MX91 EVK in Dec'24 imx93-11x11-frdm-tianma-wvga-panel.dtb 7inch Capacitive Touch IPS Display for Raspberry Pi, with Protection Case, 1024×600, DSI Interface Waveshare MIPI DSI 7" 1024x600 Yes Click Here imx93-11x11-frdm-dsi.dtb Camera Vender Interface Size Resolution Sensor Purchase Link dtb RPI-CAM-MIPI onsemi MIPI CSI  1/4-inch 1M pixel, 1280H x 800V AR0144 Click Here imx93-11x11-frdm.dtb RPI-CAM-INTB 　 Parallel Camera 40pins 1/6-inch 1.26 Mpixel 1296H × 976V MT9M114 Will launch with MX91 EVK in Dec'24 imx93-11x11-frdm-mt9m114.dtb Audio Vender Interface Channel 　 　 Purchase Link dtb MX93AUD-HAT Cirrus 40pins 8 　 　 Click Here imx93-11x11-frdm-aud-hat.dtb 8MIC-RPI-MX8 NXP 40pins 8 　 　 Click Here imx93-11x11-frdm-8mic.dtb   FRDM-IMX93 Yocto Release Usage 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 FRDM-IMX93 layer into Yocto code base: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git Yocto Project Setup: $ MACHINE=imx93frdm DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-setup.sh -b frdm-imx93 Build images: $ bitbake imx-image-full Flashing SD card image: $ zstdcat imx-image-full-imx93frdm.rootfs.wic.zst | sudo dd of=/dev/sdb bs=1M && sync Using uuu to burn image and rootfs to SD: $ uuu -b sd_all imx-image-full-imx93frdm.rootfs.wic.zst   FRDM-IMX93 Yocto Release – Matter support Based on i.MX Matter 2024 Q3 Usage: −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 −Download i.MX Matter 2024 Q3; $ cd ${MY_YOCTO}/sources/meta-nxp-connectivity $ git remote update $ git checkout imx_matter_2024_q3 −Download FRDM-IMX93 Layer: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git −Yocto Project Setup: $ MACHINE=imx93frdm-iwxxx-matter DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-matter-setup.sh bld-xwayland-imx93 −Build images: $ bitbake imx-image-multimedia     FRDM-MX93 Debian Release Debian is a free Operating System (OS), also known as Debian GNU/Linux. i.MX Debian Linux SDK distribution is a combination of NXP-provided kernel and boot loaders with a Debian distro user-space image. −Debian 12 −NXP packages are based i.MX SW Release 2024 Q3 i.MX Debian Linux SDK distribution uses Flexbuild to build system. −Debian-based RootFS; Debian Base (basic packages) Debian Server (more packages without GUI Desktop) Debian Desktop (with GNOME GUI Desktop) −Linux kernel; −BSP components; −various  applications (graphics, multimedia, networking, connectivity, security, and AI/ML); Source: https://github.com/NXP/flexbuild Introduction:  https://nxp.com/nxpdebian  Quick Start with Debian Flexbuild compiles and assembles the distro images as three parts: BSP firmware image Boot image RootFS image Creating an SD card on the Linux host Download flex-installer −$ wget http://www.nxp.com/lgfiles/sdk/lsdk2406/flex-installer −$ chmod +x flex-installer; sudo mv flex-installer /usr/bin Plug the SD card into the Linux host and install the images as below: −$ flex-installer -i pf -d /dev/sdb (format SD card) −$ flex-installer -i auto -d /dev/mmcblk1 -m imx93frdm (automatically download and install images) Plug the SD card into the i.MX board and install the extra packages as follows: −$ dhclient -i end0 (setup Ethernet network interface by DHCP or setting it manually) −$ date -s "22 Nov 2024 09:00:00" (setting correct system time is required) −$ debian-post-install-pkg desktop (install extra packages for GNOME GUI Desktop version) −or −$ debian-post-install-pkg server (install extra packages for Server version without GUI Desktop) −# After finishing the installation, run the reboot command to boot up the Debian Desktop/Server system.   Building Debian Images with Flexbuild Run the following commands for the first time to set up the build environment: −$ git clone https://github.com/nxp/flexbuild −$ cd flexbuild && . setup.env −#Continue to run commands below in case  you need to  build in Docker due to lack of Ubuntu 22.04 or Debian 12 host −$ bld docker (create or attach a docker container) −$ . setup.env   Flexbuild usage: −$ bld -m imx93frdm (build all images for imx93frdm) −$ bld uboot -m imx93frdm (compile u-boot image for imx93frdm) −$ bld linux (compile linux kernel for all arm64 i.MX machines) −$ bld bsp -m imx93frdm (generate BSP firmware) −$ bld boot (generate boot partition tarball including kernel, dtb, modules, distro bootscript for iMX machines) −$ bld multimedia (build multimedia components for i.MX platforms) −$ bld rfs -r debian:base (generate Debian base rootfs with base packages) −$ bld apps -r debian:server (compile apps against runtime dependencies of Debian server RootFS) −$ bld merge-apps -r debian:server (merge iMX-specific apps into target Debian server RootFS) −$ bld packrfs (pack and compress target rootfs)   Related Documentation   FRDM-IMX93 Documents: FRDM-IMX93 Quick Start Guide FRDM-IMX93 Board User Manual FRDM-IMX93 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 Debian documents at http://www.nxp.com/nxpdebian i.MX Debian Linux SDK User Guide

  The RW61x is a highly integrated, low-power tri-radio wireless MCU with an integrated MCU and Wi-Fi ®  6 + Bluetooth ®  Low Energy (LE) 5.4 / 802.15.4 radios designed for a broad array of applications, including connected smart home devices, enterprise and industrial automation, smart accessories and smart energy. The RW612 MCU subsystem includes a 260 MHz Arm ®  Cortex ® -M33 core with Trustzone ™ -M, 1.2 MB on-chip SRAM and a high-bandwidth Quad SPI interface with an on-the-fly decryption engine for securely accessing off-chip XIP flash. The RW612 includes a full-featured 1x1 dual-band (2.4 GHz/5 GHz) 20 MHz Wi-Fi 6 (802.11ax) subsystem bringing higher throughput, better network efficiency, lower latency and improved range over previous generation Wi-Fi standards. The Bluetooth LE radio supports 2 Mbit/s high-speed data rate, long range and extended advertising. The on-chip 802.15.4 radio can support the latest Thread mesh networking protocol. In addition, the RW612 can support Matter over Wi-Fi or Matter over Thread offering a common, interoperable application layer across ecosystems and products. Hands-On Trainings Introduction to RW61x and FRDM-RW612 Quick introduction to RW61x family, module offering and FRDM-RW612 evaluation board FRDM-RW612 Out of the Box Experience Wi-Fi CLI (Command Line Interface) demo provides the user with a menu with different commands to explore the Wi-Fi capabilities of the FRDM RW612 board. When the board is powered on for the first time, the green RGB LED should be blinking indicating that the demo is loaded into the board. FRDM-RW612 Getting Started. Wi-Fi CLI on VS Code This lab guides you step by step on how to get started with FRD-RW612 board using Visual Studio Code  FRDM-RW612 BLE Sensors over Zephyr This demo shows the temperature from the i2c temperature sensor integrated in the board. This demo is based on Zephyr RTOS. The information can be monitored in the UART terminal or in the IoT Toolbox app. FRDM-RW612 Kitchen Timer using Low-cost LCD This lab shows how to modify a Kitchen Timer graphical application using LCD-PAR-S035 display Changing the date and button colors. The timer can also be viewed on a serial terminal.   Community Support If you have questions regarding this training or RW61x series, please leave your comments in our Wireless MCU Community! here 

Getting Started Video:   This guide provides step-by-step instructions on how to verify successful communication with the Ara240 module and the runtime software environment to interface  with the FRDM i.MX 95 development board.   Out of the Box   Get Familiar with the Ara240 Module   Ara240 Module [Top view] Ara240 Module [Back view]                Connecting the M.2 Module   This section explains how to connect Ara240, a discrete module, to the FRDM i.MX 95 development board. The instructions in the FRDM i.MX 95 Quick Start Guide will walk you through the boot-up process for the pre-loaded Embedded Linux image on the board and how to connect the USB debug cable. For additional details, see the official FRDM i.MX 95 Development Board documentation. References: FRDM i.MX 95 Quick Start Guide FRDM i.MX 95 Development Board product page FRDM i.MX 95 getting started page Getting Started with ARA2-M2-16G-GT Follow the steps below to connect the Ara240 module to the FRDM i.MX 95 development board: Important: Ensure the board is powered off before making any connections. Insert the Ara240 module into the M.2 Key-M socket on the FRDM i.MX 95 development board. Using the screw provided, secure the module. Connect the fan cable to the board’s fan header (refer to the FRDM i.MX 95 board documentation for the exact header location). Connect the Ara240 to the FRDM i.MX 95 development board.     Power on the Board   Follow the instructions to power on (boot) the board found in the Getting Started with FRDM-IMX95. After powering on, verify that the fan and green LED indicators Ara240 module are on are on.   Get the Software   This section will walk you through the Ara240 Runtime software development kit (SDK), a streamlined subset of the Ara240 SDK designed for rapid enablement and execution on NXP platforms. The Runtime SDK simplifies installation and configuration, enabling developers to quickly deploy and run AI/ML workloads on the Ara240 module with minimal effort. Overview   Refer to Ara240 software release notes for details on the Ara240 software development kit (SDK) The Getting Started page for Ara240 only outlines usage on specific i.MX development platforms For any other platforms please reach out to your NXP representative for guidance.   Module Enumeration and Software Configuration   This section provides instructions to verify proper installation of Ara240 module and configuration of the Ara240 Runtime SDK on the FRDM i.MX 95 development board. Verify Device Detection   Once the board has successfully booted, connect to the serial debug port to monitor system logs. To confirm that the Ara240 module is being detected by the board, run the following command: $ lspci | grep 1e58   Expected output: 0000:01:00.0 Processing accelerators: Device 1e58:0002 (rev 02)   Enable Ara240 device   For quick enablement, the Ara240 Runtime SDK starts at boot time. Refer to the Ara240 Runtime SDK documentation for detailed instructions and environment setup steps.   Developer Experience   This section provides an overview of Ara240 runtime software enablement using the FRDM i.MX 95 development board. Verify Setup Environment   Use the following guidance on how to connect required devices. For most of the demos, you would need a camera, keyboard, mouse, internet connection and a HDMI display monitor. Setup preparation for FRDM i.MX 95 board [Top view]   Setup preparation for FRDM i.MX 95 board [Back view]   NOTE: You might need to use a USB hub to connect keyboard, mouse and camera at the same time.   Runtime setup Description:   Runtime SDK delivers a complete runtime environment that enables AI/ML acceleration on the Ara240 module. To run demo applications, ensure that the Ara240 bring-up process has been successfully completed and the system is ready for demo evaluation. Refer to the Runtime SDK documentation for detailed guidance on: Verifying correct installation of the Runtime SDK. Checking and updating the Ara240 firmware version. Validating proxy service bring-up status. Executing benchmark tests on Ara240. Following these steps ensures that the module is properly initialized and ready for use. Ara240 supports the execution of CNNs, LLMs, VLMs, and agentic frameworks, enabling advanced AI workloads to run directly on Ara. For comprehensive examples and end-to-end workflow guidance, please refer to the Ara SDK documentation page.

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 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.

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 tools and let you know the material required for the FRDM-MCXW72 Channel Sounding Hands On 

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  

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.