MCUXSDKMIMXRT116XRN

MCUXpresso SDK Release Notes for MIMXRT1160-EVK

Rev. 2.14.0 — 27 July 2023 Release notes

Document Information
Information Content
Keywords MCUXpresso SDK, Release Notes, MIMXRT1160-EVK
Abstract This document describes the MCUXpresso SDK release notes for MIMXRT1160-EVK.
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

1 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 IAR, KEIL, and GCC with Cmake. 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.

2 MCUXpresso SDK
As part of the MCUXpresso software and tools, MCUXpresso SDK is the evolution of Kinetis SDK, includes
support for LPC, DSC, 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.

3 Development tools
The MCUXpresso SDK is compiled and tested with these development tools:
• Keil MDK, version is 5.38.a
• MCUXpresso IDE, version is 11.8.0
• GCC Arm Embedded, version is 12.2.Rel1
• IAR Embedded Workbench for Arm, version is 9.40
Note: There are some issues when using Segger J-Link Version 7.00 to debug CM4/CM7 flash related targets.
NXP is working with Segger to get this issue fixed in the future. However, if you want to use the JLink probe to
debug flash related targets before the issue is fixed, contact NXP for a temporary patch.

4 Supported development system

This release supports boards and devices listed in table below. The boards and devices in bold were tested in
this release.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

2 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

Table 1. Supported boards and devices

Development boards MCU devices
MIMXRT1160-EVK MIMXRT1166DVM6A, MIMXRT1166CVM5A, MIMXRT1166XVM5A, MIMXRT1165DVM6A,
MIMXRT1165CVM5A, MIMXRT1165XVM5A

5 MCUXpresso SDK release package

The MCUXpresso SDK release package content is aligned with the silicon subfamily it supports. This includes
the boards, devices, documentation, and middleware.

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

5.1.1 Board support

The boards folder provides the board-specific demo applications, driver examples, and middleware examples.

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

5.2 CMSIS DSP Library

The MCUXpresso SDK is shipped with the standard CMSIS development pack, including the prebuilt libraries.

5.3 Middleware

5.3.1 AWS IoT

Amazon Web Service (AWS) IoT Core SDK.

5.3.2 Azure RTOS FileX

A file system based on Azure RTOS.

5.3.3 Azure RTOS GUIX

A GUI library based on Azure RTOS.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

3 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

5.3.4 Azure RTOS IoT

A software package that connects to the IoT Hub through Azure RTOS.

5.3.5 Azure RTOS LevelX

NOR/NAND Flash wear leveling component

5.3.6 Azure RTOS NetX Duo

A network protocol stack based on Azure RTOS.

5.3.7 Azure RTOS ThreadX

Azure RTOS ThreadX.

5.3.8 Azure RTOS USBX

A USB library based on Azure RTOS.

5.3.9 canopen
MicroCANopen Stack from Embedded Solutions Academy

5.3.10 eIQ
eIQ machine learning SDK containing:
• Arm CMSIS-NN library (neural network kernels optimized for Cortex-M cores)
• Inference engines:
– TensorFlow Lite Micro
– DeepView RT
• Example code for TensorFlow Lite Micro, Glow, and DeepView RT

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

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

5.3.13 FreeMASTER
FreeMASTER communication driver for 32-bit platforms.

5.3.14 IoT Sensing Software Development Kit (ISSDK)

The IoT Sensing Software Development Kit (ISSDK) is the embedded software framework enabling the NXP
digital and analog sensors for IoT applications. ISSDK combines a set of robust sensor drivers and algorithms

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

4 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

along with example applications that allow users to get started with using NXP IoT motion & pressure sensors.
ISSDK is being offered as a middleware component in MCUXpresso SDK.

5.3.15 JPEG library

JPEG library

5.3.16 littlefs
LittleFS filesystem stack

5.3.17 LVGL
LVGL Open Source Graphics Library

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

5.3.19 Motor Control Software (ACIM, BLDC, PMSM)

Motor control examples.

5.3.20 mbedTLS
mbedtls SSL/TLS library

5.3.21 MCU Boot

MCU Bootloader source code.

5.3.22 MMCAU
MMCAU

5.3.23 multicore
Multicore Software Development Kit

5.3.24 NAND Flash Management Stack

NAND Flash Management Stack.

5.3.25 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).
MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

5 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

5.3.26 Openh264
H.264 Codec Library

5.3.27 openvg
Openvg library

5.3.28 Simple Open EtherCAT Master

