AnsweredAssumed Answered

ST-Link v2 not working with custom board

Question asked by pregetter.richard on Jan 21, 2016
Latest reply on Jan 22, 2016 by pregetter.richard
Hi,
i have my custom board all set up and checked and tried to program my STM32L051C6 with the ST-Link V2.
I am running the board with 1.8V, the NRST line has a 10k external pull up. SWDIO and SWCLK are just rooted to the header. Boot0 was tried with high and low. The header is the same as on the STM32L0 discovery kit, because at first I wanted to use this to program the device.(1.8V not possible with discovery board, my foult).

When I try so connect to device in STM32-Link Utility (lastest, also latest, firmware upgrade for ST-Link V2) I get the error: No target connected.

Settings: SWD;
 Connect under Reset;
Enabled Debug in low power mode;
Hardware Reset;

The connection from the debugging header to the debugger is done with jumper cable.
Connection: PIN 1 and 2 of debugger : 1.8V
PIN 3 and 4: Ground
PIN7 : SWDIO
PIN9: SWDCLK
PIN15: NRST

The same connections where used with the discovery board(not using the on board debugger) with success.

I can measure 1.8V on PIN 2 if I remove it from header and debugger. So the debugger should definitely see 1.8V as MCU VDD.

I observe NRST, SWDIO and SWDCLK while trying to connect(here Boot0 = low):
Yellow NRST
Red SWDCLK
Blue SWDIO

scope_0 shows the timing between NRST and the clock start. It can already seen that SWDIO is on 1.8V until SWDCLK starts. Then it switches to 3.3V. Same as SWDCLK from the get got.

scope_1 shows the start of SWDCLK and SWDIO. Dutycylce is not 50%?

scope_2 shows the first activity on the SWDIO line.

scope_3 shows the second activity on the SWDIO line. They are alternating for 6 times than SWDIO and SWDCLK stop.

If there is more info I could provide please tell me. Right now i can not supply with 3.3V because an ADC with 2V max. supply is on the same supply.

kind regards,
Richard

Attachments

Outcomes