Atollic/CubeIDE Automatically start SWO trace - still not done?

[Pavel A.]

"Is it possible to automatically record SWV output in the SWV Console window so i do not have to push the red button manually on every launch?"

This was asked back in 2018 and still annoyes users...

https://blog.atollic.com/learn-serial-wire-viewer-debugging-on-cortex-m

Any chance it will be done?

Thanks,

Pavel

[Markus GIRDLAND]

I've tried to raise this issue as well. Apparently it's more complicated than at least I would have guessed. There's more to that little red button than meets the eye. But I'll keep on fighting to make it no longer necessary to activate it every launch! :smiling_face_with_smiling_eyes:

[Pavel A.]

Thank you for your efforts, Markus.

If this can be done via some monitor command in the debug start script, would be OK for me.

-- pa

[bully]

I agree, this one is really annoying...

R.

[Schmid.M.]

still annoying!

[Rob Meades]

...and it can't be that complicated to do 'cos I can make it happen from the command-line using the OpenOCD and configuration files that are provided inside the STM32Cube directory with:

openocd –f stlink.cfg –f stm32f4.cfg -c init -c "itm port 0 on" -c "tpiu config internal temp.dat uart off 168000000 2000000" -c "reset init" -c resume

Surely it can't be easier to do from the command line than from inside what I assume is an Eclipse plug-in!?

[RRodr.2]

waiting for some progress...

[paul19]

Also looking forward to this.

[NZahr.1]

Any update for this feature?

[Markus GIRDLAND]

Yep!

The errata for release 1.8.0 states under "Fixed issues":

95519 SWV Start Trace button now remembers its state.

Which means that as long as you are using 1.8.0 or a newer release of STM32CubeIDE it should no longer be necessary to press the button for each debug session.

[LaurentL]

Hello,

This feature is supported since STM32CubeIde 1.8.0 version.

You have to start it once (with the red button) and it will be automatically started on the next debug sessions.

Rgds,

Laurent

[Pavel A.]

@LaurentL​  @Markus GIRDLAND​  don't laugh at me.... but on the second thought - can automatic start of trace cause trouble?

The problem is that the server must know the target system clock frequency.

Usually the target starts on a different clock (internal vs external .... etc) and only some time later switches to the frequency specified in trace parameters.

Can bad trace data that arrives before the target clock switch confuse the server?

-- pa

[Markus GIRDLAND]

Hello @Pavel A.​ ,

No laugh here, the point is valid. I asked the developer who implemented it and he said that it's possible that some "garbage" data could appear in the SWV views if, for example, you printf before the clock is configured. However, it shouldn't be able to crash, confuse and/or sabotage anything as far as he is aware.

But as always, if you find a use case that proves him wrong then let me know and I'll write a ticket ;)