ST-LINK V3 bricked by STM32CubdeIDE v1.8.0 ?

[CanisSomnolentus]

I fired up CubeIDE again after a while, it updated from v1.4 or so to 1.8 now.

When I was about to debug, it offered to update the firmware of my ST-Link V3 SET.

It claimed that was successful.

When I then wanted to debug, it claims there is no target.

I USB un/re-plugged, no change.

I tried to go into update mode with ST-Link-Utility.exe in hopes of down-grading, but that says:

"The content of the ST-Link is corrupt"

EDIT: Windows device manager still does show "Univeral Serial Bus devices"/{STLink Bridge, STlink Dongle} and "COM & LPT"/"STlink Virtual COM Port". The COM port seems to work.

ST-Link util still is convinced this thing is "corrupt" and debugging still doesn't work because "no device found on target", while debugging that device worked before, and it is running andoutputting some over that virtual comport, but then gets stuck (but the target board blinks its LEDs, so something is running in its firmware, and debugger should be able to attach?)

1. what gives?
2. what now?

[TDK]

Can STM32CubeProgrammer connect? What board are you working with?

> Windows device manager still does show "Univeral Serial Bus devices"/{STLink Bridge, STlink Dongle} and "COM & LPT"/"STlink Virtual COM Port".

So it's probably still working.

[CanisSomnolentus]

Custom board, and it still works, other that I can't connect - but clearly something is running.

"Can STM32CubeProgrammer connect?"

I will, under protest, try that incredible bloatware that needelessly replaces a perfectly working program...

I'll be back.

[CanisSomnolentus]

So the, for no conceivable reason ~570 MB large (how about 1/10?), STM32CubeProgrammer, does detect the STLink and will also open it in update mode, which the STlink Util refused.

Is this a deliberate move by ST to force people to use this hunk of software ?

Still claims "no target", though. Can this possibly be due to a driver update?

Otherwise I guess I need to thoroughly check the cable to target, looks allright at a glance... unfortunately I have no other target with such a connector. Was using STLink V2 before with a less finely pitched connector.

Edit:

Forget that, the morbidly obese Programmer program can connect to target. With both ends of cable in, previously removed for inspection, things work much better.

Now I just need to find out why debugging does not work.

-> The inbetween restarted CubeIDE still claims "no target" when trying to debug - while the CubeProgrammer connects to a target and shows its contents.

I have not changed the debug configuration which used to work.

[CanisSomnolentus]

For some reason there was a 2nd debug config of the same name present, and I didn't realise this one was active, not the one where I already had set the speed to "1000 kHz" instead of "auto" as I once had problems with that - even though that "auto" setting once used to work.

I guess this is an artifact of working 2 different machines, and something with the git repo not benig set up optimally, or the IDE doing things in unexpected ways w.r.t. debug config files.

Aside:

As for the CubeProgrammer - I guess deleting those .svd files of devices I am very unlikely to ever use won't make it complain as long as I don't try to connect to such device?

Those files seem to be among the bigger things in the install directory.

I took the file for STM32H7B3x.svd, which is 4.2 MB in size.

7zip with default setting (LZMA normal) compressed this by factor 30, to 141 KB or something.

If that's representative, and I guess it is, my idea of this whole thing being able to be 1/10 the size doesn't seem off.