Accurate timing of events - SPI DMA

[sreyas40]

In the above image (logic analyzer) , SPI in DMA was supposed to start at the end of high on the second signal, but it starts a bit later. (3rd signal CS of SPI, 4th signal SCLK)

And the SPI was to supposed to be active at every period (the first signal) whose period is 8.607us. 

The second signal is a slave timer to the first and a period elapsed callback of this signal call HAL_SPI_Receive_DMA.

There is also a 1 second timer

What should i do to correct this? I don't how to proceed, any solutions, learning materal would be really helpful

[Imen.D]

Hello @sreyas40 

I advise you to follow the SPI example and available with STM32CubeH7 MCU package, which shows how to perform SPI data buffer transmission/reception between two boards via DMA:

Eg:STM32CubeH7/Projects/NUCLEO-H743ZI/Examples/SPI/SPI_FullDuplex_ComDMA at master · STMicroelectronics/STM32CubeH7 · GitHub

[sreyas40]

@Imen.D 

The example gave me a few more ideas to improve the code, earlier i wasn't checking the state of SPI state before calling again.

Now during a cycle SPI triggers at same time and finishes before next cycle, but from the interrupt it takes 6.5us to trigger SPI in DMA mode. Why is it taking that much time, i dont have anything else going on in the code, i haven't even written logic to process the receieved values. 

And it's still not getting triggered for every cycle, anything else to look out for

 

edit: i don't think it worked because initially at the moment of start ,spi happens within the cycle, but with time spi creeps into the next cycle :(

 

 

 

@TDK 

[TDK]

> SPI in DMA was supposed to start at the end of high on the second signal, but it starts a bit later. (3rd signal CS of SPI, 4th signal SCLK)

There will always be some delay between the event and SPI starting, especially if you're doing it with the CPU as in the code. If you're transmitting a few bytes, you could use DMA to reduce this, but not eliminate it.

[sreyas40]

I'm using SPI in DMA , but as of now , it takes 6.5us to start SPI , that's a bit long right.

CPU at 480MHz

[TDK]

If HAL is not fast enough, you can try compiling with higher optimization settings. If that is insufficient, you will need to write your own driver.

You haven't specified what is good enough. It will never be 0 us, so what is sufficient? Unclear how the "trig" variable is getting set. You could be losing all your time there--between it getting set and calling HAL_SPI_Receive_DMA. I suggest toggling a pin just before calling HAL_SPI_Receive_DMA to measure the approximate delay native to HAL_SPI_Receive_DMA.