In order to recover your board, you need to accomplish the following: Ensure that your PC successfully enumerates the LinkServer debugger under the COM ports. Confirm that you can attach to the running code on the board. When attempting to program the board, the following error appears: image (6).png   The device stops during initialization because the value of SIM_CHIPCTL is not set to its default after reset. This happens because SRAMU and SRAML are retained across resets, which causes a flash initialization error. To resolve this issue, modify the debug script to override the SIM_CHIPCTL register with its default value: 0x0030_0000. Locate the file MCXE24x_connect.scp. If you are using the default installation path, it should be located at: C:\NXP\LinkServer_YourVersion\binaries\Scripts   Open the file and add the line "Poke32 this 0x40048004 0x00300000" I recommend do it after the "Release NRESET" message.     carlos_o_2-1761067984849.png Note: You need to add a number to each line of code    After making this change, you should be able to program your MCX E24x board as usual.

1. Introduction During recent customer technical support, we have find that power supply design issues frequently occur when using MCXN94X/MCXN54X products with HLQFP 100-pin packaging. To address this, we have developed this design guide specifically for 100-pin packaged chips, based on the power supply design diagrams provided in the MCX Nx4x Power Management User Guide (UG10101). Description of Package Types The MCXNx4x series currently includes three package types: VFBGA 184-pin HDQFP 172-pin HLQFP 100-pin The power supply design solutions in the User Guide(UG10101) primarily target the 172-pin and 184-pin packages. 2. Special Design Requirements for HLQFP 100-Pin Packages 2.1 Power Supply Design Solution for HLQFP 100-Pin Packages (LDO_CORE Mode) When using a 100-pin MCXNx4x chip and selecting the LDO_CORE mode (with DCDC_CORE disabled), the power supply design shall comply with the following specifications: Alice_Yang_0-1756959564497.png Key Design Differences 1)Shared Power Pin Characteristics In the 100-pin package, VDD_DCDC and VDD_LDO_SYS share the same pin. When DCDC_CORE is turned off, DCDC_LX must be left floating, and the DCDC function must be disabled through software configuration. 2) Port Power Supply Design The power supply pin Vdd_p2 for PORT2 shares a single pin with VDD. The 100-pin packaged chip cannot provide independent power supply to PORT2; instead, it must be uniformly powered by VDD, consistent with the power supply configuration for PORT0/PORT1. 2.2 Power Supply Design Solution for 100-Pin Packages (DCDC_CORE Mode) If the DCDC_CORE mode is used (with LDO_CORE turned off), the 100-pin chip can directly refer to the MCX Nx4x Power Management User Guide (UG10101). However, special attention must be paid to the following: PORT2 still cannot be supplied with independent power and must adhere to the port power supply design requirements specified above. 3.Technical Support If you have any issues during the power supply design of MCXNx4x series chips, please feel free to leave a message for communication at any time.   Thanks for Yang Zhang's help with the review.  

Clone an Example Project Using MCUXpresso Config Tool    The following steps will guide you through the manipulation of the general-purpose outputs. The example sets up a SCTimer to generate a PWM signal and change a LED brightness. Open the MCUXpresso Config Tool In the wizard that comes up, select the “Create a new configuration based on an SDK example or hello word project” radio button and click on Next Sabina_Bruce_0-1767119880873.png On the next screen, select the location of the MCUXpresso SDK . The SDK package must be unzipped beforehand. Then select the IDE that is being used. Note that only IDEs that were selected in the online SDK builder when the SDK was built will be available and click on clone select example. Then select the project to clone. For this example, we want to use the gpio led output project. You can filter for this by typing “ctimer” in the filter box and then selecting the  “ctimer_match_interrupt_example”  example project. You can then also specify where to clone the project and the name. Then click on Finish Sabina_Bruce_1-1767119904068.png After cloning go to the directory you selected and open the project for your IDE. Import, compile, and run the project as done in previous sections You should see the BLUE and RED LED changing back and forth Terminate the debug session Use MCUXpresso IDE Pins Tools to Modify Example   Note: Previously, you had to clone an SDK project like in the previous step. Open the pins tool by selecting “ConfigTools” on the top right hand of the file explorer window and then select “ Open Pins” Sabina_Bruce_2-1767120013932.png   The pins tool should now display the pin configuration for the ctimer project Sabina_Bruce_4-1767120027738.png   In the Pins view deselect “Show dedicated pins” and “Show no routed pins” checkboxes to see only the routed pins. Routed pins have a check in a green box next to the pin name. The functions selected for each routed pin are highlighted in green Sabina_Bruce_5-1767120078772.png In the current configuration, PIO3_2 and PIO3_3 are routed as the outputs of the CTimer. Let’s add a third Ctimer Match output and enable the Green LED Select “Show no routed pins” to see the other options. To enable the third Ctimer Match Output, browse the column for Ctimer and select and output. In this example, we will select, Ctimer4 Match 2 on PIO3_6. Select the item in the Ctimer column to enable Sabina_Bruce_6-1767120106023.png Now, let’s route the Green LED. In the search box type “green” so that the routed pin for this LED is shown. Finally, click the box under the GPIO column. The box will highlight in green, and a check will appear next to the pin Sabina_Bruce_7-1767120126540.png Next configure the GPIO pin as an output in the “Routing Details” window Sabina_Bruce_8-1767120146570.png Now it’s time to implement these changes into the project by exporting the new updated pin_mux.c and pin_mux.h files that are generated by the Pins tool. Click on Update Project in the menu bar Sabina_Bruce_9-1767120171233.png The screen that pops up will show the files that are changing and you can click on “diff” to see the difference between the current file and the new file generated by the Pins tool. Click on “OK” to overwrite the new files into your project Sabina_Bruce_10-1767120200258.png Let’s add some additional code to the example. Open  simple_match_interrupt.c  file and add the following macros for the third ctimer output. Sabina_Bruce_11-1767120247499.png Add the Green LED functions as well. Sabina_Bruce_12-1767120256133.png Some additional code to be implemented will be the third ctimer’s callback, this can be copied from  ctimer_match1_callback  and modify the content to match2. To be able to visually identify the new ctimer, we will remove one of the previous ctimers as shown Sabina_Bruce_13-1767120270163.png   The main function will need to include the initialization of both the Green LED and the Ctimer Sabina_Bruce_14-1767120284285.png Build and download the project as done in the previous section Run the application. You should now see the Green and Blue LED blinking back and forth Terminate the debug session  

