STM32 MCUs Software development tools

CubeProgrammer is reading from some suspicious addresses on the stm32u031.For example, sector erase from the GUI:09:24:20:751 : r ap 0 @0x1FFF37FE 0x00000001 bytes Data 0xFFFFFFB109:24:20:755 : Flash sector erase ...09:24:20:755 : r ap 0 @0x40022040 0x00000004 bytes Data 0x0000000009:24:20:755 : Flash erase...and from the CLI:...r ap 0 @0x1FFF777C 0x00000004 bytes Data 0x00000000...Erase sector(s) ...r ap 0 @0x40022040 0x00000004 bytes Data 0x00000000Flash erase...0x40022040 is offset 0x40 into the FLASH block which is labelled as reserved in RM0503 3.7.22 Table 19.0x1FFF37FE and 0x1FFF777C are high in the option bytes block.

I am using STM32h743XIH6 MCU with qspi flash MT25QL512ABB8ESF-0SIT same as STM32H743I-EVAL. when i try to load data to qspi flash using STM32CubeProgrammer and loader MT25TL01G_STM32H743I-EVAL.stldr provided by ST, data read/write working without any on eval board. But when i try the same in my custom board with same configuration it is not working. In my custom board if I erase and read flash content i am getting data as shown in QspiFlashMemoryErase.pngWhen i write data and read it back, i am getting data as shown in QspiFlashMemoryDataWrite.pngData is being written correctly on every even bytes, but all odd number bytes are wrong and always showing as 0x99I have chechked all signals on scope, all signals are coming.i have replaced the flash IC, just to confirm IC functionality, but still not working.

Downloaded the update of STM32CubeMX 6.17.0 to install the ARM version on my M4 MacBook Air with macOS Tahoe.  The issue is that it installs an Intel version and not an ARM version.  I uninstalled version 6.16 before installing this updated version.The installer file was SetupSTM32CubeMX-6.17.0-Mac-ARM.app.tar downloaded from the STM32CubeMX download page.The next macOS version after Tahoe will not support Intel apps and was expecting an Apple Silicon version as per the download!What is up with this?

Hello.I created a project for the STM32F769I-DISCO board using CubeMX.I am trying to follow an LVGL example, but the example uses BSP-based libraries, and they are not working in my project. After checking, I found that there is no BSP included anywhere in the generated project.From what I understand, when selecting a board in CubeMX, the BSP should normally be included automatically. However, in my case, it is not.I tried downloading the STM32F769I-DISCO BSP from GitHub and manually copying it into the Drivers folder. However, this caused many build errors, possibly due to missing dependencies or incomplete integration, so I reverted those changes.Could you please advise how to properly include or enable BSP for this board when using CubeMX?Thank you.

Hello,Trying to move complete *.cpp.obj to external SRAM configure via FMC. Check the below .ld file for STM32F7 controller.MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 512K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 2048K EXT_SRAM_DATA (rw) : ORIGIN = 0x60000000, LENGTH = 256K EXT_SRAM_MODULES (rw) : ORIGIN = 0x60040000, LENGTH = 256K } /* ========== Section for Buffers / Variables (up to 256KB) ========= */ .ext_sram_data : { . = ALIGN(8); KEEP(*(.ext_sram_data)) KEEP(*(.ext_sram_data*)) . = ALIGN(8); } > EXT_SRAM_DATA AT> FLASH .ext_sram_modules : { . = ALIGN(8); KEEP(*(testModule.cpp.obj)) . = ALIGN(8); } >EXT_SRAM_MODULES AT> FLASH After code compile, I can see the build details asMemory region Used Size Region Size %age Used RAM: 119928 B 512 KB 22.87% FLASH: 246444 B 2 MB 11.75% EXT_SRAM_DATA: 0 B 256 KB

In STM32CubeMX v6.17.0, in the left side of the Pinout & Configuration panel, if the mouse cursor is within a table that lists peripherals, the scroll wheel doesn't do anything. I expect it to scroll the window. You need to move it outside of the table but still within the bounds of the "Categories" tab in order to scroll up and down. This is super annoying because it means you have to have the cursor on the far left or far right of this window otherwise a table will appear when scrolling and the mouse wheel will stop working.In the screenshot, having the cursor anywhere in the red box will stop it from scrolling. I expect it to scroll the green scrollbar.

