Event Recorder and Component Viewer
Version 1.5.1
MDK Debugger Views for Status and Event Information
|
The following steps enable the MDK debugger views for Event Statistics on timing, number of calls, and current consumption.
To use Event Statistics in the application code:
Event Execution Statistics functions may be placed throughout the application source code to measure execution performance between corresponding start and stop events:
The Event Statistics window shows collected data about execution time, number of calls, and (when using ULINKplus) the current consumption for each execution slot.
For the minimum and maximum time or current consumption it also shows for start and stop events the:
Each execution slot is identified by the function name group letter G = {A, B, C, D} and a slot number (0 to 15). Event filtering may be used to control the recording of each group. A call to EventStopG or EventStopGv with slot=15 stops measurement for all slots in a group and may be used at global exits of an execution block.
The following code is from the SCVD Event Statistics example project that is part of the Keil::ARM_Compiler pack:
Code example
Build and run the example project which uses the µVision simulator (available in all versions of MDK). In a debug session, Event Recorder, displays the following output:
The Event Statistics window shows the statistical data about the code execution:
For more information on the usage of the functions, refer to the Event Execution Statistics API.
Using a ULINKplus debug adapter, you can also record and analyze the energy that has been consumed in each execution slot. Using the above example on a hardware target with a ULINKplus, you get the following displays in the Event Statistics window (the Event Recorder window does not change):