STM32 MCUs

Hello, I am using a firmware package with the System Workbench for STM32 IDE and would like to ask how I can configure a peripheral and integrate it into my code. Additionally, does it support code generation similar to STM32CubeMX? Thank you in advance!      

Trying to flash F1 and F0 series boards (not a clone, resoldered the MCU with a genuine from mouser) with L4 ST link V2.1, but having no success. Doing the basic CN2  headers out, CN3 VDD(with or without), SWCLK, GND, SWDIO. Spamming every option in CubeProgrammer to talk to the MCU with changing boot settings, doing resets before, while and after connecting, but nothing. L4 talks normally with the internal MCU. I measured MCU - STLink pin to pin resistances, everything seems ok with 22 ohm termination, the only problem i see is when connecting the 3.3V sense to the AIN_1 (CN3 1st pin), then i read in programmer 5.98V (VDD is not 5V, measured, stable 3.3V). In the schematic there is a voltage divider and when 3.3V ST_LINK is there, AIN is 1.65, which goes directly to MCU and shows in Programmer double of that. But by the same meaning, when connecting VDD i bypass with 3V (- schottky diode) and in the programmer get the double. Since its only sense voltage, it shouldnt be neccesary

The CubeMX suddenly can't generate some .h files such as stm32f103xb.h, core_cm3.h, stm32f1xx_hal_rcc.h ..., I tried to use legacy CubeMX to generate but still the same.How to fix it?Left picture is what it should look like ,and the right one is the wrong one.

Hi,I´m trying to migrate the example Application p2pServer (BLE) from the Nucleo board to a custom board with an STM32U575CI, but it fails initializing:#### Welcome to ST67W6X BLE P2P Server Application #####<\n># build: 17:52:14 Mar 18 2026<\n>--------------- Host info ---------------<\n>Host FW Version: 1.2.0<\n>[ERROR] [4000] [ST67W6XTask] (w61_at_sys.c:340) sem_if_ready not received<\n>[ERROR] [4000] [ST67W6XTask] (w61_at_common.c:375) sem_if_ready not received<\n>[ERROR] [4000] [ST67W6XTask] (w61_at_sys.c:312) Could not init Modem handler<\n>[ERROR] [4000] [ST67W6XTask] (main_app.c:975) [ERROR] in W6X_Init API<\n>[ERROR] [4000] [ST67W6XTask] (w6x_sys.c:115) W61 Init failed<\n>[ERROR] [4000] [ST67W6XTask] (main_app.c:401) Failed to initialize ST67W6X DriverAny idea what could be the problem?BestAchim

I have same error since days on differnt machines in different networks.While this is working:cube bundle list-online PS C:\git\nucleo-h753zi-canfd> cube bundle list-online Name : Platform Version --------------------------------------------------------------------- adoptium-jre : x86_64-windows ["21.0.8+9.st.2", "17.0.16+8.st.1", "17.0.15+6.st.1", "17.0.14+7.st.6", "17.0.14+7.st.5"] cmake : x86_64-windows ["4.2.3+st.1", "4.0.1+st.3"] cube-cmsis-scanner : x86_64-windows ["2.4.2", "2.2.1", "1.1.3", "1.1.0", "1.0.1"] cube-code-doc : all ["0.0.7+st.2", "0.0.6+st.2", "0.0.5+st.1", "0.0.3+st.1", "0.0.2+st.1"] cube-code-manifest : x86_64-windows ["1.1.3+st.1", "1.0.9+st.2", "1.0.6+st.1", "1.0.3+st.1", "1.0.1+st.1", "1.0.0+st.1"] cube-wrapper : x86_64-windows ["0.10.2", "0.8.3", "0.7.3"] gnu-gdb-for-stm32 : x86_64-windows ["14.3.1+st.2", "13.3.1+st.10", "13.3.1+st.9"] gnu-tools-for-stm32 : x86_64-windows ["14.3.1+st.2", "13.3.1+st.9", "13.3.1+st.8"] gnu-tools-for-stm32-13_3_1-d

