STM32 MCUs Boards and hardware tools

Hi all,I am designing a custom PCB using the STM32N657Z0 and am looking for some advice on how to treat some of the specialized pins that I don't plan on using. Specifically I have not been able to find any recommendations on how to treat any of the CSI pins if they are not in use. The closest I've found was https://community.st.com/t5/stm32-mcus-products/stm32n6-minimal-hardware-design/td-p/794094 which did inform me on what to do with my unused USB OTG pins for the most part. Would it be acceptable to ground all these pins with a shared external pull-down? This is what AN5967 would lead me to believe but I wasn't sure if these pins were grouped in with what was described in section 12.7. Appreciate any help, thanks!

Is there a detailed user manual available for the NUCLEO-U3C5ZI-Q?The product page links to a generic getting started document and a generic document on Nucleo 144 boards, but I can't see anything that lists the I/O or that documents the links.

Hello!I was working on a project of mine and put it on pause for a few weeks and now when I tried to connect the stlink to my PC its no longer detected. Its not showing up in the device manager and the stlink has dim red and green lights lit.Does this mean that it's somehow bricked? What could have caused it?I tried it on two of my computers and with 3 different cables. I am assuming it's a different problem from this one https://community.st.com/t5/stm32-mcus/how-to-solve-connection-errors-when-connecting-and-programming/tac-p/786977 .Thanks in advance!

Hello, I purchased an STLINK-V3PWR from Mouser. When I tried to use it, STM32CubeIDE 2.1.1 suggested updating the firmware. This failed, and the STLINK-V3PWR appears to be unusable (bricked). What can I do? Return the device for a refund/replacement? Or is there a way to re-flash the firmware using an STLINK-V3SET? If it is possible to restore the firmware by re-flashing it, where can I find the correct firmware? Kind regards, Jack.

Hello everyone! I'm new to the NUCLEO-H743ZI2 board. I need help with two questions: 1) I can't find a description of the STLK backup port -CN2 anywhere. Can you tell me if I can use it to program other STM32 devices on other boards, and how? 2) Can anyone share the schematic for the H743ZI2 board?  

Hello,I am currently experiencing some difficulties using the NUCLEO-N657X0-Q board.I am using STLinkUpgrade v3.17.10, and the device ID is correctly recognized as 003500244142501120353451, as shown in the attached image.However, when I click "Open in update mode," the PWR_STATUS LED on the Nucleo board turns off and the connection is dropped.I am not sure if this specific update is critical for operation, but I would greatly appreciate any guidance or help to resolve this issue.

Hi,for a project involving a custom educational flight controller, I need to use the following hardware:- steval-FCU001V2 board- steval-drone02 drone kitFor clarity, here are st product page links that i used.Manual:https://www.st.com/resource/en/user_manual/um3117-how-to-build-your-own-minidrone-with-the-stevaldrone02-and-stevalfcu001v2-stmicroelectronics.pdfSteval-drone02 Drone kit companion:https://www.st.com/en/evaluation-tools/steval-drone02.htmlSteval-FCU001V2 FCU board:https://www.st.com/en/evaluation-tools/steval-fcu001v2.htmlMy main issues are as follows: I can’t get it to fly with the factory-loaded firmware, and I can’t even reload the firmware.I followed the UM3117 manual to assemble the kit and perform the initial tests. Compared to the materials and manuals available for version V1 of the drone kit and the Steval FCU001V1, this one seems less comprehensive, and in some images the connections aren’t very clear.When I connected the motors according to the manual, I found th

Hi,I'm using STM32H755 Nucleo board and I'm evaluating ADC. I'm using 1.92MSPS per ADC sample rate for ADC1 and ADC2. I'm using A0 and A5 pins from CN9. I'm using ethernet to transfer data. My input to A0 (I channel) is 100kHz sine and A5 (Q channel) input is constant 1.6V. The problem is periodic noise around 320kHz.What might cause that and is it possible to get rid of that? I have read that it might be caused by ethernet connection. I would need ethernet in final application, so would need to solve the issue somehow. 

