STM32 MCUs Software development tools

Hi all,I'm using an stm32f746 and I switched to a stm32u5a9 mcu. I was learning about freeRTOS with the f746 and now it looks like I should be using threadX instead. Since I don't know much about RTOS, switching is not a big deal. But using cubeIDE build in cubeMX I could make multiple threads for freeRTOS before. Now it looks like I can make one in cubeMX by clicking the "generate app init code" and setting the "Create threadX application thread" to true. I know I can add more threads to the files manually. I'm wondering if I can make more than one in cubeMX ... like freeRTOS? Thanks 

As you can see below picture, B-WL5M-SUBG1 Connectivity Expansion Board's UART pins are PC0 and PC1:But in the STM32Cube_FW_WL_V1.3.1 repository Sigfox_AT_Slave application for B-WL5M-SUBG1 describes uart pins are PA3 and PA2:So in this case, application's UART AT interface doesn't work. Buf if you change LPUART1 pin configurations, it works fine:  Thank you for your interest.

 Weird things are happening.The breakpoint  i set in the void Read_ToF_From_VL53L0X_FreeRTOS_Task(void *pvParameters) task is not getting hitthis task calls VL53L0X_Measure_Distance function in which i set a breakpoint which is working ok ! also i put another breakpoint in the file VL53L0X_FreeRTOS_Queues.c which is called upon initializationthis is also not getting hitis it a problem with teh specific folder?but the VL53L0X_Core_Functions.c also on the same main dirdoes the FreeRTOS dir have any problems?Has anyone experienced this problem?@Andrew Neil @mƎALLEm @TDK 

Hi, I am trying to bring up some software on an STM32N6570-DK.I'm able to upload example code from the STM32CubeIDE when the board is in DEV mode, e.g. when BOOT1 is set to 1. I followed the steps in this KB article: FSBL Explained However, I am unable to even connect to the board with STM32CubeProgrammer, even when in DEV mode. Here are the logs from STM32CubeProgrammer: Port 010:59:00 : STM32CubeProgrammer API v2.13.0 | MacOS-64Bits10:59:21 : UR connection mode is defined with the HWrst reset mode10:59:21 : ST-LINK SN : 002000413234510E3733393410:59:21 : ST-LINK FW : V3J16M910:59:21 : Board : STM32N6570-DK10:59:21 : Voltage : 3.29V10:59:21 : Error: ST-LINK error (DEV_CONNECT_ERR)Port 110:59:25 : UR connection mode is defined with the HWrst reset mode10:59:25 : ST-LINK SN : 002000413234510E3733393410:59:25 : ST-LINK FW : V3J16M910:59:25 : Board : STM32N6570-DK10:59:25 : Voltage : 3.29V10:59:25 : Error: Cannot connect to access port 1! If you are trying to connect to a d

Split from Cannot connect to NUCLEO-N657X0-Q - which is solved.This is a new question.Follow up question: what should i do if i want to connect using flash boot?

Hello,(ST-LINK + CubeProgrammer UART/USB both failing)I am using a NUCLEO-N657X0-Q board. I cannot flashing my code via the ST-Link ( ST-Link windows driver is installed and detected through device manager and I had already updated the stlink). it throws this error:STMicroelectronics ST-LINK GDB server. Version 7.11.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 : Enabled Target unknown error 32 Error in initializing ST-LINK device.Reason: Unknown. Please check power and cabling to target.Then tried with CubeProgrammer to connect via STlink but it connects then quickly drops , here is the log :17:22:24 : STM32CubeProgrammer API v2.20.0 | Windows-64Bits17:22:39 : UR connection mode is defined with the HWrst reset mode17:22:40 : UR connection mode is defined with the HWrs

Hi, I have been flashing STM32L151VE by using DFUSe tool for a while. But I could find some difficulty after the OS upgrade to windows 11. Also, I found that the DFUSe tool may not support new ST Boards as per official STM website, so I started using STM32Cubeprogrammer tool, with which I am unable to flash.When I select the erase option while flashing, it fails.When I skip the erase option while flashing, file download works, verification fails and it works inconsistently.Starting address for application part is 0x8008000.I tried integrating the DLLs and API provided in the installed tool's folder. By using methods: massErase() and sectorErase() as per the API, response is successful but when I manually check the memory, they are not erased and even the downloadfile() method fails.I tried doing the same with ST Link debugger interface and it works fine, but the issue still remains the same with USB DFU interface.So, can you please let me know on how to use these AP

