STM32 MCUs Software development tools

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

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

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

Environment:STM32CubeIDE version: 1.16.1MCU: STM32H753RTOS: Azure RTOS ThreadXDebug probe: ST-Link (V3)RTOS Proxy plugin:com.st.stm32cube.ide.mcu.externaltools.rtosproxy.win32_1.1.1.202408301240OS: WindowsIssue description:RTOS-aware debugging for ThreadX breaks completely when at least one ThreadX thread name length exceeds ~20 characters.ThreadX itself has no limitation on thread name length (thread name is CHAR *).However, STM32CubeIDE RTOS-aware debug stops working if any thread name is longer than ~20 characters.When this happens:RTOS thread list becomes incomplete or unusableSwitching between threads is not possibleCall stack for inactive threads is

I've noticed a behavior with MX25UM5124G_STM32U5x9K-DK External loader over the past 2 years that I feel is a bug. I think the bug lies within the sectorwise erase of the MX25UM5124G_STM32U5x9K-DK External loader fw. If you flash a bin to external flash using the external loader with "erase before programming" enable , there is near 100% likelihood the verification step will fail. I believe this caused by the sectorwise erase not working as intended. The work around has been to do full chip erase on external flash then attempt the flash again. This will succeed almost every time. The behavior that led me to suspect the issue lies within the external loader is when I wrote a proprietary external flasher onboard the stm32. It uses sectorwise erase and has high reliability. This proves to me that flash chip and flash driver on the STM32 are working as intended. Note: We use this proprietary flasher for customer flashing updates

Hello,Due to limitations with the STM32WBA's silicon & Bluetooth stack we've had to significantly re-engineer our hardware and add an external Bluetooth chip. As part of this, we updated our SAI blocks so that one block is transmit and one is receive, and moved our PDM microphones to a SPI bus.Since we have two PDM microphones, we've followed AN5027 "Interfacing PDM Digital Microphones":In our setup, we have SPI2 SCK (mapped to PB10) connected to PA1, and connected PA9 to the DMIC_CLK line. Our plan has been to map PA1 (input) -> TIM17_CH1, which then triggers (via ITR8) TIM3_CH2 which is

The callback messages seem corrupt and I get a connection error or -162025-12-09 12-05-03.130|INFO||: Type = 0 Message = USB speed : Full Speed (12MBit/s)2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Manuf. ID : 2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Product ID : STMicroelectronics2025-12-09 12-05-03.130|INFO||: Type = 0 Message = SN : STM32 BOOTLOADER2025-12-09 12-05-03.130|INFO||: Type = 0 Message = DFU protocol: 1.12025-12-09 12-05-03.130|INFO||: Type = 0 Message = Board : --2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Device ID : unknownShould be:2025-12-04 14-55-46.892|INFO||: Type = 0 Message = USB speed : Full Speed (12MBit/s)2025-12-04 14-55-46.892|INFO||: Type = 0 Message = Manuf. ID : STMicroelectronics2025-12-04 14-55-46.892|INFO||: Type = 0 Message = Product ID : DFU in FS Mode2025-12-04 14-55-46.892|INFO||: Type = 0 Me

STM32CubeIDE is creating a new folder inside ".stm32cubeide\.jxbrowser-7.41.4" everytime STM32CubeIDE launches.It would be nice if the application cleaned up its junk, at least deleting old profile subfolders, as each one eats up 75MB.I just manually deleted over 75 of them dating back to October. 

