Known Issues#
This section lists the known issues, limitations, and/or workarounds.
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>.
Parent topic: Known Issues
SEGGER J-Link debugger usage problem#
When an M core software is already running, it is possible to get HardFault or data verification issue during loading image into TCM by debugger.
The following steps are recommended to use the J-Link debugger.
Configure switch SW5 to M core boot; low-power boot. Ensure that there is no image on the boot source.
Power the board and start the debugger for use.
To restart the debugger, stop the debugger, power off the board, and repeat step #2.
eDMA examples accessing AIPS peripheral bridge memory must run through U-Boot loading method#
Non-secure access to Arm IP Bus (AIPS) must be configured in Trusted Resource Domain Control (TRDC) for enhanced direct memory access (eDMA) controller. Due to the limitation that Sentinel ROM can release TRDC only once, such examples must run through U-Boot loading method after Trusted Firmware-A (TF-A） configuring TRDC.
To make low-power boot mode work for only M core in such example, you need to implement the request of the TRDC release and configure TRDC. However, it will break the single boot mode with TF-A/Linux BSP.
The following eDMA examples need access to AIPS.
cmsis_lpi2c_edma_b2b_transfer_master
cmsis_lpi2c_edma_b2b_transfer_slave
cmsis_lpuart_edma_transfer
flexcan_loopback_edma_transfer
lpi2c_edma_b2b_transfer_master
lpi2c_edma_b2b_transfer_slave
lpuart_edma_transfer
pdm_edma_transfer
sai_edma_transfer
Examples hello_world_ns, secure_faults_ns, and secure_faults_trdc_ns have incorrect library path in GUI projects#
When the affected examples are generated as GUI projects, the library linking the secure and non-secure worlds has an incorrect path set. This causes linking errors during project compilation.
Examples: hello_world_ns, hello_world_s, secure_faults_ns, secure_faults_s, secure_faults_trdc_ns, secure_faults_trdc_s
Affected toolchains: mdk, iar
Workaround: In the IDE project settings for the non-secure (_ns) project, find the linked library (named hello_world_s_CMSE_lib.o, or similar, depending on the example project) and replace the path to the library with <build_directory>/<secure_world_project_folder>/<IDE>/, replacing the subdirectory names with the build directory, the secure world project name, and IDE name.