STM32CubeMX (MCUs)

Hello,I want to enable thread safe APIs in a CubeMX configuration. When working with STM32F7, after RTOS enabling, the <NO_SYS (OS Awarness)> option has been automatically enabled so I could enable <LWIP_SOCKET (socket API)> option as well.Now I want to try it on STM32H7 but after RTOS enabling the option <NO_SYS (OS Awarness)> stays disabled. Is there something I am missing? Thank you in advance!

I have installed Version 1.11.0 from STM32CubeIDE and have to install an older toolchain for my stm32H7 project. But Toolchain Manager throws the error "Failed to fetch the toolchain list, please check your network settings."In the thread behind this link Employee Julien D say that this is a known error, but in my case I'm not able to choose a new toolchain. Is there a workaround for this problem?

STM32CubeMX 6.11.1 was released on st.com as well as an in-tool update patch. Main issues fixed in this patch: Ticket 176645 : STM32CubeMX V6.11.0 has lost the "JTAG (5 pins)" debug mode for all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers. Ticket 176638 : STM32CubeMX V6.11.0 has lost 3 modes for all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers on ADC3 Ticket 176658 : STM32CubeMX V6.11.0 is not generating the call to "HAL_PWREx_EnableVddA()" function for STM32U5 series. Ticket 177071 :  Compilation error related to MX_FLASH_Init() function for STM32H5 series. Ticket 176763 : An issue affects ADC oversampling when writing OVSR bits for all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers. Ticket 177285 : An error occurs when switching the timebase source from SysTick to a timer for the STM32C0 series. Check the errata under this link for more details. Where do I obtain STM32CubeMX 6.11.1 ? STM32CubeMX 6.1

hello, Dose anybody have solution why Ethernet shut down randomly every few days? i'm working on ethernet (UDP/IP) without RTOS in keil, stm32cubeMX some old versions 5.4.0 FW versions 1.5.0 work fine but if i send data continuously for 5-6 days then the ethernet stop working and in newer stm32cubeMX 6.6.0 FW version 1.11.0 even ping doesn't happen.

Hi there,I'm trying to use an NHD-2.7-12864WDW3 model OLED LCD that has SSD1322 driver. Im using m68 parallel interface.The MPU im using is Nucleo-F072RB and im using CUBEMX for adjusting it's settings and using KEIL IDE for coding. Whatever i done i cannot make it work and i don't know what is causing this problem. Can u guys help me pls? Here is my codeThis is for functionsvoid send_to_lcd(char data, int dc) { HAL_GPIO_WritePin(D7_GPIO_Port, D7_Pin, ((data>>7)&0x01)); HAL_GPIO_WritePin(D6_GPIO_Port, D6_Pin, ((data>>6)&0x01)); HAL_GPIO_WritePin(D5_GPIO_Port, D5_Pin, ((data>>5)&0x01)); HAL_GPIO_WritePin(D4_GPIO_Port, D4_Pin, ((data>>4)&0x01)); HAL_GPIO_WritePin(D3_GPIO_Port, D3_Pin, ((data>>3)&0x01)); HAL_GPIO_WritePin(D2_GPIO_Port, D2_Pin, ((data>>2)&0x01)); HAL_GPIO_WritePin(D1_GPIO_Port, D1_Pin, ((data>>1)&0x01)); HAL_GPIO_WritePin(D0_GPIO_Port, D0_Pin, ((data>>0)&0x01)); HAL_GPIO_WritePin(DC_G

I'm a new user to STM32CubeMX. I tried to generate code for IWDG on the STM32F746NGHx and the pProject Manager Setting dialog appeared saying 'The Firmware Package (STM32CU FW_F7V1.17.1) or one of its dependencies required by the Project is not available in your STRM32CubeMX Repository. Do you want to download this now? Yes or No."I click Yes and a User Authentication Manager dialog pops up and saying "Please login to download a software package. 'OK'"I click 'OK' and a box appears with a spinning icon and message "Loading.... please wait."Then a User Authentication Dialog appears with 5 undulating blue lines appear. This eventually times out.Then the dialog Authentication Error Manager appears saying "Connection lost... Try check the network etc,."The same thing happens when I click the myST icon and try to log in.I'm clearly missing something very fundamentally that isn't intuitively obvious to me being a first time user. Please advise.  Thank you,  scotte

I've been using CubeMX for the last 2.5 years and am in the process of updating our ioc files to the latest version of the CubeMX software, the latest STM32 Firmware and to use AzureRTOS rather than the old ThreadX and NetX releases from Express Logic.Whilst I am familiar with being able to set a custom path for the STM32 Firmware in Project Manager -> Project -> Mcu and Firmware Package -> Fimware Relative Path to: C:\ThirdPartyCode\STM32Cube\Repository\STM32Cube_FW_F4_V1.28.0 for example I cannot work out how to set a custom location for other packages such as AzureRTOS.As such the IAR project files that are generated then contain include paths to X-CUBE-AZRTOS-F4 under the local user directory. For example:C:/Users/Developer/STM32Cube/Repository//Packs/STMicroelectronics/X-CUBE-AZRTOS-F4/1.1.0/Middlewares/ST/netxduo/common/drivers/ethernet/C:/Users/Developer/STM32Cube/Repository//Packs/STMicroelectronics/X-CUBE-AZRTOS-F4/1.1.0/Middlewares/ST/netxduo/common/inc/C:/

