Lines Matching refs:task
199 The stack monitoring runs in the Tracealyzer Control task, TzCtrl. This task
201 In snapshot mode, the TzCtrl task is only used for stack monitoring and is
220 each execution of the Tracealyzer Control task (TzCtrl). Note that the stack
222 are monitored, but HOW OFTEN each task stack is analyzed.
227 However, note that the stack analysis runs in a separate task (TzCtrl) that
254 The delay between loops of the TzCtrl task (see TRC_CFG_CTRL_TASK_PRIORITY),
268 The stack size of the Tracealyzer Control (TzCtrl) task.
327 (as User Events) from TzCtrl task, that monitors this.
343 (as User Events) from TzCtrl task, that monitors this.
351 The maximum number of object data entries (used for task priorities) that can
353 will be warnings (as User Events) from TzCtrl task, that monitors this.
394 context, i.e., a task or a preempted ISR. But if another traced ISR
452 task, queue, semaphore, ...).
475 task, queue, semaphore, ...).
498 task, queue, semaphore, ...).
521 task, queue, semaphore, ...).
544 task, queue, semaphore, ...).
567 task, queue, semaphore, ...).
590 task, queue, semaphore, ...).
613 task, queue, semaphore, ...).
636 task, queue, semaphore, ...).
801 - Blocking on "input" operations, i.e., when the task is waiting for the
856 "Unknown Actor" instead of task scheduling for periods with UB data only.
925 context, i.e., a task or a preempted ISR. But if another traced ISR