cancel
Showing results for 
Search instead for 
Did you mean: 

Clone ST-LINK Error: No STM32 target found!

AlexPCB
Associate II

Title edited to note that this is not a genuine ST-Link


11:19:26 : ST-LINK SN : 37FF71064E57343652791543
11:19:26 : ST-LINK FW : V2J46S7
11:19:26 : Board : --
11:19:26 : Voltage : 3.24V
11:19:26 : Error: Unable to get core ID
11:19:26 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

 

I am using a LoRa module E77-900M22S that has incorporated a STM32WLE5CCU6. Also i am using a ST-Link V2 mini connected to program the micro. I have connected SWDIO and SWCLK properly and the module has 3.24V so the problem its not the connections. I dont know why it doesnt detect the MCU.

1 ACCEPTED SOLUTION

Accepted Solutions

Again, there is no guarantee that those will work properly (or at all) with ST's tools.

They are simply not supported.

You could try faffing around; you might get lucky - or you could just get a genuine ST-Link (or other genuine supported brand) and get on with your project ...

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

View solution in original post

8 REPLIES 8
Andrew Neil
Super User

@AlexPCB wrote:

i am using a ST-Link V2 mini .


There is no such ST product as a V2 Mini - do you mean one of these ?

There is no guarantee that those will work properly (or at all) with ST's tools - see this.

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
Andrew Neil
Super User

@AlexPCB wrote:

I am using a LoRa module E77-900M22S .


You mean this: https://www.cdebyte.com/products/E77-900M22S/2 ?

Have you checked with EBYTE for support: https://www.cdebyte.com/ContactUs ?

 


@AlexPCB wrote:

I have connected SWDIO and SWCLK properly and the module has 3.24V so the problem its not the connections.


Please show your schematic for people to confirm.

A good, clear photo could also help.

You haven't mentioned VTARGET, GND, or NRST ... ?

 


@AlexPCB wrote:

I dont know why it doesnt detect the MCU.


Maybe EBYTE have locked-out programming?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

I am using one of those actually. There is any problem with it or should I use an original one?

https://www.cdebyte.com/products/E77-900M22S/2 This is exactly the one that i am using

This is the schematic of the connection:

Captura de pantalla 2026-03-24 162355.png


@AlexPCB wrote:

There is any problem with it 


Again, there is no guarantee that those will work properly (or at all) with ST's tools - see this.

Note also that the pinouts do vary.

 


@AlexPCB wrote:

 should I use an original one?


That would remove one area of doubt and uncertainty!

Just be sure to buy from an Authorised ST Distributor - not Amazon, ebay, Ali, or similar

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

To be clear, I have a clone ST-LINK but CubeProgrammer recognizes it and I can update its firmware perfectly just as seen in the image:
Captura.PNG

Even if it is recognized, does the problem "No STM32 target found" come from it being a clone?

 

Again, there is no guarantee that those will work properly (or at all) with ST's tools.

They are simply not supported.

You could try faffing around; you might get lucky - or you could just get a genuine ST-Link (or other genuine supported brand) and get on with your project ...

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

>Even if it is recognized, does the problem "No STM32 target found" come from it being a clone?

Depends...

- CubeProgrammer should always work fine

- CubeIDE little bit more picky, but if genuine stm32 inside your "clone" , it should work fine

-- BUT : set to reset -> software reset !   Because the "clones" have no working hardware reset for stm32 !!!

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