STM32 MCUs Software development tools

Due to issues with text selection and copy/paste in STM32CubeIDE 2.0, I reinstalled the operating system (I was previously running a beta version) and moved to a stable release (Tahoe 26.2 (25C56)) on an Apple Silicon Mac (M4). I then downloaded and installed STM32CubeIDE and STM32CubeMX. The installation completes successfully, but when launching either application, an error occurs and the tools fail to start. Has anyone experienced this issue or knows the root cause? Any insights would be appreciated.

The STM32H7RS series includes a USB HS PHY with a special PLL that generates the 480MHz clock required as well as a 60MHz clock for the OTG HS peripheral and optionally a 48MHz clock for the separate OTG FS peripheral. The PLL for the USB PHY has several configuration bitfields in the RCC->CCIPR1 register that are used to set the source of the PLL reference clock, as well as its frequency: Bits 13:12 USBPHYCSEL[1:0]: USBPHYC kernel clock source selection. Set and reset by software.00: hse_ker_ck (default after reset)01: hse_ker_ck / 210: pll3_q_ck11: reserved, the kernel clock is disabledBits 11:8 USBREFCKSEL[3:0]: USBPHYC kernel clock frequency selection .Set and reset by software.This field is used to indicate to the USBPHYC, the frequency of the reference kernel clock providedto the USBPHYC.0011: The kernel clock frequency provided to the USBPHYC is 16 MHz1000: The kernel clock frequency provided to the USBPHYC is 19.2 MHz1001: The kernel clock frequency provided to the USBP

Hello, I am using a custom environment for development and debugging for NUCLEIO-STM32F767ZI.It is based on a custom devcontainer, VSCode and gdb-multiarch. On the server side I have OpenOCD, running on a ubuntu 24.04 PC. This is connected via USB to the board. The Board itself is not changed in any way, maybe I changed jumpers at some point, I would need to check this if this might effect the behavior. The first connection after Powerup works always as expected, the Firmware is flashed and works as expected.If I rebuild the project or flash the firmware again, the MCU is in some kind of undefined state.Calls to different HAL functions fail, return Errors. As some return values are not verified within the generated calls, I don´t see the errors immediately, but very late during debugging. Missing interrupts as an example. The code is a simply generated STM32CubeMX project, without any changes. I am using only GPIOs and Systick interrupt so far. I need the right Reset com

When I build  my project in "Debug" mode all works fine, if I build the project in "Release" mode an error appears: C:/ST/STM32CubeIDE_2.0.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.100.202509120712/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: cannot find -llibarm_cortexM7lfdp_math.a: No such file or directory GCC linkerLibraries (-l):                     libarm_cortexM7lfdp_math.aLibrary search path (-L):   "${workspace_loc:/${ProjName}/Drivers/CMSIS/Lib/GCC}"    Any help ?Thank you

When creating a project in STM32CubeMX, ST ARM Clang was selected. Compilation and debugging in VSCode all work, but some variables are optimized out, which seems like the compiler optimization is set too high. However, it's unclear where to set the compile flag -O0.CMakeLists.txt like this, does not work# Define the build typeif(NOT CMAKE_BUILD_TYPE)set(CMAKE_BUILD_TYPE "Debug")set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -g -O0")endif() 

Greetings everyone,Using the C programming language, I'm creating the encryption algorithm AES-256 code for a trusted execution environment and checking to see if the hardware supports it.AES/CRYP enabling is giving me trouble. I can't find it under Connectivity or Security, and I can't enable it with STM32CubeMX.I'm getting this error, so please assist. 

HelloIf I use CubeIDE 1.19.0 there was a target board selector after starting a new project. In 2.0.0 I can not find it. Slso the GPIO config.What happens?   

Hello.Due to reasons, I had to completely reset my laptop, and I am setting up STMCubeIDE and STMCubeMX again. That said, I became used to CubeMX being integrated inside of CubeIDE and I want my project generation to include the .ioc file. Hence, I'm choosing to install STM32CubeIDE 1.19.0 (despite the documented issues and reasoning for Version 2, I have yet to encounter a serious problem that would steer me away).  That said, after reinstalling STM32CubeIDE version 1.19.0, the code generation is locked behind an error message:`Go to Help -> STM32Cube updates -> Connection to myST`. When I go to `Help->Check for Updates`, the only update available is to STM32CubeIDE 2.0.0. As I've explained above, I've been actively avoiding this version due to the removal of CubeMX integration in CubeIDE.  Seeing as this was the only update, I tried to simply go to`Project -> Generate Code`, but nothing happened.  This leads me to believe that for new install

We are using STM MCU MPN : STM32U375VGT6Q for one of our new projects, we are currently using HSE External 16 MHz crystal for system clock.We are trying to configure the STM32U375 MCU to run at 96 MHz using an HSE external 16 MHz crystal. In STM32CubeMX, we are unable to find the PLL option sourced from HSE in the clock tree on the Clock Configuration page.Could you please advise us on below points:Use HSE (16 MHz) as the PLL sourceSet the PLL multipliers/dividers to achieve SYSCLK = 96 MHz

