INPUT CAPTURE using DMA || Measure High Frequencies and Low Width 

THANK YOU;;;;;;;;;;;;;;;;;;;

Hello can you please explain your suggestions in a more clear way? I have trouble to understand it.

@@Gruftgrabbler I'll give you an example for STM32G051, but most STM32 timers can be configured this way. First, open Cube and go to Timers configuration. Select TIM1 and choose Slave Mode = Reset Mode and Trigger Source = TI1FP1, this will reset timer by signal on TIM1_CH1 pin. Select "Channel 1" = Input Capture direct mode, this will use TI1 as capture signal for CC1 channel. Select "Channel 2" = Input Capture indirect mode, this will also use TI1 for CC2 channel. Now, in configuration for Channel 1 select polarity = rising edge, for channel 2 = falling edge. In DMA settings add two DMA channels for TIM1_CH1 and TIM1_CH2. Configure both DMA in Circular mode with Data Width = Half Word. The way it works, is that rising edge of PWM signal on TIM1_CH1 pin captures PWM period in CC1 and resets timer to 0. The falling edge of the same signal captures pulse length in CC2. The DMA then transfers captured values into two memory locations. Since DMA is configured in circular mode next capture will override previous values in the same locations. To start he process you use HAL_TIM_IC_Start_DMA with an address of first memory location, e.g. uint16_t period, and again with address of second location, e.g. uint16_t duration. Whenever your program needs data, you simply do duty = (100*duration)/period. Note, that you need to deal with zero values when there are no pulses. Also some MCUs support dedicated PWM capture mode, that does all of this automatically for you, but it can be tricky to make work, so I prefer the above method.

@@dmitrymarukh6857 I can't thank you enough for this information. I am just starting my journey with STM32 and this is a hidden gem! Tried and worked. I used duty = (100*(duration+1))/(period+1), as I was thinking the counter started from 0. I wonder if this is correct or not...

​@@dmitrymarukh6857 Ah I understand. Thank you very much for the accurate explanation. This will be a very good reference for future ones. In my own project I am measuring the duty cycle of a 1Mhz signal using the "PWM Input" Mode of a Timer. (Using a STM32G4 series) It is a very elegant solution but also has the downside of consuming a lot of cpu time. According to my understanding it basically does the exact same thing as you described. However I think the advantage of doing it manually is that you can increase the DMA buffer size and avoid triggering the ISR so often. Saving the captured CCRs in a buffer and later doing some stuff with it when the buffer is full. Is that something you would agree? In my application I am using a workaround where I disable the corresponding global Timer interrupt after a rising edge occurs and I am enabling that in a second timer which runs on ~1/10 of the pam frequency and which is also doing the actual math. Yeah this is throwing away a lot of possible readings but right now I am currently satisfied with this workaround, I might upgrade that later on.

Not to mention that the code itself is pointless. All that scanning and averaging is only there because the timer is not configured to automatically reset on rising edge

can you help me explain more detail sir, thanks

With stm, i have around 4 years..

If you use the simple method I've described in my comment, STM32F446 can capture up to 14 PWM signals, depending on the package. TIM1-5 and TIM8 two signals each, and TIM9/TIM12 one signal each. 64-pin RE package may not have all of them available due to pin multiplexing.

i use STM32F103 so the maximum Preriod is 65535 but it still get the riseData with uint32_t type. How it can be?

It was HAL_TIMex_PWMN_Start

@@ControllersTech but I again got error with this function; it seems STM32 HAL library doesn't have this function, what can I use instead?

That is why I replaced it in the video.

@@ControllersTech I get weird output with "HAL_TIM_PWM_Start" too, I'm using STM32F103C8T6

Thanks for your responding

If you are capturing a low frequency pulse, it will take some time for it to collect the required number of samples..

@@ControllersTech I capture 1 MHz, as in the example. TIM2 - 54MHz count up to 65535.

Use small frequency for timer..

@@ControllersTech I tried that, I'm hoping to use the 16 bit timer for this task, I've only successfully tested timer 2 (32bit), I'm also using a STM32F4...