STM32 MCUs Software development tools

Hi,We are using STM32H74 microcontroller STM Bootloader ST Version 0x91.We are using STMCube Programmer V2.9 while during the serial programming using UART.On few of the units , we get the erase issue : Failed to erase memory . And then GETId not responded. All the power supply of the units are stable. On checking the NRST , it went low for around 30us . Refer attached.On few good units , erase takes around 6.5seconds with V2.9 STM32Cube prograamer. This issue doesnt occur when we use STM32 Cube prograamer V2.19. Erase takes around 4.8secondsOn checking the difference between the two VERSIONS we found the command sent for erase is different in both the versions of STM32 Cube Programmer.V2.9 sends command 0xffff00 data size :3 Bytes. This is a mass erase.While V2.19 sends 0X0000000000 DATA size: 5bytes. It is a page wise erase. The erase time taken by V2.19  is less compared to V2.19.Once the unit switches to the STM Bootloader, the IWDG timeout will be 16

1.这一套硬件第三方开发已实现porting RN8302B，现在自己开发发现无法工作，线路图如下：2.在MX里配置没有像F103那样的项目，如下为H563的SPI配置3.导入RN8302B 驱动编译通过后， 发现无法读取到RN8302B deviceID,串口打印信息为0XFFFFFFFF：   

13:19:19 **** Incremental Build of configuration Debug for project Nx_UDP_Echo_Server ****make -j12 all make: *** No rule to make target 'C:/Middlewares/ST/threadx/common/src/tx_block_allocate.c', needed by 'Middlewares/ThreadX/Core/tx_block_allocate.o'. Stop."make -j12 all" terminated with exit code 2. Build might be incomplete. 13:19:21 Build Failed. 1 errors, 0 warnings. Got any ideas? ChatGPT says my STM32 Repository Path is wrong but I can't find it in IDE. I don't understand how all these paths work and package manager + "Device Configuration Tool" (New name for MX I guess.) Which AZRTOS do I use? I have an H5. And that is not one of the AZRTOS options.I had this all working in 1.18.1 - I'm not sure what's getting shared between instances. So now I'm rebuilding in 1.19.0.

I've been playing around with an STM32F7508-DK, and I was successfully programming hex files with CubeProgrammer and running the application. I eventually tried doing a "Full chip erase", and now when I program the hex files that were working previously, the application does not seem to boot. There are no error messages from CubeProgrammer, just the application hanging at the "white screen".How can I recover the dev kit?

I am using the latest (pre-release, version 3.something) official extension, on Linux.Creating a new empty project went fairly smoothly (see my other form post about missing CMSIS headers), but when I tried to build the project, cmake couldn't find the toolchain.It turns out that cmake was trying to run "arm-none-eabi-gcc" and so on, assuming that they would be in the current PATH!  In fact, these executables are bundled with the extension and (on my Linux system) are located in~/.local/share/stm32cube/bundles/gnu-tools-for-stm32/13.3.1+st.8/binNo one (at least on Linux---not sure what Windows users do these days) is going to want to modify their system path to add a weird bin directory just for a single application.  The right way to tell cmake where to find the tools is to either modify *its* environment or give it full paths to each tool.  But the extension did not do this when it was installed---I think that is a bug because it is easy to automate.Complicating matter

Hello,A set of new constants have been added to stm32g070xx.h by CubeMX v6.15.0, and one of them has the wrong value (at line 4200):#define RCC_CFGR_SWS_LSE (0x00000100UL) /*!< LSE used as system clock */According to the datasheet, the right value for LSE is 0x00000020UL. Thanks.

Hi there!Both STM32CubeIDE and the ST MCUFinder tool incorrectly mark the STM32H503 as having a CORDIC and FMAC when they don't.Could this please be fixed as it's very confusing.Thank you!

