STM32 MCUs Boards and hardware tools

Howdy,I’m running into an issue trying to re-flash the original code onto the control board (STEVAL-DPS334M1, which uses the STM32F334R8T6 MCU) for the ST totem-pole PFC board (STEVAL-DPSTPFC1).I’m using an ST-Link V2 with STM32CubeProgrammer to download the provided .bin file of the original control code back onto the board. The download completes successfully, but when I power the PFC board afterward, nothing happens. Normally, the PFC board has a startup sequence before the user can enable it, but now that sequence does not occur.When I check device memory in STM32CubeProgrammer, I see that the first data location is at address 0x08000000 (screenshot attached). This makes me wonder if I also need a bootloader file for it to work. If so, where would I obtain it?For reference, the original firmware I received from ST came as a zip file containing:Drivers folderEWRAM folder (which had the .bin file, no .hex included)Inc folderSrc folder.mxproject file.ioc fileBackstory:I originally tri

I am Using STM32U5G9J Dk2 board. I want to work with the TSC EOAIE interrupt. But some how i am unable to enbale the interrupt for the same. I couldnt find any HAL API related to TSC too. And in the STM32cue IDE when I try to debug the TSC registers. it says Reading disabled by: DCB->DSCSR->CDS == 0

I am a beginner, and this is my first time trying to use UART to send data from MCU to PC.I try to follow the deep blue embedded tutorial (STM32 Serial Print & Monitor (UART Data Debug), however the console does not receive anything when I connect to it.This is my main function codeint main(void) { /* USER CODE BEGIN 1 */ //USART vs UART //synchronous generates data on clock and sends it to //the receiver which works accordingly in synchronized manner //asynchronous generates data clock internally /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE END Init */ /* Configure the system clock */ SystemClock_Config(); /* USER CODE BEGIN SysInit */ /* USER CODE END SysInit */ /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_DMA_Init(); MX_I2C1_Init(); MX_I2S3_

Hello,I'm working on a daughter board to connect with STM32F769I-EVAL, no problem if it is obsolete. I can't find good CAD resources for the item, I need a step 3D file or a pdf with the position and the height of all components, so I can design my board with a proper placement of components, without the risk to touch something.I have only found the positions of the four connectors, but this is not enough, there are lots of thick elements around.How can I get support for cad resources of this board?Thanks,Regards

Hi everyone,I'm trying to measure the current consumption of the MCU/NPU on a NUCLEO-N657X0-Q board. According to the reference manual (https://www.st.com/resource/en/user_manual/um3417-stm32n6-nucleo144-board-mb1940-stmicroelectronics.pdf - see par. 7.4.4), I tried both removing resistor R13 and measuring the current with a multimeter across pins 9-10 on CN12, and removing R40 and measuring across pins 3-4. In the first case, I couldn't measure anything at all, so I assumed the board was in SPMS mode and tried the second option instead. However, when measuring the current across pins 3-4, I got a reading in the order of 40 microamps, which seems implausible. Notably, I'm trying to measuring while AI validation is ongoing in CubeMX.I'm wondering whether I might have made a mistake with the board, or if the issue lies with the measuring instrument. Thanks!

Greetings,I have a project on the Nucleo F767ZI board where I try to send a CAN message to another device (in particular, an Maxon EPOS4 Compact 50/5 drive). I can receive messages from this device with no problem, however, as soon as I press the button to start sending messages from the Nucleo board to that device, the drive enters into fault state, allegedly because of a 'CAN passive mode error', which arises because of a bad network configuration or baud rate setting. The Nucleo can still receive messages with no problem after this happens.I have checked the H/L connections with a scope, and can see that there is data coming from both devices. My setup is as follows:Hardware Setup:Nucleo board connected to CAN_H/_L through a TJA1050 transceiver board (schematic attached)120 Ohm termination resistor in both the TJA board as well in the other device (resistor in the EPOS drive). I get a 60 Ohm reading between H and L when using a multimeter, as expected.Connected device powered b

I was performing a firmware update to my board when the board lost connection to my computer. Ever since then I have been unable to connect to the board. I tried going through STM32CubeProgrammer to perform a connect under reset, which just says "Error: Problem occurred while trying to connect". I have also attempted to hold the reset button while performing a full chip erase but I receive an error: must connect before performing action. I have all my jumpers in the correct place and even tried jumping BOOT0 while performing the connect under reset. I would love some help from someone who has possibly been through this before, thank you. 

Hello,I have a NUCLEO-L476RG and after update the firmware of the ST-Link V2.1 embedded on the board, stops to communicate. I want to know if it's possible to downgrade this firmware. If yes, how can i do the downgrade?Thanks!!!

Hello everyone,  I'm using STLINK-V3MINIE as my programmer. The VCP is functional when I received it. But as soon as I upgrade its firmware to V3J16M8 STM32 Debug+VCP, the VCP is unusable. The VCP device enumerated on Windows 11 PC is openable but doesn't give out any digital waveforms on RXD and TXD pins, also no message is displayed when I give a valid UART TTL signal to RXD pin. Currently its firmware is running on V3J16M9 flashed with ST-LINKUPGRADE software on Windows 11. VCP is still not working. I can't remember its factory firmware version. How to solve this problem? Ideally its VCP should work as many USB-to-TTL.

Hii have issue with my nucleo -n657x0-q board, i couldn't connect to it neither ST-LINK or UART the Boot0,Boot1 jumpers are 1,0 respectively. Any idea? 

Hello all, I have been working on a keyboard PCB with an STM32F103, and I have started trying to program it with the STM32duino bootloader however, I have been unable to connect to the chip. This is my first time using the STM32CubeProgrammer with an ST-Link V2. I have verified the voltage across several points in the PCB. I have previously used similar designs with STM32F07 chips and had no issues.   Most of the time, I get an error of "No STM32 Target found" and sometimes I get the error "ST-LINK error (DEV_TARGET_CMD_ERR)". I have tried my best to look at past posts on the forum, but none of the solutions have fixed my issue.  I am happy to provide extra measurements and provide more information. Tips on how to troubleshoot this are greatly appreciated. Thank you in advance!   Schematic and PCB screenshot.

Hi everyone. I have a problem with my U5A5ZJ-Q core board. The mounted microcontroller is STM32U5A5ZJT6QU. The project is to drive a QUECTEL em05 LTE modem. I need to configure the USB port exposed by PA11 and PA12 in Host mode. I am using the standard Host libraries in Middlewares and also the files in the USB_Host folder. I am trying to configure everything without success. I can't find exact written procedures to do this. Has anyone had problems? Has anyone tried? The problem is with the initialization of the USB Host port. It remains in reset mode and the CSRST bit never returns to 0. Below is a portion of the serial log that I printed on the monitor. " [CLK] Enabling HSI48...<CR><LF>[CLK] HSI48 RDY=1<CR><LF>[CLK] CLK48 <- HSI48 (via __HAL_RCC_CLK48_CONFIG)<CR><LF>[USBH] Init...<CR><LF>[LL] USBH_LL_Init (FS)<CR><LF>[HCD] Enter HAL_HCD_Init<CR><LF>[MSP] AFRH(GPIOA)=0x000AA770 AF_PA11=10 AF_PA12=10<CR>&l

Hi everyone,I’m working with the STM32C011F6U6 in my design and would like to flash it using the system bootloader (USART1 on PA9/PA10 as described in the datasheet).Before finalizing my design, I ordered the MB1684B board with the STM32C011F6U6 to test this.However, I’m struggling to get the MCU into bootloader mode. It seems like the device never enters the system bootloader at all.Here’s what I did:I previously flashed a simple LED blink program, which works fine.I connected a push button to the BOOT0 pin (pressing the button ties BOOT0 to VDD).While holding BOOT0 high, I pressed the NRST button to reset the MCU.After reset, the LED is still blinking, which suggests the code in flash is running, not the system bootloader.On my NUCLEO-L412RB-P, doing the same BOOT0 + reset sequence works correctly and I can flash via UART. I assumed the STM32C0 family would behave the same, since the boot mode section in the datasheet looks similar.Why does the MB1684B (STM32C011F6U6) not enter the s

I've created a project for my Nucleo MB1404 - STM32HM563ZI board which uses USART2 and USART3 to send and receive data to a computer. I've just configured both UARTS in the same way with the same parameters with STM32CubeMX. The USART3 works without problems ( can send and receive data),that is the UART connected to the onboard debugging microporcessor which implements a USB virtual COM and  the debugging functionallities. The problem is with USART2. I connected a "FTDI like" device that connects and converts the USART2 lines to a virual COM through USB in the computer. I can send bytes from the nucleo board to the computer and read them in the terminal software, but when I send data from the terminal software to the board I get HAL_TIMEOUT and can't read it. If I check the state of the USART with  HAL_UART_GetState(&huart2); I get HAL_UART_STATE_READY. I keep calling HAR_UART_Receive(... ) in a while for 20 seconds but it reads nothing, I only getTIMEOUT.uint8_

Hi, I am reaching out to kindly request NUCLEO-C051C8 project files ( It seems that ST uses Altium).Altium files would greatly facilitate my development.Please help me.

We are testing the STM32F407G-DISC1 development board and trying to use an external 32.768 kHz LSE oscillator for RTC clock source. Since the onboard crystal footprint was empty, we manually soldered the following components on the LSE pins (PC14 and PC15):Crystal oscillator: ABS25-32.768KHZ-4-T from Abracon(Product link: https://robu.in/product/abs25-32-768khz-4-t-abracon/#tab-specification)Load capacitors: CC0603CRNPO9BN6R8 (Recommended value per crystal datasheet)Despite carefully soldering the components and verifying the connections, RTC initialization (HAL_RTC_Init) always fails with error code 1 (HAL_ERROR).I have attached my main.c source code here for your reference/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All right

Guys currently I am working on STM 32 H7 board and trying to achieve 3.6MSPS as per mentioned in an datasheet, after many tries currently I can able to take 175k samples/second as 12 bit resolution ADC values using an USB FS but if they claimed to be 3.6MSPS is achievable means then we can achieve it right?? here I have attached my code that can get max of 175 samples only but I have to achieve more, help me to get out this problem

Problem descriptionHi everyone,I’m working with a NUCLEO-F411RE board and I need to use USART2 (PA2=TX, PA3=RX) to communicate with a LoRa module (Reyax RYLR998).The issue is: even though I configure USART2 in CubeMX, all data I send ends up on the COM9 (ST-LINK VCP) of my PC (USB micro connector), not on the physical pins PA2/PA3.What I want:Data should go out via PA2/PA3 → LoRa module.But instead it always goes to the PC via COM9.What I already checkedCubeMX configurationUSART2 enabled in Asynchronous mode.PA2 assigned to USART2_TX, PA3 assigned to USART2_RX.Baudrate = 115200, 8N1, no flow control.SYS/Debug set to Serial Wire (not Trace Asynchronous SW).printf redirectionNo active redirection to ITM/SWV.When using printf, I have _write function pointing to huart2: int _write(int file, char *ptr, int len) { HAL_UART_Transmit(&huart2, (uint8_t*)ptr, len, HAL_MAX_DELAY); return len; } SWV disabledIn CubeMX: Debug = Serial Wire only.Not using ITM or ITM_SendChar.Direct test in c

I am trying to use X-CUBE-ST67W61M1 but I am failing to read any data with COM port set as document um3449 indicates (I am currently using a UART-TTL converter connected on CN7 of X-NUCLEO-ST67W61M1). I am trying to update the X-NUCLEO-ST67W61M1 firmware to see if anything changes, but NCP_update_mission_profile.bat from X-CUBE-ST67W61 does not support update with my Nucleo board. Are there any ways to bypass this problem?Moreover, any ideas about why I am not reading anything sensible from the X-NUCLEO-ST67W61M1 UART port? Thanks in advance for any advice

 Context (brief):Board: BMS that charges/discharges cells at 1–2 AMCU: STM32G474RET6 using HSI, 3× ADC, 1× DAC, USB FS (D+, D−), a few GPIOs.Constraint: Battery sense node carries an unavoidable ~20 MHz component from an external stim source (cannot eliminate at source).Goal: Accurate voltage sensing while keeping digital/USB activity and power-stage di/dt from polluting ADC/DAC/reference.What I need advice on (grounding only):Single solid plane vs split AGND/DGND:For STM32 with VSSA/VDDA and VSS/VDD, is the consensus to use one continuous GND plane (no hard moat) with functional partitioning—or do you still recommend a true AGND/DGND split in this use case (1–2 A BMS + ~20 MHz on the measured node)?If “single plane,” where do you prefer the AGND focus/tie—directly under/next to VSSA/VREF+ (shortest loop) versus a separate star just for the analog front end?If I were to have two separte ground planeWhat component should I connect to AGND, and DGND?: My assumption was that sin

Hi everyone, I'm having an issue with a brand new ST-Link V3 and would appreciate a quick sanity check before I return it.Here's the situation:* The device is not detected by my PC at all (it does not appear in Device Manager).* I have already confirmed my USB-C data cable is working correctly.* The red power LED on the ST-Link is extremely faint and dim.* I also tested it on a second computer, and the result was exactly the same.Since the LED is so dim and it fails on multiple PCs, I'm confident this is a hardware fault (DOA). Has anyone seen this specific issue before? I've attached a photo of the dim LED.  Thanks for any input! 

Hi,Does anyone have any idea about how to easily expand STM32L476RG NUCLEO board GPIO pins to the breadboard?I can use jumper wires but I am looking for another way like "the Raspberry Pi breakout kit" which is more neat and clean.ThanksPeyman

Is there any mapping document like this one on the H7S3L8 as there is for the H743ZI-B01?I only find this document:https://www.st.com/content/ccc/resource/technical/document/user_manual/group0/26/49/90/2e/33/0d/4a/da/DM00244518/files/DM00244518.pdf/jcr:content/translations/en.DM00244518.pdf   Thanks for your help!

I have the STLink V3MINIE. When connected to the PC the red power LED is on. But I can't program any device because there is not target voltage. ST Prog (v2.17) shows Target voltage 0.00 VHow can I fix this? Is there a jumper or solder connection missing on the stlink? Or is the board damaged?Thanks for help! 

Hi Fellow Developers,There is actually some issue while trying to configure the peripherals on the disco board.Be it USART or SPI even after selecting the core for a particular communication protocol on board i am unable to get an response over it. Earlier i was trying to configure SPI and read a external SD CARD over SPI but am unable to get an response over SPI. I even checked pins over oscilloscope and had not clock or data over MISO or MOSI.As mentioned at below pins.Then i tried sending data over USART3 pins and had no response there either.Green is Tx connected to Pin D0 which is Rx on STM boardBlue is Rx connected to Pin D1 which is Tx on STM boardAnd Orange is GND.I know HW connections are right, provided for reference.Also here is a basic code of USART transmit.int main(void) { /* USER CODE BEGIN 1 */ uint8_t txData[] ="Hello M7-DISCO!\r\n"; /* USER CODE END 1 */ /* USER CODE BEGIN Boot_Mode_Sequence_0 */ #if defined(DUAL_CORE_BOOT_SYNC_SEQUENCE) int32_t timeout; #e