2026-05-26 11:02 AM - last edited on 2026-06-05 3:08 AM by KDJEM.1
Hi everyone,
I am facing an issue with my STM32F429I-DISC1 board.
The board automatically resets after around 20–30 seconds and continuous debugging is not possible because debugger disconnects. STM32CubeProgrammer also cannot maintain stable connection for long time.
I tried flashing different simple codes (including LED blink), but same behavior is observed.
I also tried powering the board using external 5V and GND. In that condition, MCU seems to work as expected, but COM LED (LED1 red) continuously blinks and LED2 stays ON.
Can anyone suggest whether this indicates power section issue, ST-Link issue, or MCU damage?
Thanks.
2026-05-26 11:19 AM
welcome to the forum
Please see How to write your question to maximize your chances to find a solution for best results.
@BlueB_Ashutosh wrote:The board automatically resets after around 20–30 seconds and continuous debugging is not possible because debugger disconnects. .
How do you know, specifically, that it resets ?
I presume this is when powered via the CN1 ST-Link connector?
Does the USB connection drop?
Have you measured at the STM32 3V supply - is it stable?
Is this a new board, or one that's been previously enjoyed by you and/or others?
2026-05-26 8:39 PM
2026-05-31 8:26 PM
Hi, is there any update on this? I am still waiting for your response.
2026-05-31 11:01 PM
This update would have to come from you.
There is no know issue with this Discovery board in general, and only you have the board that exhibits this problems.
In addition to checking the power supply, make sure no watchdog is enabled in the code.
And third, try another USB port and/or another PC.
2026-06-01 2:28 AM
@Ozone wrote:This update would have to come from you.
Absolutely.
@BlueB_Ashutosh We have no access to your hardware, or your software; we know nothing about you or your setup other than what you post here.
Some good, clear photos would help.
What debugging/tests/investigations have you done to find what's going on?
Try to produce a minimum but complete example which illustrates the issue.
@Ozone wrote:try another USB port and/or another PC.
@BlueB_Ashutosh more things to try here:
including with/without hubs, docking stations, etc.
We’re moving the ST Community to a new platform to give you a better and more reliable community experience.