The following line of code is generated by CubeMX v6.14.0.202502271554 for a STM32G070RBTx using FW Package v1.6.2:LL_ADC_SetCommonPathInternalCh(__LL_ADC_COMMON_INSTANCE(ADC1), LL_ADC_AWD_CH_VREFINT_REG|LL_ADC_AWD_CH_TEMPSENSOR_REG);The constants used are for the Analog Watchdog in ADC_CFGR1 and have no relation to the internal path configuration in ADC_CCR.  This can configure the wrong internal paths and change the ADC clock prescaler.As stated in the function description, the constants should be one of the following: * @PAram PathInternal This parameter can be a combination of the following values: * @arg @ref LL_ADC_PATH_INTERNAL_NONE * @arg @ref LL_ADC_PATH_INTERNAL_VREFINT * @arg @ref LL_ADC_PATH_INTERNAL_TEMPSENSOR * @arg @ref LL_ADC_PATH_INTERNAL_VBAT Regards,

I encountered a bug in the initialization code for HRTIM generated by CubeMX in STM32CubeIDE.Delayed Protection is enabled for HRTIM Timer F despite the "Delayed Protection Mode"="No Action" in the timer configuration. This does not happen for other HRTIM timers.This error occurred in my project with STM32G474RBT6 in STM32CubeIDE 1.17 (CubeMX 6.13) but I reproduced this bug on a clean installation of STM32CubeIDE 1.19.0 (CubeMX 6.15.0).All you need to do is set the LL driver for HRTIM and enable Timer F.In the MX_HRTIM1_Init function in main.c, there is a function call:LL_HRTIM_TIM_EnableDLYPRT(HRTIM1, LL_HRTIM_TIMER_F)I solved it by calling the function LL_HRTIM_TIM_DisableDLYPRT(HRTIM1, LL_HRTIM_TIMER_F) in the following USER CODE block...

Platform: linuxSteps to reproduce:+ Create a new STM32 Project- Select Board->H753ZI - STM32Cube FW_H7: V1.12.1- copy only the necessary library files and finish+ Select board options all+ Software Packs | Select Components | X-CUBE-AZRTOS-H7 3.4.0 | RTOS | ThreadX | Core (6.4.0): Enable+System core | SYS  | Timebaser soruce: TIM6- Middleware and Software Packs | X-CUBE-AZRTOS-H7 | RTOS ThreadX: Enable- Middleware and Software Packs | X-CUBE-AZRTOS-H7 | RTOS ThreadX: Enable | Core Init: check| Application Thread:TrueSave ioc, generate code and build22:36:05 **** Build of configuration Debug for project h7_tx_3.4.0_iter02 **** make -j4 all arm-none-eabi-gcc -mcpu=cortex-m7 -g3 -DDEBUG -DTX_INCLUDE_USER_DEFINE_FILE -c -x assembler-with-cpp -MMD -MP -MF"Middlewares/ST/threadx/ports/cortex_m7/gnu/src/tx_thread_context_restore.d" -MT"Middlewares/ST/threadx/ports/cortex_m7/gnu/src/tx_thread_context_restore.o" --specs=nano.specs -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -o "Middle

For COMP1 on STM32G0 here are the pin assignments from the reference manualI want PA1 and so I've chosen that in the STM32CubeMXHowever, the generated code sets and the value of InputPlus is  /** @defgroup COMP_InputPlus COMP input plus (non-inverting input) * @{ */ #define COMP_INPUT_PLUS_IO1 (0x00000000UL) /*!< Comparator input plus connected to IO1 (pin PC5 for COMP1, pin PB4 for COMP2, pin PB0 for COMP3 (for devices featuring COMP3 instance)) */ #define COMP_INPUT_PLUS_IO2 (COMP_CSR_INPSEL_0) /*!< Comparator input plus connected to IO2 (pin PB2 for COMP1, pin PB6 for COMP2, pin PC1 for COMP3 (for devices featuring COMP3 instance)) */ #define COMP_INPUT_PLUS_IO3 (COMP_CSR_INPSEL_1) /*!< Comparator input plus connected to IO3 (pin PA1 for COMP1, pin PA3 for COMP2, pin PE7 for COMP3 (for devices featuring COMP3 instance)) */ Which apparently maps to PB2 which is wrong! On the other hand, COMP2 I have chosen PB6 and its getting COMP2 seems to be

