STM32 MCUs Boards and hardware tools

Hello Team,We are developing our new project by using STM32H7S7L8H6. We want to use STM32H7S7L8H6 in SMPS mode. So, refer attached schematic design image with SMPS mode. Request you to please review it and provide your valuable inputs.Note : In our application we are not used USB.  Thanks & Regards,Jignesh Karena 

Originally a comment on the How to recognize a genuine ST-LINK/V2 versus a cloned one Knowledge Base article.Moved to main forum for better visibility / discussion.I bought this  ST-LINK V2 on Amazon ( see pictures) . I don't think its' a genuine STM device. STM32CubeIDE and STM32CubeProgrammer recognize it but No STM32 target is found ( STM32L051K8U6)I notice that my ST-Link V2 does not provide clock signal on pin 9 (SWCLK) I'm using VT ref pin, SWDIO pin, SWDCLK pin, GND pin and RST pin.

Hello all and happy holidays, I am having a bit of weirdness going on. I have setup UART using stm32 HAL, confirmed it is working properly by stepping through (using an STLINK-V3-MINIE) as well as confirmed data is on the wire with a logic analyzer as well as a scope. Furthermore, I have also run a loopback test to assure the com port is working for the V3-MINIE. Despite this, I still can't get transmission to show up in my serial terminal (I did receive the message once but I beleive it was in a GDB session and I have not been able to replicate it since). Any suggestions for anyone who has run into a similar issue with this device (for context I am using an STM32F411CEU6 black pill board)? I can provide any extra context where needed but I have run through the motions and still cannot seem to come to a solution.  

I'm trying to work with a STM32F4-Discovery board, and previously it connected perfectly okay, but a couple weeks ago something, seemingly out of nowhere, broke and CubeIDE stopped detecting the board and writing programs to it showing this message:I tried reinstalling the IDE, downgraging the toolchain, upgrading the IDE, creating a fresh project and so on.I'm running version 1.19.0 CubeIDE, using EndeavourOS (Arch-based).Here are my udev rules for a relevant device:# stm32 nucleo boards, with onboard st/linkv2-1 # ie, STM32F0, STM32F4. SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374b", \ MODE="660", GROUP="plugdev", TAG+="uaccess", ENV{ID_MM_DEVICE_IGNORE}="1", \ SYMLINK+="stlinkv2-1_%n" SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3752", \ MODE="660", GROUP="plugdev", TAG+="uaccess", ENV{ID_MM_DEVICE_IGNORE}="1", \ SYMLINK+="stlinkv2-1_%n"My user is a member of the plugdev group. But the important detail is that if I run stm32cube

 Here is a more professional and technically concise rephrasing of your post, optimized for a developer forum or technical support ticket:Subject: Clarification on VBUS Sensing and Internal Pull-up Management for STM32WB55Hello,Based on the STM32 USB Training MOOC, it is highly recommended to implement VBUS sensing to distinguish between a "Suspended" state (no bus activity) and a "Disconnected" state (physical cable removal). This prevents back-powering the host via the internal D+ pull-up resistor when the device is self-powered.However, I’ve noticed a few discrepancies regarding the STM32WB55 implementation:Tooling: In STM32CubeIDE (Device Configuration Tool), there is no dedicated "VBUS Sensing" pin option available for the USB peripheral on this specific MCU series.Reference Hardware: Looking at the P-NUCLEO-WB55 schematics, there is no voltage divider or direct trace connecting VBUS to a GPIO for sensing purposes.Could someone please clarify the following for a self-powered

HiI had the stm32f746G-disco development board laying around, after while I wanted to try some application, during flash I got warning that my st-link firmware was old, I wanted to upgrade it but failed during upgrade, anyway it was very old firmware. Well I had another st-link at hand, I have connected it to the SWD port on the dev-kit, *** me I thought it is connected to stm32f7 but after pressing erase flash I saw the connected MCU is stmf103, well I accidentally erased the st-link, long story short it was a *** mistake.I have been searching online there are lots of suggestion, I am very confused, is there a way to recover the on board stlink. Because there is no jumper or pin that exposes SWD/JTAG pins of stm32f7, I need to recover it.I have tried "java -jar STLinkUpgrade.jar -d8_d32_msc_br -force_prog" with stm32f407 nucleo board but no chance.Any help appreciated thanks.

I got my STM32H745I-DISCO (STM32H745XIH6U) kit and wanted to update st-link (STLINK-V3E) firmware. Unfortunately I used unreliable USB cable and it got probably disconnected during the process. Now the STLinkUpgrade shows the line "Unknown firmware type. Don't know how to upgrade."Is there any chance to restore original firmware? Or do I have to use external ST-Link/buy new board?Thank you in advance.

Hi, I mistakenly used the pin for swd on my F446RE for other purposes and now it does not connect through st link.Can anyone guide me through a solution for it? The only thing I can do now is update the board. The two leds are always red.

