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.

CC2652P: SPI clock starts delay too long after SPI_transfer() called.

Part Number: CC2652P


Hi, I use CC2652P, simplelink_cc13x2_26x2_sdk_4_40_04_04, CCS10.2

I test the spi performance using code as below:

I use led on and off to cover SPI_transfer().

I test led pin and spi clock pin, the waveform is as below:

In the picture, the yellow waveform is led pin (low when led on), the blue waveform is spi clock.

From the picture, I find there is a 7us delay between led on and spi clock starts. Also a 5us delay between led off and spi clock stops.

Now my application is sensitive to this 7us delay and 5us delay, and I need to make them short as soon as possible (Of course the delay can not be 0 to satisfy SPI timing sequence).

This delay is too long for my application. 

And I tested another platform,the delay between cs pull low and spi clock is about 1.3us.

However, the API SPI_transfer() is the lowest layer which I can see, under this API, there is no source code.

So, could you help me with this?

Thanks.