I've relocated the .text section of a test project to SRAM1 through the C-bus address (starting at 0x0A00 0000). I have relocated the main function into SRAM1.The code runs fine, and if I suspend the chip and navigate to the 0x0A00 0000 address space on the disassembly view the code and debug information (function names, source code references, etc.) is present and visible.Navigating to 0x2000 0000 on the disassembly view also displays the same assembly instructions but without any debug informationWith main located in SRAM1, the debugger fails to stop on entry into main, despite the debug configuration setting.If I set a breakpoint on any code that is located in SRAM1, the debugger does not suspend on those breakpoints, UNLESS I set a breakpoint in the reset handler (which is in FLASH), hit the breakpoint after a reset, and step into main from the reset handler, then it stops on breakpoints normally. This behavior occurs regardless of whether code is acc

I want to debug my board on Vscode, But I cannot find openocd scripts now. Without openocd scripts, how can I debug my board?

Hi,I’m trying to understand how the build setup works in VS Code.Could you advise where and how to configure VS Code so that .bin and .hex files are always generated when building both Debug and Release configurations?Is this controlled via CMake, or through one of the .json configuration files?Whichever approach is correct, could you also share the specific scripts or commands that need to be used?Thank you :) 

Hello,I am using STM32H750ZB variant for an HMI custom project and I am using SDRAM via FMC.When I configure FMC in cubeide1.19.0, I can't see the FMC_NBL0 and FMC_NBL1.I can actually add these pins as GPIOs, but I can't define the AF as AF12_FMC.I know from the datasheet that this package supports it but I want your confirmation as I still don't have HW to test and don't want to change the package again and redo the HW.Thanks,Ayoub  

As i updated my STM32CubeIDE to the latest site version available, i am getting new errors in my working code.Those errors before update were displayed as warnings but after update they are turning into errors. passing argument 2 of 'xfunc' from incompatible pointer type [-Wincompatible-pointer-types]My -Werror is unchecked from the start.If someone can help me how to resolve it, Thanks in advance.

I'm using a STM32F407VG (actually a disc-1 board). I've set I2S2 in full-duplex master mode and generating the MCLK out on PC6 for an external slave codec. So far so good.Now i want to set SDIO interface in full-duplex 4-bits mode but CubeMX throws a warning about a partial conflict with I2S master clock out. Frankly i have no clue about it, can i safely ignore the warning? 

To sum up my project, i get temperature value from NTC. I made ADC reading. There is no problem about getting values. I define temperature value as floating point variable. When observing it on debug screen, because it was floating, numbers after . is too much like seven digit. As you see in picture, is there any way to reduce the number of digits on debug window? temperatureDisplay 

Recently, I bought a clone of ST-Link V2.I am trying to program a RAK5205 board with an STM32L151CB MCU on it, with a basic program for blinking LEDs.If I use the STM32 ST-Link Utility v 4.5.0.0, open the file RAK5205_Blink.hex and program the MCU, it ends correctly and the program runs without problems on the board. If I want to completely erase the Flash memory, it does it correctly with this indication:Device ID: 0x429Device flash Size: 128KBytesDevice family: STM32L100x8xxA / L15xx8xxAFlash memory erased.Now, if I open the STM32CubeProgrammer v2.1.0, open the same file RAK5205_Blink.hex, the ST-Link v2 is recognized and connected correctly, read the memory of the MCU without problems, but when I want to program it in the same way than before, it shows the error, "Flash loader can not be loaded".What is the difference between the ST-Link Utility and the STM32CubeProgrammer regarding device dete

I am not able to find the built in drivers, which comes by default, when you download the software. This is not allowing me to get the whole main.c file to perform the projects. Can anyone help

I created a motion_fx for stm32h562 from CubeMx. The auto generated motion_fx.h file does call (line 135)size_t MotionFX_GetStateSize(void);​But the code does miss the include #include <stddef.h>Which results in the following error:unknown type name 'size_t' motion_fx.h ./Middlewares/ST/STM32_MotionFX_Library/Inc line 135 C/C++ Problem 

Hi,In STM32CubeIDE/MX versions 1.19 and 6.15, I configured HRTIM, and it worked fine without any errors in CubeMX. I have updated STM32CubeIDE/MX to versions 2.1.1 and 6.16.1, and I have noticed the error messages shown in the pictures below.The dead time is not used, but when set Output 2 state MX displays the message "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources". The project operates like before the update, but it is not possible to add new Set Sources (I can only change the number of Set Sources to zero). How to understand this behaviour?Krzysztof  