Hi,I am currently working with a custom PCB(Print Circuit Board) that features the STM32G031F4P6 microcontroller, and I am unable to locate the option to configure the Brown-Out Reset (BOR) in the Option Bytes within STM32CubeProgrammer for this device. Interestingly, I am able to see and configure the BOR on the Nucleo-G031K8 development board. Could you please clarify if there is a specific reason for this discrepancy? Is there a way to enable or configure the BOR on the STM32G031F4P6 on my custom PCB? Additionally, are there any alternative methods to monitor the power supply or track the voltage levels of the STM32G031F4P6 microcontroller?Thanks,

I'm trying to use the BOR in the STM32G031F4P6 microcontroler, as in the datasheet it shows that there is a BOR in this series. But, when I open the STM32cubeProgrammer, it doesn't show the BOR configurations at the Option Bytes window, and I couldn't arrive to activate it by code too.My question is if there is really a BOR available for all the G0 series or it is just for some of the microcontrolers in that series?If there is a BOR available, can I do it using the LL library?

I created a project in CubeMX for STM32G0B1. I added ThreadX middleware. I chose "Add necessary library files as reference..." I generated a CMake project. It was good, it worked fine. After a few weeks of work and dozens of regenerations CubeMX leaves out ThreadX C sources from the generated CMakeLists.txt.

Hi Community,I'm new to STM32CubeIDE and currently working with the STM32H723Zx in the LQFP144 package. While configuring the SAI1 peripheral, I encountered something that seems counterintuitive.When I set the output mode to Mono, the "Number of Channels" option only allows 2 channels to be selected. However, when I switch the output mode to Stereo, I can select up to 16 channels.This behavior seems reversed to me—shouldn't mono mode allow more flexible channel selection, or at least fewer limitations than stereo?I've attached a screenshot below for reference.Any insights or explanations would be appreciated!Thanks in advance.  

HiWe work on a project with a STM32H562. We use STM32CubeMX Version 6.14 with the Firmware Package V1.5.0 to generate a STM32CubeIDE project on Windows 11. I just found a wrong description in CubeMX.The description for SRAM2_ECC, SRAM3_ECC and BKPRAM_ECC, says the parameter in CubeMX needs to be set to “Disabled” to enable ECC check.Assuming I want to disable ECC, I would set the option to “enable” in CubeMX. CubeMX then adds OB_SRAM2_ECC_ENABLE, OB_SRAM3_ECC_ENABLE and OB_BKPRAM_ECC_ENABLE in MX_FLASH_Init(). All three options are defined in stm32h5xx_hal_falsh_ex.h as 0. According to chapter 7.11.24 of the reference manual, setting the bit to 0 in the register, enables ECC (exactly the opposite of what I wanted). Therefore, the description in CubeMX is wrong. To Disable ECC, configure Disable in CubeMX and to enable ECC, configure enable.  

HiWe work on a project with a STM32H562. We use STM32CubeMX Version 6.14 with the Firmware Package V1.5.0 to generate a STM32CubeIDE project on Windows 11. I think I just found bug in the code generation of CubeMX.I could reproduce the bug below in a new empty CubeMX Project.In Flash setting its possible to change the Flash Option Bytes Settings for the SRAM erase upon system reset. For SRAM2_RST this works as expected, and the code is generated in MX_FLASH_Init().But the option for SRAM13_RST does not work.If enabled or disabled the following code with a comment about a missing parameter is generated.  

Hello,create a project with the above settings and it will result in a build error (missing header file).Thank you.Best regards potter

I am working on a project using the STM32C092CBT6 microcontroller, which is specified to have 48 pins in a LQFP 48 (7x7x1.4mm) package. However, in the STM32CubeMX software, the package is displayed as having 63 pins.Could you please clarify if this is an issue with the STM32CubeMX software configuration for the STM32C092CBT6

