Known Issues

Potential build issues

CMake build failure with multiple MCUX SDK versions

Problem: If you have previously exported different versions of the MCUX SDK, you may encounter a CMake build error similar to:

CMake Error: Cannot open file for write: /devices/Wireless/RW/RW612/cmake_install.cmake.tmpa2a74
CMake Error: : System Error: No such file or directory

Root Cause: This error occurs because CMake may attempt to load an older cached MCUX SDK package instead of the most recently exported version, leading to path conflicts and missing files.

Workaround:

  1. Delete all existing MCUX SDK CMake packages from your user environment:

    rm -rf ~/.cmake/packages/McuxSDK

  2. Re-export the updated SDK by running this command in your root sdk:

    west mcuxsdk-export

  3. Clean and rebuild your project.

Windows path length limitations causing build failures

Problem: On Windows systems, compilation may fail with “file not found” errors or similar issues, even when the files exist. This is typically caused by Windows’ limitation on maximum path length (260 characters by default).

Symptoms:

  • Build failures with missing file errors

  • Compilation stops unexpectedly during the build process

  • Files that exist in the filesystem are reported as not found

Root Cause: Windows has a default maximum path length limitation that can cause issues when building projects with deeply nested directory structures or long file names.

Prevention: To avoid path length issues on Windows, follow these recommendations:

  1. Clone the SDK close to the root directory:

    • Clone the SDK as close as possible to the root C:/ drive

    • Choose a short name for the SDK directory (e.g., C:/sdk instead of C:/Users/username/Documents/my-long-project-name/mcuxsdk)

  2. Use short paths for freestanding folders:

    • When creating a freestanding folder, prefer a location as close as possible to the SDK

    • Keep the folder name short and avoid deeply nested directory structures

  3. Shorten build directory names in VSCode extension:

    • When using the MCUXpresso for VSCode Extension with build configurations other than “debug” and “release”, edit the configuration and change the build directory to a shorter name

    • This is especially important for repository applications which tend to have longer build directory paths

Kconfig string values not preserved when passed via “CMake Extra Args” (MCUXpresso for VSCode Extension)

Problem: When using the MCUXpresso for VSCode Extension, string values passed through “CMake Extra Args” in the build configuration are not preserved as expected. Specifically, when passing string Kconfig values like CONFIG_CHIP_DEVICE_SOFTWARE_VERSION_STRING="2.0", the quotes are stripped during the build process.

Symptoms:

  • String-type Kconfig overrides via “CMake Extra Args” are not reflected in the build

  • Configuration values appear without quotes or are not applied correctly

Workaround: Manually update the example’s prj.conf file when overriding string Kconfig values:

  1. Navigate to the “Project files” section in the VSCode extension

  2. Locate and open the prj.conf file for your project

  3. Add or modify the desired Kconfig string values directly in the file (e.g., CONFIG_CHIP_DEVICE_SOFTWARE_VERSION_STRING="2.0")

  4. Save the file and rebuild your project

Matter freestanding examples do not support –bf option

Problem: When creating a freestanding example for Matter using west export_app, the --bf option (which copies board files into the freestanding folder) is not supported and causes build issues with Thread configuration.

Symptoms:

  • Build failures after using --bf option with Matter examples

  • Thread configuration conflicts during compilation

Workaround: If you need to use custom board files with Matter freestanding examples:

  1. Do not use the --bf option when exporting Matter applications:

    west export_app -b <board> <matter_example> -o <destination_folder>

  2. Manually copy your board files to the freestanding folder if needed

  3. Update the nxp_sdk_reconfig.cmake file (copied by export_app) to specify the new paths to your board folders using:

    • mcux_add_include() for include directories

    • mcux_add_sources() for source files

  4. Disable default Matter board files by adding this configuration to your prj.conf:

    CONFIG_MCUX_PRJSEG_module.board.matter.board=n

Default Matter board file locations:

  • RT1060, RT1170, and RW61x platforms: mcuxsdk/middleware/matter/third_party/nxp/nxp_matter_support/examples/platform/<platform>/board/

  • MCXW platforms: mcuxsdk/examples/_common/project_segments/wireless/wireless_mcu