STM32Cube Programmer v2.22 SWV not working

[randomguy26]

Just posting this incase it helps someone with this problem that I encountered recently.

I just update to new windows 11 laptop so I started going through the laborious process of installing all my tools including the latest STM32Cube programmer v2.22. Figured this would be a good time to update everything since I'm installing everything fresh anyway.

The issue I encountered is that v2.22 will connect and program the STM32 MCUs just fine but if I try to run the Serial Wire Viewer SWV I get no print outs. I tried a lot of things like reinstalling windows drivers and reinstalling the software but none of that worked, slowing clocks down and other stuff. In the end I removed v2.22 and installed v2.20 and that fixed the issue immediately.

#bug-report

[Pavel A.]

Hi,

Does this problem exist for specific ST-Link model (onboard or standalone)? 

[randomguy26]

I was using the ST-LINK/V2 programmer. I tried a couple with the same results.

[Kouthair]

Hey there @randomguy26 ,

SWV worked fine on my end on v2.22. Can you please provide more details about your setup (Chip/board, SYSCLK value used, etc..) that would help me with this investigation? That would be much appreciated!

[randomguy26]

I was using STM32WB55RGV6 with sysclk set to 32MHz on our own custom board. Again this was on a clean install on a Windows 11 PC. Reverting back to v2.20 fixed the issue so for now I'm good. After writing this I decided just for kicks to update back to v2.22 and the SWV does work now. I wonder if the install package for v2.22 might be missing the SWV drivers, and me installing v2.20 added something extra that the new package might be missing.

[Kouthair]

Hello again @randomguy26 and thank you for providing the extra information. It was very helpful in investigating this behavior.

I was able to reproduce this on the STM32WB55RGV6, and the team is now aware of the issue. (Internal ticket ID: 0061812)

However, reconnecting the device in v2.22 appears to work as a temporary workaround.

I'll let you know ASAP whenever the fix is live.

PS: Ticket ID: 0061812 is an internal tracking number and is not accessible or usable by customers.