Solved

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.

Hello,Is this M93C46-A125 EEPROM available in WFDFPN8 (MF) package? Because according to the datasheet, the M93Cx6-A125 series exists in 3 packages (SO8, TSSOP8,WFDFPN8). but i founded just SO8, TSSOP8.     

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

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, 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.

Hello ST Community, I am currently in the hardware selection phase of a product development project and am evaluating STMicroelectronics accelerometers for our production design. I am hoping the community and ST engineers can help clarify driver availability and support options for our target platform.Platform OverviewOur production platform is based on the Quectel SC200U module running Android 14. The key processor specifications of this platform are as follows: Application Processor: Octa-core 64-bit ARM Kryo™ 260 CPUDSP: Qualcomm Hexagon DSP, Dual-HVX @ 512 MHzGPU: Adreno™ 610 @ 950 MHzOperating System: Android 14A critical hardware design constraint of this platform is that the dedicated SENSOR_I2C interface exclusively supports sensors operating under the ADSP (Audio Digital Signal Processor) architecture. Specifically, the hardware design document explicitly states:"SENSOR_I2C only supports sensors in the ADSP architecture"Accelerometer Candidates Under EvaluationW

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?.

I’m a bit confused by the conflicting information regarding the STM part VN21-E. There is no MSL specified on the STM label – which makes sense given that it is a Pentwatt package (through-hole mounting = wave soldering = no real risk of MSL damage). However, STMs official partner DigiKey (and others) specify an MSL 3. That can’t actually be right, can it?

Hello, I am trying to build a simple firmware for my SensorTile.Box PRO to stream any data. Using MEMS Studio's AlgoBuilder, I have set the correct Toolchain (STM32CubeIDE), and the target (SensorTile.box Pro). Then I built a simple design with Quaternions 9X attached to the Sensor Hub (Data Rate: Timer/100, Accelerometer Full Scale: 2g, Gyroscope Full Scale: 245dps), outputting to a Fusion component. I can generate C code and build and program my device in DFU mode.However, when I connect it over Serial after rebooting the device, I can connect to it but the "play" button is grayed out and I cannot stream any data.Using STM32CubeProgrammer to flash other compatible firmware that came with MEMS Studio (steval-mkboxpro, steval-mkboxpro-ble), I can connect and stream (play button is enabled) data as per normal so I doubt the problem lies with the hardware.I have also tried other designs with SensorHub -> Any other sensors -> Value instead of Quaternions 9X, but none of it work

gpioinfo outputgpiochip9 - 10 lines:line 0: "PZ0" inputline 1: "PZ1" inputline 2: "PZ2" inputline 3: "PZ3" inputgpiomon output# gpiomon --num-events 1 --edges falling PZ0^C# gpiomon --num-events 1 --edges falling PZ1^C# gpiomon --num-events 1 --edges falling PZ2^C# gpiomon --num-events 1 --edges falling PZ3gpiomon: unable to request lines on chip /dev/gpiochip9: No such device or addresswhy is there a problem with PZ3 pin specifically? noone is using itshould i add something in dts?

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.

