2024-10-30 03:11 PM - last edited on 2024-10-31 01:18 AM by Andrew Neil
I have a windows 11 laptop with both ST-LINK Utility and STM32CubeProgrammer installed. I can connect to my STM32-based motherboard using a ST-LINK clone and ST-LINK but not with STM32CubeProgrammer. Anyone know what I'm doing wrong?
2024-10-31 12:07 AM - edited 2024-10-31 01:17 AM
Hello @FPayn.1 ,
Which device used?
Which STM32CubeProgrammer version used ?
Please make sure to use the latest version of CubeProgrammer.
Try then connecting in "Connect Under Reset" mode.
2024-10-31 12:59 AM
>>Anyone know what I'm doing wrong?
Using counterfeit gear for one, ST's just not cool with that. I think they've made the decision to make them not work properly. And you keep going in circles with the same problem.
Cheapest solution would probably be a NUCLEO with a snap-off ST-LINK, or an ST-LINK/V3
Copying firmware out of one unit, into another, might also be a flawed approach.
2024-10-31 01:26 AM - edited 2024-10-31 01:40 AM
@FPayn.1 wrote:I can connect ... using a ST-LINK clone and ST-LINK
So you've tried both a clone and a genuine ST-Link?
What firmware versions in each?
@FPayn.1 wrote:but not with STM32CubeProgrammer
So what, exactly, happens with CubeProgrammer?
What version of CubeProgrammer?
Show logs; screenshot error messages.
Is that also with the genuine ST-Link?
https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693
@FPayn.1 wrote:my STM32-based motherboard ?
Give details - schematics, etc:
Does this board also have clone/fake STM32?
@FPayn.1 wrote:Anyone know what I'm doing wrong?
far too little detail to tell, but using fake/clone kit just complicates everything!
eg, see:
2024-10-31 07:18 AM
Thanks for all the replies. The board is from a FlashForge Creator Pro 2 3D printer, and it is indeed a genuine STM32 product.
Regarding 'clone' vs 'genuine' ST-LINK/V2 adaptor, I could see how that might be a problem with BOTH ST-LINK and STM32CubeProgrammer, but not with just one; please correct me if I am wrong.
Background, Photos and schematics can all be seen on my engineering/3D printing blog here.
TIA,
Frank
2024-10-31 07:29 AM - edited 2024-10-31 08:10 AM
@FPayn.1 wrote:Regarding 'clone' vs 'genuine' ST-LINK/V2 adaptor, I could see how that might be a problem with BOTH ST-LINK and STM32CubeProgrammer, but not with just one; please correct me if I am wrong.
Pardon?
I was asking if you have tried this with a genuine ST-Link, and whether you get the same issues when using that genuine ST-Link.
PS:
Oh - when you say "ST-LINK", you seem to be meaning the "ST-Link Utility" software.
I'm asking if you actually have a genuine ST-Link/V2 hardware device:
and whether that device exhibits the same problem(s).
2024-10-31 07:36 AM
2024-10-31 07:57 AM
The ST-LINK Utilities have been deprecated for several years, firmware on the ST-LINK and the stance to counterfeit gear has changed.
STM32 Cube Programmer is the currently active development path and tool, so will reflect the current position more aggresively. A lot more boot-leg programmers in the channel now, and a lot of STM32 proxy devices, ie with similar form-fit-and-function.
It's not hard to tie code to a particular board or MCU, especially with encryption or keys tied to UNIQUE ID or OTP settings. For commercial boards, those vendors might not want to ceed business to pirates or nefarious third-parties.