Known Issues

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

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.

1. Configure switch SW5 to M core boot; low-power boot. Ensure that there is no image on the boot source.

2. Power the board and start the debugger for use.

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