The attached lab will describe how to add eIQ Time Series Studio generated libraries to an existing NXP embedded application.   It describes how to add the TSS library files to your application and configure the project settings in VS Code, MCUXpresso IDE, IAR, and Keil. It also covers how to call the TSS API from existing user code so that you can quickly and easily add time series ML analysis to  your embedded application.  For details on how to create a time series model with eIQ Time Series Studio, see the Getting Started with TSS Lab.

eIQ Time Series Studio includes a command line interface (CLI) that allows you to generate time series models via the command line just like you would in the GUI. Full documentation of this feature can be found in the eIQ TSS documentation. A Quick Start with the basic key commands is also available.  Below is an example using the command line interface with eIQ Time Series Studio: #Assumes the following items: #1) tss_cli is in the executable path (C:\Program Files\NXP\eIQ_TimeSeriesStudio-1.5.5) #2) The dataset is in C:\tss\dataset #3) A workspace will be setup in C:\tss\workspace #4) The license key has already been retrieved from the TSS GUI #5) The TSS GUI is not also concurrently running #Install license Key tss_cli.exe license activate --key <your_key> #Start TSS CLI tss_cli engine launch -e "C:\Program Files\NXP\eIQ_TimeSeriesStudio-2.0.5\tss_engine\tss_engine.exe" --port 18000 --workspace "C:\tss\workspace" #Install license key tss_cli license activate --key <your_key> #Create a classification project for a FRDM-MCXN947 tss_cli project create --project_name cli_fan_project --algo_type cls --device FRDM-MCXN947 --channels 3 --label_target_num 4 #List all projects in the workspace and see details for the newly generated cli_fan_project tss_cli project list tss_cli project query --project_name cli_fan_project #Add training data tss_cli signal list --project_name cli_fan_project tss_cli signal import --project_name cli_fan_project --signal_name ON --file_path C:\tss\data\fan_state_monitoring_3channel\train\train_on.csv --label_id 1 --delimiter " " tss_cli signal import --project_name cli_fan_project --signal_name OFF --file_path C:\tss\data\fan_state_monitoring_3channel\train\train_off.csv --label_id 2 --delimiter " " tss_cli signal import --project_name cli_fan_project --signal_name FRICTION --file_path C:\tss\data\fan_state_monitoring_3channel\train\train_friction.csv --label_id 3 --delimiter " " tss_cli signal import --project_name cli_fan_project --signal_name CLOG --file_path C:\tss\data\fan_state_monitoring_3channel\train\train_clog.csv --label_id 4 --delimiter " " #Check training data tss_cli signal query --project_name cli_fan_project --signal_id 1 #Start training the model. It will print out an opt_ID number, which the first time you run it will be "1". tss_cli optimization start --project_name cli_fan_project -qs --opt_name cli_fan_opt --signals 1 2 3 4 #Get opt_id number while training is running tss_cli optimization list --project_name cli_fan_project #Check how far along the training is and get ranking of models to choose a result_ids tss_cli optimization progress --project_name cli_fan_project --opt_id 1   cli_list.jpg #Can stop the training if feel like have enough results tss_cli optimization stop --project_name cli_fan_project --opt_id 1 #Get the result_ids of the best result. It will also be the top ID when checking the progress above. In this case will use 48 tss_cli optimization results --project_name cli_fan_project --opt_id 1 result_list.png #Get Execution Time estimate for that model tss_cli library time_estimate --project_name cli_fan_project --opt_id 1 --result_id 48   #Get Label Names tss_cli signal list --project_name cli_fan_project label_names.png   #Emulate the library on test data tss_cli emulation launch --project_name cli_fan_project --opt_id 1 --result_ids 48 --test_file_info "1" C:\tss\data\fan_state_monitoring_3channel\test\test_on.csv " " --test_file_info "2" C:\tss\data\fan_state_monitoring_3channel\test\test_off.csv " " --test_file_info "3" C:\tss\data\fan_state_monitoring_3channel\test\test_friction.csv " " --test_file_info "4" C:\tss\data\fan_state_monitoring_3channel\test\test_clog.csv " " #Create a TSS library tss_cli library compile --project_name cli_fan_project --opt_id 1 --result_id 48 --save_path "C:\tss\" --arch "cortex-m33" --toolchain "GCC" #Create a TSS example project tss_cli library sample_project --project_name cli_fan_project --opt_id 1 --result_id 48 --save_path "C:\tss" --arch "cortex-m33" --toolchain "GCC" Here's also some tips and common issues to be aware of:  Windows Workspace Permissions On Windows PCs, specify the workspace location when launching the TSS CLI server. The default workspace on Windows may not work properly due to a permissions issue, resulting in the following error: [PYI-12556:ERROR] Failed to execute script 'server' due to unhandled exception!   Workaround: Specify a workspace directory location where TSS has read/write access with the tss_cli engine launch --workspace <directory_location> argument   Do Not Run CLI and GUI Simultaneously The TSS CLI and TSS GUI should not be run at the same time. Also only one user should interact with the TSS CLI at a time to avoid race conditions in the TSS database if it is on a shared server.    Engine Launch Syntax Correction The TSS CLI documentation uses tss_cli engine launch –engine <path to tss_engine>, but the correct syntax is: tss_cli engine –exe_path <path to tss_engine>   Windows Command Prompt Delimiters When using Windows Command Prompt and importing sensor data with the signal import command, use double quotes (" ") to specify the delimiters (ie a space in this case) instead of the single quotes ('  ')    Terminology Clarification "Optimization" in the documentation refers to the process of training the time series model.   Finding the Optimization ID during training The my-opt-id value can be found by viewing the optimization list with tss_cli optimization list --project_name cli_test_project   Finding the Label Name The label-name value used for emulation commands can be found by viewing the name of the signals with tss_cli signal list --project_name cli_test_project   Boolean Arguments Arguments such as quick search during training are Boolean values, which are automatically enabled when included as part of the command line argument. For example, use -qs rather than -qs true.

