Reading from cortex debug + ETM

Not tinkered with this in recent years, but the trace data is a fire-hose data source, so you need some means/method to capture it, and then to process it.

This isn't an olden days ICE type trace, but rather a reconstructive process where you're holding copies of the on board memories, and replicating transactions into a state model of the processor core.

I'd probably go with the pass-thru interposer method, and buffer into an FPGA or FIFO memory.

Perhaps find a different F4 board which you can get to the SWDIO, SWCLK and TRACE pins more directly?

Or a board exposing the pins?
www.segger.com/.../cortex-m-trace-reference-board-v1_2-3d-1000x.png

Not tinkered with this in recent years, but the trace data is a fire-hose data source, so you need some means/method to capture it, and then to process it.

This isn't an olden days ICE type trace, but rather a reconstructive process where you're holding copies of the on board memories, and replicating transactions into a state model of the processor core.

I'd probably go with the pass-thru interposer method, and buffer into an FPGA or FIFO memory.

Perhaps find a different F4 board which you can get to the SWDIO, SWCLK and TRACE pins more directly?

Or a board exposing the pins?
www.segger.com/.../cortex-m-trace-reference-board-v1_2-3d-1000x.png

This: www.segger.com/.../ ?

I have found this type of adaptor useful for adapting that kind of small connector up to 0.1" pitch:

uk.farnell.com/.../2476039

You could use a 2nd one to adapt back down again for a pass-through board ...

Relly helpful for me. I will buy this one www.segger.com/.../ for my connector to 0.1 pitc.