This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220SF: SPI and SOCKET communication in parallel

Part Number: CC3220SF

Hello!

1、I have A program that starts two threads. Thread A initiates SPI transmission Master,20000000Mhz, Block mode. After SPI transmission is completed, thread B is notified to initiate Socket transmission, and thread A starts SPI transmission again.

This can easily trigger SL_DEVICE_EVENT_FATAL_DRIVER_ABORT. There is no documentation that says this is a conflict.

I don't have this problem when I use SPI and Socket sequentially within a thread, but it doesn't take full advantage of the network bandwidth, only SPI and Socket concurrency can improve efficiency.

2、

If SPI and SOCKET communication can be transmitted in parallel, it seems that NWP also uses SPI.

My application is to use SPI interface to read the chip data and send it to the network server. How to realize this requirement efficiently? Thank you!

  • There is one SPI (master or slave) interface that is reserved for the application.

    The 2nd instance is reserved for the NWP to access the external flash.

    They can work in parallel.

    Please double check that your application doesn't cause starvation for one the threads (it seems like it may be impacts SL Task thread).