Skip to main content
D
DeBa92
Associate II
August 23, 2023
Question

Connection between ADC Clock and sample rate

  • August 23, 2023
  • 7 replies
  • 9693 views

Hello all,
I am a beginner in the world of STM32 programming and need a little help with the ADCs.
I am currently using the STM32H735IG Discovery Kit and CubeIDE.

For an ongoing project I am using the ADC1 to sample channel IN0.
The DMA and sampling is working fine, but i am not sure how to set up the clockrate of the ADC properly.
The ADC is currently running in Asynchronous mode with divider 1 and the sampling time is set to 64,5 Cycles.

DeBa92_2-1692797787658.png

The clock rate of the ADC is currently set to 2.34375 MHz in the Clock Configuration.
DeBa92_0-1692797213957.png
Currently i store 16 samples in my DMA buffer:

 

HAL_ADC_Start_DMA(&hadc1, (uint32_t*) ADC_DMA_buffer, 16);

 

To monitor if the the ADC is working fine I am toggling an LED on the discovery board and monitor the signal with an Oscilloscope.

 

void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc)
{
	HAL_GPIO_TogglePin(GPIOC, GPIO_PIN_3);
}

 

With the current settings I can measure a frequency of 17,36 kHz on my LED.
This value times 16 samples times 2 toggles for one pulse, should be the actual sample rate of the ADC.

Now to the problem:
When I increase the clock frequency of the AD converter, to lets say 50 Mhz, the sample rate does not change
and I don't know why. The LED has still the same frequency of 17,36 kHz. Is there something I am missing?
In my imagination I thought the clock frequency should directly relate to the sampling rate of the ADC.

DeBa92_1-1692797726816.png

I hope someone can help me with this problem.
Thanks and best regards,

Dennis

 

This topic has been closed for replies.

7 replies

TDK
TDK
August 23, 2023

The cpu is overloaded and can't keep up with the rate at which interrupts are triggered.

Increase the number of samples to 2000 and try it again.

"If you feel a post has answered your question, please click ""Accept as Solution""."
D
DeBa92Author
Associate II
August 23, 2023

Hi,
thanks for your answer.
I don't think the CPU usage is the problem.
When i reduce the sample time to 1,5 Cycles, i can even measure a frequency of over 138 kHz at my control LED.

Best regards,
Dennis

raptorhal2
raptorhal2
Lead
August 23, 2023

The ADC does 1 conversion in (sample cycles+bit resolution+3) clock cycles.

The ADC conversion time is then conversion clock cycles/clock frequency.

Your ADC conversions are software triggered, so the sample rate is determined by whatever frequency your app is able to start the conversion, which is what TDK is referring to.

I wish we would change the term Sample Cycles to PreConversion Cycles, to avoid confusion.

TDK
TDK
August 23, 2023

Probably the ADC clock is not actually changed then. Are you regenerating the code?

Call HAL_RCCEx_GetPLL2ClockFreq and verify it returns the expected value.

Looks like your ADC clock is 40 MHz based on your LED frequency, maybe 80 MHz. Does that ring a bell?

17.36kHz*2*(64.5+7.5)*16 = 39997440 Hz

138kHz*2*(1.5+7.5)*16 = 39744000 Hz

Could be I'm missing something else but not sure what it would be.

"If you feel a post has answered your question, please click ""Accept as Solution""."
D
DeBa92Author
Associate II
August 24, 2023

Hi TDK,
When i change something in the ioc file with the CubeMX view i click on save all -> Generate Code? -> Yes -> Build (Hammer Icon) -> Run (Green Play Icon).
For the HAL_RCCEx_GetPLL2ClockFreq function you mean like this, right?

DeBa92_2-1692856510210.png
Here is an overview of my clock settings, it don't really know what causes the wrong ADC clock frequency...

DeBa92_3-1692856805551.png

DeBa92_4-1692856893093.png

@raptorhal2The ADC is only triggered once in software, then it is running in "Continous Conversion Mode" with active "DMA Circular Mode". What is limiting the sample rate with this setup?

TDK
TDK
August 24, 2023

Yes, and do the values in pll2_clocks match what you expect?

If they do, not really sure what it could be.

"If you feel a post has answered your question, please click ""Accept as Solution""."
Tinnagit
Tinnagit
Senior II
August 23, 2023

Sampling Time and Sampling Rate is not related to each other director.

Sampling time is base on ADC Clock speed and how many clock does it use in conversation which ADC Clock you can set it on clock configure.

Sampling Rate is base on how many trigger does it happen in a second which you can set it by Extrenal Trigger to choose how you can control it.

D
DeBa92Author
Associate II
August 24, 2023

Hi TDK,
unfortunately i couldn't figure out how to properly set up the continuous conversion mode.
I couldn't macht up my expected sampling rate with the real measured sampling rate.
Now I have switched over to a timer based ADC trigger input, which works fine so far.
Maybe i will try to understand the continuous mode on a later point in time.

Anyway, thanks for your help.

Best regards,
Dennis

D
DeBa92Author
Associate II
August 25, 2023

Hello,
maybe I was a little bit to quick.
Even with the Timer triggering the ADC, the ADC Clock frequency has no visible influence and I don't know why.
Currently I am generating a 500 kHz PWM signal from a Timer to trigger my ADC.
I also have mapped the signal to a Output-Pin, so I can monitor the signal, which works fine.

I am still using my DMA function like before, but now with 25 samples, which i am averaging down to a single data point signal with 20kHz sample rate.

HAL_ADC_Start_DMA(&hadc1, (uint32_t*) ADC_DMA_buffer, 25);

With 14-Bits (7.5 Cycles) and an acquisition time of 64.5 Cycles this should calculate to a minimum ADC Clock Frequency of 500k * (7.5+64,5) = 36 MHz.

But even if I lower the ADC clock to the lowest possible 2.34375 MHz in den CubeMX clock configuration, I still get my 20kHz output from my ADC, which should not be possible?
Is there something I am missing?

 

Tinnagit
Tinnagit
Senior II
August 25, 2023

Even with the Timer triggering the ADC, the ADC Clock frequency has no visible influence and I don't know why.
Currently I am generating a 500 kHz PWM signal from a Timer to trigger my ADC.

- You can use timer16 instead of your pwm and use internal trigger, the event out to as external trigger for adc
and your ADC are going to start sampling every trigger event without physical connect.
if you don't use multiplexing on ADC, the scan mode is not necessary.
you should disable a adc continuous mode and enable DMA continuous request.
and So you can check every adc conversation complete by callback function : HAL_ADC_ConvCpltCallback

for the 20KHz noise that it's possible from your switching regulator or some invertor in your system.

Terms & ConditionsAccessibility statement