Picture1.png Welcome to MCX C15 and MCX C16 Product Training! This page provides access to training materials, presentations, demos, recordings, and supporting resources related to the MCX C15 and MCX C16 MCU family. While live Q&A support will be available during the training period, all content will remain accessible for future reference and self-paced learning.  Instructions  To get started with the MCX C15/C16 training, you will need to have your FRDM-MCXC162 in hand and perform the set-up operations according to the FRDM-MCXC162 Getting Started Page which is a pre-requisite.   Step 1. Mandatory pre-work before starting with the labs:  Getting Started with FRDM-MCXC162 Step 2. After completing the pre-work, download the lab guides. Each lab has its own guide document and a video guide you can use as support material in case you have any question at any step:  Lab0: Introduction to MCX C15/C16 and FRDM-MCXC162 Lab1: Low Power is a Superpower Objectives Download and run your first project from VS Code on the FRDM-MCXC16 Explore the basics of low-power modes Description Load the SDK low-power example, walk through the code flow, and review the available wake-up options. You'll also learn how to connect a current meter to the FRDM board to measure power consumption. Lab2: Low-Power Sensing Demo Objectives Download and run your first ACH example from VS Code on the FRDM-MCXC16 Explore a low-power sensing application Description Access and download examples directly from ACH in VS Code, then run a real-world low-power sensor use case. Lab3: PWM Lighting Demo Objectives Learn how to load firmware using LinkServer/LinkFlash and simple production-style scripts Explore the timer and PWM capabilities of the MCXC family Description Use a provided binary and step-by-step instructions to program the board. The demo controls the onboard RGB LED using PWM. Source code will also be available in ACH. Lab4: Connecting Expansion Boards to FRDM-MCXC162 Objectives Download an ACH example from VS Code Connect and use expansion boards with the FRDM-MCXC16 Description Connect an expansion board, download the example from ACH, and try a low-power sensing application using an external sensor. Additional requirements as below:  MikroE OLED B/W Click display in I2C mode SparkFun Qwiic dToF Imager (TMF8820) Qwiic board cable Step 3. Review the support material and useful links to get you up to speed with some product information, FRDM board information and Getting started. Below also includes additional reading material.   MCX C15/C16 Product Page  FRDM-MCXC162 Tool Summary Page  FRDM-MCXC162 Getting Started Page  MCX C1 Family Factsheet  MCX C15/C16 Datasheet   MCX C15/C16 Reference Manual  Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here 

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: MCUXpresso SDK Developer Arm GNU Toolchain Standalone Toolchain Add ons Linkserver PEmicro neidys_vargas_0-1782232556890.png   Installing the FRDM-MCX SDK  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. neidys_vargas_1-1782232711167.png 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).                                               neidys_vargas_2-1782232751534.png Search for the remote option of the Import Repository window. neidys_vargas_3-1782232782659.png 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 or to select a specific version), optionally you can change the repository name and location. neidys_vargas_4-1782232886818.png Finally click on the “Import” button.

This document introduces how to configure and use the hardware trigger feature of the Analog-to-Digital Converter (ADC) on the FRDM-MCXA156 development board. It presents an event where using an external button initiates a reading and ADC conversion that reads an analog input from a potentiometer; the resulting digital value is then used to dynamically update the duty cycle of a PWM signal connected to an external output represented by a LED. This example demonstrates the usage of external connections and analog measurement by walking through the modifications required to enable hardware triggering via the Input Multiplexing (INPUTMUX) module.

