STM32 MCUs Software development tools

In STM32CubeMX, here is the orientation for a chip with a red dot marking pin 1 at the top left when text reads from left to right.In real life, here is the orientation for a chip with a red dot marking pin 1. As far as I'm aware, all STM32 chips are oriented like this, with pin 1 at the bottom left when text reads from left to right. Why is the text rotated 90 degrees differently? Is this intentional? If there is a reasonable explanation, I'm interested in hearing it. It seems to only add confusion. Wouldn't it make more sense if the default orientation (or at least the text orientation) to match between the two? In STM32CubeMX, you can rotate the part for convenience. This is useful. However, the text also rotates, so if you put pin 1 in the bottom left like in reality, the text is now rotated. (This is the same story in STM32CubeMX2.) 

Hi,I am trying to migrate a STM32F767ZGT6 based project to STM32H743ZGT6. According to AN4936, they should be pin to pin compatible. When I manually compared the each pin, and assigned the state of each PIN as used in STM32F767ZGT6 to STM32H743ZGT6, they seem indeed to be P2P compatible too. But If I try to list PIN compatible MCUs in STM32CubeMx, as of the latest v6.17.0, STM32H743ZGT6 is not listed. Please see the screenshot below:Am I missing something? Or this is a bug in CubeMX? I just don't want to throw 100s of $ down the sink. I attached my IOC file to see if anyone can reproduce my problem.Thanks.

