STM32 MCUs Boards and hardware tools

Hello Team,I am using the STM32N657x0-Q Nucleo board with the STEVAL-66GYMAI1 (VD66GY) camera board connected via FFC. Both CN8 and CN10 are connected to the PC, and I am viewing the camera stream through UVC.I tested the official precompiled HEX files from: X-CUBE-N6 Camera Capture STM32N6 Getting Started Object Detection In all cases, the image is heavily blurred. Objects appear relatively clear only at approximately 1–2 cm from the lens, while anything beyond that distance becomes significantly out of focus.I attempted to adjust the M12 lens focus across its full rotation range, but no noticeable improvement was observed. The same behavior occurs with multiple example projects and unmodified hardware.Could you please advise which of the following areas is most relevant to investigate? Camera board compatibility with STM32N657x0-Q Sensor/lens configuration in the example firmware Lens focus or alignment issue Defective lens or hardware issue Recommended reference project/co

Hi, I cannot manage to receive the bytes on UART protocol on an STM32U0 when using the STLINK-V3MINIE.The RX works properly (I can send data to the PC), so the pins are not swapped. The Vref of STLINK is 3V3, and the STLINK measures it correctly. Moreover, I can successfully program the U0 using the STLINK so I think both devices are in good shape.The UART baud rate is 115200 b/s. I have attached an oscilloscope to observe the signal. When NOT connected to the MCU, the TX signal is clear as expected (0V as low and 3V3 as high). If I connect it the MCU, the signal is still very clear and sharp but reduced (the "low" level is about 1.65V and the high level is 3V3). The schematic is the most straightforward: no components between the STLINK and the MCU.The firmware on STLINK is the V3J17M10.Currently, I have solved it using another USB-serial converter (CP2102) and it works flawlessly in both directions, using interrupts, DMA and whatever firmware tricks, but I would unders

Is there a standard list of SB's? I cannot for the life of me figure out the SB's on the STM32F723E-DISCO, and none of the manuals mention anything about them other than if open is on or off. I am specifically trying to use the debugger for my custom PCB based off the same MCU. Any help would be greatly appreciated!

Hello ST team,we are trying to evaluate the simple GPIO pinouts on STM32N6 Nucelo & in our custom board,we noticed that Port P & O pinouts are not functioning as expected. we just configured as simple GPIO output and tested the pin state always low. other GPIO ports look normal, but we will come to know when we do the complete testing. We've cross checked this Port P &O functionality in the Nucleo EVK as well in custom board, but No luck, it is not working in both, could you please suggest, is there any special configurations required to make port P& O functional?Regards,Madhu S

I'm debugging an STM32N647 on a custom board and running into a strange issue: the target silently drops the debug connection every time a breakpoint is hit or a single-step lands inside HAL_Delay(). Environment - MCU: STM32N647X0HXQ (Cortex-M55) - Debugger: ST-Link V2 - Debug mode: LRUN (code in AXI SRAM 0x34000000, running with XSPI/Flash boot) - Toolchain: VSCode + Cortex-Debug + ST-Link GDB Server - SWD freq: tried 400 kHz / 1 MHz / 4 MHz — same result - D-Cache: disabled (SCB_DisableDCache()) - Optimization: -O0 Symptoms 1. Download & run works fine — the firmware executes normally. 2. Setting a breakpoint → when the breakpoint hits, VSCode shows "Target disconnected" / "Lost debug connection". 3. Single-stepping into HAL_Delay() causes the same disconnect. 4. Reset via ST-Link sometimes recovers, sometimes requires power cycle. What I've checked / tried - Power supply is stable (measured with scope). - BOOT0/BOOT1 jumpers are correct for LRUN mode. - Tried lowering SWD freque

Moved from MPUs forum.Hello,I have made a custom PCB with a STM32F756 and I'm trying to program this MPU through STlink. My main workstation runs Linux and I use stlink tools.To flash this MPU, I have connected ST-Linkv2 to my PCB (NRST, SWCLK, SWDIO, SWO, GND) and I can obtain a answer from MPU:hilbert:[~/zephyros/zephyr/samples/basic/blinky/src] > st-info --probe Found 1 stlink programmers version: V2J29S7 serial: 49FF69065050825521491967 flash: 1048576 (pagesize: 2048) sram: 327680 chipid: 0x449 dev-type: STM32F74x_F75x But I unable to flash a test program... I have tested with standard user or root.hilbert:[/usr/local/bin] > ./st-flash --debug --connect-under-reset write ~/cvs/firmware-europulse/build/zephyr/zephyr.bin 0x08000000 st-flash 1.8.0-121-g8c34a4e 2026-05-22T15:44:31 DEBUG common.c: *** looking up stlink version *** 2026-05-22T15:44:31 DEBUG common.c: st vid = 0x0483 (expect 0x0483) 2026-05-22T15:44:31 DEBUG common.c: stlink pid = 0x3748 2026-05-22T15:44:

