SPI Transaction Manager transfer results in unexpected transaction lengthhttps://devzone.nordicsemi.com/f/nordic-q-a/69107/spi-transaction-manager-transfer-results-in-unexpected-transaction-lengthI am using the nRF SPI Transaction Manager (nrf_spi_mngr.c) and the SPI transfer (nrf_spi_mngr_transfer_t) isn&#39;t performing as expected. I expect the following code to result in a single-byte transfer, where the value &#39;0x15&#39; is transmitted, and theen-USTelligent Community 13Fri, 04 Dec 2020 13:33:35 GMTRE: SPI Transaction Manager transfer results in unexpected transaction lengthhttps://devzone.nordicsemi.com/thread/283326?ContentTypeID=1Fri, 04 Dec 2020 13:33:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8efabd76-6828-406e-803b-9d286210581eJ&#248;rgen Holmefjord<p>Hi,</p> <p>See the following errata:&nbsp;<a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev2/ERR/nRF52832/Rev2/latest/anomaly_832_58.html?cp=4_2_1_0_1_8">[58] SPIM: An additional byte is clocked out when RXD.MAXCNT = 1</a></p> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>