STM32 MCUs Software development tools

Hi, I am creating application using LPBAM configuration. The application simply is:Enter stop mode 2- Use ADC4-12bit channel 22 (PC4) to measure voltage using clock HSI or MISK- ADC wdog to generate interupt when the value reach threshold to exit stop mode 2- LPTIM1 will trigger ADC4 500ms cycle using clock LSE- LPDMA1 channel1 to store converted data, and save to array adc4_buffer[1]- LPDMA1 channel 0 ensure queue run LPBAMWhat I have done:ADC4 configuration (ADC4 global interrupt enable in NVIC)LPTIM1 configurationLPDMA configuration (LPDMA channel 0 interrupt enable)Scenario queueThen I generate code and face this warningI already createt project without Trust Zone, also check LPBAM check log but cannot verify it. So I need help. Thank you

Hello,I am experiencing a persistent verification error when flashing an STM32H7 via USB DFU using the STM32_Programmer_CLI. The exact same command and hardware work perfectly on Windows, but fail consistently on macOS.Environment:Tool: STM32CubeProgrammer CLI v2.9.0 (also tested on newer versions)OS: macOS vs Windows 11Hardware: STM32H7 custom boardConnection: USB DFU ModeFile: .hex file (approx. 44MB) containing internal flash and external memory data.The Problem: On macOS, the download reaches 100%, but the Verification fails at 98%. The error always points to the start address 0x0800E000 reporting a byte mismatch (0x00 instead of 0x70).Log Comparison Observations:Windows (Working): The log explicitly shows individual sector erases: erasing sector 0003 @: 0x0800c000 done.macOS (Failing): The log shows Erasing memory corresponding to segment 0... but never confirms the individual sectors as "done." It seems the erase operation is being skipped or failing silently on the Mac DFU stack

When I attempt to power cycle a STM32N6570-DK or NUCLEO-N657X0-Q board via the STM32_Programmer_CLI, I get the following error message:Error: Failed to Power ON the board ! Here is the full log:❯ STM32_Programmer_CLI --power off index=0 --power on index=0-------------------------------------------------------------------STM32CubeProgrammer v2.21.0 -------------------------------------------------------------------Power OFF...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Power OFF the board finished with success !Power ON...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Error: Failed to Power ON the board !  However, when I attempt the same command on other Nucleo boards, I don't get this error. Here's the same command run on the NUCLEO-H533RE:❯ STM32_Progr

Hello, recently I was able to flash a programm on the STM32G474CET3 but I am unable to track Live Variables.I wrote a simple program that just increases a cnt variable each second.My .ioc configuration: Every help is appreciated. 

Why can’t my cubemx configure L1 cache? How to enable it?Also, the MPU cannot be configured. You can only use the default configuration and modify it in the generate code.I also configured Memory management, but did not see the enable Cache and MPU synchronization settingsCubeMx 6.16.1 on macos MAC 26.1MCU:STM32H743IIT6  

