Skip to main content
Visitor II
May 28, 2020
Solved

Error with ST-LINK USB debugger and custom board

  • May 28, 2020
  • 1 reply
  • 956 views

Hello,

i created a custom board which foundamental schematic is like the images:

0693W000001pf1BQAQ.png0693W000001pf1GQAQ.png

I'm using the classic ST-LINK USB Debugger but i can't debut nor upload my code inside my STM32F767IGT MCU, both with STM32CubeIDE and STM32 ST-Link UTILITY.

In the utility the error was

19:34:31 : Can not connect to target!
 Please select "Connect Under Reset" mode from Target->Settings menu and try again.
 If you're trying to connect to a low frequency application , please select a lower SWD Frequency mode from Target->Settings menu.
19:34:32 : No target connected

or

19:33:54 : Can not connect to target!
 If you're trying to connect to an STM32W1xx device, please select Normal or HotPlug mode from Target->Settings menu.
 If you're trying to connect to a low frequency application , please select a lower SWD Frequency mode from Target->Settings menu.
19:33:55 : No target connected

while in STM32CubeIDE

Error in initializing ST-LINK device.
Reason: Unknown. Please check power and cabling to target.

or

Error in initializing ST-LINK device.
Reason: ST-LINK: 51FF6B064883535241202187 not found.

or

Error in initializing ST-LINK device.
Reason: No device found on target.

What should i do to keep my custom board work?

    This topic has been closed for replies.
    Best answer by Tesla DeLorean

    Typically each should be individually wired to own capacitor. Expect 1.2V on these pins

    Definitely not connected to VCC

    1 reply

    Super User
    May 28, 2020

    VCAP_1 and VCAP_2 should not be connected to VCC. Even if you fix this, the chip may be dead since the voltage on those pins is normally around 1.2V.

    Graduate II
    May 28, 2020

    Typically each should be individually wired to own capacitor. Expect 1.2V on these pins

    Definitely not connected to VCC

    AMerc.4Author
    Visitor II
    May 29, 2020

    Perfect, it works now! Thank you!