Hi,
I already tried to use the GPT driver. In principle, this worked fine (calling adcStartConversion from the callback).
But unfortunately, this approach doesn't fit for my application: For the motor power electronics need very precise timing between the IGBT gate control signal and the ADC measurement. Using the GPT driver has too much jitter.
Now, I tried to trigger the ADC conversion by EXTERNAL software trigger (instead of using TRGO of TIM3 in case my implementation is wrong).
This is the configuration of the conversion group
Code: Select all
static const ADCConversionGroup adc_commutate_group = {
TRUE, // circular mode
ADC_COMMUTATE_NUM_CHANNELS,
adc_commutate_cb,
adc_commutate_err_cb,
0, // ADC_CR1
ADC_CR2_EXTTRIG | ADC_CR2_EXTSEL_2 | ADC_CR2_EXTSEL_1 | ADC_CR2_EXTSEL_0 , // ADC_CR2: use ext event | select SWSTART event
0, // ADC_SMPR1
ADC_SMPR2_SMP_AN0(ADC_SAMPLE_1P5), // ADC_SMPR2
ADC_SQR1_NUM_CH(ADC_COMMUTATE_NUM_CHANNELS), // ADC_SQR1
0, // ADC_SQR2
ADC_SQR3_SQ1_N(ADC_CHANNEL_IN0) // ADC_SQR3
};
Trying to start the conversion by:
Code: Select all
adcStartConversion(&ADCD1, &adc_commutate_group, commutatesamples, ADC_COMMUTATE_BUF_DEPTH);
ADC1->CR2 = ADC1->CR2 | ADC_CR2_SWSTART; // Trigger the conversion!
doesn't work...
If I disable the external trigger configuration in the conversion group by replacing "ADC_CR2_EXTTRIG | ADC_CR2_EXTSEL_2 | ADC_CR2_EXTSEL_1 | ADC_CR2_EXTSEL_0)" by "0", the conversion is triggered immediately at adcStartConversion as it should (adc_commutate_cb is called).
But that is not what I want...
Although this looks very straightforward and I have no idea whats wrong there
Jörg