I have root caused the reason: My variable is only updated in the while 1 loop but not read by the software at all. If I set Access as "Read", then no waveform is shown because the variable is never read. Once I change the access to "Read/Write" or "Write", I am able to see the graph because the data trace is triggered with each write.
Have you set correct HCLK frequency in Run Configuration -> Debugger -> SWV (Enable)-> Core Clock? On YouTube examples show 80MHz but your board may have different default set - for example 216MHz. Check it in *.ioc -> Clock Configuration -> HCLK (MHz)
In my case the debugging settings are grayed out. Does somebody know what this means? And the SWV Data Trace cannot be configured, no window opens. Thank you for any suggestions. I am using a J-Link debugging probe and I have the Version:
Version: 1.10.0
Build: 12671_20220627_1643 (UTC)
with: stm32g071CBUx
Here is an example.
I think at this stage I must have tried every single option box and combination there is.
Thanks AScha.3! Core is 168MHz. I swapped to that and it immediately started working... badly. I had assumed this 8MHz value was to do with the debugger itself, not the core clock of my mcu, since it was greyed out and auto populated. Changed it in the debug config and started to get data out of it but with all sorts of glitches, and the interface simply cannot handle the amount of data it gets sent...
It also seems to be tripping the BRK, or perhaps the clock fault on the timer. MOE keeps tripping to zero, which never happens when SWV is not being used.
However, somehow this made the Segger j-scope work where it did not before (presumably embedded in the elf file or segger settings somewhere) which works pretty nicely. No MOE tripping there. I now have a nice functional scope.
