Coma FW-C2800 User's Guide Page 70

  • Download
  • Add to my manuals
  • Print
  • Page
    / 276
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 69
Instrumentation APIs
3-8
The LOG and STS APIs are also used internally by DSP/BIOS to collect
information about program execution. These internal calls in DSP/BIOS
routines provide implicit instrumentation support. As a result, even
applications that do not contain any explicit calls to the DSP/BIOS
instrumentation APIs can be monitored and analyzed using the DSP/BIOS
Analysis Tools. For example, the execution of a software interrupt is recorded
in a LOG object called LOG_system.
In addition, worst-case ready-to-completion times for software interrupts and
overall CPU load are accumulated in STS objects. The occurrence of a
system tick is also shown in the Execution Graph. See section 3.3.4.2,
Control of Implicit Instrumentation, page 3-16, for more information about
what implicit instrumentation can be collected.
3.3.2 Event Log Manager (LOG Module)
This module manages LOG objects, which capture events in real time while
the target program executes. You can use the Execution Graph, or view user-
defined logs orchestrated with the Configuration Tool.
User-defined logs contain any information your program stores in them using
the LOG_event and LOG_printf operations. You can view messages in these
logs in real time with the Message Log as shown in Figure 3-1. To access the
Message Log, select DSP/BIOS
Message Log.
Figure 3-1. Message Log Dialog Box
The Execution Graph, which is the system log, can also be viewed as a graph
of the activity for each program component.
A log can be either fixed or circular. This distinction is important in
applications that enable and disable logging programmatically (using the
TRC module operations as described in section 3.4.4, Trace Manager (TRC
Module), page 3-13).
Page view 69
1 2 ... 65 66 67 68 69 70 71 72 73 74 75 ... 275 276

Comments to this Manuals

No comments