CTSIZE becomes 0x01 after SPI communication is completed

[pass3master]

Regarding the problem that CTSIZE becomes 0x01 after SPI communication is completed,

In our program, SPI-SR-CTSIZE becomes 0x01 after SPI communication is completed.
In that state, if we try to perform the next SPI communication, a timeout error occurs in the middle of the communication.
When SPI-SR-CTSIZE = 0, no timeout error occurs.
Is there any way to set SPI-SR-CTSIZE (= TSIZE number of frames in a session) to 0?

Translated with DeepL.com (free version)

[Imen.D · Accepted solution]

Hello @pass3master ,

Did you check if this issue related to SPI errata described in the STM32H7 errata sheet, where setting non-zero TSIZE is observed as Tx traffic, or possible corruption of last-received data depending on CRCSIZE setting.

Note that TSIZE=0 (EOT is never raised) should be used either with single data packet setting or batches always aligned with the packet setting exclusively.