Hello, My project is working with stm3h743 HAL version 1.0.0 (the first one ever created).I am trying to update to the latest HAL version which auto generate by Cubeide 1.18.1 (Fw package 1.12.2).  I am using spi1/2/4/5 full duplex mode but currently I have problem with spi 5 through _IT mode (no DMA).The problem occurs only when I use HAL_SPI_Receive_IT for reading. In the old HAL I use   this->handle.Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_2 and i am reading successfully through spi5.However, if I take the new hal and don't change anything else i get overrun error. (The same slave Hw of course).  One solution (but not a good one) I found is to use SPI_BAUDRATEPRESCALER_128 but it hurts performance and seem not to be stable.What could be the problem?  One more thing, I notice that in the old HAL if we are the master and use 2 lines, we call HAL_SPI_transmitReceive_IT (inside HAL_SPI_Receive_IT).In the new HAL its different- w

Hi,I'm using STM32CubeIDE with an ST-LINK V2 debugger (possibly a clone). When I try to upload my program to the STM32 board, I encounter the following issues:1. ST-LINK not entering DFU mode, so I can't update firmware.2. STM32CubeIDE gives this error:Error with command: GNU debugger version --versionCannot run program GNU debugger versi: Launching failedSetup:- STM32CubeIDE 1.18.1- ST-LINK V2 - Board: STM32F103C8T6- Windows 10Things I tried:- Installed ST-LINK drivers (STSW-LINK009)- Installed STM32CubeProgrammer- Checked Device Manager: ST-LINK appears- Tried STM32CubeIDE reinstallNeed help with:- Forcing DFU mode for ST-LINK V2- Resolving GNU debugger version - issue in STM32CubeIDEThanks!

STM32CubeProg 2.19.0.  STM32G041F8. MacOS 15.5. ST-Link.I'm working on setting the brown-out rising, falling, and enable options on an STM32G041F8.I started out by just using CubeProg to set the BOR_EN enable bit in the option bytes. Works correctly. It gives me the reaction I expected and I'm able to reconnect via CubeProg.Next I wanted to set the BORF_LEV to something other than 3 so I can test my code. I set it to 1, hit Apply, Cube prog complains that the connection is lost and it has disconnected from the device, and now when I try and connect I just get:17:13:46 : UR connection mode is defined with the HWrst reset mode 17:13:46 : ST-LINK SN : 31FF6A064D4E353828580643 17:13:46 : ST-LINK FW : V2J46S7 17:13:46 : Board : -- 17:13:46 : Voltage : 3.31V 17:13:46 : Error: Unable to get core ID 17:13:46 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug AuthenticationNo, I did not mess with the RDP values, just BORF_LEV

Hi everyone, I created an HID bootloader for the STM32G4xxx, it works and now I am trying to optimize the size. After compiling I can read this on the Build Analyzer a flash memory usage of 17.85 kB. After compiling I get this: When I flash this compiled code and read the flash memory I canclearly see that the memory usage is around 38 kB.  I also used the STM32CubeProgrammer to look at the actual memory (I didn't manage to use this function directly on STM32CubeIDE) and I can see that more than 38 kB are used in the memoryCan somebody explain why? Am I missing something about the Build Analyzer function?  

I’m trying to understand the peripheral current consumption figures generated by the PCC tool in CubeMX for my STM32U031 based project but can’t correlate the generated numbers with the values given in Table 43 of the datasheet, so I’m wondering which is likely to be correct, the PCC values or datasheet values?I’m also struggling to understand what the names used in the PCC ‘Peripheral Selection’ tab tick-boxes refer to; e.g. TIM1 vs TIM1/SYS, PWR/TIM2,  ADC1/SYS vs ADC1 CLK_KER_SYS etc etc, as there’s no help in the tool, or guidance in the UM1718, so any help here would be much appreciated!

Hello everybody,I have this project for the STM32F103C8 where the build analyzer of STM32CubeIDE says that only ~57% of flash is used:but while I'm flashing, it shows that the erased sectors are 0 to 56 (out of 63):and also using the STM32Programmer I see that the empty region starts at 0x800E048Now 56/63 ≈ 0xE048/0xFFFF ≈ 87% which is 30% higher than the stated 57% of build analyzer. This is kind of a bummer because now I will have to upgrade MCU since some other features must still be added to the project.How is it possible such a difference?