SPI Communication Problems Concerning nRF52840

[June6]

Now there is a project, nrf52840 uses SPI to communicate with other microcontrollers. Data is currently available, but it is suspected that each packet lacks a second byte. The corresponding modification of SPI mode eliminates the problem of SPI mode. Are there any other parameters that affect the results of the data?

SPI Communication Program Reference Sample Program （sdk15.0    examples\peripheral\spi\pca10040）

[hzhuxin]

I am the colleague of June6,  give more information for the problem.

We are using the SPIS sample in examples\peripheral\spis of15.3 SDK.
As show in the above Oscilloscope, the second bytes had sent after a long time after the first bytes(maybe 4.34 ms), and i read the rx_amount of nrf_drv_spis_event_t event in callback spis_event_handler, the value always is 1.
In this period, there are two bytes clk cycles(that mean clk has the  16 high low in turn) & two bytes appear there, and at the same time, the cs is low, so according the spi protocol, i should received two bytes, am i right? 

After this period, the cs cycle changed to 500us, and in one cycle, there is a clk cycle(8 high low in turn), the interval is very short(maybe 30us), these data received perfect.

Please give us some suggestion on how to get the second bytes? how to modify the program?

[hzhuxin]

Any solution avaliable?

[Edvin]

I assume that this is the same issue/question as in your other ticket?
https://devzone.nordicsemi.com/f/nordic-q-a/52719/spis-of-nrf52-could-not-read-the-data-accuracy