Ask questions on STM32CubeMX. Discuss code generation and configuration challenges, among other topics.
We are pleased to announce that STM32CubeMX 6.16.0 release is available. What is new in 6.16.0: Added support for new microcontrollers across the STM32WBA, STM32N6 and STM32H5 series and the STM32WL3x product line. The related new boards include the...
Hello...I am struggling (for a week now) trying to figure out how this output compare stuff works....Documentation is very poor on this and naming conventions are all over the place....I would like to gate timer15 with a pulse from timer1. I am expe...
I have a nucleo-U575ZI-Q and can run the examples for the ADCs just fine. However when I try and make my own project using STM32CubeMX the code hangs at the ADC calibration. I've gone over the settings a dozen times and compared them against the ex...
I am trying to use LWIP on the STM32H723 Nucleo board to send and receive UDP packets. I have generated code using CubeMX version 6.70 and configured it to use LWIP with FreeRTOS. I have referred to the H7 series LWIP related problems and H723 addres...
I'm trying to use USB-OTG on NUCLEO-H755ZI-Q. I first created a new project within STM32CubeIDE and set all pins to their default setting. Then, I set USB-OTG to CDC and downloaded it to my board.However, with CubeMX 6.7.0, I can not see the USB dev...
SetupSTM32CubeIde 1.10.1STM32CubeMX 6.6.1.202207061420RegardingSTM32F4/F7/H7 projects (maybe also exends to others) with Ethernet, LwIP and RTOS features activated.Especially when the WITH_RTOS flag is set in LwIP>General settings.SymptomsEthernet li...
I am trying following:1) USB CDC on M4 core Clock configuration attachedWith the help of forum I understand that Descriptor cannot be read from memory location through CM4 as per below thread:I made following change in usbd_desc.c to avoid hard fault...
I try to interface Stm32f429 usb host with printer .I try to make printer class from msc . How I write usb host handle structure and attached device structure for printer
I see no practical reasons for this behaviour. When set to interrupt mode, the pin can still be read as input pin.
