STM32 MCUs Boards and hardware tools

Hello,I've just received my fresh new SMT32H747I-DISCO dev board and I wanted to try some samples.I have some experience deveolping on embedded Liuxes, but this is my second MCU (the first one was a Raspberry PICO, don't know if this counts). I am using a MacBookPro with Apple silicon (M3) and MacOS 14.4What I have done:read the specs, configured the board to get power and STLink from CN2 (as is by factory)installed every tool available:STM32CubeProgrammerSTM32CubeIDE (which also installed a SMTLink server nstall ,st-stlink-server.2.1.1-2, installed successfully ) even STM32CubeMXconnected the board to a USB-C port on my Mac via a USB-C to USB-B mini cable2 times out of three the main led (LD10?) starts red, then flashes red/green then stays green. The other times the board LED stays red. In either case, nothing on the LCD display. to me the board seems waiting.On the former occurrences, MacOS then asks me for permission to connectbut that's it. I wanted to install the Tutti Fruit

I have this Riverdi board with a STM32H757XIH6 microcontroller. I have been using it consistently and loading touchgfx programs on it.  Today I was trying to use the 40 pin header and program one of the gpio pins on it to act as a gpio output. I put an led on a ground and the PA4 pin, which was the pin I was using on the 40 pin header, to verify the toggling code was working.  Nothing happened and so I tried to load a basic program onto the board using stmcubeMX and selecting the  STM32H757XIH6 microcontroller.   I selected the PA4 pin on the .ioc file and generated the code.  However, when trying to run the program I get this error, . Not sure if it was that program or touching the multi meter to certain pins that cause a hard fault or something.  I would not think a multi meter could do anything like that, but I'm trying to figure out why all of a sudden I am unable to upload a program to the board when I have been consistently.&nbsp

Hello, While using the Nucleo-F446ZE, I observed that pin PA1 remains at approximately 2.6 V during reset, even when an external pull-down resistor is applied. On this development board, PA1 can be configured as the RMII Reference Clock. However, I have removed SB13, so this function should be disconnected and no longer influence the pin. Given that no internal or external circuitry should be driving this pin and considering that an external pull-down resistor is present I would expect PA1 to be held at 0 V during reset. Why the pin is not pulled low in this condition?

Hi,  I would like to know when samples and kits for the new STM32H5E4/5E5 will be available.I already asked my local distributor this question, but they didn't know the answer. Ari

Hi, I'm developing a custom STM32G491CEU6 board with USB-C and pins for external ST-LINK programmer. Board is powered from external source. I connected only D+, D- and GND from on USB-C to MCU, because I wanted to use this only for debug. Right now the USB-C communication works only if ST-LINK is connected (had no idea about VBUS sensing). Can i override it somehow? Schematics below  

My STM32H745I-DISCO touch screen stopped working after a HardFault/debugger crash while running a test app generated by STM32CubeMX ("Create project from board"). The display works perfectly but touch is completely unresponsive. Steps already taken: Full chip erase + reflashed official FULL.hex (with MT25TL01G external loader) Verified option bytes (RDP=AA, BCM4 and BCM7 both enabled) Fixed reset mode from "Hardware reset" to "Software reset" ST-LINK firmware is up to date (V3J17M10) I2C4 registers show uninitialized on both cores Display works, buttons visible, but no touch response at all.

