cancel
Showing results for 
Search instead for 
Did you mean: 

Why was Cmsis-DAP debugger thread locked?

atleasttwocharacterslong
Associate III
5 REPLIES 5

That's not from ST support - that's from Black Magic support!

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.

Ok that the guide is from Black magic support but the support in the ide is from st, it is their ide after all!, at least in the way that they just include it, and many people use the Black magic probe for stm32s

Split to the Feedback forum as this is now about forum policy.

 


@atleasttwocharacterslong wrote:

 the support in the ide is from st, it is their ide after all!


I think you're confusing having the potential in the IDE with getting support from ST to set it up.

For support in setting it up - which is what you were asking for - you need to go to the 3rd-party.

 

But I do tend to agree that it seems a bit heavy-handed of ST to lock that particular thread.

It's not like the Black Magic probe is pretending to be an ST product - as the fakes/clones do.

 

It does seem that the Black Magic probe is a bona fide product.

ST staff might choose not to provide support, but it doesn't seem helpful to block it entirely from the community.

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.

ok, i will go to see if they have a place to ask for their help, though to me it LOOKS like an issue in the ide(potentially my fault)

atleasttwocharacterslong
Associate III

ok, so i just asked chatgpt(i was outta options) and it said to download an older version of gdb, so i got arm-none-eabi-gdb 10.3 and it works now, it looks like it was a bug in the new versions of gdb-multiarch