Hello everyone!I am using stm32n6570-dk. My project has only FSBL and was generated using STM32CubeMX. I was able to run it in debug mode without issues. The code does not execute when flashed to external flash memory. I had to comment out "MX_ICACHE_Init();" for the code to run from external memory. I thought there may be a configuration issue from my side. So I ran the "Starter project" provided by STM located at "STM32CubeN6\Projects\STM32N6570-DK\Templates_Board". This code also runs fine in debug mode. It does not work when flashed to external memory without commenting out "MX_ICACHE_Init();".I expect the example code to work without modifications.  I figured out that the program does not reach the error handler and gets stuck in HAL_ICACHE_ConfigAssociativityMode(). This is when flashed to external memory.if (HAL_ICACHE_ConfigAssociativityMode(ICACHE_1WAY) != HAL_OK){Error_Handler();}Within HAL_ICACHE_ConfigAssociativityMode() it gets stuck in READ_B

Hi Community,Today you will provide the answers, and I will ask the questions!Looking at the statistics gathered by our tools (assuming customer consent given), we can see the huge popularity of designing software relying on an RTOS. FreeRTOS is widely used, and we assume that the adoption Azure ThreadX will also spread quickly.As CubeIDE tools guys, we have invested some effort in RTOS debug features. To quickly summarize the RTOS debug offer, let's make a list:Window > Show > View > Other > FreeRTOS / ThreadXProvides views to visualize kernel objects for the 2 RTOSesDebug config > Debugger > Enable RTOS ProxyWill allow the debugger to unwind and display the full call stack for ALL threads in the RTOS, not only the one currently in context!For Azure ThreadX CubeIDE 1.8.0 can also conveniently export trace logs to be visualized "offline" in Microsoft TraceX toolIn our view the RTOS support is now quite decent! ;)What is puzzling is the lack of feedback and bug reports

I am not able to view stm32N6 PSRAM @ 0x90000000 with IAR Memory view, it only shows --. And after I tried to access 0x90000000, the debugger seemed to hang up.I tried with STM32N6570-DK XPI_PSRAM_MemoryMapped project. I set a breakpoint at line 197 -- if (errorBuffer == 0) after it read/wrote PSRAM successfully. When it stopped at the breakpoint, I opened the memory view to check memory @0x90000000. It failed.If I did the similar with stm32CubeIDE, it worked fine.  Any idea why the IAR was not working?

Hi, I am tring to write data by the FDCAN bootloader of system memory, my target is STM32H563. Now, I can read the device ID, perform the mass erase command, but I can't write data to SRAM/Flash, the FDCAN bootloader doesn't response any CAN message after the Write_Memory command. Below picture is the CAN message log when I try to write 64 bytes data to flash at 0x0802_0000. I also check the 'Write_Unprotect' command, so the MCU is not write protect.Do I miss something have to do?Thank you.

I’m using a NUCLEO-H533RE and CLion as my development environment. Configuring and building my STM32 project works fine, but I haven’t been able to get debugging to work. I receive the following error:Error in initializing ST-LINK device.Reason: Unknown. Please check power and cabling to target.Using STM3CubeProgrammer I can connect with the board and did the full chip erase.The attached images show the current settings.Does anyone have any idea?

On an STM32H563, I am trying to write the OBkey1 data.I have successfully set the product state to provisioning (0x17) with: FLASH_OBProgramInitTypeDef optionBytes; HAL_FLASHEx_OBGetConfig(&optionBytes); HAL_FLASH_Unlock(); HAL_FLASH_OB_Unlock(); optionBytes.OptionType = OPTIONBYTE_PROD_STATE; optionBytes.ProductState = OB_PROD_STATE_PROVISIONING; HAL_FLASHEx_OBProgram(&optionBytes); HAL_FLASH_OB_Launch(); HAL_FLASH_OB_Lock();Now, when I try to write too OBKey1 with: uint32_t dataAddr = 0x20050000; memcpy ((void*)dataAddr, source, 0x60); RSSLIB_DataProvisioningConf_t * pConfig = (RSSLIB_DataProvisioningConf_t *)0x20050100; pConfig->pSource = (uint32_t*)dataAddr; pConfig->pDestination = (uint32_t*)0xffd0100; pConfig->Size = 0x60; pConfig->DoEncryption = 0xCACA0AA0U; pConfig->Crc = 0; HAL_FLASHEx_OBK_Unlock(); provisioningResult = RSSLIB_PFUNC->NSC.DataProvisioning(pConfig); HAL_FLASHEx_OBK_Lock();The call to DataProvisioning() causes