Previous versions of cube had very nice board seelction tools.At the top of the screen was aa complete board descrription that enabled the easy selection of board features when starting a new project and wanting to see what peripherals were available on the board and chipThe current version 2.0 has very, very sparse information, inadequate to find out which boards havee what preipherals. The facility is easyt to provide since it simply references the sales literature available on the ST site.This information is not even available by double clicking on the products offered in the IDE.Furthermore, the online product selector is almost useless, there are 3 columns with identical headings under ADC converters. I presume these refer to differrent ADC capabilities, but am left in the dark as to their meaning.I understand that this might be a seldom used function, occurring once or twice in a product lifecycle, yet it is an invaluable tool.The filters are also very cumbersome when compared to

It seems like CubeMX sets this default value hspi1.Init.MasterKeepIOState = SPI_MASTER_KEEP_IO_STATE_DISABLE; when doing software NSS and SPI Mode 3 like: hspi1.Init.CLKPolarity = SPI_POLARITY_HIGH; hspi1.Init.CLKPhase = SPI_PHASE_2EDGE; hspi1.Init.NSS = SPI_NSS_SOFT; This results in a non working SPI at least on STM32H652 (did not check the signals with Oscilloscope, but I assume the CLK and/or MOSI float back to an undefined value after the first transaction, breaking the next one). This can be fixed by doing:hspi1.Init.MasterKeepIOState = SPI_MASTER_KEEP_IO_STATE_ENABLE; Wouldn't it be recommended CubeMX defaults the IO_STATE_ENABLE in this case? This one Bit just cost me 5 Hours of headache :\

Just like the normal process, I generated the H7S3L8 project using CubeMX.Then I opened the project folder with VS Code, and STM32 VS Code extension detected that it is an STM32 project.But afterward it threw a problem.It required me to manually configure the specific model of the STM32. It seems that the CubeIDE for VS Code extension did not correctly recognize the model.So I just chose the NUCLEO-H7S3L8.But when I click the 'Save and close' button, it just shows the clicked animation effect, and then nothing happens. The extension still can't properly load the project and perform automated configuration.Why is this happening?I am quite sure that other projects (such as STM32F401RCT6) can be properly recognized and loaded; moreover, if I manually go to 'Setup STM32Cube project(s)', the 'Save and close' button works normally for those projects.It seems that only the NUCLEO-H7S3L8 or STM32H7XX series has this problem, or am I the only one experiencing it?I speculate that this may b

The open source code on GitHub hasn't been updated for a long time, and many devices are unsupported. How can I get the latest OpenOCD source code? Should I contact technical support? Is there a contact email?

Hello, I recently switched to a new Macbook os Tahoe. I can't flash MCU. I see some errors pop. CubeMX detects ST link V3 minie, but can't flash it. Same come with the ST link upgrade. The old Mac with the Sequoia can do the job. Any ideas please ?

Dear community supporters,I would like to add ability to share STM32 projects platforms to my team. I have setup a server on Debian 13 and setup the STLink server tool, and using a SSH tunnel to do port forwarding from the attached STLink port on the linux server (localhost:7184) to a Windows client machine where I plan to use the STM32 Cube IDE, STM32 Cube Programmer.The tunnel is operational, and I have added a wireshark capture showing discussion from my Windows client when using the STM32 Cube Programmer, and a log from a STM32 Cube IDE debug configuration. For both, the Shared STLink is ticked, and in STM32 Cube IDE, I am able to see (the snapshot STM32 Cube IDE Debug Configuration.png shows it) the STLink SN from my remote STM32 Nucleo board attached to my linux server. Though, the STM32 Cube Programmer is unable to show the SN, seems it is unable to detect the probe devices, as shown in the st-link_gdbserver_log when starting the debug session.It seems the STM32Cube Programmer i

Hi boys and girls from ST company - capitalistic USA country, I installed your new CubeIDE 1.17 today and I ascertained that:1/ If I open a project everything is closed - no window is visible. If I try to close the project, the project is NOT closed and moreower I can even COMPILE !!! and debug and to programm the closed project :) It is very cute.Whe I was very young we had a car "Škoda MB100" (green color). It was very magic car. If there were lack of water in the main cooler and if the car engine was hot enough e.g. approx. 100°C I could remove the ignition key from ignition box, but the car engine runs gaily without stopping :)   :) :) :) :)  And this situation continued even if I removed the car battery 12V/64Ah :) :) :) :)  YES !!! 2/ I tried to change dark gray text color background in C/C++ editor and ... surprisingly ...  it is NOT possible. See video here: https://cloud.fastshare.cz/share/get/t51aVjDx2LKVKJ8U3q9YqvJM

