SWO doesn't work with STLINK-V3PWR

[n4te]

I'm trying to get logging via SWO using STM32CubeIDE, an STLINK-V3PWR, and an STM32F411CEU6. It's wired and configured correctly because it does work if I use the 16MHz HSI, but I need to use my 25MHz HSE. I get no SWV entries at all when I set both the SYSCLK and the SWV clock to 25MHz. Does that make any sense? Is there some good reason for that?

I got the STLINK-V3PWR to dork with the power measurements, but now I'm wondering if it's the problem. I don't have another programmer to try. I bought a Tag-Connect for it, so if I buy another programmer to try I'd like it to be V3 or V3MINI so my cable fits (STDC14). I'd rather the V3PWR work correctly.

I could trash bin the stupid STLINK and get a JLink. At this point I just need it to work. I'd be very unhappy if the JLink also didn't work.

I posted on the ST forum but I'm skeptical about getting a useful response.

[Bud]

You can try to reflash ST-Link with JLink firmware to convert to JLink. Not sure though if JLink still provides it.

[n4te]

Interesting, but that seems to be for the Discovery and Nucleo boards. I wonder if it'd work on a V3PWR.

[n4te]

Turns out I'm an idiot and had misconfigured my clocks. I had thought my HSE was 25MHz, as it is in my other designs, but for this one I used 10MHz. After fixing that SWO logging works, but fails when messages are sent too fast. I'm not even sending all the fast, messages are sent at about 60Hz.

I kept everything the same but replaced the V3PWR with a V3SET and V3MINIE and those work fine. SWO logging never stops. This leads me to believe the V3PWR is a piece of shit.

I guess I should not have tried using ST programmers. I'll try a J-Link Mini.