Hi all,Hardware: Custom PCB, STM32H563ZGT6, USB powered.It was working fine but now gives me :Error: Cannot connect to access port 1!If you are trying to connect to a device with TrustZone enabled please try to connect with HotPlug mode. If you are trying to connect to a device which supports Debug Authentication with certificate or password, please open your device using it.Symptoms:- MCU gets hot to the touch within ~5–10 s of USB connect; cools instantly on unplug- VDD measures 3.29 V at the MCU pin- Chip is still functional: enumerates as STM32 Bootloader in DFU, ST-Link HotPlug connect succeeds, full erase + program + verify works- "Connect Under Reset" / normal connect frequently fails with Cannot connect to access port 1 or DEV_TARGET_NOT_HALTEDAlready tried:- Full chip erase via HotPlug → heat persists with empty flash- BOOT0 tied to VCC to force system memory bootloaderCan someone please assist me in resolving this issue?Thank You. 

Hi everyone. I have a problem with my U5A5ZJ-Q core board. The mounted microcontroller is STM32U5A5ZJT6QU. The project is to drive a QUECTEL em05 LTE modem. I need to configure the USB port exposed by PA11 and PA12 in Host mode. I am using the standard Host libraries in Middlewares and also the files in the USB_Host folder. I am trying to configure everything without success. I can't find exact written procedures to do this. Has anyone had problems? Has anyone tried? The problem is with the initialization of the USB Host port. It remains in reset mode and the CSRST bit never returns to 0. Below is a portion of the serial log that I printed on the monitor. " [CLK] Enabling HSI48...<CR><LF>[CLK] HSI48 RDY=1<CR><LF>[CLK] CLK48 <- HSI48 (via __HAL_RCC_CLK48_CONFIG)<CR><LF>[USBH] Init...<CR><LF>[LL] USBH_LL_Init (FS)<CR><LF>[HCD] Enter HAL_HCD_Init<CR><LF>[MSP] AFRH(GPIOA)=0x000AA770 AF_PA11=10 AF_PA12=10<CR>&l

Hi everyone, I'm facing issues connecting an external debugger to the NUCLEO-H7S3L8 board (STM32H7S3L8). Current Setup: Board powered via CN5 (ST-LINK USB) JP1 closed (to disable on-board ST-LINK) External debugger connected to CN1 (MIPI20 connector) SWD mode at low speed (500 kHz to 1 MHz) Correct power sequence: Power CN5 first → wait for COM LED (LD8) to stabilize → then connect external probe What I have already tried: BOOT0 = 1 (jumper on CN11[5-7]) to enter bootloader mode and halt using external debugger Internal ST-LINK works fine when JP1 is open (using STM32CubeProgrammer) Problem: The external debugger is unable to connect or halt the CPU, please guide me how to fix it. Thanks,regards,Surender.

ST moderator: updated the title to be more concise according to the below exchanges. Hello All,   I am facing a problem for debugging one of the board which uses stm32h7 controller. I am not sure why this is happening but on other board I am able to debug it, but for first one its not working. Though the code and debug config settings are same for both the board and using same system to debug both, but on one board I am able to debug while on other its is not. so could you please tell me what I can try to resolve this issue.   Thanks, SD 

Dear STMicroelectronics Community / Support Team,I hope you are doing well.I am currently working with the STM32N6 Discovery Kit and noticed that it uses an external Octal NOR flash device with the part number MX66UW1G45G. However, I have been unable to locate a public datasheet for this exact component.I was able to find datasheets for similar parts such as MX66U1G45G and MX66UM1G45G, but not for the “UW” variant used on the board. This has led to some confusion regarding the exact specifications, supported features, and command set of the device.I would appreciate your guidance on the following points:Is MX66UW1G45G a custom or internal part number used specifically for STM32 evaluation boards?Is there a publicly available datasheet for this device, or can it be shared upon request?Can MX66UM1G45G (or another publicly documented part) be considered a fully compatible equivalent for development purposes?Are there any specific differences (e.g., command set, timing, interface behavior)

