FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [May 2011 Threads] vtaskstarttrace and interpreting traceConPosted by jinx on May 18, 2011 Hi I am trying to put together a trace environment and need help interpreting the results. Basically I set up a project that calls vtaskstarttrace() function to start then creates a task with a predefined timeout which when it occurs stops the trace and then prints each byte of the trace buffer to the console window in my eclipse environment. I've redirected my console to save to a file, so then I run the ensuring binary file through tracecon to get me the results. I'm not sure what the results mean. The results below are the .txt file output....Could some help interpret the results?
Here is the .txt file (after it ran through traceCon): 808858460.00000012636 808858460.05000012636 808858460.05000012636 808858460.10000012636 808858460.10000012636 808858460.15000012636 808858460.15000012636 926363996.00000012636 926363996.00000013148 926363996.05000013148 926363996.05000013148 926363996.10000013148 926363996.10000013148 926363996.15000013148 926363996.15000013148 926363996.20000013148 926363996.20000013148 926363996.25000013148 926363996.25000013148 926363996.30000013148 926363996.30000013148 926363996.35000013148 926363996.35000013148 926363996.40000013148 926363996.40000013148 926363996.45000013148 926363996.45000013148 926363996.50000013148 926363996.50000013148 926363996.55000013148 926363996.55000013148 926363996.60000013148 926363996.60000013148 926363996.65000013148 926363996.65000013148 926363996.70000013148 926363996.70000012380 892482396.00000012380 892482396.00000023559 925981744.00000023559 925981744.00000023607 925981744.05000023607 925981744.05000023607 925981744.10000023607 925981744.10000023607 925981744.15000023607 925981744.15000023607 925981744.20000023607 925981744.20000023607 925981744.25000023607 925981744.25000023607 925981744.30000023607 925981744.30000023607 861669173.00000023607 861669173.00000012342 861681463.00000012342 861681463.00000012342 861681463.05000012342 861681463.05000012342 861681463.10000012342 861681463.10000012342 861681463.15000012342 861681463.15000012342 861681463.20000012342 861681463.20000012342 861681463.25000012342 861681463.25000012342 1543976759.00000012342 1543976759.00000013875 1547122481.00000013875 1547122481.00000013875 1547122481.05000013875 1547122481.05000013875 1547122481.10000013875 1547122481.10000014129 1546663475.00000014129 1546663475.00000014129 1546663475.05000014129 1546663475.05000014129 1546663475.10000014129 1546663475.10000014129 120926771.00000014129 120926771.00000013148 926363996.00000013148 926363996.00000013148 926363996.05000013148 926363996.05000013148 926363996.10000013148 926363996.10000012636 808858460.00000012636 808858460.00000012636 808858460.05000012636 808858460.05000012636 808858460.10000012636 808858460.10000012636 909335559.00000012636 909335559.00000023600 909335607.00000023600 909335607.00000023600 909335607.05000023600 909335607.05000023600 909335607.10000023600 909335607.1000003376 909335607.1500003376 909335607.15000023600 909335607.20000023600 909335607.20000023600 842226743.00000023600 842226743.0000001845 828125238.0000001845 828125238.00000014135 828125238.05000014135 828125238.05000014135 828125238.10000014135 828125238.10000014135 828125238.15000014135 828125238.15000014135 828125238.20000014135 828125238.20000014135 828125238.25000014135 828125238.25000014135 1546663475.00000014135 1546663475.00000014129 1546663475.05000014129 1546663475.05000014129 1546663475.10000014129 1546663475.10000014129 1546662448.00000014129 1546662448.00000012851 808858460.00000012851 808858460.00000012636 808858460.05000012636 808858460.05000012636 808858460.10000012636 808858460.10000012636 892482396.00000012636 892482396.00000023559 925981744.00000023559 925981744.00000023607 925981744.05000023607 925981744.05000023607
RE: vtaskstarttrace and interpreting traceConPosted by MEdwards on May 18, 2011 I think the first number is a time, and the second number the handle of the task that was running at that time. You can open it in a spread sheet and plot of graph.
But, that is a very old way of creating a trace. Look up the trace macros section on the FreeRTOS web site for a very flexible alternative that lets you trace nearly all kernel events.
RE: vtaskstarttrace and interpreting traceConPosted by jinx on May 19, 2011 I thought so too, until you look at the first column and realize that the numbers do not increase, they go up and down...
Is there a ready-made example that one can utilize to achieve the same results using the newer trace functions in the example files?
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|