Simple Open EtherCAT Master (SOEM) is an open source EtherCAT master stack that is used to write custom
EtherCAT Master applications. For more information on how to use SOEM, see the Getting Started with
MCUXpresso SDK for SOEM document.

5.3.29 USB Host, Device, OTG Stack

See the MCUXpresso SDK USB Stack User’s Guide (document MCUXSDKUSBSUG) for more information.

5.3.30 USB Type-C Power Delivery Authentication

USB Type-C Power Delivery Authentication

5.3.31 VG-Lite GPU Library

vglite lib.

5.3.32 Voice intelligent technology library

Voice Intelligent Technology (VIT) Library.

5.3.33 Wireless EdgeFast Bluetooth PAL

For more information, see the MCUXpresso SDK EdgeFast Bluetooth Protocol Abstraction Layer User's Guide.

6 Release contents
Table 2 provides an overview of the MCUXpresso SDK release package contents and locations.

Table 2. 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
Board Project Template for MCUXpresso IDE NPW INSTALL_DIR/boards/<board_name>/project_template
Driver, SoC header files, extension header files and INSTALL_DIR/devices/<device_name>
feature header files, utilities
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

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

6 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

Table 2. MCUXpresso SDK release package contents and locations...continued

Deliverable Location
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 INSTALL_DIR/docs
documents
Tools such as shared cmake files INSTALL_DIR/tools
Middleware INSTALL_DIR/middleware

7 MISRA compliance
All MCUXpresso SDK drivers comply to MISRA 2012 rules with exceptions in Table 3.

Table 3. MISRA exception rules

Exception rules Description
Directive 4.4 Sections of code should not be commented out.
Directive 4.5 Identifiers in the same name space with overlapping visibility
should be typographically unambiguous.
Directive 4.6 Typedefs that indicate size and signedness should be used
in place of the basic numerical types.
Directive 4.8 If a pointer to a structure or union is never dereferenced
within a translation unit, then the implementation of the
object should be hidden.
Directive 4.9 A function should be used in preference to a function-like
macro where they are interchangeable.
Directive 4.13 Functions which are designed to provide operations on a
resource should be called in an appropriate sequence.
Rule 1.2 Language extensions should not be used.
Rule 2.3 A project should not contain unused type declarations.
Rule 2.4 A project should not contain unused tag declarations.
Rule 2.5 A project should not contain unused macro declarations.
Rule 2.6 A function should not contain unused label declarations.
Rule 2.7 There should be no unused parameters in functions.
Rule 4.2 Trigraphs should not be used.
Rule 5.1 External identifiers shall be distinct.
Rule 5.4 Macro identifiers shall be distinct.
Rule 5.9 Identifiers that define objects or functions with internal
linkage should be unique.
Rule 8.7 Functions and objects should not be defined with external
linkage if they are referenced in only one translation unit.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

7 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

Table 3. MISRA exception rules...continued

Exception rules Description
Rule 8.9 An object should be defined at block scope if its identifier
only appears in a single function.
Rule 8.11 When an array with external linkage is declared, its size
should be explicitly specified.
Rule 8.13 A pointer should point to a const-qualified type whenever
possible.
Rule 10.5 The value of an expression should not be cast to an
inappropriate essential type.
Rule 11.4 A conversion should not be performed between a pointer to
object and an integer type.
Rule 11.5 A conversion should not be performed from pointer to void
into pointer to object.
Rule 12.1 The precedence of operators within expressions should be
made explicit.
Rule 12.3 The comma operator should not be used.
Rule 12.4 Evaluation of constant expressions should not lead to
unsigned integer wrap-around.
Rule 13.3 A full expression containing an increment (++) or decrement
(–) operator should have no other potential side effects other
than that caused by the increment or decrement operator.
Rule 15.4 There should be no more than one break or go to statement
used to terminate any iteration statement.
Rule 17.5 The function argument corresponding to a parameter
declared to have an array type shall have an appropriate
number of elements.
Rule 17.8 A function parameter should not be modified.
Rule 19.2 The union keyword should not be used.
Rule 20.1 #include directives should only be preceded by preprocessor
directives or comments.
Rule 20.10 The # and ## preprocessor operators should not be used.
Rule 21.1 #define and #undef shall not be used on a reserved identifier
or reserved macro name.
Rule 21.2 A reserved identifier or macro name shall not be declared.
Rule 21.12 The exception handling features of <fenv.h> should not be
used.

8 Known Issues
This section lists the known issues, limitations, and/or workarounds.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

8 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

8.1 Maximum file path length in Windows 7 operating system