Subject edited to mention ARM64 - p.a. Hi everyone, I am having trouble getting my STM32 NUCLEO - F411RE setup. When I attempt to run a simple program through CubeIDE I am met with "NO ST-LINK detected! Please connect ST-LINK and restart the debug session." It also returns the same error when I attempt to run other programs.Here's what I have tried thus far :      - In my Device Manager I can see "ST-Link Debug" which has the status: "The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device. To find a driver for this device, click Update Driver." I've tried both the "search automatically for drivers" and "Browse my computer for drivers" (using C:\Users\jthom\OneDrive\Desktop\stsw-link009\amd64), however both have thus far failed.     - Restarted computer multiple times      - I've installed CubeProgrammer however when I attempt to connect ST-LINK through there I am met with: "Err

Hi! I'm using a STM32N657 Nucleo Board, and, considering the 1.8 V reference voltage for the ADC, the value returned by the ADC is half of what it should be. For example, for a 1,410 V value in the pin, the reading is 1742. Here is the initialization for reference: static void MX_ADC2_Init(void) { /* USER CODE BEGIN ADC2_Init 0 */ /* USER CODE END ADC2_Init 0 */ ADC_ChannelConfTypeDef sConfig = {0}; ADC_AnalogWDGConfTypeDef AnalogWDGConfig = {0}; /* USER CODE BEGIN ADC2_Init 1 */ /* USER CODE END ADC2_Init 1 */ /** Common config */ hadc2.Instance = ADC2; hadc2.Init.Resolution = ADC_RESOLUTION_12B; hadc2.Init.GainCompensation = 0; hadc2.Init.ScanConvMode = ADC_SCAN_DISABLE; hadc2.Init.EOCSelection = ADC_EOC_SINGLE_CONV; hadc2.Init.LowPowerAutoWait = DISABLE; hadc2.Init.ContinuousConvMode = DISABLE; hadc2.Init.NbrOfConversion = 1; hadc2.Init.DiscontinuousConvMode = DISABLE; hadc2.Init.ExternalTrigConv = ADC_SOFTWARE_START; hadc2.Init.ExternalTrigConvEdge

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.

Hi everyone, I’m designing my first custom PCB for an underwater ROV project  (Leak Detection + ESC Control + Jetson Interface) and I would really appreciate feedback before moving closer to manufacturing. A few months ago I shared the schematic review here, and after applying suggestions I completed the PCB routing stage.Now I would like to ask for a review of the PCB layout itself, especially regarding signal integrity, grounding, routing quality, and overall reliability. The board is designed around an STM32G431CB and acts as a sensor/control board communicating with a Jetson Orin Nano and a separate Power Distribution Board (PDB). Main Functions Reading 4 leak sensors Generating ESC PWM outputs Communicating with Jetson Orin Nano Processing leak sensor states and sending a digital LEAK_FAULT signal to the PDB Interfacing with: BNO08X IMU D300 depth sensor ESCs Leak sensors Board Layout Overview Bottom side: 4 leak sensor connectors Left and right sides: ESC connector

