STM32 MCUs Software development tools

Hello. My current set up is STM32Cubeide 1.19 which has an integrated version of the CubeMX (6.15)I'm currently working on some st git examples, that seem to have been created with CubeMX (6.16), thus i cannot open the .ioc file on cubeIDE. I installed cubeMX 6.16 in order to edit the .ioc file and hit generate. Once i tried to build the project on cubeIDE though i got various errorsmake: *** No rule to make target 'C:/Users/asantorinaios/STM32CubeIDE/workspace_1.19.0/BLE_Beacon/Drivers/STM32WBAxx_HAL_Driver/Src/stm32wbaxx_hal_gtzc.c', needed by 'Drivers/STM32WBAxx_HAL_Driver/stm32wbaxx_hal_gtzc.o'. Stop. "make -j12 all" terminated with exit code 2. Build might be incomplete.If i try to exclude said file from the build, i another similar error. Is the cubeMX 6.16 incompatible with the 1.19 cubeIDE. Do i need to download cubeide 2.0 or is there another solution ?

In STM32CubeIDE, it is possible to view two different source files side by side by dragging editor tabs with the mouse. However, there is no keyboard shortcut or command to move the active editor to the left/right split.This slows down workflow when frequently comparing files (e.g., main.c and app.c). A command such as “Move editor to right/left split” with assignable key binding would greatly improve productivity.Best regards.