The Windows 7 operating system imposes a 260-character maximum length for file paths. When installing the
MCUXpresso SDK, place it in a directory close to the root to prevent file paths from exceeding the maximum
character length specified by the Windows operating system. The recommended location is the C:\<folder>.

8.2 New Project Wizard compile failure

The following components request the user to manually select other components that they depend upon in
order to compile.
These components depend on several other components and the New Project Wizard (NPW) is not able to
decide which one is needed by the user.
Note: xxx means core variants, such as, cm0plus, cm33, cm4, cm33_nodsp.
Components:issdk_mag3110, issdk_host, systick, gpio_kinetis, gpio_lpc, issdk_mpl3115,
sensor_fusion_agm01, sensor_fusion_agm01_lpc, issdk_mma845x, issdk_mma8491q, issdk_mma865x,
issdk_mma9553, CMSIS_RTOS2, and components which include cache driver, such as enet_qos.
Also for low-level adapter components, currently the different types of the same adapter cannot be selected at
the same time.
For example, if there are two types of timer adapters, gpt_adapter and pit_adapter, only one can be selected as
timer adapter
in one project at a time. Duplicate implementation of the function results in an error.
Note: Most of middleware components have complex dependencies and are not fully supported in new project
wizard. Adding a middleware component may result in compile failure.

8.3 CMSIS-PACK svd issue

CMSIS-PACK DFP installation takes a while. When installing cmsis-pack DFP, Keil MDK processes the MCU
SVD file. The large size of SVD file takes considerable time to finish this conversion. During the installation, the
progress appears stalled. However, it finishes after approximately 20 minutes.

8.4 CMSIS PACK new project compile failure

The generated configuration cannot be applied globally. The components, serial_manager_usb_cdc_virtual and
serial_manager_usb_cdc_virtual_xxx (xxx means core variants like cm0plus, cm33, cm4, and cm33_nodsp) are
unsupported for new project wizard of CMSIS pack and will lead to compile failure if selected while creating new
project(s).

8.5 MCUXpresso IDE limitation

• Cannot debug cm4 sdram related demos with CMSIS-DAP
MCUXpresso IDE does not support initialization of sdram when debugging.

8.6 IAR debug limitation

CM4 flash target demos cannot be debugged on IAR with JLINK.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

9 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

8.7 Extra option required when using CMSIS-DAP to debug

When using CMSIS-DAP to debug CM4 sdram related target in IAR, such as flexspi_nor_sdram and sdram_txt,
an extra option must be specified in the debugger settings. For details, see Section 8.6.

8.8 Cannot add SDK components into FreeRTOS projects

It is not possible to add any SDK components into FreeRTOS project using the MCUXpresso IDE New Project
wizard.

8.9 aws_httpscli_corehttp example for evkmimxrt1160 issue in MCUXpressoIDE

release target
The aws_httpscli_corehttp example for evkmimxrt1160 does not work correctly in MCUXpressoIDE release
target. Use the debug target only in this IDE.

9 Change Log
Change log of software components included in the package, see the MCUXpresso SDK
ChangeLog_MIMXRT1166.pdf.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

10 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

10 Legal information
10.1 Definitions Terms and conditions of commercial sale — NXP Semiconductors
products are sold subject to the general terms and conditions of commercial
sale, as published at http://www.nxp.com/profile/terms, unless otherwise
Draft — A draft status on a document indicates that the content is still agreed in a valid written individual agreement. In case an individual
under internal review and subject to formal approval, which may result agreement is concluded only the terms and conditions of the respective
in modifications or additions. NXP Semiconductors does not give any agreement shall apply. NXP Semiconductors hereby expressly objects to
representations or warranties as to the accuracy or completeness of applying the customer’s general terms and conditions with regard to the
information included in a draft version of a document and shall have no purchase of NXP Semiconductors products by customer.
liability for the consequences of use of such information.
Export control — This document as well as the item(s) described herein
may be subject to export control regulations. Export might require a prior
10.2 Disclaimers authorization from competent authorities.

