- This topic has 3 replies, 2 voices, and was last updated 8 hours, 37 minutes ago by
.
-
Posts
-
Hello,
I am trying to setup Hardware ARM Tracing on a STM32WB55.
I have setup the traceclk and the traceswo (async SWO using Manchester encoding). When attaching the logic analyser I see the clock and data-pin (traceclk and traceswo) working as expected.
Unforturenately, I dont see the trace in the Hardware Trace. I am using a J-Trace Pro Cortex-M and have tested (previously tested with the Cortex-M Trace Reference Board STM32F407).What should I do to get the data into VisualGDB?
Hi,
The hardware ARM tracing requires more pins than just traceclk/traceswo. Generally, the J-Trace documentation should explain all the necessary wiring and you can verify that it is working with the Segger Studio.
For VisualGDB integration, you can check this tutorial: https://visualgdb.com/tutorials/arm/tracing/traceback/
I have run the linked example with the segger evaluation board – it works like it should.
When running an example on the stm32wb55 I see trace data being transmitted, but it doesn’t show in visualGDB. I have both tried with traceclk + 4x data pins and traceclock + traceswo.
The pins are setup in code according to the reference manual. And TPI is setup as well.
Therfore I suspect that something is missing in the visualGDB setup.
In the example nothing is setup for trace to work other than ticking the hardware trace box in the visualGDB properties, but with stm32wb55 trace has to be setup in code too.
How can this be?
- You must be logged in to reply to this topic.