A piece of code from STM32CubeMX v4.25.0 and latest F1 drivers generated for STM32VLDiscovery (the button is pulled-down by external resistor):
static void MX_GPIO_Init(void)
/* GPIO Ports Clock Enable */
GPIO_InitStruct.Pin = LL_GPIO_PIN_0;
GPIO_InitStruct.Mode = LL_GPIO_MODE_FLOATING;
and the results from the Keil debugger:
So commented the line below to prove that there is only one line of code used for GPIOA initialization:
// LL_GPIO_Init(GPIOA, &GPIO_InitStruct);
and got as expected (the default settings for GPIOA)
It seems that the LL_GPIO_Init gives messy config on more than one pin. Am I wrong?
Have no luck with F1 line and LL drivers - this issue seems to be continuation of my previous finding:
So switching back to register programming when working with boards with low SRAM size. It takes less time than investigating issues in LL drivers.
I wonder if you use LL drivers for F1 line. I know that more people prefer SPL drivers for this line.