[69] SPIM: STOPPED event might not be generated in suspend state

nRF54LS05B Engineering A Errata

This anomaly applies to Engineering A, build code QFAA-Axx.

Symptoms

The STOPPED event is not generated.

Conditions

SPIM is configured with IFTIMING.RXDELAY > 0, and the STOP task is triggered after DMA.TX.MAXCNT number of bytes of TX data has been transferred to SPI peripheral, but before the final RX byte has been received.

Consequences

The STOPPED event is not generated.

Workaround

Before triggering the START task, write value 0x82 to the corresponding SPIM instance address offset 0xc80.

After triggering the END task, write value 0x00 to the corresponding SPIM instance address offset 0xc80.