We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I own a ULINK Pro. Managed to get ETM trace working on my STM32F4, but when I stop the CPU or run into a breakpoint, I can only look back about 1ms (at 168MHz) or about 2ms at 100MHz. How much I can see in the trace window seems to depend on the complexity of the code. More function calls or even function pointers seem to reduce the number of instructions.
It seems to me that I can not use streaming trace, but only the buffer in the ULINK Pro, which seems to be very small (around 64KB?) With streaming trace, the number of instructions should be unlimited since my harddrive can be used as buffer.
Any way to get streaming trace up and running?
It would be helpful if Bob Boys jumped in here to provide some definitive statement about the function and configuration of the trace modes.
One of the compelling cases for trace is a long term buffer that can run indefinitely and provide postmortem data about just how the heck the code got to where it is, and why.
As Sven points out, the STM32 family has a complete debug instantiated with the core. The STM3240G board has trace headers as I recall.
Bob Boys, where are you?
And again: Does ANYBODY HAVE STREAMING TRACE ACTUALLY WORKING ???
Does not seem like it. If not, I will probably have to use J-Trace from Segger and/or switch to another tool chain (Who? Do not want to use IAR ...) as I need a bigger trace buffer.