Trying to flash F1 and F0 series boards (not a clone, resoldered the MCU with a genuine from mouser) with L4 ST link V2.1, but having no success. Doing the basic CN2  headers out, CN3 VDD(with or without), SWCLK, GND, SWDIO. Spamming every option in CubeProgrammer to talk to the MCU with changing boot settings, doing resets before, while and after connecting, but nothing. L4 talks normally with the internal MCU. I measured MCU - STLink pin to pin resistances, everything seems ok with 22 ohm termination, the only problem i see is when connecting the 3.3V sense to the AIN_1 (CN3 1st pin), then i read in programmer 5.98V (VDD is not 5V, measured, stable 3.3V). In the schematic there is a voltage divider and when 3.3V ST_LINK is there, AIN is 1.65, which goes directly to MCU and shows in Programmer double of that. But by the same meaning, when connecting VDD i bypass with 3V (- schottky diode) and in the programmer get the double. Since its only sense voltage, it shouldnt be neccesary

I’m using the X-NUCLEO-LPM01A (PowerShield) and previously had firmware version 1.0.1, where I could connect via a serial terminal over USB and interact with the board using commands. But error occured short after, with LED 2 on the board indicating USB enumeration failure. Updating the STM32-LPM01-XN firmware version to the latest one (1.0.8) solved that issue but now no sign of connection via a COM port terminal. Everything works fine using via a graphical user interface using the STM32CubeMonitor-Power software tool. But would prefer controlling via COM terminal ... Thanks for the support

Hello guys, I would like to know if it is possible to directly connect  NUCLEO-F446RE board with  steval-mic003v1 mic array without any expansion board. Would love to know your feedback and much appreciated.

Hello everyone,I have followed the steps in this forum post (“Solved: Deploying a deep learning model on NUCLEO-H753ZI”) Solved: Deploying a deep learning model on NUCLEO-H753ZI - Page 2 - STMicroelectronics Communityto try X-CUBE-AI’s validate feature on the STM32N6570-DK board. Below is my workflow and the problem I encountered:1. BackgroundDevelopment Board & Firmware VersionsBoard: STM32N6570-DKX-CUBE-AI Version: 10.1.0ST Edge AI Core Version: 2.1.0Models That Have Validated SuccessfullyI first used the simple example model provided in that forum post, and validation completed with results.I then tested one of ST’s official STM32N6 AI-demo models; validation completed successfully and reported the expected accuracy metrics.New Model Under TestMy colleague provided a different, more complex model from the STM32 Model Zoo(The model file is attached at the end of this post.). All earlier steps—generate, compile, download to the board—worked fine. However, during the validation ste

New question moved from this post. Another question: which is the best way to proceed for the schematic design of a custom board with series G49 or H5? is it better to: - start from the datasheet of the MCU, - or from some applications notes like this https://www.st.com/content/ccc/resource/technical/document/application_note/76/f9/c8/10/8a/33/4b/f0/DM00115714.pdf/files/DM00115714.pdf/jcr:content/translations/en.DM00115714.pdf - or the reference schematic of the NUCLEO - or the CUBMX configurator (but all the connections for power, crystal are not specified here) - or other resources are more indicated for easy design setup?   thanks again

I'm using a  * STM32N6-DK * Brightsense VD56G3 I've made 2 camera drivers so far and the only difference i can see from the cameras is that my first camera module has MIPI short packets start and stop.  I'm making this observation from the scope.  So i know it's sending the data it's just receiving black messages.     Question * Do you need short packets frame start and end for it to grab images.      Other info * I'm using Zephyr, but i just want to make sure from the hardware i don't need short packets because i don't think VD56G3 can generate short packets.     

