STM32L151C6 SWD issue

[wal99d]

Posted on March 17, 2015 at 22:42

Greeting,

I'm facing an issue while trying to program STM32L151C6 using STM32F4 Discovery board as programmer. What I did are the following:

1. I removed CN3 jumpers from STM32F4 Discovery board page 14 in [

https://www.google.com.sa/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB4QFjAA&url=http://www.st.com/st-web-ui/static/active/en/resource/technical/document/user_manual/DM00039084.pdf&ei=f58IVcOiNcb4Uo7vgNAD&usg=AFQjCNE7wWFkc36n9LqACgAqzuc_c-tdGw

][1]

2. I connect NRST, SWDIO, GND, SWCLK, Vdd to my target STM32L151C6 SWD pins except SWO ( I kept it floating)

Pin:number CN2 (STM32L151C6) Pin:1 Vdd Pin:2 SWCLK (PA14) Pin:3 GND Pin:4 SWDIO (PA13) Pin:5 NRST (NRST) Pin:6 SWO (No Contact)

3. I used STM32 ST-Link Utility V2.2.6 to test SWD.

The result is ''Cannot connect to ST-Link''

I've attached the schematic for my circuit design.

I really appreciate your prompt help guys to facilitate this issue. 

#swd #st-link/v2 #stm32l151c6

[Tesla DeLorean]

Posted on March 17, 2015 at 23:41

I'm not sure if that error means it can't see the ST-LINK, or the chip attached to it. If you go back to the F4 settings, does that work immediately.

Is the VDD connection necessary, or is it powering your board?

Is the part correctly orientated?

[wal99d]

Posted on March 18, 2015 at 00:11

Hi Clive,

The part is oriented correctly I double checked it.

  

Regarding Vdd I do have power from my pcb battery  (Vcc = 3.3V) I'm just following the SWD connection that's why i kept it connected to Vdd. should I remove it?

I've tested the ST-Linkv2 which is provided from STM32F4 Discovery board and it's working fine with its attached STM32F4 MCU but once I disconnect the CN3 jumpers and make the connection to SWD in my PCB I got this error message.

Appreciate your kind advice

[daniel239955_st]

Posted on March 18, 2015 at 10:12

Hello alharthi.waleed,

I'm using the ST-Link/V2 myself on a custom PCB and it works fine.

Your SWD setup looks correct except for one part that makes me suspicious:

VDD->Vcc

The SWD interface does not provide means to power the MCU, but it does take the MCU VDD as an input. 

You need to provide a power supply for the MCU from elsewhere (as you wrote, you use a battery).

Not sure what Vcc voltage is since you run it over a resistor, but the SWD VDD should be connected directly to the MCU VDD (3V3).

From the ST-Link/V2 documentation:

''The power supply from the application board is connected to the ST-LINK/V2 debugging and programmingboard to ensure signal compatibility between both boards.''

Here is some documentation on the ST-Link/V2 (check out p. 12):

http://www.st.com/st-web-ui/static/active/en/resource/technical/document/user_manual/DM00026748.pdf

[wal99d]

Posted on March 18, 2015 at 15:07

Hi Daniel,

I've checked the power and it's fine there is no drop in voltages however once I tried to connect with STM32 ST-LINK Utility with the below configurations:

I got below error message:

[Tesla DeLorean]

Posted on March 18, 2015 at 15:09

You would only need to connect the GNDs between two independently powered systems.

I'd look at the firmware on the ST-LINK, and check if any of the solder bridges related to NRST, etc need to be removed from the DISCO board.

[Tesla DeLorean]

Posted on March 18, 2015 at 15:15

From the ST-Link/V2 documentation:

 

''The power supply from the application board is connected to the ST-LINK/V2 debugging and programming board to ensure signal compatibility between both boards.''

That's for the stand-alone ST-LINK/V2 which has buffering chips between the signals, the DISCO board implementation has the signals come directly out the F103 to the pins. In this context the power is derivied from the USB supply and feed to the target board, if the target board is self powered at 3.0 or 3.3V the signal levels will be compatible, and a common ground provides a path for the current/electrons.

[wal99d]

Posted on April 08, 2015 at 21:18

First of all I would like to thank each one of you guys. I found the problem which is related to the STM32F4Discovery board I was trying to use it as a programmer. but there were issues not easy to grasp in order to modify the disco board.

What i've done was that I bought a new ST-Link-V2 and it works like charm :) without any changes to the circuit design.

Cheers, Waleed

[gtopba]

Posted on January 31, 2016 at 18:15

Hi, I'm having the same problem as yours. I made my custom board using STM32L476RET6. The programmer is the ST-Link/V2-1 from STM32L4-Discovery board. Below is my connections.

Custom board              Discovery board

VDD -------------------------- 3.3V

SWCLK ---------------------- SWCLK

GND  ------------------------- GND

SWDIO ---------------------- SWDIO

NRST -------------------------NRST

The BOOT0 pin is pulled down by 150 ohms. The jumpers on CH3 of the Discovery board are already removed. I'm successfully using the SWD of the Discovery board to program another discover board by simply connect those 6 pins of SWD ports together. However, when I tried to program my custom board, I got the same message as yours.

I have checked that the clock and data signals are available on the target pins by using an oscilloscope. I really have no idea what is happening to me right now. What is the programmer are you using and where did you buy it?

This is my very first comment and I cannot find the comment button in this forum. I only see reply button which seems to reply to specific comment.

Regards

[Tesla DeLorean]

Posted on January 31, 2016 at 19:08

See ''New'' top left corner of the list of postings.

Without seeing your schematics, guessing you don't have the supplies connected correctly. Check VDDA, and scope what NRST is doing.

[gtopba]

Posted on February 01, 2016 at 04:52

Problem solved!

The orientation of the MCU was incorrect. I missed understand that the Pin1 is at the top left according to STM32L476xx Datasheet page 59/232. Actually, Pin1 is at bottom left according to the datasheet page 223/232.

I could not find the 'New'. I have used Ctrl+f to search for it. There is no such thing.

Thank you for your help.