STM32CubeMX (MCUs)

Error messages when trying to load .project file in STM32CubeIde v1.6.0

I have installed STM32CubeIde 1.6.0 and STM32CubeMX 6.2.0 on my Win7 64 bit PC using all the defaults and administrator rights. i have downloaded the MCU package and I am trying to run one of the projects from the Repository. The training video sugge...

How to install an STM32 expansion pack?

I was able to start a project in CubeMX from a NUCLEO board selection, GENERATE CODE and build and debug it in CubeIDE or TrueSTUDIO (depending on which app a .CPROJECT file is associated with in Windows).Now I'm trying to import 'STM32CubeExpansion_...

How to solve CubeIDE1.6.1 Frequency searched for is out of range for this VOS range in clock wizard.

Possible CubeMX clock setup bugs (STM32H7)

1) When changing HPRE prescaler only CubeMX unexpectedly changes timer clock limits.I think those limits should depend on VOS voltage which, in turn, depends on SYSCLK, rather than on post-HPRE clock. As a result, lowering timers' clock lowers the ma...

[BUG] CubeMX, STM32H723, EXTI/Input, LL drivers

STM32H723 has startup/default GPIOs configuration as "Analog mode". If i select EXTI at PE11 (and probably many other pins), CubeMX generate code which does not change pin mode from "analog" to "input" (and thus EXTI doesnt work). Tested on CubeMX v6...

The ETH on STM3220G-EVAL is not linking with demo firmware 1.3.0

The Ethernet on STM3220G-EVAL is not linking. PHY never links with demonstration firmware 1.3.0 or my own STMCubeMX generated code. The LEDs doesn't even blink. I investigated BSR and the state shows "Not linked" but also "Remote fault". The BCR is 0...

BUG: STM32CubeIDE 1.6.1 code generator fails to generate SysTick_Handler () if used with RTOS and non-systick timer as timebase source

Using STM32CubeIDE 1.6.1 with a project based on Version 1.6.0 of the STM32H7 firmware package the code generator will not generate a void SysTick_Handler (void) { method as long as according to the recommendation a non-systick-timer is configured as...

HAL GPIO pins definitions seems weird? Useless for portable code?

For example:#define IO_Pin GPIO_PIN_5 #define IO_Port GPIOAIn stm32fxxx_hal_gpio.h:#define GPIO_PIN_5 ((uint16_t)0x0020) /* Pin 5 selected */Why do that? Setting an absolute number instead defining the pin number itself (5), which could be later c...