This post pulls together the work from prior posts on the timers, ADC, DMA and GPIU for the STM32F372.
The idea is to get the MCU to do periodic ADC measurements and store the results away on its own without needing the CPU to intervene. This means no interrupts or polling, just the peripheral blocks working together on their own. This type of design is becoming more and more common in the low power world where the CPU and its subsystem is kept asleep, leaving the peripherals to do their job with the CPU only woken when some control needs doing.
The demo works like this:
Timer 2 is set up to produce a PWM train with a 5 second period. I use 2 channels in the same counter with the same mark:space ratio settings so that the first can drive the ADC whilst the second flashes an LED so that I know something is happening…
Timer2 has a nice feature where you can set it to send a Trigger Event at each Update Event (UEV). Here I set the UEV to be when the counter spills over the period count and gets re-zero’d. This Trigger Event can kick the ADC into action causing it to do a measurement. But here’s the gotcha: not every channel of every timer can do this. On the F372, only the following:
- Timer 19: channels 3 & 4
- Timer 2: channel 2
- Timer 4: channel 4
So pick your timer carefully…
When the ADC is kicked into action, is takes a measurement and then itself can signal the DMA engine to start. The result needs storing away in memory since the ADC will over-write the last data after the next measurement.
Here is the code:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
#include "stm32f37x.h" int main(void) { int data[200]; //Array to capture ADC measurements int *pData = data; //First power up Timer, ADC, DMA and GPIO blocks RCC -> AHBENR=RCC->AHBENR | RCC_AHBENR_GPIOAEN | RCC_AHBENR_DMA1EN; // Switch on GPIO port A and DMA1 RCC->APB1ENR = RCC->APB1ENR | RCC_APB1ENR_TIM2EN; // Switch on TIM2 RCC->APB2ENR =0x200; // Start clock to ADC peripheral at bit 9 in RCC_APB2ENR //Allocate pins on GPIO // Set Alt Func mode for timer pins PA0/PA1 and analogue for PA2 (ADC_C2) GPIOA->MODER=GPIOA->MODER | (0x3<<4) | (0x2<<2) | (0x2); // Select Alternate Function 1 for PA0, AF1 for PA1 GPIOA->AFR[0] = GPIOA->AFR[0]| (0x1<<4)| (0x1); //Set up ADC1 ADC1->CR2=0x160101; // Switch on, enable DMA channel & start conversion on TIM2 event ADC1->SQR3=0x2; // Set the conversion "sequence" to be 2 channel ADC1_IN2 //Set up DMA DMA1_Channel1->CPAR=0x4001244c; // Peripheral source address for ADC->DR DMA1_Channel1->CMAR=(int) &pData; // Memory destination address DMA1_Channel1->CNDTR=200; // Number of DMA cycles DMA1_Channel1->CCR=0x981; // Set MINC mode, PSIZE=16, MSIZE=32 //Set up and start Timer2 TIM2->CCMR1=0x6060; // Enable channel 1 and 2. Set both to PWM mode1 TIM2->CCER=0x11; // Channel 1 and 2 output enable TIM2->PSC=0xfffe; // Pre-scale to 65535 TIM2->ARR=0x262; // Set period for both channels TIM2->CCR1=0x131; // Set t (high) for channel1 TIM2->CCR2=0x131; // Set t (high) for channel2 TIM2->CR1=TIM2->CR1 | TIM_CR1_CEN | TIM_CR1_ARPE; // Start Timer 2 while(1); } |
Note again I am not using the ST driver code. When you move beyond their Discovery boards, I find their code difficult to port to custom systems without bringing along the entire code base. It serves its purpose as a demo well, but not much beyond that.
It was interesting to tie the ADC input to the battery Vdd, make a couple of hundred measurements and then look at the noise on the data:
With full scale 3300mV as code 4032, 3 standard deviations on 200 data points came in at 1.36 codes or 1.1 mV. I’d like to build a power supply accurate to 10mV; should be possible with some careful low noise board design.