Limited warranty and liability — Information in this document is believed Suitability for use in non-automotive qualified products — Unless
to be accurate and reliable. However, NXP Semiconductors does not give this data sheet expressly states that this specific NXP Semiconductors
any representations or warranties, expressed or implied, as to the accuracy product is automotive qualified, the product is not suitable for automotive
or completeness of such information and shall have no liability for the use. It is neither qualified nor tested in accordance with automotive testing
consequences of use of such information. NXP Semiconductors takes no or application requirements. NXP Semiconductors accepts no liability for
responsibility for the content in this document if provided by an information inclusion and/or use of non-automotive qualified products in automotive
source outside of NXP Semiconductors. equipment or applications.
In no event shall NXP Semiconductors be liable for any indirect, incidental, In the event that customer uses the product for design-in and use in
punitive, special or consequential damages (including - without limitation - automotive applications to automotive specifications and standards,
lost profits, lost savings, business interruption, costs related to the removal customer (a) shall use the product without NXP Semiconductors’ warranty
or replacement of any products or rework charges) whether or not such of the product for such automotive applications, use and specifications, and
damages are based on tort (including negligence), warranty, breach of (b) whenever customer uses the product for automotive applications beyond
contract or any other legal theory. NXP Semiconductors’ specifications such use shall be solely at customer’s
own risk, and (c) customer fully indemnifies NXP Semiconductors for any
Notwithstanding any damages that customer might incur for any reason
liability, damages or failed product claims resulting from customer design and
whatsoever, NXP Semiconductors’ aggregate and cumulative liability
use of the product for automotive applications beyond NXP Semiconductors’
towards customer for the products described herein shall be limited in
standard warranty and NXP Semiconductors’ product specifications.
accordance with the Terms and conditions of commercial sale of NXP
Semiconductors.
Translations — A non-English (translated) version of a document, including
the legal information in that document, is for reference only. The English
Right to make changes — NXP Semiconductors reserves the right to
version shall prevail in case of any discrepancy between the translated and
make changes to information published in this document, including without
English versions.
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior
Security — Customer understands that all NXP products may be subject to
to the publication hereof.
unidentified vulnerabilities or may support established security standards or
specifications with known limitations. Customer is responsible for the design
Suitability for use — NXP Semiconductors products are not designed,
and operation of its applications and products throughout their lifecycles
authorized or warranted to be suitable for use in life support, life-critical or
to reduce the effect of these vulnerabilities on customer’s applications
safety-critical systems or equipment, nor in applications where failure or
and products. Customer’s responsibility also extends to other open and/or
malfunction of an NXP Semiconductors product can reasonably be expected
proprietary technologies supported by NXP products for use in customer’s
to result in personal injury, death or severe property or environmental
applications. NXP accepts no liability for any vulnerability. Customer should
damage. NXP Semiconductors and its suppliers accept no liability for
regularly check security updates from NXP and follow up appropriately.
inclusion and/or use of NXP Semiconductors products in such equipment or
applications and therefore such inclusion and/or use is at the customer’s own Customer shall select products with security features that best meet rules,
risk. regulations, and standards of the intended application and make the
ultimate design decisions regarding its products and is solely responsible
for compliance with all legal, regulatory, and security related requirements
Applications — Applications that are described herein for any of these
concerning its products, regardless of any information or support that may be
products are for illustrative purposes only. NXP Semiconductors makes no
provided by NXP.
representation or warranty that such applications will be suitable for the
specified use without further testing or modification. NXP has a Product Security Incident Response Team (PSIRT) (reachable
at [email protected]) that manages the investigation, reporting, and solution
Customers are responsible for the design and operation of their
release to security vulnerabilities of NXP products.
applications and products using NXP Semiconductors products, and NXP
Semiconductors accepts no liability for any assistance with applications or
customer product design. It is customer’s sole responsibility to determine NXP B.V. - NXP B.V. is not an operating company and it does not distribute
whether the NXP Semiconductors product is suitable and fit for the or sell products.
customer’s applications and products planned, as well as for the planned
application and use of customer’s third party customer(s). Customers should
provide appropriate design and operating safeguards to minimize the risks
associated with their applications and products.
10.3 Trademarks
NXP Semiconductors does not accept any liability related to any default, Notice: All referenced brands, product names, service names, and
damage, costs or problem which is based on any weakness or default trademarks are the property of their respective owners.
in the customer’s applications or products, or the application or use by
customer’s third party customer(s). Customer is responsible for doing all NXP — wordmark and logo are trademarks of NXP B.V.
necessary testing for the customer’s applications and products using NXP
Semiconductors products in order to avoid a default of the applications
and the products or of the application or use by customer’s third party
customer(s). NXP does not accept any liability in this respect.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

