cancel
Showing results for 
Search instead for 
Did you mean: 

Destroy the MCU and ST-Link v3

RTaka.3
Associate II

I destroyed the MCU(STM32H743ZIT6) and ST-Link V3.

But I don't know what happen.

When I connect the ST-LinkV3 with the Laptop, then the ST-Link and MCU was broken.

So, if you know what happen, please teach for me.

14 REPLIES 14
MGatt.2
Associate II

The same thing happened to me too.

With an STM32H735-DK. One day, I turn on it but it didn't run. The integrated ST-Link V3 seems to work correctly (I can connect it to the PC) but the STM32H735 does work: it not run and I cannot program it. The day before everything was working fine !!!! I didn't understand what could have happened.

RTaka.3
Associate II

Thank you for reply!

I resolve this problem.

This problem is made by some causes, I found these causes.

Uwe Bonnes
Principal III

It is very very rare that breackage happens out of the blue. In most cases something happened, e.g.:

  • ESD discharge
  • Voltage differences in ground on PC USB connection and external board
  • External voltages outside the absolute maximum ratings applied to the board
  • USB cable breackage
  • Bad USB cable, having only power but no communication
  • ...

So carefully think about what you did since you last handled the board. Is the Stlink still recognized? Is the board still powered(green led) ? ...

Otherwise, when y

It might be helpful for others in the future if you share what caused your issue.

Embedded UI/UX Consulting: cadenza.design

Takes some skillz

At the places I've worked there's usually a guy with the Technology Kiss of Death, who can break pretty much any hardware or software if left alone with it even briefly..

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

The H7 can be bricked by incorrect LDO/SMPS and VOS settings.

The NRST is not a true reset in the classic sense.

One of the tricks to un-brick the H7 is to pull BOOT0 HIGH, and then cycle the power completely a couple of times, ie fully disconnect and reconnect the USB/Power from the device. Then connected and erase with BOOT0 still HIGH, stopping broken code on the device from running

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

I think so too.

This is embarrassing, but I can't speak English​ well.

So, I can't speak well about the detail.

Its cause, short circuit between the ST-Link and MCU through the​ electrical outlet.

So, it isn't concern about ST.

I'm so sorry.

And thank you for any reply.​

​

Hi.

For me, the USB cable is ok because with other board it works correctly.

The power source is the USB

The LD5 and LD6 are ON

With ST-Link Upgrade Utilities I can connected to ST-LINK V3 (inside on the board STM32H735-DK) and upgrade it to last version (V3.J7.M2); but when with STM32CubeProgrammer the message "Error: NO STM32 target found!" will be displayed.

The display backlight is on (also when I press the RST button).

If I try press "Run Target" from TouchGFX, I read the following messages:

ST-LINK SN : 001C003F3438510534313939

    ST-LINK FW : V3J7M2

    Board    : STM32H735G-DK

    Voltage   : 3.29V

    Error: No STM32 target found!

    c:/works/ST/ConfIndustries_0/gcc/include/flash_sections_int_ext.mk:2: recipe for target '_extflash_' failed

    make[1]: *** [_extflash_] Error 1

    ../gcc/Makefile:52: recipe for target 'flash' failed

With STM32CubeIDE I read the messages:

STMicroelectronics ST-LINK GDB server. Version 5.8.0

Copyright (c) 2020, STMicroelectronics. All rights reserved.

Starting server with the following options:

    Persistent Mode      : Disabled

    Logging Level       : 1

    Listen Port Number     : 61234

    Status Refresh Delay    : 15s

    Verbose Mode        : Disabled

    SWD Debug         : Enabled

    InitWhile         : Enabled

Target no device found

Error in initializing ST-LINK device.

Reason: No device found on target.

Thanks.

Please check that JP7 is in position 1-2.

+ Try to connect under reset.