STM32 MCUs Boards and hardware tools

Hello, NUCLEO-F411RE JP5 in E5V reset When my F411RE board is powered with 5V, I have to press the reset button to start it. Why doesn't it start? Thank you for your help.

I am currently working on a new hardware design using the STM32U575VIT6 (LQFP64, 10 × 10 mm) microcontroller.I would like to request:Reference schematics and layout guidelines for STM32U575 in LQFP64 packageRecommended power supply and decoupling capacitor designCrystal oscillator and reset circuit design guidelinesAny available design checklists or application notesMy design overview:,low-power IoT sensor node Peripheral interfaces planned: SPI, I²C, ADC, etc.Kindly share any relevant schematics, PCB layout examples, and design documentation to ensure proper implementation.Thank you very much for your assistance.ThanksHarshith

Hi ST, I'm looking for STM32 boards that are permitted for end-product usage. In particular, I find Nucleo wonderful but my understanding is they are not to be distributed in the product. Does ST offer any comparable SBCs to Nucleo that can be essentially be mounted on a host board without having to do a custom PCB just for the MCU? If not, to what extent can Nucleo/Discovery boards be used, f.e. development/evaluation only, test/cert, etc? Historically I have seen assortments of off-the-shelf SBCs being used even in industrial/medical equipment which struck me as very practical and I haven't come across anything from ST for this, so maybe I am looking in the wrong place. Open to suggestions and guidance. Thank you!

I have an STM32L4R on a custom PCB. I am able to flash firmware using CubeProgrammer/CubeIDE to it via an ST-LINK SWD connection as well as a DFU Bootloader via a USB D connector. I have a makeshift connection between the USB D connector to a USB C cable to my laptop in order to flash it using USB_DM, USB_DP, and VBUS wires between the D and C connectors. When the PCB is powered, the ST-LINK is connected to my target MCU and my laptop, and my PCB is connected to my device, my laptop is able to recognize the ST-LINK as a VCP and my target MCU as an "STM32 BOOTLOADER", which allows it to be flashed. The ST-LINK connection is critical in the target MCU being recognized by my laptop. I have written CDC initialization code in order to enumerate my target MCU as a VCP and transmit data to my laptop, however, I am having trouble with that...My code works on the NUCLEO that I have for the STM32L4R. I am also able to step through initialization all the way to the CDC_Transmit() function inside

I have configured WWDG Timer in CM7 of Stm32H747I-Disco and configured WW1RSC=0 in RCC global control register (RCC_GCR) for CM7 Reset only instead of system reset.Issue:HAL_WWDG_EarlyWakeupCallback is getting called before watchdog Reset. but afrer CM7 Reset, some times it is going to hardfault and not booting again and some times booting properly.but in both cases, clock configuration of CM4  is disturbed. main code as follows/* Reset of all peripherals, Initializes the Flash interface and the Systick. */HAL_Init();/* USER CODE BEGIN Init *//* Configure the system clock */SystemClock_Config();/* Configure the peripherals common clocks */PeriphCommonClock_Config();MX_GPIO_Init();MX_TIM7_Init();// MX_WWDG1_Init();MX_USART1_UART_Init();/* USER CODE BEGIN 2 */if(is_wwdg_reset){printf("After Watchdog Reset\n");}else{printf("After Reset\n");}HAL_GPIO_WritePin(GPIOI,LED1_Pin,GPIO_PIN_SET);HAL_Delay(1000);HAL_GPIO_WritePin(GPIOI,LED1_Pin,GPIO_PIN_RESET);HAL_Delay(1000);MX

Post edited by ST moderator to be inline with the community rules for the code sharing. In next time please use </> button to paste your code. Please read this post: How to insert source code. Hello, I’m using the STM32F429I-Discovery board and trying to display “Hello World” on Tera Term via USART1 (PA9, PA10). I configured the project in STM32CubeIDE as follows: USART1 → Mode: Asynchronous TX: PA9, RX: PA10 Baudrate: 115200, 8N1, No Flow Control Using the ST-LINK Virtual COM Port (USB connector CN1)   main.c HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_USART1_UART_Init(); const char msg[] = "Hello World\r\n"; HAL_UART_Transmit(&huart1, (uint8_t*)msg, sizeof(msg)-1, HAL_MAX_DELAY); while (1) { HAL_UART_Transmit(&huart1, (uint8_t*)"Hello Again\r\n", 13, HAL_MAX_DELAY); HAL_Delay(1000); } However, nothing appears on Tera Term.The “ST-LINK Virtual COM Port (COMxx)” is visible in the Windows Device Manager, and I’ve selected the correct COM port in Te

