Hello @JWolf.5
First let me thank you for having reported :smiling_face_with_smiling_eyes:
Actually you're right, I've been able to reproduce the same misbehavior from my side when using the same configuration as you.
As you mentioned in your poste you can set the EXTSEL-bits in the code as a temporary solution while we investigate the issue.
I want to add an other solution; you can use the already declared macro to set TIM3_TRGO.
In the static void MX_ADC1_Init(void) function change make the modification showed bellow:
hadc1.Instance = ADC1;
hadc1.Init.ClockPrescaler = ADC_CLOCK_ASYNC_DIV1;
hadc1.Init.Resolution = ADC_RESOLUTION_12B;
hadc1.Init.DataAlign = ADC_DATAALIGN_RIGHT;
hadc1.Init.ScanConvMode = ADC_SCAN_DISABLE;
hadc1.Init.EOCSelection = ADC_EOC_SINGLE_CONV;
hadc1.Init.LowPowerAutoWait = DISABLE;
hadc1.Init.ContinuousConvMode = DISABLE;
hadc1.Init.NbrOfConversion = 1;
hadc1.Init.DiscontinuousConvMode = DISABLE;
hadc1.Init.ExternalTrigConv = ADC_EXTERNALTRIG_T3_TRGO; // change ADC_EXTERNALTRIG_T1_TRGO with ADC_EXTERNALTRIG_T3_TRGO
hadc1.Init.ExternalTrigConvEdge = ADC_EXTERNALTRIGCONVEDGE_RISING;
hadc1.Init.DMAContinuousRequests = DISABLE;
hadc1.Init.Overrun = ADC_OVR_DATA_PRESERVED;
hadc1.Init.OversamplingMode = DISABLE;
if (HAL_ADC_Init(&hadc1) != HAL_OK)
{
Error_Handler();
}
With this being said, this problem is raised internally to be reviewed. I'll keep you posted with the updates.
Internal ticket number: 134734 (This is an internal tracking number and is not accessible or usable by customers).
Thanks for your contribution.
Semer.