MCX N series of highly integrated Arm Cortex-M33 microcontrollers are designed for high performance and low power consumption. MCX N includes intelligent peripherals and on-chip accelerators providing multitasking capabilities and performance efficiency. Select MCX N families include NXP's eIQ® Neutron neural processing unit (NPU) for machine learning applications. The low-power cache enhances system performance, while the dual-bank flash and full ECC RAM support system safety and offer an extra layer of protection and advanced security. These secure MCUs include our EdgeLock® Secure Enclave, Core Profile offering a secure-by-design approach, secure boot with an immutable root-of-trust and hardware-accelerated cryptography. Documents: MCX N Series  MCX N Fact Sheet MCX N Series Hardware Design Guide MCX Nx4x TSI QSG UG10101 MCX Nx4x Power Management User Guide Migration Guide Froom LPC55xx to MCX Nx4x MCX N Series Products: MCX N94/N54/N53/N52/N24:  The MCX N94, N54, N53, N52 and N24 include up to two are based on dual high-performance Arm® Cortex®-M33 cores running up to 150 MHz, with 2 MB of Flash with optional full ECC RAM, a DSP co-processor and an integrated eIQ Neutron NPU. The NPU delivers up to 42x faster machine learning throughput compared to a CPU core alone enabling it to spend less time awake and reducing overall power consumption. The multicore design delivers improved system performance and reduces consumption by enabling smart, efficient distribution of workloads to the analog and digital peripherals.  Documents: Data Sheet MCX N947/946/547/546/536/527/526/247 MCXN_1P02G Errata MCXNx4x_0P02G Errata Reference Manual  Secure Reference Manual  AFCI 8HC Demo QSG Omdia Market Radar: AI Processors for the Edge 2024 MCX N94x MCUs: Bringing more intelligence to the Edge  MCX N23: The MCX N23x is based on a high-performance Arm® Cortex®-M33 running up to 150 MHz, with 1 MB of Flash, 352 kB ECC RAM and SmartDMA. The MCX N23x is optimized for cost, memory and system performance and offers a single core option with efficient distribution of workloads to the analog and digital peripherals. The EdgeLock Secure Enclave on the MCX N23x is a self-contained, on-die hardware security subsystem that has its own dedicated security core, internal ROM, secure RAM and it supports state-of-the-art side-channel attack-resilient symmetric and asymmetric crypto accelerators and hashing functions for security services. Documents: MCX N23x Data Sheet MCXN23x_0P21K Errata Reference Manual Security Reference Manual MCX N23 HLQFP100 Hardware Design Guide Boards: FRDM-MCXN947: FRDM-MCXN947 are compact and scalable development boards for rapid prototyping of MCX N94 and N54 MCUs. They offer industry standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces, external flash memory and an on-board MCU-Link debugger. Documents: FRDM-MCXN947 QSG MCUXpresso SDK Field-Oriented Control of 3-Phase PMSM and BLDC Motors -FRDM-MCXN947 FRDM-MCXN947 Getting Started FRDM-MCXN947 Board User Manual  FRDM-MCXN236FRDM-MCXN236 is a compact and scalable development board for rapid prototyping of MCX N23x MCU. It offers industry-standard headers for easy access to the MCU's I/Os, integrated open-standard serial interfaces, external flash memory and an onboard MCU-Link debugger Documents: FRDM-MCXN236 Development Board QSG Getting Started with FRDM-MCXN236 FRDM-MCXN236 Board User Manual  MCX-N9XX-EVK is a full featured evaluation kit for prototyping of MCX N94 / N54 MCUs. They offer industry standard headers for access to the MCU’s I/Os, integrated open-standard serial interfaces and an on-board MCU-Link debugger with power measurement capability. Documents: Getting Started with MCX-N9XX-EVK MCX-N9XX-EVK Board User Manual MCX N to FRDM Board Mapping: Supported MCU(s) Recommended Board Best fit for  Key Differentiators MCX N94 / N54 / N53 / N52 / N24 FRDM-MCXN947 Rapid prototyping across the MCX N portfolio Arduino-compatible headers, MCU-Link debugger, Ethernet PHY, CAN-FD, camera and LCD expansion support. MCX N94x / N54x MCX-N9XX-EVK Full-featured evaluation, performance benchmarking, advanced prototyping Energy monitoring, external memory support, Ethernet, CAN, PMIC, M.2 expansion, MCU-Link debugger. MCXN236 FRDM-MCXN236 Ultra-low-power IoT devices, battery-powered sensors, edge nodes Arm Cortex-M33 MCU, low-power architecture, integrated analog peripherals, optimized for connected sensing applications.   Applications Notes: Software, hardware and Peripherals AN15071 Implementation of Optical module CMIS protocol over I3C on the MCX N94: This application note introduces how to implement the CMIS protocol demo on an MCX N947 microcontroller using the I3C interface. AN15072 Implementation of an I3C Secondary Bootloader on MCX N947: The I3C interface is widely used in many scenarios, such as data center, PCs, and optical modules. As a result, I3C-based secondary bootloader for firmware updates have become a common requirement. AN14407 DICE Attestation for MCX N Series Devices: This application note explains and provides a demo on how to implement DICE on MCX N series devices. In this implementation, DICE uses the UDS of the device, its hardware state, firmware, and RTF to create a unique identity that gets registered on an offline database system. This offline database system is later used to verify the genuineness of the device. AN14320 Ease ISA/IEC 62443-4-2 Compliance with MCX N Series: This document is addressed to OEMs interested in understanding how the MCX N can be used to facilitate the implementation of ISA/IEC 62443-4-2 requirements. AN14166 MCX N Over-The-Air (OTA) Update by Using SB3 file: This document describes a method to secure OTA via SB3 files. For demonstration purposes, this documentation uses the EVK and onboard Ethernet. AN15087 Implementing Three I2C Target Interfaces Using SmartDMA on the MNC N947: This demo implements three virtual I2C target ports on MCX N947 using SmartDMA-assisted GPIO-style signaling, without dedicating three hardware LPI2C target peripherals AN14900 Using eDMA and Ping-Pong Buffer ti deserialize Multi-Channel ADC Result FIFO:  This application note describes how to use eDMA to tackle the Analog-to-Digital Converter (ADC) result First-In First-Out (FIFO) and deserialize each channel data in FIFO to respective buffer for each channel. It is useful for high-speed and multi-channel ADC result process by reducing CPU loading and improving data processing speed. AN14807 Accelerate FFT Computation with PowerQuad: In high-performance signal processing applications, the Fast Fourier Transform (FFT) plays a critical role. To enhance efficiency, the LPC55 Series and MCX N Series microcontrollers integrate a hardware accelerator called PowerQuad. This application note presents an approach to accelerate FFT computation using PowerQuad while addressing its limitation of a maximum FFT length of 512 points AN14175 Using FlexIO to emulate Quad SPI controller: Quad SPI serves as a common interface for flash memory, Wi-Fi modules, and LCD displays. However, some microcontrollers do not support the Quad SPI interface. In such cases, FlexIO offers a versatile alternative. AN14712 Advanced PowerQuad Operation Guide: This application note provides some information, code snippets, and tips to help users accelerate their calculations with MAU. The MCX N Series microcontrollers feature a powerful and efficient coprocessor called PowerQuad. It operates in parallel with the CPUs to offload intensive mathematical computations and enhance overall performance. AN14650 SmartDMA Cookbook: This application note primarily introduces the internal architecture, main functions, and features of EZH or SmartDMA, and finally lists the usage and meanings of the main instructions AN14520 General MCU PWM DAC Application: This application note introduces how to set the low-cost Digital-to-Analog Converter (DAC) using the PWM output. The main application is household electrical and industry appliances, which need a low cost and accurate DAC without a high-bandwidth requirement.  AN14567 How to implement USB microphone on MCX Series MCUs: This documentation describes how to implement a USB microphone on MCX Series MCUs. The data source could be an external digital microphone or generated data. A USB Audio Class 1.0 (UAC 1.0) and USB Audio Class 2.0 (UAC 2.0) microphone is used in this document. AN14553 Building a GPS Speedometer using GUI Guider and FREM-MCXN947: This application note provides examples to build a GPS-based speedometer with FRDM-MCXN947, LVGL, GUI Guider tool, and a GPS module. The document describes how to deploy LVGL on the MCX Nx4x platform with GUI Guider and SDK. AN14470 How to Use FlexIO State Mode to Generate Center-Aligned PWM: This application note describes how to use the FlexIO state mode to generate a center-aligned PWM waveform on the MCXN series MCUs. AN14259 SDK Example to Write CMPA and CFPA with monotonic Counter dor MCXN947: This document provides an example of changing the Customer Field Programmable Area (CFPA) bit field using the ROM APIs.  AN14532 Migration from Kinetis K Series to MCXNx4x Series: This application note is about migrating Kinetis K series to MCXN94x/N54x series and lists the differences between both the series. AN14543 Connect Barcide Scanner with MCX N Series USB Host port: This application note describes how to build a USB host port connected with a USB barcode scanner using the FRDM-MCXN947 board for demonstration. NXP’s MCX N series devices feature a high-speed (HS) USB port capable of reaching transmission speeds up to 480 Mbit/s and compatible with Full-speed mode. AN14509 How to Use SmartMDA to Implement MDIO Slave Interface on MCX MCU:  This application note describes the use of SmartDMA to implement the MDIO slave interface on MCX series MCUs. AN14479 OTA Recovery Boot Image Stored in 1-bit SPI Flash: This application note describes the step-by-step process to load a recovery image to the external 1-bit SPI flash memory using a secure firmware update. In addition, the steps demonstrate how to trigger a recovery boot from the application using the ROM APIs. AN14300 MCX Nx4x Unleashing the Power of eDMA Controller: his application note provides a working knowledge by covering the following topics: introduction and overview of eDMA controllers, features of the MCX Nx4x eDMA module, interaction between the eDMA and DMA multiplexer (DMAMUX), and configuration advice for applications. AN14423 On-Device Training for Fan Anomaly Detection Using FRDM-MCXN947: This document describes how to prepare the software environment and set up the hardware for fan anomaly detection using FRDM-MCXN947. This demo uses an accelerator sensor on the fan to monitor in real-time whether the fan is operating normally. AN14145 Flash Memory Swap feature on MCX N Series: This application note describes how to use the flash remap feature of MCX series. AN14305 Permanent Magnet Synchronous Motor Field Oriented Control Using MCX Microcontrollers: This application note describes the implementation of Field Oriented Control (FOC) application for a 3-phase Permanent Magnet Synchronous Motor (PMSM) on NXP MCX MCUs, including the N and A series. AN14184 Using SmartDMA for Keyscan on MCX N Series MCU: This application note mainly introduces the Keyscan solution for MCX N series MCU. It includes the introduction of the Keyscan solution, its features and API routines, and a demo. AN14191 How to use SmartDMA to implement Camera Interface in MCXN MCU: This application note describes the parallel interface for the camera solution in MCXN947 and MCXN236. It includes the introduction of camera interface, features, API routines, and demo.  AN14172 Using SmartDMA for Graphic on MCX N Series MCU: This application note introduces the application of SmartDMA on the graphic. AN14196 Flex Pulse Width Modulator (FlexPWM) usage on MCXN MCU: This document introduces several operation modes, including the corresponding implementation, to provide reference for different applications.  AN14253 USB to CAN-FD Adapter based on MCXN Microcontroller: This application note provides two demo examples to build a USB to CAN-FD adapter where the USB retransmits data to the CAN-bus and vice versa. It uses MCX_N9XX_EVK and MCX_N9XX_FDRM boards for the demo.  AN14284 Timing Parameter tuning for FlexIO Emulated Interface: This application note describes how to use additional timers to tune the setup time in SPI master. AN14254 Use QDC/ENC/Quad Timer Peripherals to Calculare the Angle and Speed of the Quadrature Encoder: This application note provides an angle measurement method and an enhanced M/T speed measurement method that can take into account both high and low speeds. AN14167 Internal Reference Clock (IRC) Trim Feature on MCX N Series: This application describe how to use auto-trim feature on MCX N series. AN14241 How to integrate Customer ML Model to NPU on MCX N94x: This document describes how to integrate the customer ML model to NPU on the FRDMMCXN947 board. AN14195 USB Remote Wake-up on MCXN947: MCXN947 contains two USB 2.0 interfaces. USB0 is a full-speed interface. It comprises an On The-Go (OTG) dual-role subsystem with OTG protocol support. AN14185 DCDC Usage on MCXNx4x/Nx3x: This application note is designed to provide a better understanding of the on-chip DCDC module. It offers a comprehensive guide on how to control both basic and advanced parameters, as well as how to configure the DCDC module to work efficiently with other peripherals. AN14178 MCXNx4x Flash Command Example: This document explains how to use the flash command controller to perform flash read and write operations, which can be more efficient than using calls to the ROM API. AN14177 Headset with Touch Function on MCX Nx4x: This application note describes how to use the MCX-N5XX-EVK to implement USB audio with touch control. AN14151 MCX Nx4x MICFIL interface: This application note is based on examples how to leverage the MICFIL coupled with eDMA, interrupts to send the audio stream to the SRAM for postprocessing. AN14146 CANopen Bootloader in MCX N Series: This application note discusses how to implement CANopen bootloader AN14132 Face Detection demo with elQ Neutron NPU Accelerated on MCX N947: This application note shows how to implement the face detection example on the FRDM-MCXN947 board. AN14150 MCX Nx4x Inter-Core Communication Application Note: This application note introduces how dual core devices can communicate using the Mailbox interface. Power Management AN15066 Direct Current arc Fault Circuit Interrupters Solution with Time Series Studio: This application note presents a DC AFCI reference solution based on the MCX N547 MCU. It describes the system architecture, hardware design considerations, and software and algorithm concepts to assist system designers in implementing reliable and standards-compliant arc fault detection solutions AN14180 Estimating Device Lifetime for MCX Nx4x: This document describes the estimated product Power-on Hours (PoH) for the MCX N94x and MCX N54x devices, based on the criteria used in the qualification process. AN14190 OPAMP usage on MCXM947: This application note describes the functions of OPAMP module and how to use OPAMP features on MCXN947. AN14139 Design Considerations for Optimizing Performance with MCX N Series: This application note explains the features of MCX N-series devices that can affect system performance Security AN14148 Secure Boot on MCX N Series: This application note describes the steps for secure boot using the Secure Provisioning Tool (SEC) AN14162 MCX N Debug Authentication: This application note describes the secure debug feature on the MCX N series devices. The document walks through the steps used to configure a device to enable secure debug using the Secure Provisioning Tool. The document also shows the debug authentication steps to unlock the debug port. AN14096 Encryption and Decryption Enablement Using NPX Module on SEC tool:   AN14361 Generating Digital Signature Using ELS ECSIGN command with RTF Enabled: This application note focuses mostly on the ECSIGN command and creates a demo to use it with Run Time Fingerprint (RTF) enabled. The MCX N series SDK contains various ELS command example projects including the ECSIGN usage but not with RTF enabled.  AN14154 Secure Provisioning Guidelines for MCX N Series MCUs: This application note assumes that you are already familiar with the security features available on the MCX N series devices. AN14086 Encryption and Decryption Enablement Using IPED Module on SPSDK Tool: IPED is the abbreviation of Inline Prince Encryption Decryption. The MCX N series devices offer support for real-time encryption and decryption for external flash using the IPED algorithm. Compared to AES, IPED is fast because it can decrypt and encrypt without adding extra latency. IPED operates as data is read or written, without the need to first store data in RAM and then encrypt or decrypt to another space. It operates on a block size of 64 bits with a 128-bit key. This functionality is useful for asset protection, such as securing application code that resides in external NOR flash memory. AN14095 Encryption and Decryption Enablement using IPED Module on SEC Tool: The MCX N series supports seven regions for encryption and decryption. Each crypto region resides at a memory address boundary of the external flash from 0x0800_0000 to 0x0FFF_FFFF. There must be no overlap among these seven ranges. Otherwise, the behavior of IP is undefined. AN14087 Encryption and Decryption Enablement Using NPX Module on SPSDK tool: A trend in embedded processor design is an increasing need for hardware to support cryptographic calculations that are required for system security. There are emerging customer requirements to protect application code and data stored in flash memories in an encrypted form. AN15038 EdgeLock 2GO Provisioning MCUs via Product Type using Secure Provisioning (SEC) tool:  This document offers an outline of the EdgeLock 2GO platform and discusses the "Device provisioning via product type" flow. In this case, the MCUXpresso Secure Provisioning Tool (SEC) is the proxy being used to provision an MCU. AN14670 EdgeLock 2GO Provisioning via SPSDK for MCUs: This document offers an outline of the EdgeLock 2GO platform and discusses the “Device provisioning via proxy” flow. In this case, the SPSDK command line tool is the proxy being used to provision an MCU. AN14687 Ease CRA Compliance with MCX N: This document addresses OEMs who want to understand how the MCX N series can facilitate the implementation of CRA requirements. While the MCX N series provides core security capabilities that can be mapped to the cybersecurity requirements of the CRA, the OEM must fill the remaining compliance gap by performing additional actions.  AN14624 EdgeLock 2Go Provisioning via Secure Provisioning (SEC) tool: This document offers an outline of the EdgeLock 2GO platform and discusses the "Device provisioning via proxy" flow. In this case, the MCUXpresso Secure Provisioning Tool (SEC) is the proxy being used to provision an MCU. AN14460 How to program MCX N series internal flash through ISP: This application note describes how to use USB/UART/SPI/I 2 C ISP to program internal flash of MCX N series MCUs via blhost or MCUXpresso Secure Provisioning Tool AN14544 EdgeLock 2GO Service for MPU and MCU: This application note introduces various methods that the EdgeLock 2GO service can be used with MCU and MPU devices and the features available for each method. AN14248 Recovery Boot from IFR0 for MCX Nx4x: This application note describes the step-by-step process of boot recovery of the signed binary image from Flash Bank 1 IFR 0 of the MCX Nx4x device upon failure of the image execution from the program flash. AN14255 Recovery Boot from 1-bit SPI Flash for MCXNx4x: This application note describes the step-by-step process of boot recovery of the signed binary image from 1-bit SPI flash on the MCXNx4x device upon failure of the image. AN14475 Dual Boot Secure Firmware Update using OTA HTTP Server:  This application note describes the step-by-step process to do a secure firmware update with dual image boot enabled. Covers the example provided in the SDK, which runs from internal flash and what changes are necessary to run from external memory. AN14271 CRC Calculation Features and Performance on MCX: This application note has been divided into two main parts. The first part provides information about the cyclic redundant checker (CRC). The second part introduces the features and performance of the CRC module on an MCX MCU. Training: Introduction: Flexible and Rapid Development with MCUXpresso: Getting Started with Your FRDM Development Boards Fe.... Learn more about NXP's FRDM Development Platform featuring our MCX MCUs portfolio. Discover why specific applications benefit from MCX and features to help differentiate your next product. You will also learn more about the MCUXpresso Developer Experience and how to get started with your FRDM development board. MCX Lab NXP initiative designed to foster collaboration with universities, providing students and educators with cutting-edge hardware, software, and educational resources.  ML/AI: eIQ Time Series Studio Training: Build and Run Time Series ML Models on FRDM-MCXN947 Getting Started with eIQ Time Series Studio Graphics Getting Started with Embedded GUI Development Using GUI Guider and LVGL Useful Links: See some demo videos created based on FRDM-MCXN Application Code Examples Expansion Boards and Accesories: accessories list in Expansion Board Hub compatible with FRDM-MCXN boards. Find displays, rotary, joystick, sensors, and more. Explore the different expansion boards which are supported by software to help you extend and evaluate the features in combination with FRDM-MCXN boards. Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here   