I recently bought a STM32F446 64 pin chip and wired it up. The following circuit is made: I've installed 0.1uF capacitors between two power pins, and two I've not (It's difficult to do so)   it's consuming around 20 to 30 mA Pin 30 shows 1.132 volts (4.7uF cap is installed) voltage 3.298 v oscillator is working fine I tried bypassing the 15uH inductor as I thought that is too much, but neither way works The chip is perfectly soldered, checked for resistances multiple times   Tried uploading code from both usb to ttl converter and STM programmer from Nucleo f072rb board   all the wiring is correct according to me checked multiple times, but when I upload the code using arduino ide, I get this issue: Sketch uses 16576 bytes (3%) of program storage space. Maximum is 524288 bytes.Global variables use 1212 bytes (0%) of dynamic memory, leaving 129860 bytes for local variables. Maximum is 131072 bytes.NODE_F446RE not found. Please ensure the device is correctly connected.Faile

Hello, I am designing a USB-C power sink using the TCPP01-M12 and STM32G071CBT6 (UCPD peripheral). The connector is a Molex 2171790001 receptacle. I have two separate issues and would appreciate guidance on both. --- ISSUE 1: No power at all with Type-C to Type-C cable When I connect a USB-C to USB-C cable between my board and a USB-C charger, the board does not power on. However, when I use a Type-A to Type-C cable (from a USB-A charger), the board powers up fine. Hardware setup:- J1: Molex 2171790001 (CC1 on A5, CC2 on B5 — both routed)- IC1: TCPP01-M12 (CC1C and CC2C connected to J1; CC1 and CC2 connected to STM32 PA8/PB15)- IC2: STM32G071CBT6 (UCPD1_CC1 = PA8, UCPD1_CC2 = PB15)- TCPP01 VCC (pin 12) is driven by STM32 PB12 GPIO (TCPP01_PWR net)- TCPP01 DB/ (pin 10) is connected to STM32 PB11 GPIO- C1 and C2 (330 pF each) are now soldered on CC1c and CC2c lines to GND- R8 and R9 (0 Ω, intended to connect UCPD_DBCC1/PA9 and UCPD_DBCC2/PA10 to GND) are NOT yet soldered — so DBCC1 and D

Hi! I am working on a design that uses an SD card and an STM32U5 MCU. In trying to educate myself more thoroughly about SDIO bus design, I've come across LVS (low voltage signaling), which is part of the UHS-I spec and required for reaching SD speeds above 25MB/s. I've not designed for this before, and an interested in examples that demonstrate the level-shifting part of this. I'd be particularly interested in solutions that allow the MCU to run at 3.3V, rather than 1.8V, though it's possible that this is an unusual thing to want (I'm still fairly ignorant about this...but keen to learn!)I'm wondering, then, if there are any ST eval boards that demonstrate this in any form? I found this forum post that suggests a few solutions, but most rely on the MCU being run at 1.8V. (I am further aware of the notion that some MCU's have a VDDIO domain that allows the MCU to run at 3.3V but allow some peripheral to be run at a different/lower voltage. Unfortunately the U5 series uses this

I have a Nucleo-WL33CC1 board which has been working fine, but after starting to work on a DEEP SLEEP implementation I can not connect any longer using SWD neither through Crossworks IDE nor CubeProgrammer. Any possibility to unbrick the board?

I have used a Micro USB cable and it doesn't insert. Help

Hi,   I wanted to set up time keeping on my Discovery board for testing something. I see the following in the documentation for the larger STM32F769-EVAL:   https://github.com/STMicroelectronics/STM32CubeF7/blob/master/Projects/STM32F769I_EVAL/Examples/RTC/RTC_InternalTimeStamp/readme.txt   - This example runs on STM32F779xx/STM32F777xx/STM32F767xx/STM32F769xx Devices.- This example has been tested with STMicroelectronics STM32F769I-EVALboard and can be easily tailored to any other supported device and development board. - STM32F769I-EVAL Set-up- Make sure that JP15 is in position 2-3 to connect 3V battery to VBAT pin.   At first I didn't know -EVAL and -DISCO are two different things and kept searching through the manual for the -DISCO where JP15 seems to have a different role. But the first line from the docs makes me think there has to be an RTC on the -DISCO board. I take it I need to put a 3.3V battery somewhere. In the diagram I see a number of 3.3V conne

Title edited to reflect that this relates specifically to the NUCLEO-G070RB board.NUCLEO-G070RB in this board  ADC channel 0,1 working ,other ADC channel not working is they any reason?

Dear ST Technical Support Team,I am writing to request technical assistance regarding a recurring hardware failure with the STM32H743IIT6 MCU on my custom-designed PCB.Problem Description:After initial assembly, the MCU is correctly recognized by STM32CubeProgrammer and STM32CubeIDE via the ST-LINK (Serial Wire mode). I can successfully flash the firmware and debug the device for a limited number of cycles (typically 2 to 5 times). However, the MCU eventually enters a state where:It is no longer recognized by any programming tool ("No STM32 target found").The chip begins to draw excessive current (overheating rapidly).The hardware suffers permanent damage (internal short-circuit).Firmware Configuration:Debug Hardware: Serial Wire (SWD).Timebase Source: SysTick.Clock Configuration: Configured via STM32CubeIDE (no errors reported in the clock tree).Operating Voltage: 3.3V stable.Technical Concerns:I have verified the schematic, but the repeated physical failure suggests an internal latch

Hello all! I need some rubber ducking help here. I have got hold of a B-U585I-IOT02A dev board, where I'm trying to get learn and get to know the STM32 family. I have got a lot of things working, but the ADC1 is giving me a hard time: Here is my MX config: IN1 enabled, and expecting the data to be stored in the DR register. PC0 is selected as ADC1_IN1: Global interrupts are enabled: So far, so good( I think ). my application code: /* Running in my main while(1) loop */ // Other stuff before here if (StartConv) { if (HAL_ADC_Start_IT(&hadc1) != HAL_OK) { /* Start Conversation Error */ Error_Handler(); } StartConv = 0; } HAL_Delay(10); And when above is executed, I can see that I'm getting a interrupt and call to my own ConversionCallback function: void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* AdcHandle) { /* Get the converted value of regular channel */ adc_raw = HAL_ADC_GetValue(AdcHandle); printf("ADC Raw Value: %lu\r\n", adc_raw); // Retrigger convertion