No SPIM Stopped Event

RE: No SPIM Stopped Event

abkirchhoff — Mon, 08 Aug 2016 12:38:40 GMT

Thanks for the workaround ideas. The timeout is a good idea as my SPI transfers are fairly short. My current solution that seems to be working is to use the NRF SPI driver to attempt a zero-length transfer, which starts and stops the SPI module.

RE: No SPIM Stopped Event

abkirchhoff — Mon, 08 Aug 2016 12:33:55 GMT

I am using the nrf_drv_spi driver. However, I am using a PPI channel to trigger the start of the SPI transfer, so I only use the driver to setup the transfer. When I tear things down, I want to make sure the SPI module is stopped.

RE: No SPIM Stopped Event

Stefan Birnir Sverrisson — Mon, 08 Aug 2016 10:27:12 GMT

Are you doing this without the help of the nrf_drv_spi driver?

RE: No SPIM Stopped Event

Stefan Birnir Sverrisson — Mon, 08 Aug 2016 10:27:01 GMT

Hi Austin

I agree that the PS indicates that stopped event should always be triggered when SPI is enabled, even though the start task has not been called. If it is the case that STOPPED event is not fired when SPI is not started, then I suspect you could update a status register is_started so you will know when the SPI is actually started or stopped. Another option would be to have timeout for the stopped event to arrive, perhaps a few milliseconds timeout. If the timeout expires, and the STOPPED event has not arrived after calling the STOP task, then you can assume the SPI has stopped.