Known issues {#known_issues}

Maximum file path length in Windows 7 operating system {#known_issue_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 {#known_issue_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.

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 {#known_issue_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

Bluetooth LE {#topic_igj_dsw_dbc}

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.

Bluetooth LE controller:

  • Max number of connections supported : 8

  • Potential instabilities particularly with short Connection Intervals

Parent topic:Known issues

LIN New Project Wizard (NPW) issue {#known_issue_npw_issue}

  • The lin (LIN Driver) and lin_stack (LIN Stack Driver) drivers components should not be enabled at the same time while creating the new projects in MCUXpresso. Otherwise there will be the compiling issue.

  • The lin_stack (LIN Stack Driver) is not actually a driver. It is an adapt layer for LIN Stack middleware to adapt to the low level lpuart driver and cannot be used in NPW alone. So, select the LIN Stack middleware and then the lin_stack is selected automatically since it is required by LIN Stack middleware. Besides, customer need to add the lin_cfg.c/h in application layer for user definition of frame data and add FSL_SDK_LIN_STACK_ENABLE=1 in MCUXpresso preprocessor, otherwise the compiling of LIN Stack will report error.

Parent topic:Known issues

Flash ROMAPI {#known_issue_flash_ROMAPI}

Note that:

  • If using ROM API for internal flash or SPI NOR operation, reserve RAM location 0x200030A0 - 0x200032CF (0x300030A0 - 0x300032CF).

  • If using kb API, reserve 0x20002000 - 0x200032FF (0x30002000 - 0x300032FF).

Parent topic:Known issues

Other limitations

  • The following Connectivity Framework configurations are Experimental and not recommended for mass production:

    • Power down on application power domain.

    • XTAL32K less board with FRO32K support.

    • FRO32K notifications callback is for debug only. Application shall not execute long processing (such as PRINTF) as it is executed in ISR context.

  • A hardfault can be encountered when using fsl_component_mem_manager_light.c memory allocator and shutting down some unused RAM banks in low power. It is due to a wrong reinitialization of ECC RAM banks. To be sure not to reproduce the issue, gPlatformShutdownEccRamInLowPower should be set to 0.

  • 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 the CM33 Core then the debug session will block 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).

  • Low power reference design applications are not supported for the armgcc toolchain from zip archives. Please use MCUXpresso IDE or IAR toolchains for development using these applications.

Parent topic:Known issues