Question 1The first image shows the toolchain configuration of my previous project, and the second image shows the configuration displayed in my newly created project. Why do I need to reinstall the toolchain when creating a new project on the same computer?Question 2I remember that when I first used the extension, these tools were all specified through scripts. However, after using it for a period of time, I found that CMake, programmer, and other tools could not find the specified paths, so I had to add them all to the environment variables. 

Hi thereI'm a little embarrassed to post this, but..  Coming from Microchip world I would just change TRISx, so simple.As I've learned so far the MX are in charge for setting up a port.But in my application I need to set a 8 bit wide port for parallel interface to a device.Also it needs to change output <> input.My first thoughts were not to tell the MX about the device on port PC0 to PC7.Then do the setup "manually" in the code.But then again I think this so common, there must be a MX way of doing this. Thank you.

Hi,If I use STM32CubeIDE 1.19 to start a new project for the STM32H755 Nucleo board, the startup assembly files in both the CM7 and CM4 sub-projects are the same file with the same contents, startup_stm32h755zitx.s.  It looks like this file is the one generated for the M7 core that just gets copied over to the M4 directory, because inside it has: .cpu cortex-m7Now, I know both cores share all the peripherals and interrupts.  But I would assume the ".cpu" definition would need to be cortex-m4 for the M4 core.  So far I haven't seen any issue, but this is probably a hidden bug.Thanks,-m

Hi, I am creating application using LPBAM configuration. The application simply is:Enter stop mode 2- Use ADC4-12bit channel 22 (PC4) to measure voltage using clock HSI or MISK- ADC wdog to generate interupt when the value reach threshold to exit stop mode 2- LPTIM1 will trigger ADC4 500ms cycle using clock LSE- LPDMA1 channel1 to store converted data, and save to array adc4_buffer[1]- LPDMA1 channel 0 ensure queue run LPBAMWhat I have done:ADC4 configuration (ADC4 global interrupt enable in NVIC)LPTIM1 configurationLPDMA configuration (LPDMA channel 0 interrupt enable)Scenario queueThen I generate code and face this warningI already createt project without Trust Zone, also check LPBAM check log but cannot verify it. So I need help. Thank you

Hello,I am experiencing a persistent verification error when flashing an STM32H7 via USB DFU using the STM32_Programmer_CLI. The exact same command and hardware work perfectly on Windows, but fail consistently on macOS.Environment:Tool: STM32CubeProgrammer CLI v2.9.0 (also tested on newer versions)OS: macOS vs Windows 11Hardware: STM32H7 custom boardConnection: USB DFU ModeFile: .hex file (approx. 44MB) containing internal flash and external memory data.The Problem: On macOS, the download reaches 100%, but the Verification fails at 98%. The error always points to the start address 0x0800E000 reporting a byte mismatch (0x00 instead of 0x70).Log Comparison Observations:Windows (Working): The log explicitly shows individual sector erases: erasing sector 0003 @: 0x0800c000 done.macOS (Failing): The log shows Erasing memory corresponding to segment 0... but never confirms the individual sectors as "done." It seems the erase operation is being skipped or failing silently on the Mac DFU stack

When I attempt to power cycle a STM32N6570-DK or NUCLEO-N657X0-Q board via the STM32_Programmer_CLI, I get the following error message:Error: Failed to Power ON the board ! Here is the full log:❯ STM32_Programmer_CLI --power off index=0 --power on index=0-------------------------------------------------------------------STM32CubeProgrammer v2.21.0 -------------------------------------------------------------------Power OFF...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Power OFF the board finished with success !Power ON...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Error: Failed to Power ON the board !  However, when I attempt the same command on other Nucleo boards, I don't get this error. Here's the same command run on the NUCLEO-H533RE:❯ STM32_Progr

Hello, recently I was able to flash a programm on the STM32G474CET3 but I am unable to track Live Variables.I wrote a simple program that just increases a cnt variable each second.My .ioc configuration: Every help is appreciated. 

Why can’t my cubemx configure L1 cache? How to enable it?Also, the MPU cannot be configured. You can only use the default configuration and modify it in the generate code.I also configured Memory management, but did not see the enable Cache and MPU synchronization settingsCubeMx 6.16.1 on macos MAC 26.1MCU:STM32H743IIT6  

Updated post to reflect permanent fix Dear STM32CubeIDE user, Further to the recent STM32CubeIDE project creation issue, we would like to inform you that a solution is now available for you. This permanent fix applies to all STM32CubeIDE versions. Issue description When creating a new STM32 project in STM32CubeIDE, the “STM32Cube” radio button may have become unresponsive, blocking the “Next” button after the product selection screen. This prevented the project creation from being completed. Permanent fix You can apply this resolution to any STM32CubeIDE version, even if you applied the temporary workaround that we recently shared with you. Open STM32CubeIDE. Refresh the database.Go to Help > STM32Cube updater > Select “Check the Target selector Device Database Updates” Restart STM32CubeIDE If you deactivated the auto refresh function previously, you may wish to reactivate it for all your STM32Cube tools. Here is how to proceed: STM32CubeIDE:Go to Window > Preferences