Hi Community,I am trying to get the Automatic Mode working, without success. There is a very similar (but locked) post about this going back to 2021 here, for which there is no accepted solution, so this may be an unresolved bug.I am using API V2.20.0 and my ST-Link/V2 firmware is up to date. My target device is STM32C071 on my own pcb, using SWD. I have no issue with manual programming but automatic mode is problematic. To keep it simple until working properly, I am not programming any option bytes at this stage.I start with the ST-Link connected to a board, then click Start Automatic Mode. After a delay of a few seconds it is programmed no problem and the dialogue then requests the device be disconnected and does recognise that it has been. So far so good.However, it then fails to recognise the second device and hangs, not only the API but also the ST-Link, which must be unplugged and replugged before it will connect to a new instance of STM32CubeProgrammer.Is it something I'm d

When I build and debug my project, I get the error window below when the debugger connection is established. The download takes place and verifies successfully, but displays the message again.However, when I start program execution, the console displays the message:Target is not responding, retrying...And then stops. So debugging is not possible. Any suggestions on how to resolve this?

Hello,On the STM32u5g9, using STM32CubeIDE 1.19.0 (CubeMX 6.15, just in case) with jpeg hardware .When debugging the Huffman tables, the rm-0456 gives the address boundaries for the AC0 and AC1 tables; 2 strictly non overlaping tables.In the SFRs menu of cubeide, AC0 starts at the right address, but not AC1 which starts in the middle of the AC0 table, here 0x4002a5dc instead of 0x4002a660 and finishes at 0x4002a738.Then AC0 and AC1 are overlaping/interleaving in the SFRs with same addresses which makes it difficult to follow. I don't think this behavior was wanted. 

Here are some threads which describe the problemshttps://community.st.com/t5/stm32-mcus-boards-and-hardware/32f417-how-to-use-swv-itm-swo-debug-output-without-cube-ide-or/td-p/843611/page/2https://www.eevblog.com/forum/microcontrollers/stlink-debugger-configures-some-32f4-target-registers-e-g-swo-trace-macrocell/msg6056111/#msg6056111Basically, if you want to do Statistical Profiling, you have to enable PC Sampling and then Cube leaks memory at around 100kbytes/sec. Eventually it crashes, obviously. The SWV ITM debug mode does not need PC Sampling and is thus a lot more reliable, but only in the OpenOCD debugger mode.Instead of adding more stuff which nobody uses, ST should fix this program properly, starting with the famous "random file opening" issue which about 100 people have complained about.Another way to crash Cube is to use a STLINK debugger with some unspecified fault on the USB side. Cube just leaks lots of memory and bombs. Poor error detection...

I am using the Nucleo board as a prototype before I get a board made.Is there a complete STM32CubeIDE project anywhere I can use which has all the memory etc set up?ThanksAndy. 

Worth checking this on whatever new version comes out. This is really sloppy Java code, which is something ST tend to not fix (see the random file opening bug for example).It is about 10k bytes per second.Probably not noticed by most people, using this feature only occassionally.For long term debug you will probably be using either a UART or USB VCP.

I am using STM32G474RCT6 microcontroller, I want perform firmware upgrade through CAN communication. But my controller doesn't provide the feature of Firmware upgrade through CAN communication.is there any possibility to use CAN communication for firmware upgradation in my controller. 