Dear STMicroelectronics Support Team,   I am working with two ST-LINK/V2 debuggers and have observed a difference in the VTref (VAPP) signal location on the 20-pin connector. I would like to understand whether this is expected behavior.   Details of the debuggers: 1. ST-LINK/V2 marked: B2025 162. ST-LINK/V2 marked: A2017 10   Used board to flash : BLUENRG-M2SP Used flasher tool : RF-Flasher utility v4.5.0   Observation: * In the B2025 16 debugger, the target voltage (~3.3 V) is measured on Pin 1 of the 20-pin connector.* In the A2017 10 debugger, the target voltage (~3.3 V) is measured on Pin 19 of the 20-pin connector.   Both debuggers are being used under similar conditions with the same target hardware.   Could you please clarify:   1. Whether such variation in VTref (VAPP) pin location is expected across different ST-LINK/V2 units?2. If there are any known hardware variations or revisions related to this behavior?3. Any guidance to ensure cor

Hello all, I want to connect a 3.3 V I2C based keypad with STM32U5G9J-DK1 via a carrier board on which the STM32 board sits via expansion connectors CN9 and CN10 present on it. I am using pins PG13, PG14, and PG9 for my I2C SDA, I2C SCL, and INTERRUPT, which are available as Pin No. 4, 2, and 8 respectively on CN10. The signals pass through a level shifter (TXS0104VDR) on the carrier board for conversion between 1.8 V signals at the STM32 end and 3.3 V signals at the keypad end. These lines are also connected with external pull up resistors as indicated in images attached. All the capacitors between the signal lines and GND have been unmounted. Also, 0 Ohm resistors (R27, R28, and R29 have been unmounted). During operation, STM32 can't detect any I2C device connected whereas the keypad seems to work perfectly when used in a different setup. Upon further investigation, it appears that all the three pins have become unresponsive, even when the board is used standalone, disengaged from th

Dear people,   I use these little square pins and headers (see image), to obtain access to the contacts of CN11 / CN12 of Nucleo Boards, e.g. H723ZG, or F756ZG?. However these are impractical, because movement or vibration might lead to interruptions. And I want to avoid soldering, for specific reasons. Ideally would be some sort of connector that makes good electrical contact and can be coupled/decoupled easily. Can someone suggest an efficient and ergonomic solution?   Thank you  

Dear all,I'm unable to connect via SWD to my STM32F103C8T6. What ever I try I get no target found with STM32CubeProgrammer or ST-LINK Utility (I have tried all combinations at slow and high speeds). - device is virgin- BOOT0 is low- NRST unconnected (shows 3V3) and connected/removed while testing- Connections go through from ST-Link to STM32 pins- 30 Ohm and 0 Ohm tested for SWCLK and SWDIO (GND and 3V3 connection to ST-Link with no resistor)- Correct mapping of ST-LINK pins to STM32 checked multiple times- There are no obvious shorts between any of the paths- 3V3 is stable and GND closed- The ST-Link was tested with a "blue pill" board with the same STM32 on it and it worked flawlessly I have also tried:- Cutting the path to the esternal 16MHz crystal curcuit- Connecting/Disconnecting VCC- Soldered a new STM32 onto the board I am currently running out of ideas, I think there is either a fault in the PCB design that damages the MCU or prevents booting or maybe some confi

  Hello everyone, I’m facing an issue while trying to debug my project custom_for_stm32f103c8t6 in STM32CubeIDE. When I launch the debug session, I get the following error message: Error in final launch sequence:Failed to start GDB server What I’ve tried so far: Installed ST-LINK driver (STSW-LINK009). Changed USB cable and port. Reset the STM32F103C8T6 board. Interestingly, I can still flash the firmware successfully using STM32CubeProgrammer, but debugging through STM32CubeIDE fails with the error above. Unfortunately, the error still persists. Has anyone encountered this problem before and found a solution? Any guidance would be greatly appreciated. Thank you in advance!    

Hi, I tried to configure the USB Host for a project, but it’s difficult to configure, and I am not finding any online support available for the STM32H5 series controller. My requirement: I configured PB4 as an output, which is connected to a green LED. Whenever I plug the USB into my controller, the green light turns on, and whenever I remove the USB from the controller, the green light turns off. I’ve tried some methods, but they are not working. Can anyone please help me?      

