STM32 MCUs

I have four quite mature projects which I have developed with STM32CubeIDE 1.19.0 so far. Now I tested these projects with STM32Cube for VS Code using both toolchains.My environment:Debian TrixieVS Code 1.108.2  STM32CubeMX 6.16.1STM32CubeIDE for Visual Studio Code 3.7.0 fresh installed with all STM-Extension Packs and the following bundles in the project (from .settings/bundles.store.json): "name": "cmake", "version": "4.0.1+st.3" "name": "ninja", "version": "1.13.1+st.1" "name": "gnu-tools-for-stm32", "version": "14.3.1+st.2" "name": "st-arm-clangd", "version": "19.1.2+st.3" "name": "programmer", "version": "2.21.0" "name": "stlink-gdbserver", "version": "7.12.0+st.2" "name": "st-arm-clang", "version": "19.1.6+st.10" "name": "st-arm-clang-hybrid", "version": "19.1.6+st.3" I only used the release configuration and flashed the devices either with ST-Link or USB using the bundled programmer.I set up the project as follows:Generate a

I have a project that builds with no errors but when I "Run as..." the project builds but  never enters the upload sequence so doesn't upload.The board in question is a Nucleo F411RE & is communicating fine over UART. A previously loaded project is still sending out its debug messages, so I know the USB is good.Debug is not playing either... 

I noticed some options in the CUBE IDE for my H745's ADCs labelled "ADC 12-bit optimized resolution" and likewise for 14 bits. I have searched the references and the internet and find no explanation of how "optimized resolution" differs from the regular resolution. Does anyone know what this means, and where it is documented? Thanks 

I am facing an issue with STM32CubeIDE installation where the “STM32 Project” option and CubeMX functionality are missing even after downloading the latest STM32CubeIDE package from the official ST website, extracting the ZIP file, and running the installer as administrator. The IDE opens successfully, but essential features such as MCU/Board selection, CubeMX integration, and embedded software package management are not available, which prevents me from creating a standard STM32 project. I have already tried reinstalling the IDE, but the problem persists. I would appreciate guidance from the community on the correct installation procedure or any additional steps required to enable full STM32CubeIDE and CubeMX support on Windows. 

I am using the USB OTG FS on the STM32H7. My MCU is self powered, so I need to use VBUS sensing. Can a 3.3V signal be used for the VBUS sensing on PA9 or must it be 5V? Based on the linked forum, I believe 3.3V would work, but would like to confirm with the STM32H7 series.https://community.st.com/t5/stm32-mcus/management-of-vbus-sensing-for-usb-device-design/ta-p/49485#:~:text=On%20STM32F2/F4/F7/,136): How should I configure OTG_FS_ID PA10 so my MCU is device only? Should I leave it floating, pulled to LOW, or pulled HIGH?   Thanks in advance for any help on this topic.

The screen has 4 containers and many widgets. I am interested in keeping the names during the export to save lot of repertitive work

I am using below component tools MCU: STM32H750IBT6 IDE: STM32CubeIDE Version: 1.20.0 GUI: TouchGFX Version: 4.26.0 SDRAM: IS42S32400J-6TLI FLASH: MT25QL512ABB8ESF-0SIT (QUADSPI) QUADSPI With the following pin out:   QUADSPI Configuration:   Thank you in advance!  

I'm trying to use dual layers in LTDC of STM32N657X0HxQ controller. In the STM32CubeMX, I tried to set the Secure bit of RISUP for LTDC_L2 in RIF setting view, but the box is in gray color and is not selectable as follows.When I generate code with this box unchecked, my program does not work. So I manually changed the Secure bit in source code, which made LCD display work fine.How can I change the Secure checkbox in STM32CubeMX?My STM32CubeMX is version 6.16.1 for Windows 11.I've attached the ioc file.