I’d like to propose an improvement to the search functionality in the "Pinout & Configuration" → "Pinout View" section of STM32CubeMX.Currently, the search allows filtering by port names and peripheral signals. It would be extremely helpful if the search could support wildcards or regular expression-like patterns. For example:Searching for SPI?_MOSI would return all pins associated with SPI1_MOSI, SPI2_MOSI, SPI3_MOSI, etc.Searching for PA[0-9]+ could list all pins from PA0 to PA15.This enhancement would significantly improve usability, especially when working with large pinouts or when trying to locate signal mappings across multiple instances of peripherals.Thank you for considering this suggestion!Best Simon 

 Hello,We are working with the STM32N657X0-Q and we would like to understand the best way to flash my C/C++ program onto the board using STM32CubeIDE or STM32CubeProgrammer.Specifically, we have the following questions:Flashing from STM32CubeIDE:Is it possible to directly flash my compiled C/C++ program to the STM32N657X0-Q using STM32CubeIDE?If yes, what are the required configurations for the debugger and the flash settings?Using a Binary or Hex File:When compiling a project in STM32CubeIDE, where can I find the generated .bin or .hex file?What are the correct steps to extract the binary or hex file from STM32CubeIDE? ==>  We managed to retrieve binary and hex files from STM32CubeIDE, but we are unable to flash them using STM32CubeProgrammer.Flashing with STM32CubeProgrammer:Once I have the .bin or .hex file, what is the correct procedure to flash it onto the STM32N657X0-Q using STM32CubeProgrammer?Are there specific memory regions or settings that I need to configure be

  Hi, I created a project on the STM32N6570DK and I only have the project "in (STM32CubeIde)", I don't have the FSBL and the Appli. How do I flash my firmware? I tried to use the fsbl provided by the official ST repository, namely "ai_fsbl.hex", but the program does not start

Hello, superhero MCU fans.I'm trying to create an STM32N6 project with two projects: FSBL and Appl in its simplest form.Both will live in external flash.The FSBL should start Appl in XiP mode, and that Appl should only blink an LED (Hello World) for now.Of course, I signed the bin files, used the correct EL in STM32CubeProgrammer, and flashed the FSBL to 0x7000000 and the Appl to 0x70100000.I think it looks a lot like the JPEG_DecodingFromOSPI_DMA example, which works just fine!However, I have no idea how it can be created in STM32CubeMX.For example, the example has a "extmem.c" file, but CubeMX isn't generating it. I think there's a problem.So, with STM32CubeMX 6.15.0, I couldn't generate a project where FSBL could launch Appl. The FSBL can blink an LED, but it apparently can't launch the APPL. I'm sure I'm doing it wrong, but I'm new to this and couldn't find a tutorial.It may have to do with the default protection mode.I attached the ioc file.What do I need to do to get this working

Chip Model: STM32F030RBT6HAL Version: HAL Package "FW.F0.1.11.0", Patch="FW.F0.1.11.5"Symptom: After writing Data0 and Data1 to the Option Bytes (OB), debugging becomes unavailable. When checked with a programming tool, the protection level of the OB field changes to "BB". The system returns to normal after rewriting the protection level to "AA".Analysis:HAL API Function: HAL_StatusTypeDef HAL_SLASHEx_OBProgram (FLASH-OBProgramInitTypeDef * pOBInit) The parameters, uint8_t RDPLevel; There is no complement.and then, another function was called to rewrite configuration: FLASH-OB_RDP_LevelConfig (pOBInit ->RDPLevel); The register written here is only an 8-bit protection mode parameter whitout complement code. During option byte loading, the bit-wise complementarity of the option byte and its corresponding complemented option byte is verified. In case of failure, an option byte error (OPTERR) is generated and the corresponding option byte is considered as 0

Last week we ran into issues flashing our custom boards (STM32H7S3L8H6) with the STM32Progammer_CLI. Originally we were using the version packaged with CubeCLT 1.18.0 (STM32CubeProgrammer v2.19.0). I noticed that ~7% of flashes failed flash verification after a "successful" flash. The errors were always grouped within a small region of addresses, and this region stayed the same until a new .elf file was compiled. Using CubeProgrammer GUI i was able to validate that those memory regions were in-fact invalid. For example, here is one of the test runs on our custom board:=== Final Statistics === Total Flashes: 624 Successful: 580 Failed: 44 Success Rate: 92.95% Failed Addresses (failure count): 0x080065C8: 12 0x080065C9: 7 0x080065CE: 6 0x080065CF: 5 0x080065CD: 5 0x080065CA: 4 0x080065CC: 3 0x080065CB: 2 As you can see by the addresses, this was flashing the bootloader (in internal flash).The command used to flash for all versions wasSTM32_Programmer_CLI -vb