I have a NUCLEO-F103RB (MB1136 rev C05). My goal is to remove the ST-LINK and power via a hat supplying 3.3v. For the 3.3v I have: Moved JP5 to pins 2-3. Checked JP1 is removed. Removed SB2 zero ohm resistor. Removed SB12 zero ohm resistor. Verified my shield is putting out a good 3.3v which is attached to connector CN7 pin 16. For the HSE I have: Removed SB54 and SB55. Soldered zero ohm resistors to R35 and R37. Soldered 20pf capacitors to C33 and C34. Removed SB16. Removed SB50. Added 8Mhz 16pf crystal X3. The ST-LINK is still physically attached at the moment, but I do plan to cut it off once things are working. The board comes up and accepts programming and works in the debugger. Stepping through the initialization it gets to where the HSE is set up and then sits in an infinite loop waiting for the HSE to come ready. I tried replacing the crystal X3 just in case I got a bad one but there was no change in behavior. The clock config is unchanged, other than setting HSE to "crysta

Hello, I’m having a problem with a board I’m developing based on the STM32H747BIT6. The issue is related to SPI communication. When I connect any device to the SPI bus, the signal level drops from 3.3 V to around 1.5 V. I have tested different SPI peripherals, but they all show the same behavior. Could this be related to the drive strength or power capability of a specific pin?

Hi all, I have a small issue with the STM32N6570-DK board and the VENC_SDCard example code. The PN12 pin has a voltage of 0V (card inserted) or 1.80V (no card inserted); on the MCU side, the GPION data register (IDR) always shows a logic 0 in both situations. The VENC_SDCard / VENC_SDCard_ThreadX example code basically jumps over SD Card detection as it assumes a logic level of 0 == card present. If there is no card, mounting fails and aborts further processing. I have the requirement to react to card inserts / removals, so I'd like to trigger an interrupt or at least be able to read a logic high once in a while but could not find out what exactly is missing in the code. * I tested with an empty CubeMX project and set this PN12 to input; here I do see logic level changes.   * I susptected the VDDIO voltage domains to be at 3V3 for that block and manually switched VDDIO_SD to be at 1V8, but that did not show a change as well * I did not fiddle with security bit settings... may

Hello ST Community,My name is Gorakhnath. I am currently pursuing M.Tech (Power Electronics and Drives) at NIT Kurukshetra. I am using the STM32F4DISCOVERY (STM32F407VGT) board and I need stable DAC outputs for my hardware application.What I need (requirement)When the DAC command is 0 V, I need the output to be as close as possible to true 0.0000 V, because my external circuit maps:0 V → 0 A3 V → 50 AEven a small voltage like 0.045–0.05 V produces unwanted current (~0.5 A) in my system.Issue / ObservationOn both DAC pins:PA4 (DAC_OUT1)PA5 (DAC_OUT2)I measure about:~0.05 V (sometimes ~0.045 V) when the command is 0 VThis happens even when I am not sending any command from LabVIEW, or when I send 0,0.What I tried (software checks)Set DAC values to 0 using HAL on both channels:HAL_DAC_SetValue(..., 0) for DAC channel 1 and channel 2Forced PA4/PA5 to GPIO output LOW when command is 0 V:Configured PA4/PA5 as GPIO_MODE_OUTPUT_PP and wrote&nbs

Hello,I got a radio MCU which connects to cloud and can receive binaries from database. And I got a STM32 that controls some stuff, including other MCUs. In production this means a lot of headers and programming time for all of them, no way to update remotely, and even if the code is thoroughly tested - glitches are still possible.So I want to connect things in a chain, so that if something apart from the radio crashes - radio MCU could re-flash the whole system. This of course could be done with UART when using bootloaders, but this again means you have to pre-program bootloaders on MCUs, and there's still a very slim chance it might fail.So I need an example of how one MCU can flash another via JTAG or SWD (preferably), and then verify the result. From there I could get it to work on Arduino / STM / AVR / radio ARM. What I really want is a proof of concept simple test example to show it works with the peripheral (bit banging is always possible, but surely there is a smarter way to do