Hi, Please suggest STM32L562 UFBGA-132 Fanout guidelines.I looked into STM32L562E-DK design files for fanout, in which signals are routed in top and S1 layer but there is not via details for layer transition from top to S1. Here attached the fanout for U7 of eval board.Drill for U7  Top Layer layout for U7  Sig 1 layer layout for U7.Regards,Aman

Hi everyone, I’m trying to use the STLINK-V3MODS Bridge GPIOs (GPIO0–GPIO3) as digital outputs, but none of them show any voltage change at the pins — not even in Open-Drain mode with an external pull-up. All API calls (InitGPIO / SetResetGPIO / ReadGPIO) report BRG_NO_ERR,but on the hardware side, the GPIO pins stay flat at 0 V regardless of the configuration or the logical state set.   🧩 Setup Probe: STLINK-V3MODS  OS: Windows 10/11, Visual Studio x64 DLL: STLinkUSBDriver.dll in the same folder Using official STLINK-V3 Bridge API from ST::backhand_index_pointing_right: STLINK-V3 Bridge Software Package (stlink-v3-bridge-v1-2-0.zip)(contains bridge.h, bridge.cpp, and example project apiBridgeProject)   :gear: What I did Used InitGPIO() + SetResetGPIO() Tried both Push-Pull and Open-Drain modes T_VCC is connected (3.3 V detected) Closed all COMs between runs (CloseBridge(COM_UNDEF_ALL)) Result: Software side → success (BRG_NO_ERR, errMask = 0x00)

I purchased a Nucleo-L476RG eval board and downloaded the PWR STOP2 RTC example code to test for a low power application.After following the instructions for the jumper settings outlined in UM1724 for external power, I built and tried the example. The user LED blinked for five seconds then stopped as the board went into power-down/STOP2 mode for several seconds.This all appeared correct but instead of the expected STOP2 current of about 1.5uA, the current was about 450uA.I searched the STMicroelectronics Community and tried several different fixes for similar problems on other boards. But nothing worked.The provided PWR_STOP_RTC code is good and correct. So, I examined the schematic more closely and found extra required jumper settings and power connections not mentioned in the UM1724 user manual.UM1724 (7.3.3) states to apply +3.3V to CN6-4, CN7-12, 16. And SB2 and SB12 are removed.The problem is applying external +3.3V to the +3V3 net at CN6-4 which draws excess current into R23

I cannot get the VCP function of ST-LINK v3 mini working.Windows sees the com port and can open itConnected TX output of UART to pin 14 of ST-LINK 3 mini, but nothing is received on the PC side.Connected some other serial TTL-USB adapter (set to 3.3V), and it works properly.​However, the serial TTL-USB adapter has a ground connection and ST-LINK's VCP has common ground with other functions.The debugger function works properly.Is the TX level of VCP 3.3 or 5 V? Does the VCP function work for anyone?Thanks,-- pa

Post edited by ST moderator: This post has been translated from Chinese to comply with the ST Community guidelines. Please use English language as it's an international community and to let others to understand your post. Thank you for your understanding.

Hi, i am planning to use Steval Stwinbx1 to setup an IOT network for condition monitoring of wind turbine blades. i would like to know whether this board is compatible with Microsoft azure as the B-U585I-IOT02A Discovery Kit has the same micro controller in it. i would also like to know whether it is possible to monitor the data from sensors online since the board has a WIFI with azure or AWS or any other cloud serviceskind regards Jose John

I have purchased the STM32F469-DISCO development board. If I want to replace the chip or design my own development board, how can I use ST-Link or a serial port to flash the code?

I flashed firmware that sets. Now STM32Cubeprogrammer refuses to connect to the STLINK portion.How to recover from this / debrick the boards ? I tried pulling up PA14 / boot0 pin with a pull-up to CN7 pin 7, but no such luck...