Hello, I have a problem verifying the HCLK frequency for Nucleo-C562RE. I configure the clock to 144MHz (see image below). When I start the application I print the HCLK frequency: SEGGER_RTT_printf("---- MCU started at %lu[Hz] ----\n", HAL_RCC_GetHCLKFreq()); I get 48MHz: ---- MCU started at 48000000[Hz] ---- While stepping through the HAL_Init code I see that the code thinks that the clock source is LL_RCC_SYS_CLKSOURCE_STATUS_HSIDIV3 (48MHz) uint32_t HAL_RCC_GetSYSCLKFreq(void) { uint32_t sysclockfreq; uint32_t sysclk_source; sysclk_source = LL_RCC_GetSysClkSource(); if (sysclk_source == LL_RCC_SYS_CLKSOURCE_STATUS_HSIS) { /* HSIS used as system clock source */ sysclockfreq = HSI_VALUE; } else if (sysclk_source == LL_RCC_SYS_CLKSOURCE_STATUS_HSIDIV3) { /* HSIS used as system clock source */ sysclockfreq = HSI_VALUE / 3U; } #if defined(HSE_VALUE) else if (sysclk_source == LL_RCC_SYS_CLKSOURCE_STATUS_HSE) { /* HSE used as system clock source */ sysclockfreq = HSE_VALUE; } #endi

I’m working with an STM32H533 and would like to generate an SFI firmware using STM32CubeProgrammer.Is it possible to use the SFI procedure without an HSM?In particular, can the license file be generated without the card?

Hi C++ Developers,   As you may know, developers downliading Cube tools from st.com will receive an e-mail asking them to provide feedback. From this feedback we see some complaints vs the C++ support in STM32CubeIDE. The complaints are however lacking details. We are aware of several C++ topics which could be improved. But without detail, it is hard to tell what is seen as the highest priority... Here is where we need your help!   Brainstorming on the main C++ issues in STM32CubeIDE (and Cube ecosystem) I arrive at this list of issues::   CubeMX issue: CubeMX does not generate a main.cpp, I have repeatedly seen beginner struggle to create their main.cpp and make calls to C code...   HAL issue: Nor do we offer C++ based HAL drivers or any other middleware.   CubeIDE editor: The Eclipse/CDT indexer providing auto-complete and other editor features in Eclipse was largely sponsored by Intel. There is much less up-stream activity on C++ support

Hi everyone,the update to CubeMX 6.17 seems to introduce a new valid range of the "First RX Descriptor Address" of the Ethernet setup on a NucleoH755 board. This is also the case for the STM32H745.This is the valid range according to the CubeMX field description (there is also a typo for the Parameter Description "Fisrt"):First Rx Descriptor AddressFirst Rx Descriptor Address must be between 0x24000000 and 0x30047fff.Parameter Description:Fisrt Rx Descriptor address must be only in the D2 Domain AHB SRAM. Rx descriptor address must not exceed Max value and must no overlap with Tx descriptor and Rx buffer. These areas must not be cacheable.This contradicts the knowledge base article: How to create a project for STM32H7 with Ethernet and LwIP stack working The reference manual also states that 0x3004000 - 0x3004FFFF should be part of the D2 Domain AHB SRAM3 and hence be part of the intended area. Is this just a bug or do I overlook something?Kind regards

I do not know what happened. If I double-click ioc file, it used to open inside CubeIDE. But now it will open inside another separated cubemx window. I may have changed some settings by mistake.How to change the settings back so I can open ioc file inside CubeIDE?

Where can I find the Option in the Preferences  to set the text of the function Name to “Bold”?

I am running the pre-compiled "object Detection" files on the STM32N6570-DK and am in the process of trying to generate my own STM32CubeMX setup project for the fsbl.I am having difficulty setting up the numerous options for the DCMIPP for this project and have read a lot of the recommended documentation but there does not seem to be any specific details for interfacing to the MB1854 camera module on this kit.From what I can figure out the "Object Detection" demo uses pipe1 for the display and pipe2 for the NPU processing but I am lost as to what settings to use for DCMIPP in STM32CubeMX.I need to know what pipe formats, data types etc are needed for each of the pipe1 and pipe2 settingsCan anyone please help me with this?

Hello,I have a custom PCB that uses an STM32L4R9 controller and runs two applications. One is a bootloader and other is the actual app. The files are called boot.hex and app.hex.The boards are made via a vendor and programmed with these files during ICT. We use ST Link programmer and SWD connection to program the devices.I use the ST Link V2 Utility CLI to do this.A batch file is made that runs all the commands that program the option bytes, erase chip, and programs the above files.The problem I am facing is, the batch file fails to execute the first time. It fails after the option bytes step. The second time however, it always executes and programs the applications successfully.I did wonder whether this is because the Read Out protection for STM32L4R is set to 1 from the factory? But again, I tried to revert the option bytes to factory after which I cannot read the flash memory again before setting it back to Level 0.But if I connect a new and unprogrammed board to the ST Link V2 Util

Hello guys, I started a project using STM32C552RET6 and STM32CubeIDE. When I use the autocomplete feature to select a HAL function, I can’t find it. I have to type the function manually.Does anyone know how I can fix this problem?Thanks for your help.

Locking the controller (NUCLEO-C562RE - RDP level 2 with OEM key) works fine with J-Link / ST-Link (SWD). E.g.stm32_Programmer_CLI.exe -c port=JLINK -lockRDP2 0x11111111 0x11111111 0x11111111 0x11111111 -ob RDP_level=0x72 ------------------------------------------------------------------- STM32CubeProgrammer v2.22.0 ------------------------------------------------------------------- Connecting to J-Link/Flasher Probe Device=Cortex-M33 Device ID : 0x44E Voltage : 3.29V Frequency : 4000 KHz NVM size : 512 KBytes Lock RDP2 password successfully done UPLOADING OPTION BYTES DATA ... Bank : 0x00 Address : 0x40022050 Size : 112 Bytes ██████████████████████████████████████████████████ 100% Bank : 0x01 Address : 0x40022098 Size : 8 Bytes ██████████████████████████████████████████████████ 100% Bank : 0x02 Address : 0x40022070 Size : 8 Bytes ██████████████████████████████████████████████████ 100% Bank : 0x03 Address : 0x40022080 Size : 8 Bytes ███████████████████████████

Hi SupportI have experience in STM32 with Zephyr but I am trying out AMP for the first time.So I am trying out OpenAMP example from STM32CubeIDE. I can compile the example but cannot flash the same.I have the following errorThe ST-Link device is present as shown below I have tried other boards like NUCLEO-G431RE with some simple UART example and work well.I have problems only with AMP board, I am not able to flash M4 and M7 core. My dev environmentUbuntu 22.04 and STM32CubeIDE ver1.1.8.1 Could anyone please help me understand the same?  

CubeMX Project Manager has a bug, where when I accidentally cleared the "Project Location" field and moved the cursor away CubeMX complains that project location cannot have special characters and cannot be empty. But this popup does not go away and gives you no chance to correct your mistake. Screenshot attached. Host OS: Ubuntu 24.04.4 CubeMX version: 6.15.0  Edit: Turns out there was a new version of CubeMX (6.17.0) where this problem disappears. You click 4-5 times on OK and the dialog disappears. Should I delete the question in this case?

Hi,When I downloaded a .hex file to my STM32H563VGT6 (1MB Flash) using STM32CubeProgrammer v2.20.0, I encountered an issue where it would erase the wrong sector. For example, as shown in the image below, it was supposed to erase sectors (76..91) and sector 115, but I found that the contents of sector 27 is erased.I also try to "Erase selected sectors" (76..116) manually, but sector 27 still be erased.However, I did not have this problem when downloading the same .hex file using an STM32H563ZIT6 (2MB Flash).

I use  GPU2D on STM32U599Z .On CubeMX, I  checked Activate check box  GPU2D  at "Pinout & Configuration".and  I saw " Project Manager > Advanced Settings" There is not GPU2D In Register Callback Groupe. However , The Generated code stm32u5xx_hal_conf.h have  "  #define USE_HAL_GPU2D_REGISTER_CALLBACKS 0U /* GPU2D register callback disabled */How to set this setting? 

(Moved to a separate thread from  Do you need a fast slave interface with high throughput? This is for you.)MCUFinder does not consider PSSI if I do not overlook something.

Hi,I use cubemx to generate code for STM32CubeIDE, compile is OK, but the initial process run fail with HAL_Delay function, the HAL_GetTick() always return 0 so the program blocked here. attached is my .ioc file, any anyone help for thie issue?

Finally was able to test STM32CubeMX2 with a NUCLEO-C562RE board.Simple LED blinking project, and here's what I found out. Project bloat:STM32CubeMX2: 26.2 MB of generated data and when compiled 41.1 MB (NUCLEO-C562RE)STM32CubeMX: 4.6 MB generated and compiled 15.7 MB (NUCLEO-C031C6, same functionality) The old STM32CubeMX included only the HAL libraries actually used.The new one dumps everything in.That's a 5.7x increase for a blink LED. Missing Release configuration:Generated CMake project contains only Debug configuration - No Release.Interesting, because the official "MOOC STM32CubeMX2" video at 4:53 clearly shows both configurations.Either something changed or the video is misleading. Creating Release configuration manually requires editing multiple CMake files, including inside the cmake folder — supposedly overwritten on regeneration (in practice, changed only at project creation).Not trivial if you're not a CMake expert.I did it once manually, but then ended up using Claud

  @lbthomsen of STM32World has published a review of the new STM32CubeMX2, what is good (not so much), indifferent and BAD (a lot). He tries to get it working, browse through the features, and has a lot of opinion on this matter.  https://www.youtube.com/watch?v=61r83TTzDfk End of the day, IF you plan to use future STM32 families (starting with STM32C5) you have no choice than to use CubeMX2 AND the very painful migration from HAL to HAL2 (not compatible, maybe some future tool can assist in such migration). Even if migration is possible, then you will have the pleasure to support multiple versions of YOUR code on old vs new MCU families. Have FUN. For the people without perfect vision (like myself), embrace yourself for 4 pixels font sizes, and contrast-free dark-white-on-white-backgrounds text. Lovely! At least there is plenty of white space around the text that can sooth your soul. Now is the best time for experienced STM32 shops to leave HAL, CubeMX and go Bare

Moved to CubeMX forum as this is about the CubeMX functionality - even though it's within CubeIDE.hello everyone. I'm trying to code my H7 chip. In the .ioc shen I try to generate code I take this error. (I'm using CubeIDE 1.19.0) then I turn back and look at my Clock configuration, only this HSI button has a issue.  and ı dont know how to fix this and is there any problem with the HSI usage. also the other of all the clock config is :I couldtn find same problem in the forum. or a solution. 

Hello,STM32CubeMX2 looks good and I started my first STM32C5 Project.But what I miss: The Power Consumption Calculator. It was a helpful and often used tool in STM32CubeMX and I could find it in the new Generation 2.Is it planned to be integrated in future releases?Thanks!Markus

Subject: Performance difference between GCC (-O2) and Keil ARM Compiler in motor control applicationDescription:I am currently developing a motor control application using STM32F303 and comparing the performance of two development environments: STM32CubeIDE (GCC ARM toolchain) and Keil µVision (ARM Compiler).Hardware & Software Environment:MCU: STM32F303STM32CubeIDE Version:2.1.1Keil MDK Version: v5Motor Control SDK Version: X-CUBE-MCSDK v6.4.2Optimization Level: -O2 for both compilersFOC Algorithm: [hall FOC]PWM Frequency: [16 kHz]Test Methodology:I have ported the exact same motor control source code to both environments. Performance is measured by:I noticed that the .hex file generated by Keil （100 KB） is smaller than the one generated by STM32CubeIDE （103 KB）. Does this come from the compiler difference?Has anyone performed similar benchmarks between GCC and ARM Compiler for motor control and found strategies to close the gap?

Hello,We are developing a STLDR to be used with STM32CubeProgrammer and are having what is seemingly random issues when programming hardware.We have already written the XSPI interface which works when executed in FLASH using test calls, but as soon as the interface is placed into the STLDR framework and used with STM32CubeProgrammer we are seeing failures of either the Init or SectorErase functions.Sometimes it will work after a full board reset, but not always.We have tried linking the loader at the undocumented 0x20003004 RAM address but this seemingly does not fix the issue.We have tried using our standard development IDE (not ST) which has been successful in the past, but also following the STM32Cube tutorial and repository here, replacing the QSPI calls with XSPI:https://wiki.st.com/stm32mcu/wiki/Getting_started_with_External_memory_Manager_and_External_memory_loaderhttps://github.com/STMicroelectronics/stm32-external-loaderThe hardware is a custom board using the H573II with

Description:In STM32U083 series, when multiple UART/LPUART instances share the same NVIC interrupt vector (e.g., `USART3_LPUART1_IRQn`), STM32CubeMX incorrectly generates `HAL_UART_IRQHandler` for all instances, even if one of them is configured in IrDA mode.This leads to a compilation error because:1. The handle for the IrDA instance is generated as IRDA_HandleTypeDef hirdax; (correct).2. However, in stm32u0xx_it.c, it attempts to call HAL_UART_IRQHandler(&huartx); using an undefined huartx handle.Environment:STM32CubeMX Version: 6.17.0OS: Ubuntu 24.04 LTSMCU: STM32U083RCTxFirmware Package: STM32Cube FW_U0 V1.3.0 Steps to Reproduce:1. Create a new project for STM32U083RCTx.2. Configure USART3 mode as IrDA.3. Configure LPUART1 mode as Asynchronous.4. In the NVIC Settings tab, enable the interrupt for "USART3 + LPUART1 global interrupt".5. Generate the code.6. Check `stm32u0xx_it.c`.Actual Result:The generated ISR code looks like this:/** * @brief This function handles US