I need to learn more (detail) about STMCubeMX  "extended mode" and small-pincount multi-bonded MCUs (this posting label specifies STM32C0 series which is what I'm currently working with.)STM32CubeMX UM1718 section 4.5.8 describes extended mode (I encountered when exploring this option while using STM32CubeMX with a new project), but other than cautions (that an option byte is required and that improper use can affect power consumption etc) I could find no further ("how it works") detail there.HAL_SYSCONFIG_SetBinBinding doesn't provide a suitable solution (concurrent access to a single physical pin by more than one possible peripheral.)Any recommendations on where (=application note?) I can proceed to learn about multi-bonding implementation and limitations for these small-packaged MCU products?Thanks! 

I have recently started a project in VSC using an STM32 device.  I first used STM32CubeMX to generate code, so that created most of the project.  I am using CMAKE.Initially there was no issue, and everything worked fine after disabling intellisense.  However, I have now become plagued by the stubborn red squiggles which refuse to disappear whatever I do.  I would prefer to continue using VSC, but will have to ditch it and move to another IDE if this problem does not go away, as I cannot work like this.  Further down the file there are many other red squiggles.  The project compiles fine, no issues there.  An example of the problem:No matter what I do, the first #include has red squiggles under it.  If I change the order of the #includes, then it is always the first one which has the squiggles.  settings.json file:c_cpp_properties.json file:Any help would be gratefully appreciated, please.

I am using STM32CubeIDE V1.11.0I have exactly the same issue which was described in this post:https://community.st.com/t5/stm32-mcus-boards-and-hardware/st-link-gdb-server-issues/m-p/64010#M623Multiple weeks everything works fine. But suddenly it stops working and i always get this error message when I try to Debug my code in CubeIDE:Failed to bind to port 61235, error code -1: No errorFailure starting SWV server on TCP port: 61235Failed to bind to port 61234, error code -1: No errorFailure starting GDB server: TCP port 61234 not available.Shutting down...Exit. I tried multiple things:Shuting down PC completely (and disconnect from power supply) and booting again multiple times - it didn't change anythingI changed the Port in the Settings to 61238 - same error message, but with the 61238 port numberI changed the ST-Link Device - same error messageI connected the ST-Link to an other board with an other controller (and selected the appropriate project in cube) but get the same error

Hello allI am trying to integrate CMSIS-DSP in my CMake project. From CubeMX, I have the following options:and I see the following folder struct:and to include DSP folder in my project, I have done the following changes in my top level CMakeLists.txt.... some code # Enable CMake support for ASM and C languages enable_language(C ASM) # Create an executable object type add_executable(${CMAKE_PROJECT_NAME}) # Add STM32CubeMX generated sources add_subdirectory(cmake/stm32cubemx) add_subdirectory(Drivers/CMSIS/DSP/Source) # Link directories setup target_link_directories(${CMAKE_PROJECT_NAME} PRIVATE # Add user defined library search paths ) # Add sources to executable target_sources(${CMAKE_PROJECT_NAME} PRIVATE # Add user sources here ${CMAKE_SOURCE_DIR}/Core/Src/tm1638.c ) # Add include paths target_include_directories(${CMAKE_PROJECT_NAME} PRIVATE # Add user defined include paths # Include CMSIS core headers ${CMAKE_SOURCE_DIR}/Drivers/CMSIS/Include ${CMAKE_SOURCE_DIR}/Driv

My projects are all in C++ and were building completely fine. After I generated the code from CubeMX, the language switched back to C. I had to go and manually switch to C++, then it gave me build errors with linker script... Please fix!

Hello,I'm facing an issue in CubeMX with the AES IV in CTR ModeThe IV is not saved in the IOC file and is discarded from the generated code, replaced with a full 0 value.The AES content inside the IOC file:AES.Algorithm=CRYP_AES_CTRAES.DataType=CRYP_DATATYPE_8BAES.DataWidthUnit=CRYP_DATAWIDTHUNIT_BYTEAES.IPParameters=KeySize,DataType,DataWidthUnit,pKey,AlgorithmAES.KeySize=CRYP_KEYSIZE_256BAES.pKey=-------- -------- -------- -------- -------- -------- -------- --------MCU: STM32F423VHTCubeMX: Latest version 6.16.1AES SettingsAlgorithmData encryption type AES CTRParametersData type 8b(byte swapping)KeySize 256bEncryption/Decryption key -------- -------- -------- -------- -------- -------- -------- --------Initialization vector E467824C 805348FF 4CE1DF70 566ED4A9Data width unit ByteKey and IV configuration skip Always 

 It happens to from time to time that I have a flashed project in a hardware, e.g. a bluepill, but I forgot which source project was belonging to it in the STM32CubeIDE's project treeview.Is there a way to write the name of the project by means of some C-macro in text form into the program as kind of a signature or even more safely, compute a checksum of the flash binary and write that checksum into the program (yes I know, this may become tricky since the checksum alters the checksum itself :)Is there a common technique for this?

Created a new project with v6.8 and reproduced the issueSteps: 1.cubeMX create new STM32F334 project and generate code.(Project-application structure-advancedProject-IDE-MDK-v5.32Code Generator- copy only the necessary library filesCode Generator- Delete previously gernerated files) 2.Create a Middlewares folder (/project folder/Middlewares), copy some folders in this folder (/project folder/Middlewares/mymiddleware).3.Generate code again, Middlewares folder is deleted.os:Win10jre:IBM Semeru jre 11.0.18.10​

The STM32N6 supports YCbCr as an input format (see reference manual RM0486 section 21.3.5). As of version 6.16.1, this option is still not available in STM32CubeMX. The generated code can be manually modified to make it work by settinghdma2d.LayerCfg[x].InputColorMode = DMA2D_INPUT_YCBCR;   

I am using STM32F103C8T6 MCU and STM32CubeIDE ver 19.0.0. When i enabled PA8- PWM generation Channel 1 i get warning RCC Mode and Configuration Tab: Master Clock Output as a error/warning. I have reset state the PA8 pin again enabled as TIM1_CH1 and Tim1 setting Channel 1 : PWM generation CH1 again same error/warning i have get. when generated code closly monitored i didnot find and MCO related code in main.c. What to do? should i ignore cubeMX warning/error and relay on generated code? 

Hi, I have brought 2 STlinkV3MODS. I have soldered wire at CN5 connector with 5+3 pin general connector to target the bluepill(not sure original or clone) the target MCU is STM32F103C8T6. when i select STlink at cube programmer shows error: debug authentication or STM32 target not found. Where as clone stlink V2 (usb dongle) type detected target MCU (cap1.jpg) Now question: 1) if cloned or fake chines STM32F103C8T6 is the cause?                                                             2) i am waiting from supplier the original STM32F103C8T6 chip, and they                                                                           suggest not

