• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 399 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/MSP432P401R: TI-RTOS Execution Graph - is there an easy way to "mark" the graph with a line/symbol with an API call to UIA via my code?

Eric Wilbur
Intellectual 770 points

Part Number: MSP432P401R

Tool/software: TI-RTOS

In code, I can do a printf() to say "I am here" or "this event happened" or "I entered this function". The output is on the console window....but what about the same "marker" occurring on the Execution Graph?

It would be great to have an API call in UIA that would "print" or "mark" the Execution Graph to do the same thing. Tracking HWIs or other high-freq events requires a large RAM buffer. Instead, it would be very helpful to indicate an event with a Log event (or error message or Log_info) that printed something graphically on the Execution graph that I (or any user) could call in code.

Is there an API call in UIA that indicates a "mark" or "symbol" on the graph that says "I am here"??

In the old days, I think there was a Log_error (or some assertion) that made this happen. Maybe that doesn't exist any longer. I am just curious. Because sometimes, just tracking events via SWI, HWI, Semaphores, Task context switch, etc. is not enough or requires a large RAM storage that is not practical. Having an API I can call when I need to in code to indicate an event would be very helpful.

Does this capability exist in UIA and TI-RTOS? If so, is it universal to Simplelink, C6000, Cortex A8 and C2000?

  • 0
    TI__Expert 8510 points

    The UIA Logging Setup Twiki has some references that may offer what you are looking for.

    Several possibilities for logging  events are:

    1. Semaphores- Depending on your usage, dummy semaphores might suffice, but without the ability to define a text label
    2. Count Analysis -not on Execution graph, but you can use this to see how variables change over time
    3. Function Profiling- though this needs an "entry" and "exit" point. Generates Stats but not on the Execution graph
    4. "Snapshot Events" feature (see the main UIA Twiki page for a description)

    You can combine items 2,3 above with the Execution graph by grouping views as described in this page.

    For completeness, Here's the link to the System Analyzer User's Guide. Section 1.3.1. states:

    The UIA and xdc.runtime.Log APIs can be used in your C or C++ code directly to log software events
    to instrument your application code. You don't have to write RTSC modules; just #include the
    appropriate header files in your software and call the provided APIs. Examples are provided in
    Section 5.4 as well as in the help files that ship with the UIA target content.

    Hope that helps.

    -Bob 

  • 0 in reply to Bob Landers
    Intellectual 770 points

    Thanks Bob. I use grouping in the workshop I teach to sync the system log to the graph and that is helpful. I think your idea about using a dummy semaphore is a decent choice. It puts a flag on the graph and semaphore_post() is not a heavy function call. I use Log_info often as a replacement for printf() and it works well - but nothing goes to the graph. A semaphore flag just might do the trick.

    Thanks for your response. Very helpful.

**Attention** This is a public forum