In this lab, we will learn how to program a firmware binary onto the FRDM-MCXC162 development board. The lab will guide you through the complete firmware programming process, starting with the required hardware and software, and continuing with the development environment setup. Hardware requisites: FRDM-MCXC162 Board Type C USB Cable Software requisites: IDE: Visual Studio Code 1.130.0 or later SDK: v26.06.00 Windows OS (It was used Windows 11 for this hands-on) Link Server v25.5.59 Any Recent Phyton 3 Version Windows Command Prompt (CMD) This hands-on describes  Firmware Binary Programming Lab Guide Application Code Hub   Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here 

In this lab, we will learn how to import and run a low-power SDK demo on the FRDM-MCXC162 development board. We will configure the application, build and debug the project, and use a serial monitor to control the available power modes. Hardware requisites: FRDM-MCXC162 Board Type C USB Cable Software requisites: IDE: Visual Studio Code 1.130.0 or later SDK: v26.06.00 Windows OS (It was used Windows 11 for this hands-on) This hands-on describes Low Power SDK Lab Guide Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here 

In this lab, we will learn how to connect and configure expansion boards on the Freedom MCXE 162, including a pressing sensor and a display. Hardware requisites: FRDM-MCXC162 Board Type C USB Cable MikroE OLED B/W Click display in I2C mode SparkFun Qwiic dToF Imager (TMF8820) Software requisites: IDE: Visual Studio Code 1.130.0 or later SDK: v26.06.00 Windows OS (It was used Windows 11 for this hands-on) This hands-on describes Expansion boards Lab Guide Application Code Hub Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here 