I'm currently using an STM32H7S78-DK, and I'm correctly able to run TouchGFX with FreeRTOS and everything. I also an error handler function that, in case of a crash of TouchGFX it writes directly to the framebuffer.Now, I would like to do a similar thing but on the boot code, so basically before the classic jump if (BOOT_OK != BOOT_Application())I have an external RAM mapped at the address 0x90000000 which works correctly in TouchGFX with .icf likedefine symbol __region_EXTRAM_start__ = 0x90000000; define symbol __region_EXTRAM_end__ = 0x91FFFFFF; define region EXTRAM_region = mem:[from __region_EXTRAM_start__ to __region_EXTRAM_end__]; place in EXTRAM_region { first section TouchGFX_Framebuffer , section Video_RGB_Buffer , section Nemagfx_Stencil_Buffer };I wanted to use the same section of memory in the Boot, accessing the framebuffer directly, so I edited the .icf of the boot withdefine symbol __region_EXTRAM_start__ = 0x90000000; define symbol __region_EXTRAM_end_

I'm currently using an STM32H7S78-DK, and I'm correctly able to run TouchGFX with FreeRTOS and everything. I also an error handler function that, in case of a crash of TouchGFX it writes directly to the framebuffer.Now, I would like to do a similar thing but on the boot code, so basically before the classic jump if (BOOT_OK != BOOT_Application())I have an external RAM mapped at the address 0x90000000 which works correctly in TouchGFX with .icf likedefine symbol __region_EXTRAM_start__ = 0x90000000; define symbol __region_EXTRAM_end__ = 0x91FFFFFF; define region EXTRAM_region = mem:[from __region_EXTRAM_start__ to __region_EXTRAM_end__]; place in EXTRAM_region { first section TouchGFX_Framebuffer , section Video_RGB_Buffer , section Nemagfx_Stencil_Buffer };I wanted to use the same section of memory in the Boot, accessing the framebuffer directly, so I edited the .icf of the boot withdefine symbol __region_EXTRAM_start__ = 0x90000000; define symbol __region_EXTRAM_end_

Hello,I'm experiencing an issue with the internal LDO regulator on the STSPIN32G4 MCU. The LDO is outputting 4.1V instead of the expected 3.3V, and I've been unable to resolve it despite trying multiple configurations.Problem Details:Target: 3.3V VDD from internal LDOActual output: 4.1V when input voltage > 4VBehavior: When input voltage is 3.33V, output is 3.05V (which seems reasonable given dropout), but when input is >4V, output remains at ~4.1V instead of regulating to 3.3VWhat I've Tried:All configuration options listed in Section 5.1.2 of the datasheetReplicated the three circuit configurations from Figure 9 ("3.3V LDO regulator supplied through VCC")Various register settings without successExpected Behavior: The LDO should regulate the output to 3.3V whenever the input voltage is above 3.3V + dropout voltage, correct?I've attached my schematic and screenshots showing the output voltages. Any insights into what might be causing this behavior or what configuration I might be

Code generated by CubeMX use Windows line-endings, which generate huge problems under other operating systems (repository, editors, etc.). You have to strip CR-LFs after every code generation.Somebody should use standard method of platform-independent text file generation (StringBuffer and System.lineSeparator()).

Hi,I just wanted to check if is it dangerous to move the isr_vector inside the text section like this:.text :{. = ALIGN(4);KEEP(*(.isr_vector)). = ALIGN(4);FILL(0x00000000);. = ALIGN(4);*(.text) /* .text sections (code) */*(.text*)*(.glue_7) /* glue arm to thumb code */*(.glue_7t) /* glue thumb to arm code */*(.eh_frame)KEEP (*(.init))KEEP (*(.fini)). = ALIGN(4);_etext = .; /* define a global symbols at end of code */} >FLASHI implemented a CRC32 integrity check and it doesn't work because the gap between the isr_vector and text section is always Fs when I debug with the CubeIDE, but if I download the .elf with CubeProgrammer, the gap is filled with 0s, and in that case it works.TY for your help.