Hi Team, Currently, I am working on the STM32N657-DK EVB with an SPI interface (ADS118 sensor). I have enabled SPI5 in the .ioc file. The configured pins are: PE11 – SCK PH8 – MISO PG2 – MOSI PA3 – CS According to the schematic, these pins are connected to the CN12 connector. My question is whether these pins can communicate correctly using the SPI5 interface or not. Secondly, I want to generate PWM signals. Could you please let me know which pins are suitable for PWM generation on this board? I tried using the CN11 and CN12 connectors to drive PWM signals on pins such as PE9, PE10, and PE11, but PWM is not being generated. Kindly let me know your inputs.  

New question Moved from this thread. Hello @mƎALLEm  Thankyou for the reply. I was trying to connect stm32U585aii6Q and STM32N6 with  same audio codec MB1219 & wifi, of course one at a time. Can you guide is it possible to do.   Thanks  Regards, Sakshi 

Hi allI am looking for a solution to prevent the NULCEO-H563ZI board from resetting every time the USB-C cable to the PC is plugged in and out. The virtual COM port of the ST-LINK is used to send configuration data to the board. Therefore, it is not so handy if it resets itself every time I unplug the PC. It is supposed to continue to run.The NUCLEO is supplied by 3.3V from a host board, so no PWR-SEL jumper is set and SB1 is removed. The on-board crystal oscillator is used (SB48 and SB50 equipped with 0R's and SB49 of ST-LINK clock is removed). Thanks for your inputs :) 

Hello, I want to use the STM32 H723ZG Nucleo board 144p in my LoRaWAN project. For that, I need my microcontroller to consume less than 10uA of current in standby or sleep mode. Is that achievable? If yes, then,1- What will be the hardware?2- clock configurations?3- What will be the configurations in the IOC file?4- How can I not give power to the Ethernet port?or if there is anything else i need to keep in mind.

We just purchased one STM32U5G9J-DK1 from Digikey. We try to replace the LCD module on it with our own selected display with one MIPI lane. Thus, we are designing a interface board so that it can mate with CN2. And since we are also using a touch screen with I2C interface, we also need to connect CN4 I2C5. In this case, may I have the schematic and BOM of the main board MB1928B so that I can have all the pin definitions and connector model information?Thank you.

Hello Team,I have a new STM32F401RE board along with the ST-Link.I tried installing all the drivers required for the STM32 hardware, but the USB device itself is not getting recognised. Can you please help me resolve this issue? 

I created system_clock_initial function to config my board using PLL as system clock and running at 200MHz and also get APB1 timer at 100Mhz (for TIM5 delay function). See my code below. After that I create delay function from TIM5 and test with build-in LED when I upload my code to board and it begin to run, at beginning of time LED blink faster than delay time(1second) that I specify but after about 30 second LED blink properly with 1 second delay.What should I fix it?void system_clock_initial(void) { /* Turn ON HSE oscillator */ RCC->CR |= (RCC_CR_HSEON); while(!(RCC->CR & RCC_CR_HSERDY_Msk)){} /* Enable Power interface clock */ RCC->APB1ENR |= (RCC_APB1ENR_PWREN); /* Enable Backup Domain Write Protection for Access Backup RTC & SDRAM */ PWR->CR1 |= (PWR_CR1_DBP); /* Set flash period to 7 wait state */ FLASH->ACR = (FLASH_ACR_LATENCY_7WS | FLASH_ACR_PRFTEN); /* PPRE1 Divide by 4 */ RCC->CFGR = (RCC->CFGR & ~(RCC_CFGR_PPRE1_M

Hello everyone. I was trying to implement the 6 Step PWM using STM32F411RE Nucleo board to drive a BLDC motor via 3 half bridges. Each half bridge was driven by signals from TIM1, using 3 of it's channels along with their complementary output for HIN and LIN of  IR2110.TIM1_CH1 is located at PA8 for this board. This pin is shows continuity towards the 5V and U5V pins. The voltage for PA8 in reference to GND is around 2.8V. I have tried almost everything including disabling the TIM1, disable the GPIO pins, setting the PA8 as analog pin, disabling the peripheral clock, disable MCO, cleared MODER and AFR, tried NVIC_SystemReset, RCC clock reset, Timer Reset, shorted BOOT0 and VDD - power cycling the board, lastly I also pulled NRST low, did all of these separately, but still it showed a short between PA8 and 5V-U5V pins. This pin worked fine before. It was only after I accidentally set LOCK to level 2 in BDTR register of TIM1 that I saw weird behaviour from this TIM1 Channe

Hello,recently I made a board for a project and was planning to flash firmware  with ST-LINK/V2. However, when I wanted to flash a test program I got a message from Console:Target no device foundError in initializing ST-LINK device.Reason: No device found on target. I checked all the connections and VDD pins with decoupling caps and looks like everything is properly connected. Yet still I don't understand what is the reason of not connecting. Schematic of the project:Physical connections:Attached as connections.jpeg  I upgraded ST-LINK tool to the latest version and the MCU I am using is STM32G474CET3ST-LINK/V2 model: B202533Most of the design is just copied from the Reference design STM32G4 Series document.Any help is highly appreciated.

Hello everyone,I am facing a persistent OVRCR (LD6) over-current indication on a NUCLEO-H723ZG board and would appreciate guidance.Board behaviorPowering the board via CN1 (ST-LINK USB) onlyNo external connections: no peripherals, no wires, no common ground, no shieldsPower source selector JP2 set to STLINKObservationsJP4 removed (VDD_MCU / IDD link open):LD6 (OVRCR) OFFLD5 solid greenST-LINK enumerates correctly on PCE5V ≈ 5 V3V3 ≈ 3.2–3.3 VJP4 installed:LD6 (OVRCR) turns RED immediatelyLD5 flickers faintlyUSB power switch (U2 near CN1) starts heatingBoard does not stay poweredCurrent measurement across JP4:Measured by replacing JP4 with a multimeter (DC current mode)Target domain draws ~1 AThis happens regardless of JP5 position (VB–VDD or VDD–3V3)Resistance measurements (USB unplugged):With JP4 installed:3V3 → GND ≈ 10–60 ΩIOREF / VBAT → GND similar rangeWith JP4 removed:3V3 / IOREF / VBAT → GND ≈ 150–200 ΩConclusion so farBase power system is OKOvercurrent occurs only when the VDD_

Hi does anybody know how to locate the nRST, pin on a GT2p, control board? When I connect st link it says UR connection needs SWrst which says I need to find the nRST, pin.  to connect another wire that goes from St link, v2, cloneto the nRST,  pin or button on the GT2p, control board. I can take a picture of what the PCB, looks like in about an hour? Thanks

Hello STM32 Community,I am a newbie and facing an issue with my NUCLEO-STM32H755ZI board.I am unable to connect to the STM32H755 target using STM32CubeProgrammer, even though the ST-LINK appears to be working correctly,HardwareBoard: NUCLEO-STM32H755ZIDebugger: On-board ST-LINKUSB connection: CN1 (USB-A to Micro-B).SoftwareSTM32CubeProgrammer: v2.21.0OS: WindowsConnection mode: ST-LINK / SWDObserved BehaviorST-LINK is detected correctly by WindowsST-LINK Virtual COM Port is visible in Device ManagerTarget voltage ~3.27 V is shown in Cube programmer. Green power LED (LD3) is Red ST-LINK LED is blinkingError: No STM32 target found!Unable to get core IDIf your product embeds Debug Authentication,please perform a discovery using Debug Authentication

Title edited to clarify that STM32H7 Nucleo-144 boards is the subject.Table 5 on Page 20 of UM2407 contains erroneous info on the STDC14 connector. I am very sure that the descriptions for STDC14 pins 8 and 12 are wrong, maybe others aswell.

Hello,We need to add WiFi connectivity to an STM32N6570-DK board and run Zephyr on it.Is that possible? Can you propose a solution? We have seen X-NUCLEO-67W61M1 expansion board that can work with STM32N6. But can that board be connected with the DK board? Thank you very much for any suggestion.Regards.

I’m running into a confusing SPI issue and would appreciate a second set of eyes.I have an ADXL345 accelerometer over SPI working perfectly on an STM32F446RE Nucleo board. I can reliably read the DEVID register (0x00 → 0xE5) and stream XYZ data.I moved the exact same code (verbatim) to an STM32H723ZG board and swapped the SPI handle / GPIO definitions accordingly. The SPI peripheral initializes correctly, but the ADXL345 no longer returns 0xE5. Reads either return 0x00 / 0xFF or garbage depending on settings.Things I’ve already checked / changed:Same ADXL345 breakout (verified working on F446)SPI mode (CPOL/CPHA) set to Mode 3 per datasheetMSB + READ bit set correctlyChip select manually controlledSPI clock slowed way downCorrect SPI instance & pinsNSS handled in softwarePower and ground verified at the sensorWhat’s odd:Works 100% on F446REFails consistently on H723ZG with the same transaction sequenceCan’t even read the DEVID register (0xE5)I’m starting to suspect something H7-spe

Hello everyone,Working on the STM32U5G9ZJT6Q on a custom board.On STM32CubeProgrammer (V2.20), I face an unexpected issue when trying to program my board.The ST-Link (official, V3PWR, power not used) simply cannot communicate anymore with the mcu with BOOT0=0 (tied with gnd). The stlink isn't broken as it still works on other custom boards.Error: Unable to get core IDError: No STM32 target found! [...]With the USB and PH3 BOOT0=1 (tied to Vdd), I can erase the chip and program it, however, when trying to run the program, the mcu resets and gets back into the idle usb waiting mode.Here is the current consumption diagram without running after programming (left) and with running after programming (right). The base reset pattern for reference is the 3rd image. The run seems to trigger the reset and put it back to idle/wait for device at the bootloader base address.It's worth noting that with BOOT0=1, stlink still doesn't work. I tried all possibilities to communicate with th

Hello,First, I would like to express my deepest gratitude for your assistance.I intend to update the firmware using STM32CubeProgrammer with the following hardware configuration Additionally, I have set the Boot0 pin to High using a jumper.However, my PC is not detecting DFU mode.Additionally, the programmer is not recognizing the USB connection. Did I miss anything? PS. The board has undergone a full chip erase.