The MCX C series MCUs, powered by Arm® Cortex®-M23 up to 72 MHz or Arm® Cortex®-M0+ up to 48 MHz, are designed for cost effectiveness and efficiency, making them ideal for low-end Industrial and IoT applications. Featuring precision analog peripherals as well as USB and segment LCD options, these MCUs cater to diverse needs. The MCX C Series extends the classical IPs within NXP MCUs, providing flexible and scalable memory and packages. MCX C MCUs offer features like USB and segment LCD support, making them ideal for a wide range of general-purpose applications. With a focus on versatility, these MCUs provide the performance and scalability needed for today’s evolving technology demands. Documents: MCX C Series  MCX C Fact Sheet MCX C Series Products MCX C04x:  The MCX C04x microcontrollers, featuring an Arm® Cortex®-M0+ core, offer 32 KB Flash, 2 KB SRAM, and 8 KB boot ROM. Designed as entry-level MCUs, they prioritize simplicity and ease of use for a variety of applications. Key peripherals include a 12-bit ADC, comparator and multiple-channel timer/PWM modules. The enhanced low-power architecture ensures efficiency, with static power consumption as low as 2.2 μA and a 7.5 μs wake-up time for full retention. In deep sleep, static mode power consumption drops to just 77 nA. This series supports scalable memory options and flexible packaging, accommodating diverse application needs. Documents: MCX C041 Sub-Family Reference Manual Data Sheet - MCX C04X Errata: MCXC041 Mask Set MCX C14x/C24x/C44x: The MCX C14x/24x/44x microcontrollers, featuring an Arm® Cortex®-M0+ core, offer a range of memory configurations, from 32KB to 256KB Flash and up to 32KB SRAM, with 16KB Boot ROM. These entry-level MCUs are optimized for cost-sensitive and battery-powered applications requiring low-power USB connectivity and segment LCD support. The FlexIO technology enables customization for various serial peripheral emulation needs. They feature optimized low-power modes, achieving efficiency down to 54uA/MHz in very low-power run mode and 1.96 uA in deep sleep mode with retained RAM and RTC. Documents: Data Sheet - MCX C24x/C14x Data Sheet - MCX C44x Errata:  MCXC - x41 x42  Errata: MCXC - x43 x44 MCX C44x Sub-Family Reference Manual MCX C24x Sub-Family Reference Manual MCX C15/C16: The MCX C15 and MCX C16 microcontrollers (MCUs) are low‑cost, entry‑level devices featuring an Arm® Cortex®‑M23 core running at up to 72 MHz, with memory configurations offering up to 64 KB of flash memory and 16 KB of static random‑access memory (SRAM). These devices bring precision analog and control peripherals into the low‑cost, entry‑level MCU class, making advanced features—such as a 16‑bit analog‑to‑digital converter (ADC), comparator with digital‑to‑analog converter (DAC) and flexible pulse‑width modulation (FlexPWM) for motor control—accessible to cost‑sensitive IoT applications. Designed as an upgrade path from legacy 8‑bit and 16‑bit MCUs, as well as devices based on Arm Cortex‑M0+ cores, this entry‑level 32‑bit MCU series delivers higher performance and greater scalability without increasing costs. Documents: Data Sheet -MCX C151/C161/C162  Fact Sheet - MCX C1 Family Reference Manual - MCX C15/C16  Boards: FRDM MCX C444: FRDM-MCXC444 is a compact and scalable development board for rapid prototyping of MCX C444 MCU. It offers industry-standard headers for easy access to the MCU's I/Os, integrated open-standard serial interfaces and onboard MCU-Link debugger.  FRDM-MCXC444 QSG Getting Started with FRDM-MCXC444 FRDM-MCXC444 Board User Manual FRDM MCX C242: FRDM-MCXC242 is a compact and scalable development board for rapid prototyping of MCX C242 MCU. It offers industry standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces and on-board MCU-Link debugger. FRDM-MCXC242 QSG Getting Started with MCXC242  FRDM-MCXC242 Board User Manual  FRDM-MCX C041:  is a compact and scalable development board for rapid prototyping of MCX C041 MCU. It offers industry-standard headers for easy access to the MCU’s I/Os, integrated open-standard serial interfaces and onboard MCU-Link debugger. FRDM-MCXC041 QSG Getting Started with FRDM-MCXC041 FRDM-MCXC041 Board User Manual MCX C to FRDM Board Mapping Supported MCU(s) Recommended Board Best fit for  Key Differentiators MCXC041 (16QFN, 24QFN) FRDM-MCXC041 Ultra-Low-cost entry-level designs  32KB flash - 2KB SRAM- 48MHz Cortex M0+ - LPUART - SPI - I2C - ADC MCX C141/ C142/ C241/ C242 /C441 /C442 / C444 FRDM-MCXC444 General-purpose USB and Segment LCD application Industrial / Consumer Up to 256KB Flash - 32KB SRAM - 48MHz Cortex-M0+ - USB FS 2.0 - SLCD - FlexIO - DMA 0 CAN-FD - Multiple UART/SPI/I2C MCX C151/ C152/ C161/ C162 FRDM-MCXC162 Motor Control Precision analog Power tools    medical devices Up to 64KB flash - 16KB SRAM - 72MHz Cortex-M23 - 16-bit ADC 2.4MSPS - FlexPWM - 4xUART - 45 GPIO   Application Notes: Software, Hardware and Peripherals: AN14321 Using Segment Liquid Crystal Displays (SLCD) Controller on MCX C444 MCU: This document describes the usage of the on-chip SLCD controller by enabling an SLCD device called S401M16KR. The S401M16KR is a four-digit 0.17-inch seven-segment LCD panel. AN14590 Running RT-Thread on MCUXpresso IDE: This document is intended for the users who are familiar with RT-Thread and want to port it to MCUXpressoIDE. It provides steps to streamline the porting process. The porting steps are applicable to other NXP chips also. This document uses FRDM-MCXC444 as an example. AN14319 FlexIO Emulating UART with IRDA: This application note introduces how to use the universal peripheral module FlexIO for emulating the UART bus with IRDA. The FlexIO peripheral, initially introduced on the MCXC242 and MCXC444 family, is a highly configurable module capable of emulating a wide range of different communication protocols. These communication protocols include UART, I2C, SPI, I2S, and so on. AN14322 USB to multi VCOM on MCX C444 Series MCU: This document describes how to implement a USB to functions of multiple VCOMs on MCX C444 series FRDM boards. AN14349 Emulating I2C Bus Controller by using FlexIO on MCX C: This application note lists the steps to use the FlexIO module for emulating the I2C bus controller Power Management:  AN14811 Estimated Power-on Hours for the MCX C04x, MCX C14x, MCX C24x and MCX C44x: This document describes the estimated product power-on hours (PoH) for the MCX C04x, MCX C14x, MCX C24x, and MCX C44x industrial MCUs. It uses the criteria from the qualification process. AN14332 MCX C444 Power Mode Switch Application: This application note focuses on the power management controller (PMC), system mode controller (SMC), Multipurpose Clock Generator Lite (MCG-Lite), and Low-Leakage Wakeup Unit (LLWU). Training: Design without Bounds FRDM Training and Resources FRDM Training Hub MCX C15/C16 Product Training Useful Links: FRDM Boards Enclosures (3D Print) MCX C:  How to Enter the ROM Bootloader to Update the firmware MCUXPresso for Visual Studio Code - MCX MCUXpresso Config Tool for MCUXpresso IDE MCUXpresso Config Tool for 3rd party IDE Download Firmware to MCX microcontrollers over USB, I2Cm UART, SPI, CAN Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here   

In this lab, we'll learn how to access Application Code Hub directly from Visual Studio Code, download a low-power sensing application, and run it on the FRDM-MCXC162. Hardware requisites: FRDM-MCXC162 Board Type C USB Cable Software requisites: IDE: Visual Studio Code 1.130.0 or later SDK: v26.06.00 Windows OS (It was used Windows 11 for this hands-on) This hands-on describes Low Power Temperature Sensing Lab Guide Application Code Hub   Community Support If you have questions regarding this training, please leave your comments in our MCU Community! here 

This document describes the complete process required to enable and use GPIOs from a Zephyr Non-Secure application running on the FRDM-MCXN947. It covers the configuration of the AHB security attribution settings, the Zephyr and TF-M project configuration, and the use of the GPIO alias mirror registers to grant Non-Secure access to the desired GPIO ports. After completing these steps, GPIO peripherals can be controlled directly from the Zephyr application while maintaining the security isolation provided by TrustZone.