STM32CubeMX (MCUs)

STM32H743ZI I was trying to read multiple channels from ADC1 and ADC3. Using polling method i am able to get the values but when I try using DMA(HAL_ADC_Start_DMA(&hadc1,(uint32_t*) adc,6);) I am not getting any values.

In community they have asked to disable D cache (https://community.st.com/s/article/FAQ-DMA-is-not-working-on-STM32H7-devices). How to disable D cache globally. I made the necessary changes in the linker script. I am using system workbench for stm an...

I have setup ADC1 & ADC2 for dual mode sampling in CubeMX for the Nucleo-H743ZI, when I change the input channel for ADC2 then Cube sets the "DMA Access Mode" to disabled for both channels. Is this normal behavior?

CubeMX counts USART parity as data? A bug in CubeMX

Actually it says it counts parity bit in USART word lenght. I'm pretty sure that is not so and perhaps even not what they would actually do, and what is word in this contekst anyway.

STM32F205. I2C failed to start hi2c1, but hi2c2 is worked fine. Generated from CubeMX version 5.6.0

I use code generation tool STM32CubeMX in order to generate initiation function. However when I want to implement I2C1 I have a strange problem. STM32Cube generates all necessary initiation steps. In main function in while I try to check is someone o...

BUG report on code generation STM32L476

Hello,I have installed STM32Cube FW_L4 v1.15.1 in CubeMx.When generating new project STM32L476RG nucleo with Additional Software "STMicroelectroncs.X-CUBE_BLE1.5.0.0", a file "Core/Inc/stm32l4xx_nucleo_errno.h" is created.In top of the file, there is...

Decoding ST's "Marketing Status" entries

Hello,Can anyone provide a bit of clarity regarding ST's "Marketing Status" terminology? For example, in the STM32CubeMX MCU/MPU selector, I see the following entries for various 'H7 devices:"NA", "Proposal", "Evaluation", "Preview" & "Active". I p...

STM32F205. When generating a new cubeMX project with I2C1 (master) enabled, I2C1 transmission does not work.

when trying to call HAL_I2C_Master_Transmit returns HAL_ERROR. If I2C2 starts, then everything works

Enabling low level driver for one peripheral, includes the low level driver for RCC in GPDSC project.

But main.c contains code for the high level RCC access. Tested with CubeMX 5.6.1 and STM32L452VCTChanging RCC also to the low level driver, includes the RCC HAL driver to the project, but main.c contains the low level access

BUG: CubeMX generates erroneous SVC and PendSV handlers with FreeRTOS

CubeMX selects and will not disable code generation for SVC and PendSV interrupts. The generated empty ISR handlers in stm32f4xx_it.c conflict with FreeRTOS handlers:IOC is attached. This did not happen in other projects.Windows 10, STM32CubeIDE Vers...