Runtime Object Viewer (ROV)
Instrumentation 3-11
not get an item at the last breakpoint, it has nothing to compare it to at the
current breakpoint. In short, if a field is not red, this does not necessarily
mean that the data did not change.
While the target is running, you may continue to explore ROV. Any data that
was retrieved at the last breakpoint is shown with a gray background. If data
was not retrieved, you see a "Target running..." message that indicates that
ROV cannot retrieve new data while the target is running.
ROV highlights errors by making the background red. Hover your mouse over
a field with a red background to see the error message. ROV can detect the
following types of errors:
❏ Validation errors. Modules can provide validation information for ROV.
For example, a particular structure field can have a maximum value of 32.
If the value on the target is 33, the module can report this as a problem.
❏ Memory. ROV may report bad memory accesses or other detectable
problems.
❏ ROV errors. ROV reports standard exceptions if a corrupted data from
the target causes ROV-related code in a module to behave incorrectly.
3.3.1 Tasks
The properties listed for tasks (TSK) are as follows:
❏ Name. The name of the task. The name is taken from the label for
statically-configured tasks and is generated for dynamically-created
tasks. The label matches the name in the configuration.
❏ Handle. The address of the task object header on the target.
❏ State. The current state of the task: Ready, Running, Blocked, or
Terminated.
❏ Priority. The task’s priority as set in the configuration or as set by the API.
Valid priorities are 0 through 15.
❏ Timeout. If blocked with a timeout, the clock value at which the task
alarm will occur.
❏ Time Remaining. Time remaining until the timeout expires.
❏ Blocked On. If blocked on a semaphore or mailbox, the name of the
SEM or MBX object the task is blocked on.
To Next Page
Loading...
Need help?
General
