STM32CubeMX (MCUs)

Resolved! UART DMA not work with STM32F767ZI and STM32F745VE

Hi Team​UART DMA not works with STM32F767ZI and STM32F745VE.It does not transmit or receive data.​Testing same code with STM32F405 and STM32G474, UART DMA works fine.​Does anyone know why UART DMA doesn't work on STM32F?Is there anything to be care o...

Resolved! How to: CubeMX + FreeRTOS + CrossStudio

I am trying to add FreeRTOS support in an STM32CubeMX project, and import into Rowley CrossStudio.In CubeMX, I have tried all toolchains, and then import them into CrossStudio.But none of them works, and I get a ton of compiler errors.When generating...

Resolved! Bug Report on Code Generation for STM32H745 using STM32CubeMX V6.4.0

The PB7 pin is set as GPIO_EXTI7 and TIM17 is enabled for PWM output. In the generated code, the IRQ routine is generated wrongly as follow:void EXTI9_5_IRQHandler(void) { /* USER CODE BEGIN EXTI9_5_IRQn 0 */   /* USER CODE END EXTI9_5_IRQn 0 */ ...

Resolved! Dear all, I use Cube Mx to generate code for good start and I made a project with STM32F745VETx. PD8 is set as EXTI8 and interrupt is activated. PE8 is defined as normal input.

When I generate the code, Cube MX generates interrupt handler for EXTI9_5 and it is like that: /* USER CODE END EXTI9_5_IRQn 0 */ HAL_GPIO_EXTI_IRQHandler(DIN2_Pin); /* USER CODE BEGIN EXTI9_5_IRQn 1 */DIN2_Pin actually corresponds to PE8 and it is n...

Resolved! STM32CubeMx Code generation inconvenient

STM32CubeMx will generate the code as below.HAL_GPIO_EXTI_IRQHandler (GPIO_OUTPUT_PA0_Pin);But I want it to be generated as follows:HAL_GPIO_EXTI_IRQHandler (PB0_EXTI0_Pin);orHAL_GPIO_EXTI_IRQHandler (GPIO_PIN_0);The user label of the pin assigned to...

Resolved! CubeIDE incorrectly generates the initial code of EXTI handlers: namely, it substitutes the wrong names with User Labels

Resolved! LL_SPI_SetStandard created for STM32L151 although Firmware does not support this call.

Hi Folks, Currently Stm32CubeMx Generator for STM32L151 creates an "LL_SPI_SetStandard" call in spi.c which is not available for that device. That seems to be a bug here.

Resolved! Since STM32CubeF7 Firmware V1.16.1 it is no longer possible to enable ADC2 or ADC3 continuous conversion mode, when ADC1 is enabled.

I tested it with CubeMX version 6.2, 6.3 and 6.4, they all work up to STM32CubeF7 Firmware V1.16.0, but not newer versions.See also: https://github.com/STMicroelectronics/STM32CubeF7/issues/63