nrf52832 SPI read transfer after writehttps://devzone.nordicsemi.com/f/nordic-q-a/20170/nrf52832-spi-read-transfer-after-writeHi, I discovered unusual behaviour in a SPI read transfer. My transfer consists of writing one byte (peripheral register address) and receiving one byte (contents of the written register address). When this transfer is executed once it goes flawlessen-USTelligent Community 13Sun, 05 Mar 2017 20:13:06 GMTRE: nrf52832 SPI read transfer after writehttps://devzone.nordicsemi.com/thread/78584?ContentTypeID=1Sun, 05 Mar 2017 20:13:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c9ce2e83-5c0a-4b14-b5b2-c911e2799d54Roger Clark<p>Check the API docs, I dont think the value of size should be 1, it should probably be 2 in this case</p><div style="clear:both;"></div>RE: nrf52832 SPI read transfer after writehttps://devzone.nordicsemi.com/thread/78583?ContentTypeID=1Sun, 05 Mar 2017 14:03:32 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b7d913e0-06df-4580-aafa-fb8e9e0c2ca9jroorda<p>Yes, I checked that. The problem also exists when not using &#39;size&#39; but hardcoding it to 1.</p><div style="clear:both;"></div>RE: nrf52832 SPI read transfer after writehttps://devzone.nordicsemi.com/thread/78582?ContentTypeID=1Sun, 05 Mar 2017 10:07:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:783445ae-a4e2-4e9c-a5fe-15751c9ce596Roger Clark<p>Have you checked what the value of &quot;size&quot;</p><div style="clear:both;"></div>