You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request]: Concept for Trace Port Configuration #581
Multicore devices need a different type of trace configuration. New generation devices have Performance Counters and the Cortex-M3 ITM configuration does not longer scale.
This diagram shows various configuration dialogs. Overall they seem to be overwhelming. The block diagram (right button) is the topology of a multicore device).
Initial Tasks:
What are the minimum parameters that a Trace Port configuration requires. Initial focus can be limited to just SWO UART mode (however my preference would be to take this wider).
Would be Trace Clock and Baudrate sufficient?
Can Baudrate be a single 'default' setting so that only Trace Clock is exposed in a UI?
Is the configuration of SWO UART mode enough standardized across various devices?
Is it feasible to move ITM/DWT (ect.) setup to *.dbgconf? As such features are specific to a processor and a multi-core system has multiple trace components this seems to be an obvious way. However perhaps there are existing scripts that can be reused instead.
Activity
Trace configurations (#586)
Updates for settings for pyOCD Trace (#604)
Trace configuration updates (#395)
List of children for trace: node (#637)
jreineckearm commentedon Jul 17, 2026
Some minor details still in flight and will be extended with more functionality over time. But overall concept stands as documented by @ReinhardKeil here: https://open-cmsis-pack.github.io/cmsis-toolbox/Experimental-Features/#trace . Will move to a permanent documentation location later.