Known issues

The following are the known issues in this release.

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:\nxp folder.

Parent topic:Known issues

New project wizard compile failure e}

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.

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.

Parent topic:Known issues

Only FreeRTOS is tested for RTOS support

This release only supports the FreeRTOS kernel and a bare-metal non-preemptive task scheduler.

Parent topic:Known issues

Disabled pairing and bonding for most sensor applications

Most sensor applications have pairing and bonding disabled to allow a faster interaction with mobile applications. These two security features can be enabled in the app_preinclude.h header file.

Parent topic:Known issues

Bluetooth LE

TX data path integrity is not guaranteed during the Bluetooth LE handover.

Some instabilities may occur in demanding Bluetooth LE connection scenarios (such as mutiple Bluetooth LE connection, very short Connection Intervals), and in some Channel Sounding configurations.

Bluetooth LE controller:

Max number of connections supported : 8

Potential instabilities particularly with short Connection Intervals

Channel Sounding (CS) not supported:

  • RTT with Random sequence

  • RTT Random sequence NADM

  • TX SNR

  • LE 2M 2BT PHY

  • More than one CS procedure in parallel

  • Potential instabilities with small CS offset or small subevent interval

Note: Documentation may not be fully updated to refer to MCX W72 devices.

Parent topic:Known issues

Other limitations

  • Zigbee: incorrect randomization of transmission CCA backoff may cause packets to be missed by receiver nodes or procedure retry.

  • Documentation may not be fully updated to refer to MCX W72 devices.

  • Low Power configurations are not supported for Bluetooth LE Reference Design and IEEE 802.15.4, (Zigbee/Thread) stacks in this release.

  • GenFSK Connectivity_test application is not operational with ARMGCC compiler.

  • GenFSK Connectivity_test application is not operational with Low Power enabled.

  • Serial manager is only supported on UART (not I2C nor SPI).

  • The --no-warn-rwx-segments cannot been recognized on legacy MCUXpresso IDE versions.

    The --no-warn-rwx-segments option in MCUXpresso projects should be manually removed from the project settings if someone needs to use legacy (< 11.8.0) MCUXpresso IDE versions

  • If the FRO32K is configured as the clock source of Core 0 then the debug session will stuck in both IAR, MCUX CMSIS-DAP while debugging. Use a lower debug wire speed, for example 1 MHz instead of the default one.

    In IAR, the option is in Runtime Checking -> Debugger -> CMSIS DAP -> Interface -> Interface speed.

    In MCUXpresso IDE, the option is in LinkServer Debugger -> Advanced Settings -> Wirespeed (Hz).

  • If the configuration tool is used to clone tfm-related projects, there is a problem that region_defs.h cannot be found in the cloned project.

  • Low-power configurations are not supported.

  • Not supported features:

    • Platform low power modes not fully enabled in this release.

    • FRO32K mode not fully supported in this release.

  • Low power reference design applications do not work properly with armgcc toolchain

  • NBU core can enter in hardfault if a call to PLATFORM_NbuApiReq()(mainly used by Controller_xxx APIs) happen while the NBU is sending a HCI message

  • Some connection event can be missed by the nbu core when asynchronous wake up are also triggered from the host

Parent topic:Known issues s

Latest MCUX IDE 24.9.25 cannot support MCXW72 multicore compiling

The latest MCUX IDE 24.9.25 cannot support MCXW72 multicore compiling, users need to upgrade to the Linkserver_24.10.22 or higher version, and change the LinkServer path configuration in the MCUX IDE. Two ways to change the LinkerSever path in the MCUX IDE.

Option 1 (recommended): Using the custom Path

Option 2: Using the command-line to change the settings

  1. Close the MCUXpresso IDE if it is open.

  2. Execute the following command:

    <path_to_MCUXpressoIDE_installation_folder>\ide\mcuxpressoide -application com.nxp.mcuxpresso.headless.application -nosplash -run set.config.preference com.nxp.mcuxpresso.core.debug.support.linkserver:linkserver.path.default_path=<path_to_LinkServer_installation_folder>

    where:

    • <path_to_MCUXpressoIDE_installation_folder> is the folder where the MCUXpresso IDE is installed.

    • <path_to_LinkServer_installation_folder> is the folder where the new/custom LinkServer is installed.

Example:

C:\NXP\MCUXpressoIDE_24.9.25\ide\mcuxpressoide -application com.nxp.mcuxpresso.headless.application -nosplash -run set.config.preference com.nxp.mcuxpresso.core.debug.support.linkserver:linkserver.path.default_path=c:\NXP\LinkServer_24.10.15

Parent topic:Known issues