SPI Slave problems with nRF51822

RE: SPI Slave problems with nRF51822

Szabolcs Székelyi — Sun, 23 Oct 2016 16:06:06 GMT

So it works now. Lessons learned:

On the slave side you have to call SPISlave::reply() for each transaction before receive() and read() would work.
On the master side you have to pulse the NSS signal for every transaction (set to low before sending and high afterwards). Just connecting it to GND will not work.
SPISlave::frequency() has no use. No surprise, since the clock is generated by the master.

Steven Kim — Sun, 23 Oct 2016 08:42:14 GMT

i found before similar problem on mbed site,

and can are you check the format and frequency?

*The default format is set to 8-bits, mode 0, and a clock frequency of 1MHz

thanks :)