Skip to main content
J.Park
Associate II
June 27, 2019
Solved

STM32CubeIDE-- how to use SWV data trace timeline graph

Hello, now I'm using F429IDiscovey and STM32CubeIDE to grahp via SWV.

I refre to this official video(URL: https://www.youtube.com/watch?v=eumKLXNlM0U)

In the STM32CubeIDE, I configured same like video.

(Please see the attached file named 'SWV_Config' and 'Debug Config')

After configuration, I can run debug mode normally.

Also I can check variable(LED_state) that get value 1 and 0 per 500ms as I coded.

But I cannot any graph on the SWV Data Trace Timeline Graph...

(Please see the attached file named 'LED_State=0' and 'LED_State=1')

Do I miss something? How can I fix?

Thank you in advance

This topic has been closed for replies.
NBinh
NBinhBest answer
Visitor II
August 5, 2019

I found my problem. It cause by the st link v2 device from china so it's not enough function.

Now Im trying to solve it follow that https://engenhariaegambiarras.wordpress.com/2017/06/25/using-swd-and-swv-with-stm32-ucontrollers-printf-and-logic-analyzer-into-debbug-mode/

24 replies

DMolo
Associate III
December 31, 2022

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.0693W00000Y79uNQAR.png0693W00000Y79uXQAR.png

AScha.3
Super User
December 31, 2022

cool !

+

my new stlink V3 (mods) running now with SWV !

statistic profiling :

0693W00000Y7A48QAF.png+ Happy New Year !

If you feel a post has answered your question, please click on " Best Answer ".
DMolo
Associate III
December 31, 2022

0693W00000Y7A5BQAV.png 

Bit more investigation and it seems there is a Cube Monitor tool now that is available, and works just fine. Guessing ST gave up bugfixing SW viewer on CubeIDE.

ATale.2
Visitor II
January 18, 2023

[SOLVED] Hi, if someone is facing the same issue probably you need to make sure that the clock frequency set in debug configuration is the same as your HCLK. For me it was 72 MHZ. See figures.0693W00000Y8ZHiQAN.png0693W00000Y8ZHYQA3.png

FShah.1
Associate III
May 16, 2024

Hi,

I am trying to use the SWV Timeline Graph, but I am unable to run it for more than 4 to 6 seconds. Could you please provide some advice on this? I am attaching all the screenshots. I am using I2S communication to interface MEMS mics SPH0645LM4H.

I have a custom board with an STM32F446RE and an ST debugger model STLINK-V3SET.

Thank you.

MCU --- Debugger

Gnd --- Vcc

Clk -- Clk

Gnd -- Gnd

SWDIO -- SWDIO

NRST -- NRST

SWO---SWO

I tried same code on Nucleo-F446 an

FShah1_6-1715896024052.png

 

d SWV Timeline Graph works continuously. Kindly check the screen shots and let me know if you see any issue.

Thank you,

FS

 

FShah1_2-1715895971321.pngFShah1_3-1715896001566.pngFShah1_4-1715896010855.pngFShah1_5-1715896017050.png