Stream Data from SPIS to S130 SoftDevice on nRF51822

RE: Stream Data from SPIS to S130 SoftDevice on nRF51822

Stefan Birnir Sverrisson — Mon, 08 Aug 2016 16:41:53 GMT

Hi jtrovato Im thinking that you could use this single RDY line to indicate that it is safe for SPI slave to send data or to indicate that the SPI slave (nrf51) has data to send. You could set this RDY line whenever there is event received from the softdevice of successfully transferred packet. Then the SPI master would transfer 20 bytes and then wait for the RDY line to be set again. In the case the SPI slave has data to send, it could also set the RDY line and the spi master transfers 20 bytes. The SPI master could set the first byte of the transaction to indicate the length of the packet (actually sending 21 bytes then), enabling the slave to transmit only valid data. If the slave has less than 20 bytes to send, it will send ORC character automatically to the master. There are also defined 5 wire and 6 wire SPI protocols which could be good to look at.

RE: Stream Data from SPIS to S130 SoftDevice on nRF51822

jtrovato — Mon, 08 Aug 2016 15:08:02 GMT

Hi Stefan, thanks for your response! I have a RDY line that is controlled by the SPI slave that indicates to the master when it is ready. The problem I am running into, is that in some situations, the slave also needs to tell the master that it has data to send, which is what the RDY is currently used for. I think I am going to need another line, so I have a RDY and REQ line for the spi slave both being ready and wanting to send data. I could implement one of these in software in the form of some type of acknowledge pack instead of RDY? With only 1 extra line on my SPI connection, what do you think the best way to do this is?

RE: Stream Data from SPIS to S130 SoftDevice on nRF51822

Stefan Birnir Sverrisson — Thu, 04 Aug 2016 16:38:24 GMT

Good questions.

For latest BLE throughput tuning advice, this thread could help. For SPIS throughput considerations, this thread could give pointers. This thread could also give some pointers on the SPIS side and also for the SPI master side.

Optimally you would want to transfer 20 byte packets and configure the softdevice for 6 packets per connection event and set the BLE connection interval to minimum 7.5ms for maximum throughput, but this may be limited by the BLE peer side as mentioned on the first link above.

Is all the data you mention in a single SPI transaction? Do you have some control over the SPI master side? Optimally, you would have control line from SPIS to SPI master, letting the slave indicate when it is safe for the master to send data. The master could send 120 bytes when it receives signal. The SPIS would get "transaction finished" event and send 6 packets of data over BLE, each with 20 bytes (fewer packets if the BLE peer device limits packets per connection event). Signal the SPI master again when the softdevice has received all the packets.