Skip to main content
Visitor II
June 17, 2021
Question

STM32CubeProg: No STM32 target found on ST-LINK

  • June 17, 2021
  • 2 replies
  • 1299 views

I have a board (MCU: STM32H7B3LIH6Q) that I've been trying unsuccessfully to connect to using an external J-Link module, and recently I've switched to the internal ST-Link debugger. However, when I try to connect on STM32CubeProg for software reset, I get this output:

 16:55:24 : ST-LINK SN : 0035002E3438510534313939
 16:55:24 : ST-LINK FW : V3J8M3
 16:55:24 : Board : STM32H7B3I-DK
 16:55:24 : Voltage : 3.28V
 16:55:24 : No STM32 target found!
 16:55:24 : ST-LINK SN : 0035002E3438510534313939
 16:55:24 : ST-LINK FW : V3J8M3
 16:55:24 : Board : STM32H7B3I-DK
 16:55:24 : Voltage : 3.28V
 16:55:24 : Error: No STM32 target found!

For hardware reset, I get the following:

 16:54:40 : ST-LINK SN : 0035002E3438510534313939
 16:54:40 : ST-LINK FW : V3J8M3
 16:54:40 : Board : STM32H7B3I-DK
 16:54:40 : Voltage : 3.28V
 16:54:41 : ST-LINK error (DEV_CONNECT_ERR)
 16:54:41 : ST-LINK SN : 0035002E3438510534313939
 16:54:41 : ST-LINK FW : V3J8M3
 16:54:41 : Board : STM32H7B3I-DK
 16:54:41 : Voltage : 3.28V
 16:54:41 : Error: ST-LINK error (DEV_CONNECT_ERR)

    This topic has been closed for replies.

    2 replies

    ST Employee
    June 21, 2021

    Hi @FSkro.1​ ,

    Can you please try to connect under reset and tell me if it is Ok?

    0693W00000BbW1iQAF.png 

    Houda

    FSkro.1Author
    Visitor II
    June 22, 2021

    Under reset or in power down mode I get the following:

     09:06:08 : ST-LINK SN : 0035002E3438510534313939
     09:06:08 : ST-LINK FW : V3J7M2
     09:06:08 : Board : STM32H7B3I-DK
     09:06:08 : Voltage : 3.28V
     09:06:09 : ST-LINK error (DEV_CONNECT_ERR)
     09:06:09 : ST-LINK SN : 0035002E3438510534313939
     09:06:09 : ST-LINK FW : V3J7M2
     09:06:09 : Board : STM32H7B3I-DK
     09:06:09 : Voltage : 3.28V
     09:06:10 : Error: ST-LINK error (DEV_CONNECT_ERR)

    Visitor II
    June 22, 2021

    Hi

    I Have faced the same issue. Pull up boot pin of controller to 3.3v, reconnect your device with boot pin pull up. And try connecting to smt32cubeProgrammer.

    It worked for me.

    FSkro.1Author
    Visitor II
    June 22, 2021

    I've been trying booting up from flash and sys mem in alternation, but both produce the same output.