Hi All,GreetingsWe are using STM32U585 on custom board with Trust zone enabled and now facing a connection issue with stm cube programmer in hotplug mode, now unable to connect to the microcontroller and getting ST-LINK error  as : DEV_TARGET_CMD_ERROR.When NRST is low continuously(pressing the Reset Switch) the connection to the controller through Cube Programmer is happening, but we are unable to change any option bytes, to revert back to Non Trust Zone Code. Once the reset switch(NRST) is high, it is going back to the same error. Any suggestions for this issue and how can we resolve this?Thanks and RegardsPhilip  

 Hardware ConfigurationMCU: STM32F469NIH6Custom Board: Pin-to-pin replica of STM32F469I-DISCODisplay: HF-35040-X365-A0 (3.5-inch, 800x480 RGB parallel interface)SDRAM: IS42S32400J/F (16MB, 0xC0000000)Interface: LTDC (NOT DSI - DSI explicitly disabled)Framework: TouchGFX 4.26.0Working ReferenceThe same display works perfectly on STM32F429 with the same LTDC configuration, so the display hardware is confirmed functional.Problem DescriptionThe display continuously shows RGBW color cycling (white → red → green → blue, repeating every ~1 second) instead of rendering the TouchGFX UI.Critical observation: Changing LTDC configuration parameters (e.g., framebuffer width from 800 to 400 pixels) has NO EFFECT on the display output - the same RGBW pattern continues unchanged.Current LTDC Configuration // Clock ConfigurationSystem Clock: 180 MHz (changed from overdrive to voltage scale 3)PLLSAI: N=192, R=5LTDC Clock: ~25 MHz // LTDC Timing (for 800x480 @

STM32CubeMX standalone hangs on File → New Project (infinite loading, no error message). The problem is fully reproducible.I have tried:– reinstalling CubeMX– different CubeMX versions– Java reinstall– offline mode– clearing STM32CubeMX cache/AppData STM32CubeIDE (latest) works normally but I can not generate projects with CubeMX. OS: Windows 11 pro Has anyone experienced this issue recently or knows a workaround / fix?Any advice from ST would be appreciated.

I am currently working with the STSAFE-A110 and I have noticed a significant lack of documentation for those who need to implement or understand the driver logic.For instance, when generating ECC asymmetric key pairs, the official datasheet mentions the Generate Key command (¶ 4) but does not document its I2C syntax or semantics.Although I am using the STSELib middleware, I have found that its APIs, such as stse_generate_ecc_key_pair() also lack exhaustive documentation. A specific example is the PLAT_UI16 usage_limit parameter; its purpose is never explained.By digging into the STSELib source code, it appears usage_limit parameter is passed directly to the STSAFE-A110 via I2C.Furthermore, in the Doxygen documentation there is an example where usage_limit is set to 100,while the STSAFE-A120 examples use 255. /* ## Generate key pair in slot 1 */ uint8_t slot_1_public_key[stse_ecc_info_table[STSE_ECC_KT_NIST_P_256].public_key_size]; stse_ret = stse_generate_ecc_key_

Hello all,I have created a project with STM32CubeMx based on this evaluation board:I generate the source code, and I  can compile it correctly from STM32CubeIDE.The problem is when I try to Run or Debug it, I get this message:If anyone can help me I would appreciate it.Much thanks in advance.  

Hello, everyone.Can the STM32F407VE encrypt multi-byte messages to maintain the confidentiality of messages between the host and client (stm32)? If so, what type of encryption can be run on this processor?Thank you:)

I am working on an STM32H563 project with a custom bootloader and two application slots (APP1 / APP2).This is my memory layoutBootloader: 0x08000000APP1: 0x08022000APP2: 0x0806C000The bootloader is already deployed in the field and cannot be modified.The bootloader jump sequence is standard:Validate applicationSet SCB->VTOR = APPx_START_ADDRESSLoad MSP from APPx_START_ADDRESSJump to reset handler at APPx_START_ADDRESS + 4 This works perfectly when I build the application the “manual” way:Manually change FLASH ORIGIN in the application linker script to 0x08022000Manually change VECT_TAB_OFFSET in system_stm32h5xx.cThen i ReBuild → flash → bootloader jumps and application runs correctly.I would like to automate this process using cmake , without manually editing the linker script and system_stm32h5xx.cSo I implemented:A parameterized linker script template (STM32H563xx_FLASH.ld.in)CMake configure_file() to generate slot-specific linker scriptsCMake target_compile_definitions() to