Hi. I am selecting for chip upgrade. In the database content of STM32H743ZG, the SPI interface characteristics section says that the VOS level should be set to VOS1 as shown in the picture, but I chose rev.V to use the main frequency 480 MHz. So my VOS level is estimated to be VOS0. can't I use spi properly?  Or, It means that VOS level is changed from VOS0 to VOS1?Sorry for not speaking English well. If you have any questions, please ask me.Additinal, is there a lot of difference between rev.Y and rev.V other than the max main frequency?Thank you.  

in https://www.st.com/content/st_com/en/products/embedded-software/mcu-mpu-embedded-software/stm32-embedded-software/stm32cube-mcu-mpu-packages/stm32cubef4.html there are the MCU package and the patch, the first can be installed from CUBE IDE with "manage embedded software packages" but when I select the second the tool says that is not a compatible file

use STM32CubeMX to get the initialization code，but UART9 not work，use the LL LibraryUART9 initializationvoid MX_UART9_Init(void) { LL_USART_InitTypeDef USART_InitStruct = {0}; LL_GPIO_InitTypeDef GPIO_InitStruct = {0}; LL_RCC_SetUARTClockSource(LL_RCC_UART9_CLKSOURCE_PCLK1); // __HAL_RCC_UART9_CONFIG(RCC_UART9CLKSOURCE_PCLK1); // __HAL_RCC_UART9_CLK_ENABLE(); /* Peripheral clock enable */ LL_APB1_GRP2_EnableClock(LL_APB1_GRP2_PERIPH_UART9); LL_AHB2_GRP1_EnableClock(LL_AHB2_GRP1_PERIPH_GPIOD); /**UART9 GPIO Configuration PD14 ------> UART9_RX PD15 ------> UART9_TX */ GPIO_InitStruct.Pin = LL_GPIO_PIN_14 | LL_GPIO_PIN_15; GPIO_InitStruct.Mode = LL_GPIO_MODE_ALTERNATE; GPIO_InitStruct.Speed = LL_GPIO_SPEED_FREQ_LOW; GPIO_InitStruct.OutputType = LL_GPIO_OUTPUT_PUSHPULL; GPIO_InitStruct.Pull = LL_GPIO_PULL_NO; GPIO_InitStruct.Alternate = LL_GPIO_AF_11; LL_GPIO_Init(GPIOD, &GPIO_InitStruct); USART_InitStruct.PrescalerValue = LL_USART_PRESCALER_DIV1; USAR

Hello, when I try to update and restart the software I get the following error on multiple machines:

Hi All! Using STM32CubeMx 6.11.1, and the STM 32L475 processor, I have successfully configured UART 5 to use DMA with interrupts on TX and just interrupts (no DMA) on receive. But whatever I do, STM32Cube seems to generate these lines: /* UART5 interrupt Init */HAL_NVIC_SetPriority(UART5_IRQn, 10, 0);HAL_NVIC_EnableIRQ(UART5_IRQn); which I don't want - enabling the interrupts before certain initialization is not what I want. On the NVIC category, and tab 'Code generation' I have unchecked the 'Generate Enable in Init': I have tried removing the use of DMA but still get this interrupt initiailization. Any ideas on what could be happening and how I can stop this interrupt initialization occuring? Thanks.

Attempting to create a project to access the onboard QuadSPI NOR flash (MX25R6435) on the SM32L4S5 Discovery kit. In STM32CubeMX, select the MX25R6435 under QuadSPI HAL says there is no QuadSPI HAL flash driver available, even though the stm32l4xx_hal_qspi.c file available in the repository.Any work arounds?

Hello,Getting a lot of these warnings in the ST generated code - prefer to be warning free, so legitimate, application code warnings are more obvious. I don't see the ability to suppress individual occurrences, and don't want to remove -Wregister completely.  Is there any alternative?Please advise,Robert  

STM32CubeIDE 1.10.1STM32CubeMX 6.6.1-RC2 In CubeMX -> Project Manager -> Code Generation there is an option to generate separate file pairs for the peripherals. These files are generated in the Core\Inc and Core\Src folder. Is there a way to have the generated in a separate directory? Ideally I would have them in Drivers\MX. Thanks in advance!

In the X-Cube Display Package there is a HelloWorld Application for X-NUCLEO-GFX02Z1 with a NUCLEO-H723ZG. Is it possible to change it in a way to make it on Nucleo-H755ZI-Q running?Otherwise, is there a step by step manual to get the display X-NUCLEO-GFX02Z1 on a Nucleo-H755ZI-Q running?Or is there an already exisiting project to download?Since I programmed everything with the Nucleo-H755ZI-Q I would like to stay on this system. Is there another display to get fast running on a Nucleo-H755ZI-Q? 

Hi guys!Still live and kicking, thanks God! My fist public version was/is vscode_nucelo_l152re (totally uninspired, I am bad with naming things) that is a visual configuration tool for the Nucleo_L152RE board and generates code that uses the old SPL driver (it provided code for LL driver, but I had to avoid clashing with CubeMX). The need for this tool come from a kind of fight with STM over the ... well, old forum people might remember the "incident" and I am not here to discuss about that. https://gitlab.com/funlw65/vscode_nucleo_l152reWhy I am here again? Well ST Community forum is pushing these notifications from time to time, nice from their part and is also nice from my part to respond in a way or another.What I am doing right now? I'm working on the next version of visual configurator for Nucleo boards and this time will generate code for the opencm3 driver, to "get rid of the heritage". No LL, no SPL. And available only for the Linux world. With a blog here that I should update

Hi,I have just updated to CubeMx 6.7 and now my stm32H755 nucleo board shows error while setting to 480MHz. I'm pretty sure that this board can run this fast before.Did the new CubeMx break clock config feature for H7 devices? There is also this crazy aliasing issue with the UI refresh while I move the mouse to select the option. Does anyone know how to get rid of this? Thank you.

I need help on some pointers or directions on how to setup virtual com port for my STM32F769I-DISCO kit.So I search a couple of youtube videos on how to setup virtual com port using STM32 CubeMX. Although the videos were for different MCUs. I followed the same steps but not successful. I could not see new virtual com port in my device manager (windows 10 OS). And also, my display graphics looks corrupted. The steps I follow basically :Enable HSE clock with Crystal/Ceramic ResonatorOn USB_OTG_FS I select mode Device_OnlyOn USB_Device I select class for FS IO to Communication Device Class (Virtual Port Com)Go to clock setup and accept whatever the default automatic fix by CubeMX.Generate code and rebuild and run on targetSo my questions :Is there official docs from STM how to configure Virtual Com Port?Are the steps to configure it different for each MCU?

Hello, I have a very simple code written with earlier versions of CubeIDE and FW_F4_1.26.2 for STM32F405rgt6It is a very simple code, just sending a message via USB as a CDC Device . If I download the old .elf file to controller, everything works fine, but windows won't see the device nor get the messages when I compile it with 1.28.0 FW .Is there a difference with usage? Or is there a bug with this?Here is the code. 

Hello,  Currently having a frustrating issues where users in my office cannot log in to ST via the Cube. Meaning we have to download it manually. We are not running a proxy. When we try to go to log in we just get a loading screen. On Windows we then get the message Connection Lost.Please Advise how to trouble shootThanks Alister 

Hello, I am new at the STM32 World. I started to buy a nucleo-f767zi and it worked fine. I was not able to get the debug Console running. Like other too. Because of that I bought the extension Board  x-nucleo-GFX02zi which should be working fine with the F767ZI.  Now I tried with CubeMX to installed the Hello World Example provided.But now I get the Message that these Packets is not Support with CubeMX 6.11. It should be support by Version 6.7 until 6.8.2.I tested 6.8.2 and 6.8 but without any changes. It seams like the SPI does not fit together. Always I got no solution found. Does the GFX02zi can be used with the F767ZI? Or do I have to everything new.  It is possible to fix this dependencies? These are related to Q-SPI and Memory Access.  Thanks for any help best regardsCarsten  

Hello CubeMX/CubeIDE users.  From the time period of May 14 to May 17, 2024, some users have faced issues when connecting to the ST network while using CubeMX or CubeIDE.Some examples were issues downloading firmware packages using STM32CubeMX and STM32CubeIDE tools, or logging in to myST through the software. The misbehavior in one of our servers that lead to the failed connection attempts was identified and fixed. The login mechanism is now working as expected. We apologize for the inconvenience faced by all the CubeMX/CubeIDE users. In case of login or download issue, we refer to the following article on how to set the “Network connection” for the tools: How to set the network connection parameters for STM32CubeIDE If you still face issues, contact us or reply to this post so we can provide support. KR,Semer.

"I am setting up the clock for 32.768kHz, but when I compile and test it, it doesn't work. I place a simple counter in the while loop, but it doesn't increment."i have in the while a counter, but not increment. 

Hi all!Where do I find the "true" version number for the CMSIS-RTOS code "injected" by CubeMX?While STM32CubeMX (v6.9.1) shows "2.0.0"..... the header file in my project (CMSIS_RTOS_V2/cmsis_os.h) has the following in the comment header* $Date: 10. January 2017* $Revision: V2.1.0** Project: CMSIS-RTOS API* Title: cmsis_os.h FreeRTOS header filefollowed by a version history, clearly mentioning Version 2.1.0.Is the cmsis_os.h header file the "proper source of truth"? Or is it a different file?The most recent revision history can also be found here: https://arm-software.github.io/CMSIS_5/RTOS2/html/rtos_revisionHistory.html (but that's of course independent of the version from what I am using). Cheers