It's been a while since I asked the related question, but has there been any update on this issue? I'm using the simplelink SDK version 5.30.00.03.
What I see is that in the file "npi_tl.c" in the function "NPITL_writeTL()" the code calls transportWrite() immediately before SRDY_ENABLE().
The transportWrite() function which links to "NPITLSPI_writeTransport()" in "npi_tl_spi.c" sets up the SPI transaction and calls SPI_transfer() which means that as soon as the NPI Master starts toggling the CLK, the slave will start sending the SPI data over MISO. Even if the MRDY line is not asserted.
This causes issues if trying to use a shared SPI bus because the Master will be talking to a different BLE module and yet this BLE module will still send data.
I'm struggling to modify the NPI files in a way that waits to set up the SPI transaction until after MRDY goes low. There's just a lot of layers and events being called that sometimes my attempts will work for 1 transaction but then nothing will be sent after that.
Any help or ideas would be great, thanks!