Hello ST Community,I have two NUCLEO-H753ZI boards and I want to use Board 1's on-board ST-Linkto program Board 2's MCU through the CN5 (MIPI-10) connector.My Setup:- Board 1 (Programmer): Connected to PC via USB, will provide ST-Link- Board 2 (Target): Connected via 10-pin ribbon cable to Board 1's CN5- Both boards are NUCLEO-H753ZI (MB1549 or MB1940)My Questions:1. Which jumpers need to be removed on Board 2 to disconnect its on-boardST-Link from the target MCU?- I see several connectors with jumpers in the ST-Link section (CN2, JP4, JP5, etc.)- Which specific jumpers control the SWD connection (SWDIO/SWCLK)?2. Should jumpers remain installed on Board 1 (the programmer board)?3. What is the correct CN5 pinout for the MIPI-10 connector on NUCLEO-H753ZI?- I want to verify my ribbon cable connections are correct4. For power, should I:- Power Board 2 through CN5 Pin 3 (VCC) from Board 1?- Or use separate USB power for Board 2?5. In STM32CubeIDE, I'm getting "Multiple ST-LINKs detected" e

Dear ST Support Team,I would like to ask about the compatibility of using the X-NUCLEO-67W1M1 expansion board based on ST67W611M1 with the NUCLEO-F446RE development board.I had read the **X-CUBE-ST67W61 Data brief document on page 3**  "The X-CUBE-ST67W61 Expansion Package runs on STM32 32-bit microcontrollers based on• The Arm® Cortex®‑M33 and Cortex®‑M55 processors with Arm® TrustZone®• The Arm® Cortex®‑M7 processor"So, my questions are:1. Is the X-NUCLEO-67W61M1 hardware compatible with NUCLEO-F44 (Cortex M4 processor)? 2. Can I use raw SPI + AT commands without X-CUBE-ST67W61?, Has anyone done this on F44(Cortex M4 processor)? 3. Any known working example or GitHub project for (Cortex M4 processor)+ X-NUCLEO-67W61M1?

Configured WWDG timer in CM7 core of stm32h747I-disco and i have taken a window period of 10msec to 50 msec and configured according to that in cubeMX. also enabled Early Wake up interrupt and Window watchdog interrupt.i am trying to check interrupt call back WWDG_IRQHandler() before reset as per reference manual rm0399.issue: Core Reset is happening properly but WWDG_IRQHandler() is not getting called before reset

Hello everyone,I am working with the STM32N6570-DK discovery kit and I have encountered a strange behavior that I cannot explain.When I use the ST-provided example projects that include both an FSBL (First Stage Boot Loader) and an Application image — for example:Template_LRUNTemplate_FSBL_XIPJPEG_EncodingFromOSPI_DMAthey fail to run correctly on my STM32N6570-DK boards.However, the exact same projects (same binaries, same flashing procedure) work perfectly on another identical STM32N6570-DK board (I was able to test the same projects on another STM32N6570-DK discovery kit provided by a friend).Interestingly, simpler examples that only contain an FSBL project (for example GPIO_IOToggle) work fine on my board.Before testing the ST-provided examples, I had tried to debug my own application on the same board.During debugging, my code ended up in a HardFault error, and since then, it seems that any project which includes both an FSBL and an Application can no longer run properly on this bo

Hi all, I am transmitting and receiving the image data using AT commands via UART in stmf767vi board. My transmission is sending successfully like sending chunk by chunk. I am able to see the count also. But the problem is while receiving side, I am able to receive the chunk for 2 min only. not all the image. If tx image size is 80k, I am able to see upto 35k only. after that my mqtt is stopping receiving the image data. I don't know where it is causing whether it is keep-alive timeout or something else. Even when I am receiving the small size data, it is receiving 6 times the full image like upto 2 min. after that it is stopping. what is the issue ? someone please help... while(1){ receive_data_test((char *)&response[0], RX_BUFFER_SIZE, 60000);}  eState_t receive_data_test(unsigned char *out_buf, uint16_t buf_size, uint32_t timeout_ms){uint32_t last_ping_time = HAL_GetTick(); uint8_t rx_byte;rcvdCount = 0;notRcvdCount = 0;while (1){if (HAL_UART_R

