Problem to download from ST Link of EWARM

[L C]

Posted on April 16, 2017 at 13:45

Hello! I can't download to STM32F103C8T6 via ST-Link(ST-Link V2#) of EWARM.

The error message is attached.

Please let me know your comment.

[Imen.D]

Posted on April 18, 2017 at 11:31

Hi,

Do you have SWD mode selected ? 

You should configure ST-Link interface as SWD:

 Project Options -> ST-LINK -> check SWD Interface option.

Imen

[AvaTar]

Posted on April 18, 2017 at 12:54

I would try a mass-erase, which helps if you have a misbehaving application on the target.

Probably in System Mode (Boot0/Boot1 pins).

[Imen.D]

Posted on April 18, 2017 at 14:36

Hi,

Try to use ST-Link Utility. Then, if still doesn't work, you should check your hardware configuration or check your IAR setting.

Imen

[L C]

Posted on April 19, 2017 at 08:00

Hi Imen

It work fine with ST-Link Uility and function with SWD config in IAR.

Is it(ST-Link V2) SWD interface only?

[L C]

Posted on April 19, 2017 at 08:08

Hi AvaTar

Mass erase has tried but it is still not work(with JTAG config).

Boot0/Boot1 pins are used to select boot location(select bootloader). Right? if not, please correct me.

I guest JTAG & SWD are low level interface to access ARM core no matter what setting of 

Boot0/Boot1 pins.

Boot0 =1 & Boot1 =0 : for UART download?

How about another setting? Please share your experience to me.

[AvaTar]

Posted on April 19, 2017 at 09:03

Is it(ST-Link V2) SWD interface only?

For the Discovery and Nucleo boards, yes. Only the stand-alone version supports JTAG.

However, this seems not to be your problem, the error message would look different.

Complains about a non-responsive target means the debug pod is found and is working.

Boot0 =1 & Boot1 =0 : for UART download?

How about another setting? Please share your experience to me.

One of the things I don't memorize - there is an application note from ST, you might try a search.

And, different parts support different interfaces in the system bootloader.

Check the datasheet and/or the reference manual for supported interfaces and the Boot0/Boot1 combinations.

Some boards already have jumpers to support a forced system bootloader entry.

In the long run, I tend to forget those details as well ...