MCUXpresso SDK Release Notes#
Overview#
The MCUXpresso SDK is a comprehensive software enablement package designed to simplify and accelerate application development with Arm Cortex-M-based devices from NXP, including its general purpose, crossover and Bluetooth-enabled MCUs. MCUXpresso SW and Tools for DSC further extends the SDK support to current 32-bit Digital Signal Controllers. The MCUXpresso SDK includes production-grade software with integrated RTOS (optional), integrated enabling software technologies (stacks and middleware), reference software, and more.
In addition to working seamlessly with the MCUXpresso IDE, the MCUXpresso SDK also supports and provides example projects for various toolchains. The Development tools chapter in the associated Release Notes provides details about toolchain support for your board. Support for the MCUXpresso Config Tools allows easy cloning of existing SDK examples and demos, allowing users to leverage the existing software examples provided by the SDK for their own projects.
Underscoring our commitment to high quality, the MCUXpresso SDK is MISRA compliant and checked with Coverity static analysis tools. For details on MCUXpresso SDK, see MCUXpresso-SDK: Software Development Kit for MCUXpresso.
MCUXpresso SDK#
As part of the MCUXpresso software and tools, MCUXpresso SDK is the evolution of Kinetis SDK, includes support for LPC, DSC,PN76, and i.MX System-on-Chip (SoC). The same drivers, APIs, and middleware are still available with support for Kinetis, LPC, DSC, and i.MX silicon. The MCUXpresso SDK adds support for the MCUXpresso IDE, an Eclipse-based toolchain that works with all MCUXpresso SDKs. Easily import your SDK into the new toolchain to access to all of the available components, examples, and demos for your target silicon. In addition to the MCUXpresso IDE, support for the MCUXpresso Config Tools allows easy cloning of existing SDK examples and demos, allowing users to leverage the existing software examples provided by the SDK for their own projects.
In order to maintain compatibility with legacy Freescale code, the filenames and source code in MCUXpresso SDK containing the legacy Freescale prefix FSL has been left as is. The FSL prefix has been redefined as the NXP Foundation Software Library.
Development tools#
The MCUXpresso SDK was tested with following development tools. Same versions or above are recommended.
MCUXpresso IDE, Rev. 25.06.xx
IAR Embedded Workbench for Arm, version is 9.60.4
Keil MDK, version is 5.42
MCUXpresso for VS Code v25.09
GCC Arm Embedded Toolchain 14.2.x
Supported development systems#
This release supports board and devices listed in following table. The board and devices in bold were tested in this release.
Development boards |
MCU devices |
|---|---|
RD-RW612-BGA |
RW610ETA2I, RW610HNA2I, RW610UKA2I, |
MCUXpresso SDK release package#
The MCUXpresso SDK release package content is aligned with the silicon subfamily it supports. This includes the boards, CMSIS, devices, middleware, and RTOS support.
Device support#
The device folder contains the whole software enablement available for the specific System-on-Chip (SoC) subfamily. This folder includes clock-specific implementation, device register header files, device register feature header files, and the system configuration source files. Included with the standard SoC support are folders containing peripheral drivers, toolchain support, and a standard debug console. The device-specific header files provide a direct access to the microcontroller peripheral registers. The device header file provides an overall SoC memory mapped register definition. The folder also includes the feature header file for each peripheral on the microcontroller. The toolchain folder contains the startup code and linker files for each supported toolchain. The startup code efficiently transfers the code execution to the main() function.
Board support#
The boards folder provides the board-specific demo applications, driver examples, and middleware examples.
Demo application and other examples#
The demo applications demonstrate the usage of the peripheral drivers to achieve a system level solution. Each demo application contains a readme file that describes the operation of the demo and required setup steps. The driver examples demonstrate the capabilities of the peripheral drivers. Each example implements a common use case to help demonstrate the driver functionality.
RTOS#
FreeRTOS#
Real-time operating system for microcontrollers from Amazon
Middleware#
CMSIS DSP Library#
The MCUXpresso SDK is shipped with the standard CMSIS development pack, including the prebuilt libraries.
memfault-firmware-sdk#
memfault-firmware-sdk
Connectivity framework#
The Connectivity Framework is a software component that provides hardware abstraction modules to the upper layer connectivity stacks and components. It also provides a list of services and APIs (see Supported services). The Connectivity Framework modules are located in the middleware\wireless\framework SDK folder.
Supported services#
FSCI - Framework Serial Communication Interface
FunctionLib - Common function library utilities
HWParameter - Hardware parameter management
LowPower - Low power mode management
ModuleInfo - Module information and versioning
NVS - Non-Volatile Storage
NVM - Non-Volatile Memory management
OtaSupport - Over-The-Air update support
SecLib_RNG - Security library and Random Number Generator
Sensors - Sensor abstraction layer
SFC - Smart Frequency Calibration
WorkQ - Work queue management
Supported platform#
KW45_MCXW71
KW47_MCXW72
MCXW23
RW61X
RT1060 and RT1170
i.MX RT595s
Advanced features supported on platforms#
KW45_MCXW71#
FRO32K with smart frequency calibration (see SFC)
Power down mode support (for evaluation only)
KW47_MCXW72#
FRO32K with smart frequency calibration (see SFC)
Power down mode support (for evaluation only)
Crystal 32M trimming with temperature
Debug module for NBU
Extended NBU support with SecLib and pseudo RNG support
wpa_supplicant-rtos#
NXP Wi-Fi WPA Supplicant
Wireless EdgeFast Bluetooth PAL#
For more information, see the MCUXpresso SDK EdgeFast Bluetooth Protocol Abstraction Layer User’s Guide.
Ethermind BT/BLE Stack#
nxp_bt_ble_stack
coreHTTP#
coreHTTP
NXP Wi-Fi#
The MCUXpresso SDK provides driver for NXP Wi-Fi external modules. The Wi-Fi driver is integrated with LWIP TCPIP stack and demonstrated with several network applications (iperf and AWS IoT).
For more information, see Getting Started with NXP based Wireless Modules and i.MX RT Platform Running on RTOS (document: UM11441).
USB Type-C PD Stack#
See the MCUXpresso SDK USB Type-C PD Stack User’s Guide (document MCUXSDKUSBPDUG) for more information
USB Host, Device, OTG Stack#
See the MCUXpresso SDK USB Stack User’s Guide (document MCUXSDKUSBSUG) for more information.
TinyCBOR#
Concise Binary Object Representation (CBOR) Library
TF-M#
Trusted Firmware - M Library
PSA Test Suite#
Arm Platform Security Architecture Test Suite
PKCS#11#
The PKCS#11 standard specifies an application programming interface (API), called “Cryptoki,” for devices that hold cryptographic information and perform cryptographic functions. Cryptoki follows a simple object based approach, addressing the goals of technology independence (any kind of device) and resource sharing (multiple applications accessing multiple devices), presenting to applications a common, logical view of the device called a “cryptographic token”.
NXP IoT Agent#
NXP IoT Agent
MCU Boot#
Open source MCU Bootloader.
mbedTLS#
mbedtls SSL/TLS library v3.x
mbedTLS#
mbedtls SSL/TLS library v2.x
Voice intelligent technology library#
Voice Intelligent Technology (VIT) Library provides wake word and voice command engine for voice control
Audio Voice components#
Audio Voice components for MCU
Maestro Audio Framework for MCU#
Maestro Audio Framework library for MCU
lwIP#
The lwIP TCP/IP stack is pre-integrated with MCUXpresso SDK and runs on top of the MCUXpresso SDK Ethernet driver with Ethernet-capable devices/boards.
For details, see the lwIP TCPIP Stack and MCUXpresso SDK Integration User’s Guide (document MCUXSDKLWIPUG).
lwIP is a small independent implementation of the TCP/IP protocol suite.
LVGL#
LVGL Open Source Graphics Library
llhttp#
HTTP parser llhttp
LittleFS#
LittleFS filesystem stack
FreeMASTER#
FreeMASTER communication driver for 32-bit platforms.
File systemFatfs#
The FatFs file system is integrated with the MCUXpresso SDK and can be used to access either the SD card or the USB memory stick when the SD card driver or the USB Mass Storage Device class implementation is used.
emWin#
The MCUXpresso SDK is pre-integrated with the SEGGER emWin GUI middleware. The AppWizard provides developers and designers with a flexible tool to create stunning user interface applications, without writing any code.
cJSON#
Ultralightweight JSON parser in ANSI C
NXP PSA CRYPTO DRIVER#
PSA crypto driver for crypto library integration via driver wrappers
NXP ELS PKC#
ELS PKC crypto library
Release contents#
Provides an overview of the MCUXpresso SDK release package contents and locations.
Deliverable |
Location |
|---|---|
Boards |
INSTALL_DIR/boards |
Demo Applications |
INSTALL_DIR/boards/<board_name>/demo_apps |
Driver Examples |
INSTALL_DIR/boards/<board_name>/driver_examples |
eIQ examples |
INSTALL_DIR/boards/<board_name>/eiq_examples |
Board Project Template for MCUXpresso IDE NPW |
INSTALL_DIR/boards/<board_name>/project_template |
Driver, SoC header files, extension header files and feature header files, utilities |
INSTALL_DIR/devices/<device_name> |
CMSIS drivers |
INSTALL_DIR/devices/<device_name>/cmsis_drivers |
Peripheral drivers |
INSTALL_DIR/devices/<device_name>/drivers |
Toolchain linker files and startup code |
INSTALL_DIR/devices/<device_name>/<toolchain_name> |
Utilities such as debug console |
INSTALL_DIR/devices/<device_name>/utilities |
Device Project Template for MCUXpresso IDE NPW |
INSTALL_DIR/devices/<device_name>/project_template |
CMSIS Arm Cortex-M header files, DSP library source |
INSTALL_DIR/CMSIS |
Components and board device drivers |
INSTALL_DIR/components |
RTOS |
INSTALL_DIR/rtos |
Release Notes, Getting Started Document and other documents |
INSTALL_DIR/docs |
Tools such as shared cmake files |
INSTALL_DIR/tools |
Middleware |
INSTALL_DIR/middleware |
Known issues#
This section lists the known issues, limitations, and/or workarounds.
Low speed devices not supported#
The host examples cannot support low-speed devices.
IAR cannot debug RAM application with J-Link#
Currently, IAR will call J-Link reset after the application is downloaded to SRAM, but such operation will cause SRAM data lost.
Here is a workaround to avoid real reset, with the cost of no any reset during the debugging, and hardware status uncleared.
Build and debug IAR project once and see the settings folder created.
Create the _.JLinkScript file in the settings folder with the following contents.
void ResetTarget(void) { JLINK_TARGET_Halt(); }
Debug the project again and now it can work.
usb_device_mtp example cannot boot on Keil MDK µVision#
After reset, the usb_device_mtp and usb_device_mtp_lite examples cannot boot successfully when using Keil MDK µVision. Adding the –predefine=”-DXIP_BOOT_HEADER_ENABLE=1” into Options for target > Linker > Misc controls can fix this issue.
Log output may be mixed in shell/hfp example#
When multiple tasks print the log, the serial port terminal output has the probability to appear mixed.
Example mbedtls_benchmark may hang on some targets on devices with ELS acceleration#
Some targets of ELS accelerated devices may experience runtime issues when run with the default configuration of the mbedtls_benchmark application.
Examples: mbedtls_benchmark
Affected toolchains: All
TF-M secure and EL2GO examples incorrect path in “Download extra image” with iar and mdk IDEs with Kex package#
TF-M secure and EL2GO examples are missing the target path for ns binary in “extra download image” with iar and mdk IDEs
Examples: tfm_demo_s, tfm_psatest_s, tfm_regression_s, tfm_secureboot_s, el2go_agent_s, el2go_blob_test_s, el2go_import_blob_s, el2go_mqtt_demo_s Affected toolchains: mdk, iar Affected platforms: mcxn5xxevk, frdmmcxn947, mcxn9xxevk, rdrw612bga, frdmrw612 Workaround: There are two ways 1.) Flash secure and non secure bins via Jlink or SPSDK after the build with IDE and providing with correct paths of secure and non-secure binaries. or 2.) Add {target} debug/release in path of “Download extra image” for iar and for MDK in xxx_flashdownload.ini file.