hi i re-downloaded STM32 Cube IDE but i cannot find <create STM32 Project> I downloaded this sw over and over but nothing changed :(please help me with this 

Hello,I searched on Google but I don't know if anyone has encountered this problem before. As we know, CubeMx and Cube IDE were recently released as two separate programs. I think this error might be related to that.The error is this: I open a project I created in CubeMx in the IDE and upload it to the chip; there's no problem up to this point. However, whenever I make an update in CubeMx, the entire update isn't reflected in the IDE (or rather, in main.c). If there were no updates at all, I would look for the problem elsewhere, but some of the configuration settings are transferred to the IDE while others are not. The most recent example I experienced was that changes to the ARR and Prescaler registers of the TIMER module were transferred to the IDE, but the changes to the PWM (CCR1) register remained the same. In this case, I had to manually change the relevant value in main.c (and it was quite difficult to notice).Look, the main problem here is that we develo

Hello guys. I'm currently trying to use the dsp libraries of the cmsis pack with no success.My device is a WBA55CG nucleo board and the version of my ide is 1.19. I tried to download the cmsis package manually, by selecting embedded software package maneger and then from local/url and successfully installed the packages. (CMSIS 5.9). I enabled core and selected CMSIS from source and dsp. I enabled dsp and core on mx configuration->middleware and hit generate. I tried to inlcuded the arm_math lib on my program to see if the installation was successful and if cube could build my program..... aaaand all hell broke loose.../Middlewares/Third_Party/ARM_CMSIS/Source/SVMFunctions/SVMFunctions.c:29:10: fatal error: arm_svm_linear_init_f32.c: No such file or directory 29 | #include "arm_svm_linear_init_f32.c" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. ../Middlewares/Third_Party/ARM_CMSIS/Source/Tra

When I used the MMT tool in STM32CubeMX to configure a 256MB NAND FLASH based on FMC, an error appeared. I am using the STM32H743IIT6 chip and have configured NAND FLASH in the FMC. I want to know how to solve this problem. 

Yes I should have taken a backup - but modern software must always have build-in backup solution so you do not corrupt your own files. Ask chatgpt if you need the code. I used 2 days to make this project, luckily I have the main.c so I can copy names from this.  I am on Linux Mint version 22.2 with STM32CubeMX version 6.16.1 and Visual Studio Code Version: 1.107.1.The fault was in STM32CubeMX, that did not save correctly. During my work I experienced the software closing without saying a word on the error, especially in the ADC1 setup. But every time I could just start it again, but not this time:-(Attached you find the surviving part of the IOC file.Thank you for listening to my disaster. Best regards   

Hi,when generating a project for the STM32G484 using STM32CubeMX (6.16.1) and create a project and code for this. I cannot seem to get it to build (and/or debug) in STM32CubeIDE (2.0.0).What am I missing here?Thanks,ErX.

In my STM32CubeIDE, the labels and tabs are displaying as garbled text (random characters). This makes it difficult to navigate and use the IDE.My current development environment is as follows.STM32CubeMX v6.7.0, STM32CubeIDE    Version: 1.15.1     Windows 10 19044.1766    JAVA_VERSION="18.0.2.1"How to solve these garbled code problems? I have reinstalled this IED many times。

Been working on this for a few weeks now, I'm losing my mind. In STM32CubeIDE, only time I can get anywhere is in hardware reset, and there it times out. In STM32CubeProgrammer, it does connect. It can read the MCU name, flash size, all of that. All addresses read 00000000. However, I can't write in the programmer, and I just can't figure out why. Write to memory failed. Failed to erase data. Failed to download data. This is my first time doing something like this, so maybe I'm missing something. But nothing I've looked up has helped.

Hi, I have a problem with my CubeIDE installation that is that I cannot create a stm32 project(the option that integrates with CubeMX) I can only create the followingI've installed it from the shell script from the generic Linux download, I'm using arch Linux(btw).I've reinstalled it at least 3 times now, also went to Help -> Install New Software, used this site: 

 We are using the STM32N657Z0H3Q (142-pin TFBGA package).CSI behavior in STM32CubeMX is inconsistent across versions:In older CubeMX versions(1.64), CSI lanes (CSI_D0P/N, CSI_D1P/N, CSI_CKP/CKN, CSI_REXT, etc.) are displayed in the Pinout view, but these signals are not actually assignable to physical pins. They appear as virtual pins only.In newer CubeMX versions(1.65), CSI is still listed in the peripheral view, but no CSI lane pins are shown at all. In case, the generated .ioc file contains only virtual signals:VP_CSI_VS_CSI.Mode=CSI VP_CSI_VS_CSI.Signal=CSI_VS_CSI VP_DCMIPP_CSI.Mode=SerialInterface VP_DCMIPP_CSI.Signal=DCMIPP_CSIOn hardware, when connecting a CSI-2 camera, the following is observed:DCMIPP and CSI registers initialize correctly,no LP-to-HS trans

I'm planning on moving from STM32F103 for more speed, so in advance of getting a board I thought I would try building an app for the STM32G431... so I found an small example project online that was using an OpAmp feature.Having got that compiled ok in STM32CubeIDE I backported my app source code into the project (which went ok), but compiling it was missing some definitions for HAL UART structures.Looking at "Drivers/STM32G4xx_HAL_Driver" in my original project and comparing it with "Drivers/STM32G4xx_HAL_Driver" in the new project I see that its missing some files like "stm32g4xx_hal_uart.h". Is it possible to force STM32CubeIDE to regenerate the Drivers subfolder from scratch?I always find switching a STM32CubeIDE project between different MCUs a harder job than it should be, e.g. it would be nice if there was a combo box listing MCUs in the project properties.  

Hi and happy new year... I'm a complete beginner, and I'm facing a major problem.I've tried creating a new project in CubeID for an STM32F401CEUx.But the project "STM32 Project" doesn't appear in the list of new projects.The closest thing I find is one called "STM32CubeIDE Empty Project," and when I create a project using this template, the initial image of the chip where I configure the pins doesn't appear, and the IoT file isn't in the project tree either.Why could this be? 

Hi,I am working with the STM32N6570-DK board. Initially, I am using the GPIO_IOToggle example project to verify the basic board functionality.I configured the hardware using STM32CubeMX v6.16 and generated the project using the STM32CubeIDE toolchain. The project was built successfully using STM32CubeIDE v2.0.0.When I run the project in debug mode from CubeIDE, the LED toggles correctly.However, the device does not boot when I flash the binary manually using STM32CubeProgrammer v2.21.0. Signing and Flashing DetailsI am using the following command to sign the output binary generated by CubeIDE:STM32_SigningTool_CLI -bin <path to fsbl project.bin file> -nk -t fsbl -hv 2.3 \-o <path to fsbl project-trusted.bin file> \-dump <path to fsbl pr