Hi,   I have a functioning project that fully compiles with only three warnings, but when I debug it and examine C structures in the live expressions viewer the the data (GovTrimControl_P structure ) appears to be offset by 4 bytes, yet the memory browser shows the correct values and when the mouse hovers over a value that value is correct:       The Build Analyser also reports the address of GovTrimControl_P  correctly Compile Problem Output: The values for the GovTrimControl_P structure are set at bootup to:       /* Parameters (default storage) */ struct P_GovTrimControl_T_ { real32_T FreqSP; /* Variable: FreqSP */ real32_T kD; /* Variable: kD */ real32_T kI; /* Variable: kI */ real32_T kN; /* Variable: kN */ real32_T kP; /* Variable: kP */ }; typedef struct P_GovTrimControl_T_ P_GovTrimControl_T; /* Block parameters (default storage) */ P_GovTrimControl_T GovTrimControl_P = { /* Variable: FreqSP */ 50.0F, /* Variable: kD *

Hello,I am trying to get the VS-Code extension to work on my Intel-Mac. I already have it running on my Windows machine no problem.The problem is, that the extensions won't activate. I have created a new project using CubeMX and choose CMake as the toolchain. Then I installed the STM32 CLI tools, as well as cmake and the ARM compiler.Then I am opening the project in VS-Code and CMake asks for a target. I choose Debug.CMake extension output:[proc] Executing command: /usr/local/bin/cmake --version [proc] Executing command: /usr/local/bin/cmake -E capabilities [kit] Successfully loaded 2 kits from /Users/jan/.local/share/CMakeTools/cmake-tools-kits.json [presetController] Reading and validating the presets file "/Users/jan/Dev/fischer-technik-motor-controller/CMakePresets.json" [presetController] Successfully validated /Users/jan/Dev/fischer-technik-motor-controller/CMakePresets.json against presets schema [proc] Executing command: uname -s [presetController] Expanding presets file /Users

The erroneous configuration in the tx_initialize_low_level.S is this: LDR r1, =0x40FF0000 // SysT, PnSV, Rsrv, DbgMThe tx_initialize_low_level.S file is generated upon selecting ThreadX 'Core' in the STM32CubeMX v6.15.0, and the above line is thereafter never changed. Specifically, upon enabling 'Enable BASEPRI support' and selecting a very common value of 5 for the TX_BASEPRI_VALUE, the above line is not updated accordingly. Not syncing the SYSTICK IRQ priority with the TX_BASE_PRI_VALUE of course leads to a system failure.This issue can be duplicated by creating a brand new project with STM32CubeMX v6.15.0 and it can be seen in the sample projects included in the Applications/ThreadX in the STM32Cube_FW_U5_V1.8.0

Hi all, I am trying to get a zephyr project running on an STM32N6570-DK, including Camera, NPU, VENC and Ethernet.I have been using STMCubeMX 6.16.1 to create the project based on the provided DK default settings.For the Ethernet block, the configurator shows pin conflicts, I double-checked and the pins are not in use by the Ethernet driver:There are similar warnings for the SD/MMC2 block:Am I missing something here or can it safely be ignored? Simon

Installing STM32CubeMx on OpenSuse Tumbleweed using/st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.rpm_bundle.sis missing libusbxsudo ./st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.rpm_bundle.sh [sudo] Passwort für root: Creating directory st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.rpm_bundle.sh.root Verifying archive integrity... All good. Uncompressing STM32CubeIDE installer 100% Verifying... ################################# [100%] Preparing... ################################# [100%] package segger-jlink-udev-rules-6.44c-4.noarch is already installed error: Failed dependencies: libusbx >= 1.0 is needed by st-stlink-server-1.2.0-3.amd64 Verifying... ################################# [100%] Preparing... ################################# [100%] package st-stlink-udev-rules-1.0.2-2.noarch is already installed error: Failed dependencies: st-stlink-server is needed by st-stm32cubeide_1.1.0-1.1.0-4551_20191014_1140.x86_64libusbx is not available for OpenSuse. On https://so

 I was making a project with CUBE IDE and compiling it on the board, and I got this error while compiling the project I was doing on the new board.No source is available for "Call Signal Handler"() in 0xfffffffe.I'm sure they're using the same CPUI can't compile it because it's STM32 ST-LINKI don't think there will be any problems with the code or MX settings because if I modify the code on the existing board, the project will also change well.Even if I create a new project and add the above code, I get the same error, so I can't compile itI want to solve this phenomenon, how do I solve it?  int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MPU Configuration--------------------------------------------------------*/ MPU_Config(); /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE EN

CubeMX 6.16.0 "Memory Management" used for ethernet and with enabled linker file generation creates the following [ORIGIN adapted from default]:RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 0K TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 0K Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1KWhat I would have expected was:RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 96 TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 96 Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1536[with just 1 ETH RX buffer - see this other post ].Can someone explain to me whether this is intentional - maybe because of a constriction with the MPU granularity?Or whether CubeMX handles this wrong and should allow sub-kilo-byte granularity?Best regardsJohannes 

  drag and drop error I have a Mac Pro M4 with Tahoe 26.2 OS, STM32CubeIDE version 2.0.2, and I am having trouble selecting and copying a selection of lines. I tried several tests and that option disappeared. If I am comparing two files, dragging and dropping text works perfectly. Is there any notification about this? Is there a solution? Thank you.   Post edited by ST moderator: This post has been translated from Spanish to comply with the ST Community guidelines. Please use English language as it's an international community and to let others to understand your post. Thank you for your understanding

Using:VSCode version: 1.107.1 on Windows 11.STM32CubeIDE for Visual Studio Code version 3.7.0.I created STM32N6 project that builds two targets: FSBL and Application. I follow the instructions here: https://community.st.com/t5/stm32-mcus/how-to-debug-the-stm32n6-using-vs-code/ta-p/833499.clangd contents:CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: Appli/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual If: PathMatch: Appli/.* --- CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: FSBL/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual If: PathMatch: FSBL/.*.vscode/c_cpp_properties.json contents:{ "configurations": [ { "name": "STM32_Appli", "compileCommands": "${workspaceFolder}/Appli/build/compile_commands.json" }, { "name": "STM32_FSBL",

Using:VSCode version: 1.107.1 on Windows 11.STM32CubeIDE for Visual Studio Code version 3.7.0.I created STM32N6 project that builds two targets: FSBL and Application. I follow the instructions here: https://community.st.com/t5/stm32-mcus/how-to-debug-the-stm32n6-using-vs-code/ta-p/833499This is a single folder project, not multi-root. The problem is that when I navigate to source code which is not under FSBL or Appli then clangd does not know which complication database to use.This disturbs during coding and during debugging when I step through grayed out code with false errors highlighted.CMake (or some STM32 utility) generates .clang file into the root directory. It's stripped down version looks like this:CompileFlags: CompilationDatabase: FSBL/build If: PathMatch: FSBL/.* --- CompileFlags: CompilationDatabase: Appli/build If: PathMatch: Appli/.*But there is no path match for Drivers and Middlewares. If I open HAL GPIO driver, I can see in the STM32cube clangd lo

Hello, I am trying to set up a project using STM32Cube Extension in VS Code. When I attempt to select the Nucleo‑F207ZG board in the Board/Device selector, the board does not appear in the list.The stm32cube_core output shows the CMSIS_PACK_ROOT environment variable, and under that directory the file .Download\cache\scanner_391867825626163.cache contains entries for nucleo-f207zg as well as STMicroelectronics.nucleo-f207zg_hw-board.1.0.0.pdsc. Despite these files being present, the board is still not discovered by the IDE. Could you please advise what additional checks or steps I should perform to resolve this issue?

Hello all,I get an error starting a debug session from STM32CubeIDE (1.18.1) (STM32 Nucleo-F767ZI):STMicroelectronics ST-LINK GDB server. Version 7.10.0Copyright (c) 2025, STMicroelectronics. All rights reserved.Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : EnabledTarget USB comms errorError in initializing ST-LINK device.Reason: USB communication error. Please reconnect the ST-LINK USB cable and try again. If I switch to SEGGER J-Link everythink works fine.Is my debug configuration:What I tried:- Restart PC- Reinstall the USB-Driver (https://www.st.com/en/development-tools/stsw-link009.html)- Erased the flash with STM32CubeProgrammer- Changes USB cable- Googled for solutionsPlease helpBest regards Nikolai   

Hi,STM32H563 chiprev Z.I am trying to work through How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled - stm32mcu using a NUCLEO-H563ZI MR1 board but using the latest STM32CubeProgrammer (2.18.0) and ST32Cube_FW_H5 (STM32Cube_FW_H5_V1.4.0).Section 2.5 is intended to demonstrate booting securely and then dropping into the System flash bootloader from non-secure application and connecting to it via UART. In my case, I use the virtual COM-port provided by the ST-Link provided on the board. I have not dared to go all the way to CLOSED but have chosen to tell the provisioning.sh that I want PROVISIONED state. I have confirmed using the SWD-connection that the TZEN is enabled after this and that PRODUCT_STATE is iROTProvisioned. I type 1 in the terminal displaying the "UI" of the non-secure app and then disconnect TeraTerm and in ST32CubeProgrammer I select connect method UART and Port = COM20, Baudrate = 115200, Parity = Even, Data

Problem:I recently updated to 2.0.0 of STM32CubeIDE and I encountered an issue when attempting to build for Debug. I first noticed an issue when trying to run a Debug Configuration. Before 2.0.0, it would build Debug before flashing the built firmware and starting the debugging server; pretty much default settings. Today, it started skipping the build step. I tried building Debug manually with the dropdown on the hammer icon and clicking "Debug." Instead, it built for Release. Solutions:- Right click on the project -> Build Configurations -> Build Selected... and select Debug.AND- Setting Debug as the active build and right click on the project -> Build ProjectThese solutions would build for Debug AND clear both of the above issues. As in the hammer icon -> Debug would actually build for Debug and the Debug Configuration would build before flashing and debugging.

I have a requirement to implement CAN based bootloader in my STM32h503rbt6 controller. Right now iam working on the testing of Flash functions which i have written on my own.My flash write, read and erase all are working fine.but when iam erasing flash sector wise,here comes the problem.after sector 7, from sector 8 onwards with y function i cant abe to erase.but i want full memory controll over my st controller flash.then only i can decide which part of flash i can use for my bootloader and which part of flash i can use for my application.HAL_StatusTypeDef Flash_Erase_Sector(uint32_t sector) { while (FLASH->NSSR & FLASH_SR_BSY); if (FLASH->NSCR & FLASH_CR_LOCK) { FLASH->NSKEYR = FLASH_KEY1; FLASH->NSKEYR = FLASH_KEY2; } /* Clear valid flags only */ FLASH->NSCCR = FLASH_CCR_CLR_EOP | FLASH_CCR_CLR_PGSERR | FLASH_CCR_CLR_WRPERR; FLASH->NSCR &= ~FLASH_CR_SNB_Msk; FLASH->NSCR |= FLASH_CR_SER; FLASH->NSCR |= (sector << FLASH_CR_SNB

Hi all,I'm looking for a way to remotely *flash* a B-U585I-IOT02A | Product - STMicroelectronics eval board using the built-in STLINK-V3.Remotely means over TCP. Can be at the same computer (e.g., to pass-through debuggers to Docker containers), or across computers.This works well with GDB for debugging, but I need this to get running with flashing, too.Questions:Is there a way to make STM32_Programmer_CLI or related ST apps connect via TCP instead of directly to the debugger? I found ST-LINK-SERVER | Software - STMicroelectronics which seems to create the TCP bridge, but do any ST tools actually use it?Are you aware of this working with free tools like openocd?I could also flash via GDB, but I'm concerned about the special parts like trust-zone, option bytes, etc. Plus, I'm evaluating Zephyr, and the default way to flash the board is to use the stm32cubeprogrammer: B-U585I-IOT02A Discovery kit — Zephyr Project DocumentationThanks.

Hi for all,I use Cube MX to generate code with CMake and then use Vscode with needed extension to compile my code.My question is : i want to use library that contain multiple folders to drive stepper motor, how to add this library to my project.best regard for all thanks for any reply 

Using latest STM32CubeMX version 6.16.1 on STM32N6570-DK. It is possible to assign peripherals like UART, I2C, etc. into multiple contexts - boot, app, memloader, but I cannot find a way to assign plain simple GPIO's into multiple contexts. CubeMX only allows to pick Free (which means none) or one of them. Needless to say, I would like to use same LEDs and buttons from multiple contexts. I don't think the RIF is the cause, not using it right now. Seems like a missing feature. 

Hello!I wanted to set up some settings from CubeMX, specifically NX_IP_PERIODIC_RATE in NetXDuo and Rx Descriptor Length in ETH section. NX_IP_PERIODIC_RATE default value is set to 100, but when I set it to 1000, the value does not change when re-generating the code.Rx Descriptor Length default value is set to 4, but when I set it to 8/16/32, the value does not change when re-generating the code. Right now, whenever I re-generate the code, I just manually change these settings in my code due to these settings being set to their default ones. The same problem occurred in CubeMX version 6.15. One thing to point out also, is that the settings I changed are not set back to their default ones in CubeMX, only in the generated code. Also, no errors or warnings are displayed.Is this a bug or am I supposed to do something else before being able to change and apply these settings?

I need help to setup TMP102 alarm function. My board is NUCLEO-F439ZIReading the temperature is working fine.uint8_t TMP102_ADDR = 0x48 << 1;uint8_t REG_TEMP = 0x00;uint8_t buf[12];buf[0] = REG_TEMP;ret = HAL_I2C_Master_Transmit(&hi2c2, 0x90, buf, 1, 10);    // OKret = HAL_I2C_Master_Transmit(&hi2c2, 0x90, 0x00, 1, 10);   //OKret = HAL_I2C_Master_Receive(&hi2c2, 0x90, buf, 2 , 10);    //OKreads the temperature correctly. Buf[0] and buf[1]has correct temperature data. I am trying to setup the alarm function. Reading/writing the Limit registers are failing.Datasheet states that Thigh=80C, and Tlow=70C. After Reset.I am reading the Thigh registers, with the following code:uint8_t reghi = 0x03;ret = HAL_I2C_Master_Transmit(&hi2c2, TMP102_ADDR, reghi, 1, 10); // failis sending 0x00 on reghi. I verified by scope.ret = HAL_I2C_Master_Transmit(&hi2c2, TMP102_ADDR, 0x03, 1, 10);  //fail     it i

Despite enabling ADC, the ADC clock option is greyed out for MCU STM32G0B1KBUx. I'm using version 6.16.1

Howdy!I'm encountering a peculiar issue using STM32CubeMX ( version 16.6.1 ) and configuring the I2C1 peripheral with firmware version STM32Cube FW_G4 V1.6.1.In short, I'm trying to configure it for SMBus-two-wire-Interface, but this option fails to appear in the drop-down, only making SMBus-Alert-Mode available. This is a problem since the alert pin is already being utilized for a different purpose.This appears to be true for all the I2Cx on this device, and in desperation, I checked a handful of other STMG4x microcontrollers, and this issue remains present throughout. Additionally, I randomly checked STM32H7x, and it appears these did NOT share this issue, with the SMBus-two-wire-Interface option appearing as expected.We have a client with a tight deadline, and using SMBUS is essential. Any updates on when this could be fixed, or workarounds would be greatly appreciated.Thanks a million in advance!

Hi,I can't seem to find the launch configuration setting to specify a device in the JTAG chain by its position and IRpre length. I'm using a J-link programmer and I can usually do this from the command line by passing the -jtagconf x,y argument to the J-link executable. However, the debug console in VScode shows that the debug launch config called the Segger J-link GDB server without this argument. I can't seem to find how to make the debug config to append this to the J-link server call Is this supported by the STM32Cube extension?Thanks