11 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11, Artisan, big.LITTLE, Cadence — the Cadence logo, and the other Cadence marks found at www.
Cordio, CoreLink, CoreSight, Cortex, DesignStart, DynamIQ, Jazelle, cadence.com/go/trademarks are trademarks or registered trademarks of
Keil, Mali, Mbed, Mbed Enabled, NEON, POP, RealView, SecurCore, Cadence Design Systems, Inc. All rights reserved worldwide.
Socrates, Thumb, TrustZone, ULINK, ULINK2, ULINK-ME, ULINK- EdgeLock — is a trademark of NXP B.V.
PLUS, ULINKpro, μVision, Versatile — are trademarks and/or registered
trademarks of Arm Limited (or its subsidiaries or affiliates) in the US and/or Freescale — is a trademark of NXP B.V.
elsewhere. The related technology may be protected by any or all of patents, Kinetis — is a trademark of NXP B.V.
copyrights, designs and trade secrets. All rights reserved.
NTAG — is a trademark of NXP B.V.
Bluetooth — the Bluetooth wordmark and logos are registered trademarks
owned by Bluetooth SIG, Inc. and any use of such marks by NXP
Semiconductors is under license.

MCUXSDKMIMXRT116XRN All information provided in this document is subject to legal disclaimers. © 2023 NXP B.V. All rights reserved.

Release notes Rev. 2.14.0 — 27 July 2023

12 / 13
NXP Semiconductors MCUXSDKMIMXRT116XRN
MCUXpresso SDK Release Notes for MIMXRT1160-EVK

Contents
1 Overview .............................................................. 2 8.5 MCUXpresso IDE limitation ............................... 9
2 MCUXpresso SDK ............................................... 2 8.6 IAR debug limitation .......................................... 9
3 Development tools .............................................. 2 8.7 Extra option required when using CMSIS-
4 Supported development system ........................2 DAP to debug .................................................. 10
5 MCUXpresso SDK release package .................. 3 8.8 Cannot add SDK components into
5.1 Device support ...................................................3 FreeRTOS projects .......................................... 10
5.1.1 Board support .................................................... 3 8.9 aws_httpscli_corehttp example for
5.1.2 Demo application and other examples .............. 3 evkmimxrt1160 issue in MCUXpressoIDE
5.2 CMSIS DSP Library ...........................................3 release target ...................................................10
5.3 Middleware .........................................................3 9 Change Log ....................................................... 10
5.3.1 AWS IoT ............................................................ 3 10 Legal information .............................................. 11
5.3.2 Azure RTOS FileX ............................................. 3
5.3.3 Azure RTOS GUIX ............................................ 3
5.3.4 Azure RTOS IoT ................................................ 4
5.3.5 Azure RTOS LevelX .......................................... 4
5.3.6 Azure RTOS NetX Duo ..................................... 4
5.3.7 Azure RTOS ThreadX ....................................... 4
5.3.8 Azure RTOS USBX ........................................... 4
5.3.9 canopen ............................................................. 4
5.3.10 eIQ ..................................................................... 4
5.3.11 emWin ................................................................4
5.3.12 Fatfs ................................................................... 4
5.3.13 FreeMASTER .....................................................4
5.3.14 IoT Sensing Software Development Kit
(ISSDK) ..............................................................4
5.3.15 JPEG library ...................................................... 5
5.3.16 littlefs ..................................................................5
5.3.17 LVGL .................................................................. 5
5.3.18 lwIP .................................................................... 5
5.3.19 Motor Control Software (ACIM, BLDC,
PMSM) ............................................................... 5
5.3.20 mbedTLS ........................................................... 5
5.3.21 MCU Boot .......................................................... 5
5.3.22 MMCAU ............................................................. 5
5.3.23 multicore ............................................................ 5
5.3.24 NAND Flash Management Stack .......................5
5.3.25 NXP Wi-Fi ..........................................................5
5.3.26 Openh264 .......................................................... 6
5.3.27 openvg ............................................................... 6
5.3.28 Simple Open EtherCAT Master ......................... 6
5.3.29 USB Host, Device, OTG Stack .......................... 6
5.3.30 USB Type-C Power Delivery Authentication ...... 6
5.3.31 VG-Lite GPU Library ......................................... 6
5.3.32 Voice intelligent technology library .....................6
5.3.33 Wireless EdgeFast Bluetooth PAL .....................6
6 Release contents ................................................ 6
7 MISRA compliance ..............................................7
8 Known Issues ......................................................8
8.1 Maximum file path length in Windows 7
operating system ............................................... 9
8.2 New Project Wizard compile failure ................... 9
8.3 CMSIS-PACK svd issue .................................... 9
8.4 CMSIS PACK new project compile failure ......... 9

Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section 'Legal information'.

© 2023 NXP B.V. All rights reserved.

For more information, please visit: http://www.nxp.com
Date of release: 27 July 2023
Document identifier: MCUXSDKMIMXRT116XRN