hello my frendsnow i habe a new doubt!i am traing to enable the DCMI in the STM32H743BGT6 whit the stmcubeIDE (in the cubeMX section)and as you can see in the image above, the program does not let me enable the DCMI because its resources are used by the "PSSI" (which I NEVER enabled, and I imagine that it is an initial configuration by default)(with fedora 41 on my PC) with this version:and according to this tutorial: https://community.st.com/t5/stm32-mcus/how-to-configure-and-use-the-pssi-on-the-stm32h7/ta-p/49811 I should be able to disable the PSSI (which I don't want) in the section you see in the tutorial imagebut I can't because that PSSI is NOT in that part, nor can I find where it is to DISABLE it anywhere in my  stmcubeIDE (as you can see in the first image I posted)the question is: where will I be able to disable PSSI to enable DCMI?:crying_face:Saludos!...

This is for an STM32F303.I've reduced my MX configuration down as much as possible so that it only has SWD and a button on GPIO PA8 configured and the incorrect behaviour still occurs. The intent is for PA8 EXTI falling edge to start a timer, and for that timer to in turn interrupt on expiry. I do get an interrupt (for both EXTI and the timer), but the duration of the timer is always wrong (sometimes instant, sometimes quite slow), and when on interrupt I check instance->CNT it is always a random value.Following https://community.st.com/t5/stm32cubeide-mcus/hal-tim-periodelapsedcallback-firing-very-prematurely/m-p/588486 I am issuinghbuttonDebounceTimer->Instance->SR &= ~TIM_SR_UIF;during USER CODE 2 (after init, before the main loop), and it has no effect.My ISRs look likevoid HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { if (htim == buttonDebounceTimer) { HAL_TIM_Base_Stop_IT(htim); } } void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin) {

Following up from my previous post, I am having issues with code generation - it seems to complete, but I don't see anything changed in the code.Here attached you will find the ioc file. I modified pin names for PB10 to PB12, but after generating the code I don't see any of the name in the project (should be in main.h, but I did a search in the whole project just to be sure). I am using STM32CubeIDE 1.16.0 on mac Sonoma 14.2.1 with M1 chip.

I'm trying to use STM32CubeMX directly or via STM32CubeIDE, and I can't find a way to configure ThreadX + USBX Host for STM32WBA65 boards such as NUCLEO-WBA65RI or STM32WBA65I-DK1.    Only Device classes show up.I've also tried to do it using the part directly instead of a board or example, and even then I only see Devices under X-CUBE-AZRTOS-WB > USB USBX > USBX from the Software Component view.I have noticed a few thingsThere is no X-CUBE-AZRTOS-WBA  only WB under select Components, but they are both there under Manage Software PacksI must change HSE to Bypass to have USB_OTG_HS enabled under connectivty.Even after configuring USB_OTG_HS to Host Only there are no UX Host parts showing in the Compnents under X-CUBE-AZRTOS-WB > USB USBX > USBX.Pinout & Configuration there is a separate THREADX and USBX between i-CUBE-wolfTPM and X-CUBE-AI which looks like I can turn on at the same time as the normal ThreadX per MCU Line.Is there an example of USB Host on

Hi everyone,I'm using STM32 Cube Programmer CLI to port an SBSFU example to STM32U5G9 platform (from U585). Other than shell script mess and no IOC files in this examples, I've managed to port the example and run it by using ST Link programmer under both Linux and Windows.The problem is that the newest release 2.20 has its J-Link functionality completely broken in Linux (I'm using Kubuntu 22.04 and 24.04, also tested in regular Ubuntu). Any command to STM32_cube_programmer_CLI ends up with:Error: Could not connect to the J-Link/Flasher, Library not found !The underlying issue is that libjlinkarm.so is not linked to the CLI executable: ldd shows it's linked for older versions, but no linkage for v2.20. I'm guessing this has happened since ST was finally moving away from weird versioned so names to non-versioned so's: i.e. libjlinkarm.so.7 -> libjlinkarm.soI'm hoping that someone from ST will read this message since the issue is not possible to resolve without re-linking... So @s