Two SPIs conflict

RE: Two SPIs conflict

Avadacadabara — Wed, 06 Jul 2022 09:50:05 GMT

Hi,

I managed to solve the problem by wirting in only one sector to flash at a time...But might not gonna work if sample rate is doubled.

Your suggestion is helpful, I'll modify the spi 2 structure for further development.

Best regards,

Ava

RE: Two SPIs conflict

Kenneth — Wed, 06 Jul 2022 09:33:23 GMT

Hi,

You can do something like:

spi2_handler()
{
spi_xfer_done = true;
}

main()
{
...
spi_xfer_done = true;
...
while(1)
{
  if(spi_xfer_done == true)
  {
    // it's possible to execute next spi2 transfer
  }
  // do other stuff
  
  sd_app_evt_wait(); // similar to WFE();
}
}

Best regards,
Kenneth

RE: Two SPIs conflict

Avadacadabara — Wed, 06 Jul 2022 01:18:15 GMT

Hi Kenneth,

Thanks for your advice.

If I managed to switch spi 2 to non-blocking mode, I'll stil need a

while(!spi_xfer_done)
{
    __WFE();
}

after each transfer right? So I thought it might be no difference from blocking mode. Or do we have any method to avoid using while loop in main?

Anyway I'll work on turning spi 2 to non-blocking mode first.

Regards,

Ava

RE: Two SPIs conflict

Kenneth — Tue, 05 Jul 2022 18:00:37 GMT

Hi,

Conseptually what you write should work. Though I don't quite understand why you want to use blocking mode for SPI instance 2, you can still call it from main() even if you are using non-blocking mode. That should free up time in main handling ble or other events, instead of just waiting for an SPI instance 2 to complete a transfer. So I suggest to look into that for a start.

In addition I am hoping you can have some GPIO's here that you can use for debugging to try to understand what is actually occuring when data is lost. E.g.

gpio1 - toggle when entering and exiting gpiote handler
gpio2 - toggle before and after spi1 transfer
gpio3 - toggle before and after spi2 transfer
gpio4 - toggle each time you are writing data to the softdevice

Best regards,
Kenneth