When connecting to our stm32n6 using a stm32 Programmer we get an unstable connection. Connecting with a low clock rate (5khz instead of 8000khz) improved the Issue but there still isn't a reliable way to connect to the board. Some retries are needed to get a connection. Also after some time the connection doesnt work entierly and the MCU needs to be powercycled.  

Hi, I'm using the STM32U5G9J-DK1 Demo Board with the STM Demo Program Ux_Device_DFU, because I need to create a specific bootloader for my board.The STM32CubeProgrammer program connects to the board via USB and I can read its memory, but the program doesn't receive information from the Flash Blocks, so programming doesn't start.If I enable the Bootloader available in the MPU's system memory, the programming via the STM32CubeProgrammer works correctly.What should I change in the STM source code to avoid this problem?Thank you in advanced

In a recent release (not sure which one) the option to select USER_PHY was added to the platform settings under LWIP.I need to implement a different PHY for a LAN9374. It is basically identical to the LAN8742. The only issue is that the LAN8742 init code fails unless modified slightly. If I select LAN8742 and modify the file I can get it working but as expected every time I regenerate the project the modifications get overwritten. Where is the documentation on how to implement a USER_PHY?

STM32G491Code generator generate wrong order of calls for SPI initialization for LL driver: LL_DMAMUX_SetSyncRequestNb  calls after LL_DMAMUX_EnableSync

Hello, Long time lurker here. First of all, thank you for the extensions, really appreciated the possibility to work directly in vscode.I have a couple of situation, however, that are really annoying and that I would like to solve. While developing in vscode with the extension enabled. It is sufficient to update the CMake presets in order to have the tools installed by the ST extension to make the git repository dirty.If before committing the files to the repo a pre-commit that formats the files in a proper way then it is amplificated.The files: c_cpp_properties.json in the .vscode folder is always updated with the compileCommands updated if dynamic folders for Debug and Release are used .clangd configuration file is updated in the CompilationDatabase field.In my opinion there are two different types of settings: settings that needs to be persinstent, and mayb

Having issues compiling the source code found in the audio kit for the designer application.C:\x-cube-audio-kit-v1-4-1\package\Projects\STM32H573I-DK\Applications\Livetune\STM32CubeIDE\DesignerAfter importing the project into STM32 Cube IDE when I attempt to build the source without changing anything I get the following error.... make -j22 all arm-none-eabi-gcc -o "firmware.elf" @"objects.list" ../../../../../../../Middlewares/ST/STM32_Audio/Addons/PDM/Lib/libPDMFilter_CM33_GCC_wc32.a ../../../../../../../Middlewares/ST/Audio-Kit/lib/libAudioChainAlgos_CM33_GCC.a ../../../../../../../Middlewares/ST/Audio-Kit/lib/libAudioChain_CM33_GCC.a ../../../../../../../Drivers/CMSIS/DSP/Lib/libCMSISDSP_CM33_GCC.a -mcpu=cortex-m33 -T"../Project.ld" --specs=nosys.specs -Wl,-Map="firmware.map" -Wl,--gc-sections -static -L../../../../../../Drivers/CMSIS/DSP/Lib/GCC -L..

Hi, I consistently hit HardFault when using PICOLIBC. I am using a STM32H735G-DK board.Setup:1. Start from a black CubeMX project, selecting the board and default pins. The FreeRTOS must be enabled, and the TouchGFX (with the MPU configured). We will target CMake and SR Arm Clang. Generate code.2. Open TouchGFX and load the project with the file ApplicationTemplate.touchgfx.part. No need to add anything, just generate code.3. Open the entire project with VSCode. The project by default uses the PICOLIBC in the file starm-clang.cmake. The project as is compiles successfully. flash onto the board and click Continue. The code will instantly go in HardFault_Handler().Here is a printscreen:

Disclaimer:Probably not quite the right place for this bug report. However, since the issue appeared with the update to CubeIDE VSCode v3.8.0 and STM32CubeMX v6.17.0, and the project in the attached ZIP was created with these versions to reproduce the behavior, I am placing it here.IntroductionLink to Project on GitHub: init_array_issue (or use the attached ZIP file)The code in file init_array_issue.cpp demonstrates a misbehavior where, under certain conditions, the initialization of objects is silently skipped without any warning or error message when picolibc is used together with the linker description file STM32H753XX_FLASH.ld