For the STM32MP135 series, specifically the STPMIC1A I'm using, can VDD_CORE and VDD_CPU share the same power rail (buck1)?

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 ?!) /** **********************************

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 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 

hello team, I am facing a debug connection issue with STM32H723VGTx using STM32CubeIDE and ST-LINK.Issue details:MCU: STM32H723VGTxDebug tool: ST-LINK (OpenOCD via STM32CubeIDE)Interface: SWDReset mode: Software resetSWD frequency: 50 kHzObserved behavior:ST-LINK connects successfully.Cortex-M7 core is detected correctly.GDB server starts, but the debug session fails during memory access.Error message: Error: Failed to read memory at 0x5c001000 Error: auto_probe failed Error: Connect failedAdditional observations:Target voltage reported by ST-LINK is ~2.8 V.I already tried:Lowering SWD frequencyUsing software resetAdding monitor gdb_memory_map disable in debug startup commandsHalting on resetIssue still persists.Request:Could you please confirm:Whether this memory address (0x5C001000) access failure is related to power / AXI-D2 domain / debug configuration on STM32H723.If there are any recommended debug settings or patches for STM32H7 devices under these conditions.Whether mi

A new STM32 sub-family (as part of the 'H5 family) came out. They have everything but the kitchen sink. As far as I can tell, 'H5E4 and 'H5E5 differ only in that the higher one has USB-HS with PHY (the 'H5Fx are crypto-enabled variants, as usually) What's new is also the PLAY peripheral, which is a small programmable logic element, fully documented and configurable through registers. It's based around 16 simple logic elements (4-input LUT and an optional register), complete with an extensive input multiplexer matrix+filter, interconnected to a variety of peripherals (timers, DMA, ADC...) and also GPIO. I wonder, if there's a Disco around... JW  

Hi,I created a blank project for STM32U5G9J-DK2 and in process of programming the board, GfxDesigner generates 400MB file intflash.elf. With GfxDesigner 4.24.1 it is 4MB.Why 4.26.1 generates  intflash.elf so large ? A bug ?Thanks  

***Update***This issue is solved and was due to improper wifi firmware upgrade. Topic can be closed.   Hi STM Team, I have been having issues for the last week with connecting to the STWIN.box via wifi from both iphones and android phones for DATALOG2 v3.2.0. (And to some extent v3.1.0). The configuration of the wifi network does not work correctly when I attempt to send it from the app. The only way I could get it to work, is when I used the Python SDK with firmware version 3.1.0. I was able then to connect with FileZilla and view/download files.Please advise what the possible workarounds are with this issue as I need to use this sensor by connecting to it via wifi and downloading the data files via FTP server.The following is an AI-generated overview of the issue in more detail: Device: STEVAL-STWINBX1 (STM32U585AI) Firmware tested: FP-SNS-DATALOG2 v3.1.0 and v3.2.0 WiFi module: EMW3080 (firmware successfully upgraded per README instructions) App tested: ST B

I have a simple question. Is it possible to use TouchGFX+ThreadX with enabled Ethernet and NETXDuo SNTP client at a same time in STM32N6570-DK board? In other words: take the TouchGFX ClockExample then in CUBEMX enable the Ethernet port with NETXDuo-SNTP server. Will it cause pin conflict? I mean the Ethernet uses the same pins as LTDC. I enabled the Ethernet in ClockExample project and I got blank screen and the app was frozen. After removing Ethernet from the project, the analog and digital clocks appeared again on the display. Thanks, Louis

Good day,I am writing firmware for a custom board using the STM32G0B1KET6 and am experiencing issues related to writing a serial number to the internal flash.As far as I can tell, this MCU has 512 KB of flash split into 2 banks of 128 pages (each page is 2 KB). I am attempting to write to the last page of the first bank (Page 127 @ 0x803F800).I have modified the linker file to reduce the flash area used by my application code like so:MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 144K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 64K }Here is my flash writing function. uint8_t Flash_Write(uint32_t startAddress, uint64_t data) { __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_OPTVERR); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_BSY1); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_BSY2); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_PGSERR); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_PGAERR); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_CFGBSY); if(__HAL_FLASH_GET_FLAG(FLASH_FLAG_CFGBSY) == 1) { return 0; } HAL_StatusTypeDef status;

Im trying to setup FreeRTOS with the new STM32N6.According to https://github.com/STMicroelectronics/x-cube-freertos, the new Nucleo board for the STM32N6 is mentioned as supported.But in the CubeIDE, when trying to enable the FreeRTOS middleware, it says that the new nucleo board is not supported. And the docs also only mention AzureRTOS as supported.Is FreeRTOS supported through the CubeIDE? Or only AzureRTOS?