ST-link V2 Connection error.

[KimJeBu]

How do I solve this error? "Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication"

I use SWD. I made the cable for SWD communication. The cable is connecting ST-LINK V2 between board. 

Yesterday, well, was connected to STM32CubeProgrammer.

But today it wasn't connected suddenly.....

I did everything I could by exploring the STM32 community.

Changed ST-LINK V2, the cable, reset mode, etc......

I saw massage what "ST-LINK error (DEV_TARGET_CMD_ERR)" in hardware rest mode.

But I don't solve this error.

Please help me....

[Peter BENSCH]

Welcome @KimJeBu, to the community!

Can you please post a photo of the ST-LINK/V2 you are using?

Regards
/Peter

[KimJeBu]

Of course. Thank you for your kindly.

[Peter BENSCH]

ST-LINK/V2 are very often illegally cloned, even the labelling of the packaging card and the housing are copied elaborately.

There are several ways to recognise a clone: you could, for example, open your ST-LINK/V2 (one screw is under the sticker on the back between the logo and the edge, another one is roughly where you have the word "SWIM") and you would then find a fake STM32F103. If you don't want to damage the sticker, you can also try to upgrade the ST-LINK/V2 with the STM32CubeProg (disconnected and right in the middle "Firmware Upgrade"). If this upgrade fails, which you can already tell from the missing or implausible serial number, you have an illegal clone and should contact the manufacturer of this clone - or buy an original ST-LINK/V2.

Regards
/Peter

[MikaelM]

Hello @KimJeBu 

could you provide us more information :

1. which kind of board (ST boards, nucleo, disco, customer board)
2. device part (U5 series, U585,....)
3. boot0 state at connection time
4. STM32CubeProgrammer version
5. STM32CubeProgrammer connection configurations
6. steps you have done before and after the issue

Thanks

Best regards

Mikael

 

[KimJeBu]

Hello. MikaeIM

It is answer to your question.

1. customer board

3. The custom board has a switch that changes Boot 0 to low level when pressed.
    So, for download a '.hex' file, power on after press the switch on the custom board..

4. Cube Program Ver. is least versoin.

5. I connected the laptop and the custom board using ST-LINK V2's STM32 (20pin) SWD.

6. Step of before and after the issue is same.
    but, I did re connected the GND(4pin) because GND was open(because the solder ran out.).

Thanks

Best regards

[AScha.3]

>Yesterday, well, ...

maybe you damaged it (static discharge) ; can you try a new one?

+

with SWD connection, need no boot action. (use system software reset , in CubeProg setting)

[gouku]

Hi Peter

I am facing same issue on 2 ST-Link I bought from Digikey. I can see the serial number on both.

Cube programmer ver: v2.15.0

FW ver: V2J43S7

Below is the image of ST Link.

Please help!

Regards

Goutham

[Peter BENSCH]

@gouku Your ST-LINK/V2 look original and if they are also recognised by the STM32Cubeprog and the firmware can be updated, you can assume that the ST-LINK/V2 are working.

However, you are guaranteed to have a different environment than the TO, so it doesn't say much if you only write that you have the same problems. @MikaelM post also applies to you, so please reply to it.

Regards
/Peter

[gouku]

Hi Peter

The issue was with the wiring.! Target Vcc (Pin no 1) was not connected to 3.3V.

I connected to 3.3v and now it works fine.

Thank you.

BR Goutham

[CSand]

It seems I have the same problem

Although I agree ST should protect their product I would expect it would prepare the customers for this decission. I used to buy STF103 MCU and ST Link V2 ( "fakes" ?? ) from fastest supplier not really looking if original or not...

I have an original ST Link V2 from ST on the back is [B 2022 48 ] just purchased 2 days ago from Digi Key ( your trusted supplier/distributor ).

I have several bluepills STM32F103C8T6 that in the STM32Programmer are visible, can connect and read memory. Amyway, when I connect to STM32CubeIDE I get the error "Cound not verify ST device !" or "No STM32 target found!".

Can anyone suggest an issue?? 

The ST Link V2 FW after update is ... V2J43S7

It can read memory in STM32Programmer

In STM32CubeIDE it does not connects ...

A photo with hardware - all seem original.

 

[Peter BENSCH]

@CSand You are trying to access a Blue Pill with STM32CubeIDE via what appears to be a genuine ST-LINK/V2. Why would STM32CubeIDE program a fake MCU that it doesn't know?

And in case it's not clear to you, although it has been discussed here many times: there has been no Blue Pill with original STMF103 for years.

Regards
/Peter

[CSand]

 

Peter, we are not super IT or MCU experts or use all features of the MCU's or any high level of technologies.

We also not staying on forums to figure out complex technical issues generated by above mentions. We only need a product that is $10- $30 to help us solve basic problems and not be an Arduino ...

So, would you suggest we should move away from this bluepill that seems it is no longer supported by ST.

What are the options as a development board from ST ? 

The actual issue at this moment is that were taken completly unprepared and weeks are going without being able to get a solution to this problem. We find ourselves - like many many others probably - in the middle of some decission that affects some of existing customers.

 

