Hello,
I could implement the trace to test.
In the example and the soft from percepio the Queue have a name. While in my test they have a name like “queue#1” in the percepio soft.
I think I did the right thing:
define configQUEUE_REGISTRY_SIZE 16
Hello,
I could implement the trace to test.
In the example and the soft from percepio the Queue have a name. While
in my test they have a name like “queue#1” in the percepio soft.
I think I did the right thing:
define configQUEUE_REGISTRY_SIZE 16
I have just tried this in FreeRTOS version 8, and in that version
calling vQueueAddToRegistry() will in turn call the
traceQUEUE_REGISTRY_ADD() macro, and the queue name as seen in the trace
is set within that macro.
The trace macros have been updated, and it is possible that in prior
versions you had to call vTraceSetQueueName() manually, although I don’t
recall having to do that.
Can you step through traceQUEUE_REGISTRY_ADD() in your debugger? In my
version I see it calling prvTraceGetObjectNumber(), then
prvTraceGetObjectType(), then vTraceSetObjectName() - with the name of
the queue being set in the call to vTraceSetObjectName().
Hello Dave,
You are right. But where to download V2.6?
Is the Tracealyzer-Linux-v2.6.0.exe works? The last one for FreeRTOS on the Percepio website is V2.5…
Hi all,
Johan at Percepio here. I just want to emphasize that FreeRTOS v8 comes with an updated trace recorder for FreeRTOS+Trace v2.6. Traces from this recorder does not work in FreeRTOS+Trace v2.5 or earlier, but the updated version of FreeRTOS+Trace has not been released yet. Unfortunately this was delayed one week more as we have decided to make some additional changes. It should be out on Friday (March 7th).
The upside is several new features. This is the largest update since v2.3 and includes better support for timers, tracing of dynamic memory allocation and full support for FreeRTOS v8, including the new Event Group objects.