STM32 MCUs Software development tools

Hi,I'm having trouble getting my ST-Link V2 dongle to be recognized by Cube Programmer. It is recognized by Windows 10 in the device manager, I have been able to update the firmware, and I can get it to load in STM32 ST-Link Utility, but that program doesn't support the .elf file format I need.When I launch Cube Programmer, it does recognize something as shown by the voltage and the firmware (image attached), but when I click the refresh button next to the serial number it says "No ST-Link detected."I've read from others that there are a lot knockoffs of these dongles floating around that don't work anymore. That might be the problem with mine (this is the second one I've bought and tried). Can anyone point me to a good source to buy a legit one? In the products page, I've only seen the bigger ST-Link V2 unit and the smaller USB-C V3 unit, but not the V2 Dongle.I'm trying to flash a board for an Atari 2600 homebrew game I made and I attached a diagram of what the instructions show

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 Community,I'm working on a storage module using SDcard for my project. In my application I would like to read and write to the SDcard using the MDMA as indicated in the reference manual of my micro-controller. For now I have the SDcard working in 4-bit mode but using the CPU.I use the STM32H757II on a PCB connected to a SDcard reader on the same PCB.With CubeMX I generated the code that allow me to mount a FATFS on my microcontroller and I can create/open/write/read on file with no problem.But my application needs to log a lot of data to the sdcard periodically, to free-up the CPU I would like to do the transfer using a DMA.In the reference manual 58.5.7 MDMA request generation it is explained that the MDMA can control the SDMMC peripheral to start new transfer"The internal trigger lines from the SDMMC allow passing direct request to MDMA controllerto enable successive transfers from/to different internal RAM addresses without CPU use. [...]The event can trigger the clearance of

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?

Hi everyone, I am developing an application for the NUCLEO-H7S3L8 kit using VS Code with the STM32 VS Code Extension. I have successfully built both the 'Boot' and 'App' projects.Currently, I am struggling with flashing the 'App' project firmware into the external Flash memory. In STM32CubeIDE, selecting an External Loader (.stldr) is very intuitive within the Debug Configuration, but I haven't found the equivalent setting in VS Code for the STM32H7RS series.Could you please guide me on how to configure VS Code to recognize the External Loader and the proper workflow for flashing code to external memory for this specific MCU?PS: On STM32cubeIDE, I'm referring to this example: https://github.com/ST-TOMAS-Examples-ExtMem/stm32h7rs_ospi/tree/main. Now, using the same example, how would I implement it if I used VS Code as my development environment? 

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.

Diving into the wild world of airdrops? This breakdown covers the hottest ones on the horizon, like Nebulai and Helios, with step-by-step tips on joining Discords, completing tasks, and snagging those $NEB or whatever tokens without getting scammed. Plus, a peek at play-to-earn games like Crypto Golf Impact on Intella X. It's all about earning smarter, not harder—kinda wish I had this when I first got into crypto, would've saved me from a few dumb moves.For more deets and fresh updates, head over to Cryptowhatsup. They've got a ton of guides that actually make sense.

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

I'm using STM32CubeIDE 2.0 and CubeMX 6.16.1. When I create a project in CubeMX, it doesn't create the STM32WBA55CGUX_FLASH.ld file. It creates the makefile when I select it in the Toolchain/IDE section, but then gives an error.