Hi everyone,I am trying to get a USBX CDC ACM device running on an STM32F407ZGT6, using a project generated by STM32CubeMX. I'm basing my work on the example provided for the STM32F469 (DEVICE_CDC_ACM).Problem DescriptionThe device is partially working. When I plug it in, Windows Device Manager recognizes it and assigns a COM port. However, when I try to connect using any terminal software (Tera Term, PuTTY, etc.), the connection fails. The software cannot open the port.Debugging FindingsThrough debugging, I've identified a key issue in the initialization sequence:Instance Activator Not Called:​ The callback function I set for cdc_acm_parameter.ux_slave_class_cdc_acm_instance_activate(which is CDC_Init_FS) is never triggered. This prevents the proper initialization of my CDC ACM instance.Null Pointer in Thread:​ The usbx_cdc_acm_read_thread_entryfails because it encounters a null pointer. Specifically, the comparison ux_utility_memory_compare(data_interface->ux_slave_interface_class

Hi Everybody,     Now i met an issue for STM32U575/STM32U585 Programming time different, below is my test log, i don't why get the different time, since i do the erase in any time. The blank chip programming time is 34s, and NOT BLANK chip programming time is 13s. NOT BlankSTM32_Programmer_CLI.exe -c port=SWD sn=55FF69064978865014230767 freq=8000 -e all -w "D:\Download_Tool\FW\EVT_SMT_2.0.1.6\RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin" 0x08000000 -v      -------------------------------------------------------------------                       STM32CubeProgrammer v2.14.0                        ------------------------------------------------------------------- ST-LINK SN  : 55FF69064978865014230767ST-LINK FW  : V2J45S7Board       : --Voltage     : 1.86VSWD freq    : 40

Hallo everyone,Before I encountered a bug in an USB_OTG_FS library function (see previous post), I struggled to find out when the function  'CDC_Transmit_FS(uint8_t* Buf, uint16_t Len)' has finished, meaning the content of the 'Buf' argument is completely transmitted.After a thorough search through the various sources and the Reference manual RM068, I concluded the Register DOETMSK has a bit XFRCM that should fire an interrupt in case the the transmission has finished. I assume the common interrupt function ' HAL_PCD_IRQHandler(&hpcd_USB_OTG_FS)' will deduce that function 'CDC_TransmitCplt_FS(.......)' should be fired when the XFRCM creates an interrupt.Despite my efforts I could not find a way to:   a) find out if my assumptions above are complete and/or correct   b) how to handle the registers for the USB_OTG_FS device. In the SWF column of the debugger I saw 4 groups of OTG registers, but never found a way to access them in my code. And the complexity of

Hi,there has been some interest in using STM32CubeMX code generation and also the Cube build tools (CMake, GCC, Ninja) in a headless mode, particularly for CI and typically via a Docker image, e.g. 1, 2, 3, 4. There are several benefits of being able to build STM32 projects automatically via CI, including specifically the code generation by STM32CubeMX, and to achieve this by using a Docker image:The CI setup acts as a "single source of truth" for the build process that defines the exact setup of tools needed, in contrast to some "random" collection of tools that happens to be installed on an individual developer's PCTherefore the CI also defines if a project's state or e.g. merge request is compilable; if it doesn't build on the CI, don't accept the change. No more "works on my machine" (at least regarding the build process)If the CI-based build is performed through Docker, the Docker image (and its Dockerfile) act as a documentation of the exact tools and versions

Hi,I'm using a Nucleo stm32WL55JC1 board, and i'm trying to run the SBSFU_2_Slots_DualCore example. Used the example selector to start the project. When I tried to compile any of the sub projects they all fail and i have a lot of warnings for include paths that dont exist in my computer. I'm using stm32cubeIDE v2.0.0, i tried using the v 1.11.0 because it said it the release notes that was the version used for STM32Cube_FW_WL_V1.4.0, but the IDE does not accept this package and does not detect it inside the repository folder, even after installing it itself because the examples it shows are from v1.4.0 of the FW package. I also get the error that i can't find the file kms.h that is included in a .c file. When the prebuild.sh runs it runs in the wrong directories, like doing "cd ../../../Middleware.....", in this case there are too many "../" in the path, and this happens a lot in the script.How can I run this example? What am I missing?Thanks in advance!