Measure core run time
In this topic:
•Understanding Run Duration values
TL;DR
To monitor how long a core runs, open Session Explorer and check the Run Duration column.
You can monitor how long each core has been running or was running before it stopped.
Overview
Run duration measurement allows you to observe core run duration using iC7 BlueBox in winIDEA.
Use cases
Use this feature when:
•Measure the function execution time using the step-over command
oImmediately see how long a function takes to execute without setting up complex measurement systems. This allows you to identify bottlenecks instantly during a debug session.
•Measure the run time between breakpoints
oMeasure the time elapsed between any two points in your code. Use this to verify that desired code segments are meeting their timing constraints.
•Real-time run time
oMonitor the run time of your core in a real-time without halting the execution.
Requirements
This feature is available with:
•iC7 BlueBox
•winIDEA Pro license
Steps
Follow these steps to monitor run duration.
Step 1: Enable high accuracy measurement
The run duration measurement is always enabled, but accuracy is highly improved.
1. Open Hardware > SoC Options > Cores.
2. Enable Always use high accuracy status.
To get better performance, refer to Accuracy considerations.
Step 2: Open Session Explorer
1. Navigate to View > Debug > Session Explorer.
2. Locate the Run Duration column.
Understanding Run Duration values
The displayed value depends on the core state:
•Running
oReal-time duration from the last run operation
oWhen hot attaching to the running SoC, duration from the attach operation
•Stopped
oDuration of the last run period
For more information about the run duration values, refer to Session Explorer.
How measurement works
BlueBox calculates run duration using internal timestamps:
•Stores timestamp when:
oRun or stop is triggered from winIDEA
oCore state changes (running → stopped)
•Continuously monitors core state while running
•Calculates duration from collected timestamps
Accuracy considerations
Measurement accuracy depends on several factors:
•High accuracy mode (recommended)
oEnable option Always use high accuracy status in Hardware > SoC Options > Cores
•Debug interface clock speed
oIncrease the debug clock to max possible in Hardware > SoC Options > SoC
•Number of observed cores
oDisable option Automatically observe this core in Hardware > SoC Options > Cores for cores not monitored for run duration
•Device-specific debug interface implementation
•Use of other features in winIDEA, e.g. real-time memory updates, DAQ, etc.
Validation
Verify that run duration is working.
1.Run the core.
2.Stop execution.
3.Check Run Duration.
Expected result:
•A time value is displayed (not N/A)
•Value updates when execution state changes
More resources
