Did I miss a news cycle? what is the source of your claim that ST "now longer allows" debugging vis fake STLINK (i.e. that there's been a software change in a recent release)? is this based on any hard evidence, or are you just having trouble with your board and jumping to conclusions?
Years ago, when FTDI pushed out a driver update that made fake versions of their chips break (and then when they retracted it, and then when they put out another hostile update later on), it made a huge noise in maker/EE circles. But I haven't heard anything of the kind, and I look at this forum almost every day.
What I do know, and this is nothing new, is that cloned chips and clone programmers are often more trouble than they're worth, and that ST (quite reasonably) will not provide support for cloned products. So "buy original products" is good advice, especially if you're not a strapped teen or student, where every 10 bucks makes a difference.
That said, and unless you point me at a bombshell news item, none of the symptoms you described sound to me like indicators of fake products. At the very least, you can download an old release of CubeProgrammer and try again. If that doesn't work either, I doubt a new stealth anti-counterfeiting campaign by ST is the cause of your current difficulties.
- If someone's post helped resolve your issue, please thank them by clicking "Accept as Solution".
- Please post an update with details once you've solved your issue. Your experience may help others.