Hello Community, I am struggling with a custom board design based on the STM32H743ZIT6 (LQFP144, non-SMPS version). I’ve replaced the MCU already, but the symptoms remain identical, suggesting a fundamental hardware/layout issue. The Symptoms: Current Draw: 10mA when BOOT0 = GND. Approx. 50mA when BOOT0 = 3.3V (System Bootloader). VCAP Voltage: Measuring approx. 1.0V. Debug Connection: Using Segger J-Link (V11). "Failed to initialize DAP" / "Can not attach to CPU". VTref is stable at 3.3V, NRST is at 3.3V. USB DFU: When BOOT0 = 3.3V, Windows reports "Device Descriptor Request Failed" (Unknown Device) when connected via usb. SWD Pins: PA13/PA14 show ~1.6V when floating (no debugger connected), which is highly unusual Same Symptoms if 3.3V are supplied by ams1117 or laboratory power supply My Schematic: VBat, all Vdds, Vdda, VRef, PDR_ON are all connected to 3.3V all GNDs and AGND are connected to GND each Vcaps (2x) has a 2.2uF capacitor (alltough i am not sure abo

I have a 14-pin connector and a 6-pin fall back connector. I can connect the 6-pin SWD via st-link V2 on a nucleo board but I cannot connect with a V3 MINIE on the 14-pin. Any ideas? I followed the schematic for a 14-pin connector I found on a NUCLEO board, which had a 100 ohm resistor on GND detect. I have bypassed it but the result is still the same. Apart from that and the TX/RX, the wires are the same for the 6-pin connector that works?Here's my output:CDLiveWatchSetup Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'. Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD Warn : The selected adapter does not support debugging this device in secure mode adapter speed: 24 kHz none separate Info : Listening on port 50004 for tcl connections Info : Listening on port 50005 for telnet connections Info : clock speed 24 kHz Info : STLINK V3J14M5 (API v3) V

Bonjour,Je me permets de vous contacter afin de solliciter votre aide concernant le débogage d’une carte basée sur un microcontrôleur STM32L471 ( comme présenté dans les images suivantes ).Je souhaiterais pouvoir programmer et récupérer les logs de la carte, et je cherche donc le matériel nécessaire pour cela (interface de debug, câble, connecteur et éventuellement sonde de programmation type ST-LINK).Pourriez-vous s’il vous plaît me partager des liens ou références des produits compatibles recommandés pour ce type de carte ?Je vous remercie par avance pour votre aide.Cordialement,Google translation:Hello, I'm contacting you to request your help with debugging a board based on an STM32L471 microcontroller (as shown in the following images). I would like to be able to program and retrieve the board's logs, and I'm therefore looking for the necessary equipment (debug interface, cable, connector, and possibly an ST-LINK type programming probe). Could you please share any links or product

I am using a Nucleo STM32F411, without any hardware modification.I am working on a project which involves only UART and Debug monitor interrupt, so my code does not write anything to flash nor to option bytes. Yet it seems that the board is bricked after running my firmware. I tried STM32_Programmer_CLI and STM32CubeProgrammer to erase the flash but both fail:is there a way to recover the board ?

Hi, I´m designing an USB host device (with STM32U5). Therefore I´ve ha a look at the schematics of the STM32U575I-EV. Could someone explain what the MOSFETs are for? Best regards, Achim

I bought STM32F4DISCOVERY. But in the STMcube IDE, i see only STM32F407G-DISC1 board.  Are STM32F4DISCOVERY vs STM32F407G-DISC1 same? Can I select STM32F407G-DISC1 and create a project in the IDE and use STM32F4DISCOVERY hardware to run the project? Will it create any issues?

Where can I download the STM32H503 Nucleo schematic?

Hello everyone. I have recently made my own STM32 board based on the STM32F405. After soldering all the components and testing all pads and connections, finding them to be wired correctly and checking that the 3.3V is being supplied to all the correct pins, I tried to upload some code but to my shock the STM32F405 isn't establishing a connection via the ST-Link V2 nor the USB cable. After trying multiple fixes, I suspect the issue might be the STM32F405 chip that I got off AliExpress itself.  So before I took any further steps to replace it, I decided to post my schematics on here for review in case the problem was in my PCB design. If you have any remarks on what might have caused this problem, please share them. NOTE: The -B label is referring to ground, and P is the VCC. schematics:    

Hello,   I designed a custom control board based on STM32G431CBT6 and before manufacturing the PCB I would like to make sure there are no fundamental hardware mistakes.   My main concern is not firmware but hardware connections.   I would appreciate if you can review especially:   SWD programming interface connections Power supply and decoupling capacitors BOOT0 and NRST configuration VDDA and VREF+ connections CAN transceiver interface (TJA1051/3 with VIO = 3.3V) Anything that may prevent programming or startup     The goal is to verify that the MCU can be programmed and start reliably after assembly.   I am attaching the schematic below.   Thank you very much for your time.   MCU: STM32G431CBT6 Supply: 3.3V regulator Debugger: ST-Link via SWD

Hello, I am using an STM32H755 Nucleo board in a system where the board is plugged into a custom PCB via headers. The system has been working for about two weeks without any issues. Occasionally I remove the Nucleo board to update the firmware and then plug it back into the PCB. Today the system stopped responding to UART commands. When I connected the board to my PC, STM32CubeIDE reported: "No ST-LINK detected! Please connect ST-LINK and restart the debug session." I also tried STM32 ST-LINK Utility and got: "Can not connect to target! Please select 'Connect Under Reset' mode..." However, STLinkUpgrade is able to detect the ST-LINK and perform a firmware upgrade. Another important observation: The ST-LINK MCU on the board (STM32F7) is getting very hot. Additional diagnostics: - The board was completely removed from the external PCB. - Even when powered independently, the ST-LINK MCU still overheats. - The board draws significantly higher current than normal. - I cannot measure proper

Hello community,  I am working with different ibis model of STM32H7, however, this is the only one that's giving me an error in my Altium Designer – could you have a look at it? The file is stm32h723_730_733_lqfp144.ibs Kind regards,Javier.

Was trying to figure out an issue I was having with the SWDCLK pin, and realized there was a difference between the STLink V3-MINIE and the V3-SET.When idle (either just plugged into a computer, or after programming), the SWDCLK idles high on the MINIE, while on the SET it idles low.Is this an intentional difference? Is there any way to make the SWDCLK idle low on the MINIE as well?

Hello everyone,I need to drive up to 11 LPS27HHTW pressure/temperature sensors using an STM32C5 microcontroller. Currently, I'm testing the setup on an NUCLEO-C562RE board with multiple STEVAL-MKI220V1 modules.At first glance, using I3C dynamic addressing seemed to solve the bus conflict issue. However, while testing, I realized that all of these sensors share the exact same 48-bit PID (0x020800B30000). This generates a collision when doing an ENTDAA broadcast.Since the sensors only have 2 possible static I2C addresses (0x5c and 0x5d, depending on the SA0 pin level), I cannot use the SETDASA command for all 11 devices either.I can't split the sensors across different buses since there are too many of them. I would like to know if there are better architectural options than playing with the CS pin levels using 11 dedicated GPIOs to enable/disable communication on each sensor individually.Any advice on how you would drive that many sensor using a STM32C5 mcu?Best regards,Mathias

Hi,I have the STM32H753ZI Nucleo board and have developed firmware around this MCU with this board as my reference platform.On our product, firmware updates will be uploaded via the UART interfaces.So the user will need to enter Bootloader.On the Nucleo board, the LD3 Red LED stays illuminated when in Bootloader.I think this is because the GPIO pin is being pulled up, and this is not intentional as an indicator?An indication to the user that they have successfully reset the MCU into Bootloader is useful.How can you recommend we can do this in a reliable way in the future?Thanks.

Hi, I have two questions regarding ST-Link V2 programming: 1. For connecting and programming via SWD, is it safe to connect only NRST, GND, SWCLK, SWDIO without the Target VDD pin? We might “fake” the voltage for space reasons. Could this cause any issues?   2. I assume ST-Link flashes the MCU memory directly via SWD, not through the bootloader like USB DFU. Can anyone explain in detail how each pin behaves during programming, and if NRST can be omitted in some cases?   It would be helpful if there is an official ST document explaining this. Thanks!  

Hi  I am using an STM32N6570-DK board. For my project, I need to measure the total MCU power consumption (core power plus the power consumed by the I/O pins while interfacing with the SDRAM and OSPI flash). I have reviewed the documentation regarding power measurement, but I am confused because there are multiple power supplies. Which pins on CN2 should I use for my measurements, and is there a common point to measure the total power?How to measure power on the STM32N6 - STMicroelectronics Community

Hello, I am experiencing an issue with my STM32U5G9J-DK2 board. Description: Board powered through STLINK USB LED LD7 is ON LED LD6 is ON LED LD1 is OFF I measured about 0.8 Ω between 3V3 and GND Component U16 overheats a few seconds after power-up No external circuit is connected I already tried: Another USB cable and power source Disconnecting all external peripherals My question:Could someone help identify where the problem might come from?Could U16 be defective or indicate a short circuit on the 3.3V rail? Thank you for your help.

Question moved from the knoowledge base article: How to use STLINK-V3 MCO output on Nucleo boards as a precise clock source for STM32 Hello,  With this method, what level of accuracy (PPM) is expected ?   Thank you and have a good day.  

Hi Team, I am working with the STM32N6570-DK board and reviewing the available power measurement methodology. From what I understand, the current approach/documentation focuses on measuring only VDD_CORE power. My requirement is different: I want to measure the total MCU power using a JS220 Joulescope, not just the VDD_CORE domain. Specifically, I would like to understand: What is the recommended hardware measurement point on the STM32N6570-DK board to capture total MCU power? Is there a board jumper, shunt, or power rail that isolates the complete MCU supply path? If measuring only VDD_CORE is the officially supported method, what additional rails should be included to estimate total MCU power? Has ST validated any method for measuring full MCU consumption on this board, including CPU, NPU, internal memories, and essential MCU peripherals? Are there any precautions regarding ST-LINK, external memories, camera/display rails, or other board circuitry