[Peter BENSCH]

Blue Pill is a board from an Asian manufacturer, but was never (officially) supported by STMicroelectronics.

Instead of the undoubtedly very inexpensive Blu Pill (now you know why it is so inexpensive), I recommend the universally applicable NUCLEO boards, which are available with many different MCUs and in three sizes: NUCLEO-32, NUCLEO-64, NUCLEO-144. You'll find some overview e.g. in the user manuals or in:

• DB2638 (STM32 Nucleo-32 boards)
• DB2196 (STM32 Nucleo-64 boards)
• DB3171 (STM32 Nucleo-144 boards)

Most NUCLEO-64 even have a detachable ST-LINK/V2 that can be used to program or debug other target platforms.

Good luck!
/Peter

[CSand]

Can I ask is it the blackpill the same story? 

[AScha.3]

I dont think so, but ...who knows...

My blackpill boards ( F411 + F401 ) have genuine STM chips and never had a problem to connect with IDE .

 

"Story" here might be: using a cheap st-link "stick" to connect, with "wrong" cpu inside, will not connect.

[Peter BENSCH]

@CSand Well, that is a question of expectations, as well as understanding what STMicroelectronics intended with this. First of all, as can be read in the Terms of Use, all NUCLEO are purely evaluation boards and are not authorised for use in production systems (usually nobody reads this, but have a look at RESTRICTIONS AND WARNINGS). Since STMicroelectronics is no longer quite a newcomer, such legal clarifications are simply necessary.

But if you find the format of the NUCLEO-64, which is intended as the base board for X-NUCLEO and was historically the first to appear, too large and unwieldy, why don't you take a look at variants of the NUCLEO-32?

[CSand]

Peter, You may missed some part of my post ...
We have Nucleo-G431 and F303, they are both Nucleo-32.

We are providing customized solutions for production check-points where quantities are small. We rearly  have 5 projects the same - is this called production?

A solution is to develope own PCB board but that is not efficient at these quatities. And there is the same risk - will ST keep these chips compatible for how long? 

So we are using existing solution that is used by many and just fits as best for our needs.

Anyways - you just seem to justify to me why ST cannot help us anymore... .

 

 

[Peter BENSCH]

@CSand indeed I haven't actually read everything in the thread, but you haven't used a complete and unambiguous description either. There are in fact

• both NUCLEO-F303K8 (NUCLEO-32) and NUCLEO-F303RE (NUCLEO-64)
• both NUCLEO-G431KB (NUCLEO-32) and NUCLEO-G431RB (NUCLEO-64)

So I had to choose a variant.

Regarding your quantities: I repeat the statement from the Terms of Use:

RESTRICTIONS AND WARNINGS
[...] The Evaluation Board shall not be, in any case, directly or indirectly assembled as a part in any production of Yours as it is solely developed to serve evaluation an d testing purposes and has no direct function and is not a finished product.
If the Evaluation Board is incorporated in an evaluation system, the evaluation system may be used by You solely for Your evaluation and testing purposes. Such evaluation system may not be offered for sale or lease or sold, leased or otherwise distributed for commercial purposes and must be accompanied by a conspicuous notice as follows: “This device is not, and may not be, offered for sale or lease, or sold or leased or otherwise distributed for commercial purposes”. [...]

Even if you only sell 5 units of such products/systems/whateveryoucallit, you are legally in breach of these Terms of Use. Whether this will be prosecuted is another question. As the saying goes: where there is no plaintiff, there is no judge.

Developing our own circuit board would certainly be the optimal solution. However, there is exactly zero risk for such small quantities:

1. firstly, there is a rolling commitment for product longevity for the STM32, which checks every spring whether each individual family can be extended for a further 10 years, which has so far been the case with only one exception (STM32L1)
2. secondly, you can still keep a packaging unit (1500 or 2400) in stock shortly before the end of these 10 years, which will last for a correspondingly long time

Have I now explained why ST can still help you?

Regards
/Peter

[CSand]

Hi Peter, thanks for clarifying all details.

But as you told, ST not producing Bluepills for years now, we would not interfier with your wornings and restrictions - right?

In any case after long internal discussion we found a local pcb supplier that can develop and deliver for us a "production" board using genuine STM32F103 and would be delivering these boards for initial evaluation quite soon. 

In the meantime they helped and populate for us some Bluepill pcb's with chips from ST so we can continue what we do.

Thanks and Regards,

 

[Peter BENSCH]

@CSand In fact, the Blue Pills are not from ST, nor does ST have anything to do with them. Also, ST's recommendations were not taken into account during their development and, on top of that, counterfeit STM32F103s have been used for several years.
ST could care less about all this, but unfortunately misguided users keep coming to the community and complaining about problems with Blue Pills.

To come back to your question: correct, since ST has nothing to do with the Blue Pills, the restrictions of the ST tools do not apply and you can do whatever the manufacturer allows you to do with it.

Good luck!
/Peter