Hello,I want to interface two SAI of STM32L4S7VIT6 with two SGTL5000, which are working as transmitter and receiver at any time as used in telephone. Also interface one Si32287 through PCM. In datasheet SAI1_D1,D2, D3 are given but in reference manual it is not given. Also can we connect for one SGTL5000 with SAI1_FS_A, SAI1_MCLK_A,SAI1_SCK_A,SAI1_SD_A and SAI1_SD_B of same SAI1. And for other SGTL5000, can we connect SAI1_FS_B, SAI1_MCLK_B,SAI1_SCK_B of same SAI1 and for data SDI1_D1 and SDI1_D2. What are the functions of the lines SAI1_D1 and SAI1_D2? 

Hi, I'm a student quite new with STM, I am using a nucleo F072RB and I have been unable to print anything onto putty for a few weeks, it was working fine before summer break but not anymore (I haven't used my nucleo during that time), I am using the same baud rate and same port com as before, I tried to run my older projects that use putty and same result, nothing appears. I have no idea what to do to try to solve it, please help. Thanks.

Hello,We have bought the new AI Assistant board from Seeed Studio and we need some help on how we can connect an external debugger.We have two STLink/V2 debuggers, the plain and the ISOL version. However with the cables that they have we cannot connect any of them to the 8-pin debug port of the Seeed board.We assume that the necessary pins are on the STM32 connector, but which are they? Additionally the picture of the STLink/V2 debugger in:https://wiki.seeedstudio.com/ai_assistant_getting_started/#additional-documentation-of-the-applicationdoes not correspond to the debugger we have. Is that a different board from the one we have?https://www.st.com/en/development-tools/st-link-v2.html#overviewThanks in advance

I have an STM32L4R5ZI-P on a custom PCB. When designing the PCB I did not think far ahead enough and do my due diligence when it came to assigning and wiring pins on the STM32 in order to flash it. My design incorporates  USB D connected to my PCB which supplies power, and such, along with connections to USB_DM and USB_DP on my STM32. I did not wire BOOT0 or NRST. After looking online a bit, I heard that I must pull BOOT0 high and NRST low, allowing the STM32 to enter boot mode and then I can flash my STM32 via the DM and DP pins (using the CubeIDE and CubeProgrammer, etc.). I was just planning to jump BOOT0 to 3.3V and NRST to GND and then use my DM and DP pins on the USB to program is somehow using my PC. Am I thinking about this correctly? Is there an easier way to flash my virgin STM32 on my custom PCB? I do have a NUCLEO evaluation board for my specific STM32L4, which I have programmed and ran code on already. I was wondering if I can utilize the ST-LINK that is on the NUCLEO

Hi Everyone,I am facing an issue with my MCU entering low-power mode.My code works fine when tested separately. I can successfully put the MCU into STOP 0 mode and wake it up through an EXTI line interrupt, but only when the Window Watchdog (WWDG) is disabled.However, when I enable the WWDG, the MCU seems to get stuck at the WFI instruction when trying to enter STOP mode. It doesn’t proceed further or wake up through the EXTI line Interrupt. The only recovery option is a power cycle.Has anyone faced a similar issue, or know what might cause this behaviour when WWDG is active?I am open to sharing the source code.Any suggestions or pointers would be appreciated! 

Hello together,like many others here, I have the problem that after a short time, the debugger closes with the error message “Failed to get status,..”.The board is the nucleo-F767ZI. It has already been mentioned in the forum that it could be due to the USB cable. But thesame cable works with an nucleo-H755ZI-Q fine.It was also written that it could be due to the settings or by the code self.Therefore i did a test and sets a breakpoint direct after start:When standing at the breakpoint, the debugger still terminates after a few seconds. Stm32Device, pollAndNotify running...Warning: Ignoring a '-' sent by client.... GDB session, device event: 4GDB session, device event: 4GDB session, device event: 2GDB session, device event: 2NVIC_DFSR_REG = 0x0000000B Stm32Device, getHaltReason, code: 4GDB session, device event: 1GDB session, device event: 1ST-LINK device status: Failed to get status, Target not responding, retrying... 3Target is not responding, retrying...ST-LINK device stat