Skip to main content
DCont.1
Associate III
September 20, 2021
Question

ST-LINK/V2 Failed to detect STM32F446RC on custom board with pin headers shown in images.

Hi!

I am currently trying to connect the ST-LINK/V2 to my custom board which is using a STM32F446RC. I am able to detect the ST-LINK using both the STM32CubeIDE or the STM32 ST-LINK utility, however this is only displaying the serial number. but it is failing to detect the target (MCU).

I have added a picture of the header on the custom board and the header am using for guidance.

Am not sure whether to use the JTAG connections or the SWD connection guidelines.

This topic has been closed for replies.

12 replies

Tesla DeLorean
Guru
September 20, 2021

Seems like your pin numbering is completely rotated vs ARM 10-pin

Just use the SWD connections, the ST-LINK expects 3.3V on Pin 1 or 2 of their header

GND, VCC, SWDIO/TMS, SWCLK/TCLK minimum

NRST allows for connect under reset

SWO/TDO allows for debug channel

Check orientation of your STM32

Make sure VDDA is powered

Check voltage/caps of VCAP pins, should see 1.25 V or about

Check level on NRST, should be high

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
DCont.1
DCont.1Author
Associate III
September 20, 2021

@Community member​ Thank you for replying. So I tried connecting it using the SWD connections. I have attached a picture of the table I used for connection. the SWO pin would be PB3 on the custom board header. Everything else maps the same. I still receive a fail connection.

DCont.1
DCont.1Author
Associate III
September 20, 2021

Using the STM32CubeIDE I change the debugger configuration to openOCD just for the sake of getting some output, the error I receive on the console is the following:

Error: target voltage may be too low for reliable debugging

Error: init mode failed (unable to connect to the target)

Using GDB server I get:

Error in initializing ST-LINK device.

Reason: No device found on target.

The BOOT0 and BOOT1 are both hard-wired to GND on the custom board

DCont.1
DCont.1Author
Associate III
September 20, 2021

The reading on the VCAP is about 4.2 mV

TDK
September 21, 2021

Recheck connections. If it's not detecting the target voltage is 3.3V, something is off. BOOTx connection doesn't matter for debugging, unless your program reassigns SWD pins.

Try STM32CubeProgrammer.

"If you feel a post has answered your question, please click ""Accept as Solution""."
DCont.1
DCont.1Author
Associate III
September 21, 2021

Thank you @Community member​ and @TDK​ I will go ahead and probe the SWD and SWCLK. I will post schematics along with the results from the probing.

DCont.1
DCont.1Author
Associate III
September 21, 2021

@TDK​ and @Community member​  using the ST-LINK Utility tool I get the follow error message when set to openOCD:

Info : Target voltage: 0.001567

Error: target voltage may be too low for reliable debugging

The voltage varies but it is usually below 1 V

Tesla DeLorean
Guru
September 21, 2021

Suggests you're not connecting the target VCC to pin 1 or 2 of the ST-LINK JTAG header, or your device isn't powered. Orange Dot is Pin 1 location

0693W00000F9vwFQAR.jpg

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
TDK
September 21, 2021

What "ST-LINK/V2" are you using exactly? How exactly do you have wires going from that to your target board?

"If you feel a post has answered your question, please click ""Accept as Solution""."