STM32 MCUs Boards and hardware tools

Hi,I am using the following codes to do system clock initialization on my STM32F411E-Discovery board:  /** Initializes the RCC Oscillators according to the specified parameters * in the RCC_OscInitTypeDef structure. */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; //Use X2 Crystal RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE; RCC_OscInitStruct.PLL.PLLM = 4; RCC_OscInitStruct.PLL.PLLN = 192; RCC_OscInitStruct.PLL.PLLP = RCC_PLLP_DIV4; RCC_OscInitStruct.PLL.PLLQ = 8; if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK) But  if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)returns time out error.I am sure crystal X2 is connected, but I don’t understand why it gives me time our error. Previosuly I also tried:RCC_OscInitStruct.HSEState = RCC_HSE_BYPASS;that also threw time out error, I gave up this configuration because I am not sure if SB14 and SB16 are bridged

GreetingsI am apprentice in electronics and for a school project I am trying to build a digital clock based on an STM32. I want to use an ST7735 based SPI display to show the time, because I am already familiar with the Adafruit GFX library (I did something similar on Arduino before). Since I have never done a project before, where I am selecting my MCU, although I already have some experience regarding PCB design. My questions/criteria are as follows:I want to have a MCU that I can solder by hand, therefore BGA packages and the like are out of the question The MCU needs to be compatible with the mentioned graphics library, I am aware of HAL libraries but would need assistance in choosing one I need at least 7 or 8 GPIOs to be available, so I can use external buttons to change the time I assume SPI and I2C (might  I want to be able to do the programming directly with the MCU soldered to the board, should I implement the programming interface via USB or should I use the SW pins?If I wer

Environment- Board: B-U585I-IOT02A (STM32U585AIIXQ)- STM32CubeIDE, FreeRTOS (CubeMX-generated), CMSIS-RTOS v2- Driver: ST vendored HTS221 component driver (`hts221.c` / `hts221_reg.c`),  untouched, accessed through the public `stmdev_ctx_t` of the object layer- I2C2 @ standard mode, internal pull-ups, 1 Hz sampling in one-shot modeHi, application on the **B-U585I-IOT02A** discovery kit (STM32U585, FreeRTOS, STM32CubeIDE). The onboard HTS221 humidity/temperature sensor is driven by ST's vendored driver from BSP.Symptoms that i am experiencing: Right after reset (cold boot), the HTS221 reports **~20 °C, then over the following minutes of operation the reading rises steadily and settles at **~30 °C**, while the actual room temperature stays ~20 °C.The drift is smooth and monotonic (thermal-looking), not noisy or jumpy.I have already verified that BSP driver conversion formula is correct. Also HTS221 internal heater is disabled.My sensor configuration:HTS221_Set_One_Shot(&hts_obj);hts2

Hi everyone,I am currently working on repairing my NUCLEO-F767ZI board (Revision: [MB1137 Rev B]). The 3.3V LDO regulator (U6) was damaged and needs to be replaced.While working on it, I found a hardware discrepancy: According to the official schematic, U6 is specified as LD39050PU33R (a 6-pin DFN package). However, on my physical board, the PCB footprint for U6 clearly has 8 pads. The damaged original IC I removed is an 8-pin package with the marking code "PH 2kE". Since a 6-pin IC cannot fit on this 8-pin footprint, has anyone encountered this before? Could you please help me identify the correct 8-pin LDO part number to replace it?I have attached pictures of the physical 8-pin IC and the 8-pad PCB footprint for reference.Any advice would be greatly appreciated. Thanks in advance! Figure 1: The removed original 8-pin LDO IC with the marking code "PH 2kE".Figure 2: The physical 8-pad PCB footprint for U6 on the NUCLEO-F767ZI board. 

I am wanting advice on the placement and routing of the power bypass capacitors on a STM32U5G9 UFBGA144 processor. Are there any layout reference designs? I am routing a 6 layer board. 

I have a NUCLEO-F091RC (on-board ST-LINK/V2-1, USB ID 0483:374b, latest firmware V2J33M25). When plugged directly into my Mac it enumerates and drops repeatedly. LD1 keeps blinking red.I found the ST FAQ "Possible communication failure between STLINK-V3 and some recent computers" (eUSB2 repeater interoperability). My symptoms look very similar, but my probe is a V2-1 that enumerates at full speed (12 Mbps), not a V3, so I'd like to know if the V2-1 is affected too.SetupMacBook Pro 14-inch (Nov 2023), Apple M3 Pro, macOS Tahoe 26.7.1 USB-C to Mini-B cable, directly into the MacSymptom (from log stream, repeating about every 0.3 s): enumerated 0x0483/374b/0100 (STM32 STLink / 1) at 12 MbpsAppleUSBIORequest::complete: device 1 (STM32 STLink) endpoint 0x00: status 0xe00002ed (transaction error): 0 bytes transferredAppleUSBHostPort::terminateDevice: destroying 0x0483/374b/0100 (STM32 STLink): hardware connection lostioreg -p IOUSB -w0 shows a new STM32 STLink entry with a different id every

I have a STM32F769I-DISCO and want to create some software and run it but i am having a problem.When i plug the board to the PC using a USB data cable, in the ST_LINK port (CN16) the board turns on, LD6 is on as well as LD5 while LD8 is blinking red. I can use the screen correctly but the problem is that my pc doesn’t seem to acknowledge the existence of the board. Nothing appears in the device manager and it makes no sound when i plug it in. Also the CN3 Jumper is placed on “stlk”. Is there something i am doing wrong?

hi I’m using the board named NUCLEO-N657X0-Q and I want to use feature of FDCANbut I couldn’t find pin map for that where is the pin number for FDCAN? Thanks

Hello ST Team,I want to use USB interface to update firmware of STM32F405RGT6 MCU.We have verified it with USB DP and DM from external USB but now want to put in our board.Our board is also generating 5V and USB will also have 5V. What should I do so that it will not conflict or cause any issue? How to connect CC1 or CC2 pins of USB to our MCU so that we got to know connection is available from USB? If we want to do firmware update using USB then how our MCU will go in boot mode?Please find screenshot of our schematic which we are working now: 

I am building a live camera feed project using an STM32H747I-DISCO (MB1166-A09) board and a B-CAMS-OMV (MB1683-CAMS-A02) camera module.I tried using the standard example capture mode ,i set up everything but i always get stuck here ,any solutions?

Hi,I want to start a custom board design using STM32F405 but later I want to upgrade to STM32F407.Below are the features I want to target.Ethernet (IEEE802.3, TCP/IP< DHCP, MAC, SNTP) Can ethernet (10/100) over SPI interface (W5500) will work for STM32F405?  USB OTG HOST UART x3 Analog 12-16 bit PWM input: at least 10KHz 8-bit Parallel interface for display.Is there any development platform available to cater all these features.Also, please suggest the programming tool as well for production.Let me know if you have any questions.Thanks, Mukesh

In this case, I want to debug a new control board whose MCU is STM32H563. But I didn’t have a proper debugger, so I want to use the ST-LINK debugger of the STM32H5 Nucleo-144 board for the new board’s debugging.The debugger connector of the STM32H5 Nucleo-144 board : The debugger connector of my own board : I want to connect the 2 connectors through a cable for the external board’s debugging.So currently my issue is that the ST-LINK debugger can’t be used on the external board, I tried some methods for this, but it didn’t work, such as removing the jumper of JP5, connecting the jumper for JP1. My question is that : Can the ST-LINK debugger of STM32H5 Nucleo-144 board be used on an external board, if possible please show me the steps of the configurations on the Nucleo board.

Hi, I'm new to PCB design. I'm planning to build a handmade board for a project that uses the STM32F103C8T6, and I've run into some issues in certain parts of the PCB design. My board only has copper on one side (single-sided). For the HSE 8MHz and LSE 32.768kHz crystal oscillators, the body needs to be placed on the bottom layer, with the pins passing through holes to reach the top layer where they will be soldered. I'm concerned about the soldered area where the solder forms a fillet on the top layer, and whether this fillet, being in line with the OSC traces running toward the MCU, could cause problems. To put it simply: could the solder fillet of the crystal on the top layer cause frequency issues, reduced performance, or make it completely unusable? Since my project is currently in the experimental stage, I haven't built the board yet. The images I've included are just for better understanding and were collected from a few websites. What's your opinion on this?

Could you share the schematic file for checking the pin out for this two programmer - STLINK-V3MINIE, ST-LINK/V2-ISOL 

Hello,I just purchased two STM32H5E5 Nucleo boards along with two of the ST Memory board kits. What I am planning is to take one of the QSPI flash M.2 boards and reconfigure it so that the memory(s) attached to OCTOSPI1 are two identical flash chips, and have two identical 64Mb PSRAMs attached to OCTOSPI2. Reading the octospi section of the reference manual it appears that each “bank” can share the clk and the OCTOSPI(1/2) chip selects and putting the respective OCTOSPI channels in DMM mode and have them memory mapped. Also, I have moved a SB on the Nucleo so that OCTOSPI2_NCS is connected to the M2.0 connector.  I have included a pic of what I am trying to do. Any help would be appreciated.  Thank you, 

Hello everyone!I just wanted to share with you all the pinout of NUCLEO-C542RC and STM32C542RCT6. I just moved from STM32F013RB, which had a lot of schematics online, but currently the C5 series has close to none.The pinout list all the available functions for each pin. I hope it’ll be as useful for you as it was for me. I attached to this post the drawio file, for easy edits.If you have any recommendation, please let me know. 

 I have redrawn the NUCLEO-H5E5ZJ schematic as a personal exercise in understanding the architecture of the board and the STM32H5E5. I have consolidated the original multi-sheet design into a main STM32H5E5 schematic and a separate STLINK schematic, using port objects to make the principal interconnections explicit. During the redraw, I cross-checked the connectivity against ST's original Altium design files and the more recent PDF schematics.My aim was to show the MCU GPIO ports rather than their alternate functions, as I found this gave me a different picture of how the MCU is connected to the board. The exercise also revealed just how much functionality is exposed by the NUCLEO-H5E5ZJ PCB: the usefulness of the M.2 Key A socket, the extensive possibilities offered by the other headers, and, in particular, the surprisingly large number of MCU GPIOs that are brought out to them and are available.I have a great deal of respect for the NUCLEO-H5E5ZJ PCB and for the STM32H5E5. The capabi

Can anyone please pint me out to a BSDL file useful for STM32H7A3VIH6Q ? Thank youGabriele

I am facing an intermittent issue with the STM32N6570-DK when using it with macOS.Setup Board: STM32N6570-DK Host: MacBook Pro STM32CubeProgrammer: v2.23.0 Connection: USB-C hub with USB-A ports ( I am currently using the following USB hub: https://amzn.in/d/02O7R7zS) One USB-A port is connected to the STM32N6570-DK USB1 USB-C port Another USB-A port is connected to the STM32N6570-DK ST-LINK USB-C port Application: AI inference application using the onboard display and USB communication to stream data back to the host Initially, JP2 was configured on pins 1–2 (5V_STLK). IssueWhen using a direct USB-C-to-USB-C connection on Windows, I do not encounter this issue.However, on macOS, a direct USB-C-to-USB-C connection results in DEV_USB_COMM_ERR. Based on a suggestion from a related ST Community discussion (ST-LINK stuck in DEV_USB_COMM_ERR until USB replug after connecting with no target | Community),Also, we found out that a known issue/ limitation regarding this (USB

Hello,I have a Nucleo-L432KC with a dead microcontroller, but the STLink IC is ok.I wanted to use the STM32F103 to develop some USB code, so I removed the broken L432 and populated the reprogramming header for the SWD, CN2.I connected there a STLINK-MINIE to erase it, but CubeIDEProgrammer cannot read back anything.At the first connection I was able to erase it (maybe just partially?), because now it is not recognized anymore as ST_Link device and the LED has only a faint red color.I also connected the reset to the STLINK-MINIE and tied the BOOT0 to 3.3V.Is there anything else I can try to fully erase and then re-program the F103? Thanks,Marco  

I’m using the MB1293 USB dongle as a daughter board for a project & am after the dimension between the 2 edge headers as I need to create a footprint on the main board. Is this information available, I’d rather not trust on manual measurement. See below,  

I have a custom board using an STM32G431RB (LQFP64) that was previously programmable/debuggable without issue. After switching to a new ST-LINK debugger, I started consistently getting:Error: ST-LINK error (DEV_TARGET_HELD_UNDER_RESET)Root cause identified: the board was being powered entirely from the debugger's VDD/VTref pin rather than an independent supply. Powering the board from an external bench supply (debugger providing only SWDIO/SWCLK/GND, not VDD) resolves the connection issue. My working theory is that the ST-LINK's VDD/VTref pin is intended as a voltage sense input, not a real power source, and different probe units/firmware versions apparently have inconsistent (often very limited) current-sourcing capability there — my original debugger happened to supply enough current for this board to stay stable; every replacement unit since (including confirmed-genuine ST-LINK/V2 and V3 probes) could not, leading to what looks like repeated brown-out resets rather than an actual st

I am currently working with an STM32 MCU and facing an issue while trying to connect the board to my PC using an ST-LINK debugger. The board powers on normally and there does not appear to be any obvious hardware issue, but STM32CubeProgrammer is unable to detect the target device. The connection attempt either fails or reports that no target is found, so I am currently unable to program or debug the MCU.So far, I have checked the basic connections and setup:USB cable and ST-LINK connection Board power supply and voltage SWDIO and SWCLK connections STM32CubeProgrammer installation ST-LINK firmware and connection settingsI am not sure if the problem could be caused by the MCU configuration, SWD interface, boot mode, or some setting that may have been changed in the firmware. I would also like to know if there are any recommended STM32CubeProgrammer options or recovery procedures that should be tried when the target MCU is not detected.Has anyone experienced a similar issue with an STM32

I am trying to build a STM32L0 based low powered project , i am hitting target hold under reset randomly and when i left it power off for few hours its back to working . idk why its happening randomly 

I have created a dev board based on the STM32H743IIT6 MCU. On first power up I have managed to destroy two MCUs and I cant figure out what is killing them. On first power up 3V3 is immediately shorted to GND, after removing the MCU the pins are permanently shorted.Here is my schematic. The only changes I have made from the physical PCB is adding 10K pull up to PDR_ON, 10K in line from VBUS to the MCU and connecting the VCAP pins. Does anything stand out in the schematic?I have created modules from multiple STM MCUs(F1,G0,G4,WB,H5,N6) and this is the first time I am running into a power issue with a PCB.