STLINK V2 not detected

KGupt.1 · ‎2021-01-16

I have ST-LINK V2 Programmer and when I connect this with STM32MCU, it shows an error like this I have checked connections, jumper Wire.

Changed the port also. But still, it is showing No STM32 Target Found.

For checking Whether My Programmer is corrupted or not, I have checked ST-LINK with STM8 by connecting to SWIM pinout and it successfully uploads on to my STM8.

So is MY MCU corrupted or damaged, I have an STM32F103C8 Blue chip board.

And have configured its Boot Mode as shown in Pic.

BOOT 0 : 0

Boot 1: opened

Please Help, I am stuck on this for 2 days scratched my head but can't find what the is the issue??

KGupt.1 · ‎2021-01-21

Well, I got the solution, I connected my Boot pins like this and then performed the erase chip thing in STM Utility with connecting under reset settings and my chip gets erased successfully and it is working fine now.

But Still, the Problem is coming with STM32CubeIDE.

It is not programming using STM32CubeIDE while successfully getting flashed with STM32CubeProgrammer. Seems there is a problem with my Setting of STM32CubeIDE.

I have raised this query with STM32CubeIDE in separate thread:

View solution in original post

Vangelis Fortounas · ‎2021-01-16

Hello

use STLink utility to erase the chip, in settings use "connect under reset"

The GND pin of bluepil must be common with the STLink GND

In case that the program itself deactivates debuging, Press for a litle time RST button just before click to "connect" button and release it after click.

Usualy the "problem" solves by connecting the RST pad from bluepil to T-NRST pin of STLink.

KGupt.1 · ‎2021-01-16

I am getting this error on ST-LINK Utility

I have connected SWIO, SWCLK, NRST pins of ST-Link to blue-chip.

And Connected GND pins and 3.3V of st-link to Blue chip respective pins.

Vangelis Fortounas · ‎2021-01-17

Hello

>I have connected SWIO

You mean SWDIO or DIO and not SWO..

In first picture you published i observe PC13 LED is ON. Under reset must be off. An indication that a HW problem exists, is when you keep reset pressed and the PC13 LED doen't turn off.

Another posibility is the RDP protection to be enabled. In this case use STM32CubeProgrammer in UART mode. PA( and PA10 pins must be connected to a USB to serial adapter and recognized from STM32CubeProgrammer as COMx. Before you click "connect" BOOT0 must be already in Hi state (3.3v) When connect successfuly , deactivate RDP option bytes, do a dystem reset and then MCU will be ready to communicate with STLink.

Tesla DeLorean · ‎2021-01-17

Show a picture of the connections to the ST-LINK, preferably a picture of the connections at both end, at high resolution and in-focus.

Are we sure this isn't using an STM32 clone part?

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

KGupt.1 · ‎2021-01-17

These are Connections,

For STM32 F103

White: GND

Orange: SWCLK

Black: SWIO

Grey: 3V3

Red: NRST

Magenta: GND

For ST-LINK,

White: GND

Orange: SWCLK

Black: SWIO

Grey: 3V3

Red: NRST

Magenta: GND

How to get to know whether my STM32 is cloned or not

Tesla DeLorean · ‎2021-01-17

Looks Ok

Does the board function?

Could be a board issue

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

KGupt.1 · ‎2021-01-17

are boot modes correctly connected ?

KGupt.1 · ‎2021-01-17

STM utilty is not able to erase the chip.....

so could it be that it is not able to communicate with STM32 MCU because it might got corrupted.

Tesla DeLorean · ‎2021-01-17

Really shouldn't make a lot of difference.

Set BOOT0 to 1 so it doesn't run code from FLASH, but I'm still leaning toward it being a chip/board issue. But I can't read the part number

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..