Hi everyone,I am migrating from STM32CubeIDE to VS Code using the official STM32Cube for VS Code extension (v3.4.11 pre-release). While I can build and debug my project, I am struggling to get the Live Watch feature to work.My Environment:IDE: VS Code with the latest STM32 official extension.Hardware: Nucleo board with onboard ST-LINK V3.MCU: STM32H7 series.Project Structure: Generated via STM32CubeMX as a CMake project.Project Name: projectBlink.The Issue: In the "STM32CUBE LIVE WATCH" tab, I constantly see the message: "There is no data provider registered that can provide view data.".What I've tried:Code: I declared my variable as volatile uint8_t count = 0; to prevent compiler optimization.Debug Session: I am in an active debug session using the STM32 Cube GDB Server.Adding Variables: When I click the "+" icon and enter the variable name, nothing happens, and the "no data provider" error persists.Version Check: I noticed some community posts suggesting that the v3.x pre-release mig

I'm using STM32CubeIDE Version 2.0.0 and would like to get the size of all the object files in my build. I know I can do this in Project Settings->C/C++ Build->Settings->Build Steps->Post-build steps->commands using arm-non-eabi-size, but what is the variable that expands to the names of the object files, and how do I use it?

I am working with an STM32N series MCU (STM32N657 / NUCLEO-N657X0-Q) and project generated with STM32CubeMX (Toolchain = Makefile).The workspace root contains:• GPIO_IOToggle.ioc• MakefileHowever, in VS Code (latest version) with STM32 VS Code Extension installed, the option “Setup STM32Cube project(s)” remains disabled (Greyed out).The project builds and debugs correctly when .vscode/launch.json is created manually, so the project itself is valid.Expected behavior:The extension should allow setup of existing CubeMX-generated Makefile projects, not only projects created via the extension or CLT.Environment:• macOS• STM32CubeMX (GUI)• STM32CubeCLT installed• VS Code latestThis appears to be a UX limitation or detection bug.

Strange things are happening: I'm running STM32CubeIDE under macOS 15.7.2 (I must admit it is OCLP Sequoia). A couple of minutes ago I was able to open .ioc files in my project - not sure whether that was before the upgrade. Nowthe .ioc are upper strip blue, lower half green. What does that mean? When I invoke the .ioc by double click, it switches over to my Windows VM (Parallels) and fires up CubeMX there (a very old version). When the VM is not running, STM32CubeIDE does nothing. The .ioc is not opened like I was used to before. I'm now updating. I'm puzzled.

When I run build in a VSCode Dev Container with STM32CubeIDE installed, the build fails and i receive an error stating arm-none-eabi-gcc and arm-none-eabi-g++ was not found in the PATH. The compilers are installed, I see them inside the bundles folder (under /root/.local/share/stm32cube/bundles/), the extension is just not picking them up.This was previously working in a separate container but I can't seem to replicate it. 

I am starting use of UM3029 Rev 3 (STM32C0 HAL drivers) and trying ensure I use HAL_SYSCONFIG_SetPinBinding properly (important because the 6 usable IO pins are multiply bonded to device peripheral pads.)I am working with STM32C011J6 (SO8 package) and am using STM32CubeMX and HAL to create example device support code (i.e., drivers.)UM3029 Rev 3 section 6 (HAL System Driver) takes me to section 6.2.1 (HAL Bind Pin Config) which has a listing for some device package/pin assignments for GPIO (my current task is to get a pin working as GPIO input), however, the list does not include any defines for SO8 package. The instruction I'm currently trying to verify (generated by STM32CubeMX for my project) is HAL_SYSCFG_SetPinBinding(HAL_BIND_SO8_PIN5_PA8), but there are others and I'd like to fully understand the utility of this function and it's arguments.I looked in UM3029 Rev 3 for a listing of allowed arguments to SetPinBinding for C0 series SO8 package in UM3029 and came up empty hande

None of the beginner's tutorials work anymore because of the removal of STM32cubeMX from the IDE. Please send me a link to one that will work. I have seen some work arounds to solve this but for a beginner they are too complicated.

Today I started STM32CubeIDE again, was notified that an update is due, installed the update (2.0.0). Got an error alert "Computing 'size'", and the Info startup said "URL not found". Anyway, ignored this, started to build my project again. I added ADC1 (before I did the update), but didn't compile that with the old version of Cube. Now the first compile under the new version fails, saying :../Drivers/STM32H5xx_HAL_Driver/Inc/stm32h5xx_hal_adc.h:1981:67: note: expected 'const ADC_HandleTypeDef *' but argument is of type 'ADC_HandleTypeDef' 1981 | uint32_t HAL_ADC_GetValue(const ADC_HandleTypeDef *hadc); | ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~

I'm working on a project with the STM32H503CBU7 which requires USB. I have a 32MHz external crystal on my board that appears to be stable. The chip works and can be programmed and such. I also troubleshot out other physical issues like cold joints and shorts because that has burned me before when the USB device fails to enumerate.My intent was to use the PLL2Q source with the USB peripheral so I could also specify a 200MHz sys clock for everything else via PLL1. When I use the PLL2Q source however,  I get no interrupts from the `USB_DRD_FS_IRQHandler` handler and so my USB stack does not operate.To make things more confusing, it also does not work even when both PLL's have the same values set for all parameters, as shown in the image below.It is important to note that this works with the PLL1Q source, as it is shown in the image, and I'm currently compromising a little on the sys clock speed. It will work for my purposes, but I'm more interested to know whether there's some "magic