Hello,I am writing to seek advice on connecting an APMemory APS12808 OSPI memory to the STM32H723ZGT6 microcontroller.Initially, I attempted to adapt the code from this thread ( https://community.st.com/t5/stm32-mcus-products/stm32h7-octospi-mode-hyperbus-hyperram-access-and-delay-block/td-p/143237/page/2 )  from @Alex - APMemory  to the STM32H723ZGT6. You can find the result in the attached file `main_1.c`. With this configuration, read and write operations do work, but I am encountering issues with data mismatches/corruption.Subsequently, I tried to enable the Memory Mapped mode based on Application Note AN5050. This is where significant problems began I cannot get this mode to activate. The relevant code is in the attached file `main_2.c`.My specific questions are:1. Is there a known working example for enabling the Memory Mapped mode for this type of memory?2. Why does AN5050 not cover the MR (Mode Register) configuration and memory initialization sequence?

I’m using the X-NUCLEO-LPM01A (PowerShield) and previously had firmware version 1.0.1, where I could connect via a serial terminal over USB and interact with the board using commands. But error occured short after, with LED 2 on the board indicating USB enumeration failure. Updating the STM32-LPM01-XN firmware version to the latest one (1.0.8) solved that issue but now no sign of connection via a COM port terminal. Everything works fine using via a graphical user interface using the STM32CubeMonitor-Power software tool. But would prefer controlling via COM terminal ... Thanks for the support

Hi, I am using an STM32F767ZI to communicate with a Dacai HMI display over UART7 at 9600 baud. Sending data from the STM32 to the HMI works perfectly, but receiving data from the HMI is unreliable. The same HMI works fine when communicating with other MCUs—both TX and RX work reliably.When I touch: screen ID = 0 control ID = 12 HMI tool shows this frame:   EE B1 11 00 00 00 0C 11 31 32 00 FF FC FF FF ( Data : 12 ( 31 32 ) ) Data reception does not match actual touch event HMI → STM32 reception is very unreliable Callback (HAL_UART_RxCpltCallback) is triggered rarely Breakpoint inside callback is almost never hit void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart) { if (huart->Instance == UART7) { HAL_GPIO_TogglePin(GPIOB, LD1_Pin); // debug uint8_t b = rx_byte; if (frameIndex == 0 && b != 0xEE) { HAL_UART_Receive_IT(&huart7, &rx_byte, 1); return; } if (frameIndex == 1 && b != 0xB1) { clearFrameBuffer();

Hi there, i'm moving my first steps into ST boards programming and I have a trouble I can't solve. Following this youtube tutorial: https://www.youtube.com/watch?v=NFljjd_vQGAI tried to create the app in TouchGFX and it worked. I can flash my STM32F746G-DISCO board correctly:   (image 1) The youtube tutorial ends with importing the project into STM32CubeIDE, to do so, you go inside STM32CubeIDE folder inside main folder named MyFirstTouchGFXProject and double-click on .project file:    which I did after editing the files .project and .cproject. Because I have multiple projects based on the same board and ALL OF THEM get imported with the same name, without possibility to change that name, that is in my case: STM3232F746G_DISCO, and rename the project from within the STM32CubeIDE breaks it. Therefore I changed this lines..project: .cproject:    At this point i double-clicked on .project and imported into STM

Hi,during porting the USBX as host stack to an stm32h7 I was getting an error indication,that a semaphore was used during interrupt context (OTG_HS_IRQHandler).For my opinion, it is wrong to call the generated code out of the ISR without decoupling the context. How did you solve the problem? Is there a posibility in cubemx the generate code with decoupling the context?.

My STM32cube IDE project has a pre-build command:${ProjDirPath}\Middlewares\Third_Party\nanopb\generator\protoc --nanopb_out=${ProjDirPath}\Application\cm4_interface --proto_path=${ProjDirPath}\Application\cm4_interface ${ProjDirPath}\Application\cm4_interface\cm4-interface.protoThe json that's generated doesn't correctly escape the '\' characters, which results in an error...   

Hi, I don't know where to post this message. There's an error in the RM0090 Rev21 reference manual, page 121: "bit 15 of the PWR_CR register" should be "bit 14 of the PWR_CR register". And most importantly, the debugger doesn't have bit 14 (VOS) of the PWR_CR register. I'm using an STM32F407ZET. I downloaded the archive https://www.st.com/resource/en/svd/stm32f4-svd.zip, and this bit is indeed missing from the STM32F407.svd file! Please email whoever needs this information, and have them fix it.

Hello,I am converting from Arduino to STM 32 Cube IDE. Here I have a Problem with include paths:What I want:- Develop Libraries in a special folder- Add the libraries as a LINK to the Cube IDE- use #include command to include the library into the project What I have done:- I made a new Project "Blinky" in the cube IDE - done- I selected a nucleo board in the cube IDE - done- I programmed a hello world blinky using HAL without libraries - done.So the environment and the board is running.- right clicking on the project  I created a new source folder "MyLibs"By drag and drop I copied my library called "After" folder into the new MyLibs folder. Answered the message by "copy link only" into the new folder "MyLibs"The copied folder "After" contains an other folder "src" where the source files are located. Here a picture of the project: Now I go to properties and set the include path to the directory /MyLibs/After/src/: The second line indicates that I have included the di

Hi,Having successfully installed SW4STM32 I recently tried to build the example project detailed on the RIP Tutorial web page entitled "First time setup with blink LED example using SW4STM32 and HAL library". This "threw up" four errors. The first was classed as a fatal error whilst the other three errors involved "make" which I believe are due to the first error.Within the IDE, on the "Problems" tab, the first error is listed as follows.Description: fatal error: usbh_conf.h: No such file or directoryResource: usbh_conf.hPath: /STM32F4_Discovery_Blinky/Middlewares/ST/STM32_USB_Host_Library/Core/Inc line 28 C/C++ ProblemWithin the ".../Inc/" directory is a further subdirectory called "usbh_core.h" within which is the "offending" (non-existent?!) usbh_conf.h This header file is clearly listed on both the Project Explorer and Outline tabs within the IDE. Opening this file shows the following. (How could this be done if the file did not exist ?!) /** **********************************

I have five projects on the go, which compile and debug well on STM32CubeIDE 1.X.X (at least for 1.12.0+), but with warnings. I am now trying to shift to more recent versions of CubeIDE (2.X.X), but they behave as if ">Properties>C/C++Build>Settings>Tool Settings>MCU>MPU GCC Compiler>Warnings>Treat warnings as errors (-Werror)" is enabled, even when it is not.I believe that my settings in the more recent CubeIDE are identical to the older one, and I have tested this on two different computers with similar results. The error which is currently causing the compilation to halt is " ...error: implicit declaration of function 'xxxxx' [Wimplicit-function-declaration]", but if I resolve it, another item which should be a (legitimate) 'warning' will appear as an 'error'. I am using "ISO C11 (-std=c11)", and have the same issue if I attempt to use GNU11.Unfortunately, I cannot resolve all the warnings without creating other problems, so this issue is preventing me f

The integrated ST-Link debugger/programmer on STMicroelectronics NUCLEO boards is widely appreciated for its ability to output messages to a serial port, enabling easy debugging and communication with host PCs. However, setting up the board to not only send but also receive commands from PC-based applications such as Tera Term requires additional programming effort. This guide will walk you through the steps to implement bidirectional serial communications, allowing your NUCLEO board to interact dynamically with your computer.

Hi, im doing a line follower and using the mcu stm32 f411, its a small development board arduino nano style, and i conected it to the motor driver tb6612fng, and it seems to have backfeed motor suply voltage on the logic pins and it burned my mcu.My question is how to prevent this?

Hi all,I recently designed and built a custom PCB for data acquisition and transmission through bluetooth using an STM32U575 as the main MCU and a BlueNRG-M2SA module for bluetooth data transmission configured as a Network Coprocessor. They are connected via SPI following the pinout on the BlueNRG-M2 datasheet and also looking at the X-NUCLEO-BNRG2A1 schematics. The BlueNRG-M2SA is connected to an external connector via SWD for flashing using an STLink-V3Minie. Resistor R13 is not usually soldered and is just used to enable the bootloader during image flashing. Schematic for the BlueNRG-M2 on the custom PCB provided below:The problem is that I have not been able to achieve communication between the STM32U575 and the BlueNRG-2 module as whenever the main MCU waits for the IRQ signal from the BlueNRG-M2, it doesn't receive any and therefore returns BLE_STATUS_TIMEOUT and gets stuck after aci_hal_set_tx_power_level() during Device_init(). I have tried uploading different DTM ima

Hello, I hope to reach the appropriate contact regarding Country of Origin (CoO) information at ST.We have identified a conflict between the CoO listed on the website and other documents (such as PCN and the attached FMD chemical document). These documents indicate that the CoO for part STM32H523RCT7 is China, while the website lists the CoO as France.Could you please clarify this discrepancy and specify what the France CoO refers to? Based on our documents, the CoO China corresponds to the country of assembly.Your clarification on this matter would be greatly appreciated. Website CoO FRANCE : https://www.st.com/en/microcontrollers-microprocessors/stm32h523rc.html#sample-buy