RTOS Debugger for RTXC Quadros

RTOS Debugger for RTXC Quadros TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents... RTOS Debuggers... RTOS Debugger for RTXC Quadros... 1 Overview... 3 Brief Overview of Documents for New Users... 4 Supported Versions... 4 Configuration... 5 Manual Configuration 5 Automatic Configuration 5 Quick Configuration Guide 6 Hooks & Internals in RTXC Quadros 6 Features... 7 Terminal Emulation 7 Display of Kernel Resources 7 Task Stack Coverage 8 Task Related Breakpoints 8 Task Context Display 9 Dynamic Task Performance Measurement 9 Task Runtime Statistics 10 Function Runtime Statistics 11 Task State Analysis 12 RTXC Quadros specific Menu 14 RTXC Quadros Commands... 15 TASK.ALaRm Display alarms 15 TASK.CouNTer Display counters 16 TASK.EVenT Display event sources 17 TASK.EXCeption Display exceptions 17 TASK.LeVeL Display levels 18 TASK.MailBoX Display mailboxes 19 TASK.MuTeX Display mutex 19 TASK.PaRTition Display partitions 20 TASK.PIPe Display pipes 20 TASK.QUEue Display queues 21 RTOS Debugger for RTXC Quadros 1

TASK.SEMaphore Display semaphores 21 TASK.TaSK Display tasks 22 TASK.THRead Display threads 23 RTXC Quadros PRACTICE Functions... 24 Frequently-Asked Questions... 26 RTOS Debugger for RTXC Quadros 2

RTOS Debugger for RTXC Quadros Version 29-Mar-2017 Overview B::TASK.THRead magic # name currlvl baselvl order runs entry 00400640 1. THREAD1 1. 1. 1. 78. 00020144 00400670 2. THREAD2 1. 1. 2. 78. 0002015C 004006A0 3. THREAD3 1. 1. 3. 0. 0002016C 004006D0 4. THREAD4 2. 2. 1. 0. 00020174 00400700 5. THREAD5 2. 2. 2. 0. 0002017C 00400730 B::TASK.Task magic # name prio entry state 004007E0 1. EXAMPLE1 5. 000201A8 ready 0040081C 2. EXAMPLE2 6. 00020254 alarm 00400858 3. EXAMPLE3 7. 000202DC acknowledge 00400894 4. EXAMPLE4 8. 00020324 sleep 004008D0 5. EXAMPLE5 9. 00020384 alarm 0040090C 6. ECHOTASK 10. 00020430 queue 00400948 7. CONITASK 3. 00023608 semaphore The RTOS Debugger for RTXC Quadros contains special extensions to the TRACE32 Debugger. This manual describes the additional features, such as additional commands and statistic evaluations. RTXC Quadros uses the terms threads and tasks. If not otherwise specified, the TRACE32 term Task corresponds to RTXC Quadros (multi-stack) tasks. RTOS Debugger for RTXC Quadros 3 Overview

Brief Overview of Documents for New Users Architecture-independent information: Debugger Basics - Training (training_debugger.pdf): Get familiar with the basic features of a TRACE32 debugger. T32Start (app_t32start.pdf): T32Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger. T32Start is only available for Windows. General Commands (general_ref_<x>.pdf): Alphabetic list of debug commands. Architecture-specific information: Processor Architecture Manuals : These manuals describe commands that are specific for the processor architecture supported by your debug cable. To access the manual for your processor architecture, proceed as follows: - Choose Help menu > Processor Architecture Manual. RTOS Debugger (rtos_<x>.pdf): TRACE32 PowerView can be extended for operating systemaware debugging. The appropriate RTOS manual informs you how to enable the OS-aware debugging. Supported Versions Currently RTXC Quadros is supported for the following versions: RTXC Quadros (ms and ss) V1.0 on ARM, C167, ColdFire, PowerPC, StarCore and TMS320C55xx. RTOS Debugger for RTXC Quadros 4 Brief Overview of Documents for New Users

Configuration The TASK.CONFIG command loads an extension definition file called quadros.t32 (directory demo/ <processor>/kernel/quadros ). It contains all necessary extensions. Automatic configuration tries to locate the RTXC Quadros internals automatically. For this purpose all symbol tables must be loaded and accessible at any time the RTOS debugger is used. If a system symbol is not available or if another address should be used for a specific system variable then the corresponding argument must be set manually with the appropriate address. In this case, use the manual configuration, which can require some additional arguments. If you want to have dual port access for the display functions (display On The Fly ), you have to map emulation or shadow memory to the address space of all used system tables. Manual Configuration Manual configuration is not necessary for the RTXC Quadros RTOS debugger. If the automatic configuration fails due to missing symbols, contact LAUTERBACH for assistance. Automatic Configuration For system resource display, you can do an automatic configuration of the RTOS debugger. For this purpose it is necessary, that all system internal symbols are loaded and accessible at any time, the RTOS debugger is used. Each of the task.config arguments can be substituted by '0', which means, that this argument will be searched and configured automatically. For a full automatic configuration omit all arguments: TASK.CONFIG quadros If a system symbol is not available, or if another address should be used for a specific system variable, then the corresponding argument must be set manually with the appropriate address (see Manual Configuration). See also Hooks & Internals for details on the used symbols. RTOS Debugger for RTXC Quadros 5 Configuration

Quick Configuration Guide To get a quick access to the features of the RTXC Quadros RTOS debugger with your application, follow the following roadmap: 1. Copy the files quadros.t32 and quadros.men to your project directory (from TRACE32 directory demo/<processor>/kernel/quadros ). 2. Start the TRACE32 Debugger. 3. Load your application as normal. 4. Execute the command TASK.CONFIG quadros (See Automatic Configuration ). 5. Execute the command MENU.ReProgram quadros (See RTXC Quadros Specific Menu ). 6. Start your application. Now you can access the RTXC Quadros extensions through the menu. In case of any problems, please read carefully the previous configuration chapters. Hooks & Internals in RTXC Quadros No hooks are used in the kernel. For retrieving the kernel data structures, the RTOS debugger uses the global kernel symbols and structure definitions. Ensure, that access to those structures is possible, every time when features of the RTOS debugger are used. The RTXC Quadros kernel must be compiled with debug information. RTOS Debugger for RTXC Quadros 6 Configuration

Features The RTOS debugger for RTXC Quadros supports the following features. Terminal Emulation The terminal emulation window can be used to communicate with the target side terminal I/O. The communication is done via two memory buffers, requiring no external interface. See the TERM command for a description of the terminal emulation. On request we can provide you with the source code for the target interface routines for RTXC Quadros. Display of Kernel Resources The extension defines new PRACTICE commands to display various kernel resources. Information on the following RTXC Quadros components can be displayed: TASK.TaSK TASK.SEMaphore TASK.MailBoX TASK.PaRTition TASK.QUEue TASK.MuTeX TASK.PIPe TASK.THRead TASK.LeVeL TASK.EVenT TASK.CouNTer TASK.ALaRm TASK.EXCeption Tasks Semaphores Mailboxes Partitions Queues Mutexes Pipes Threads Levels Event sources Counters Alarms Exceptions For a detailed description of each command refer to the chapter RTXC Quadros Commands. When working with emulation memory or shadow memory, these resources can be displayed On The Fly, i.e. while the target application is running, without any intrusion to the application. If using this dual port memory feature, be sure that emulation memory is mapped to all places, where RTXC Quadros holds its tables. When working only with target memory, the information will only be displayed, if the target application is stopped. RTOS Debugger for RTXC Quadros 7 Features

Task Stack Coverage For stack usage coverage of RTXC Quadros tasks, you can use the TASK.STacK command. Without any parameter, this command will set up a window with all active RTXC Quadros tasks. If you specify only a magic number as parameter, the stack area of this task will be automatically calculated. To use the calculation of the maximum stack usage, flag memory must be mapped to the task stack areas, when working with the emulation memory. When working with the target memory, a stack pattern must be defined with the command TASK.STacK.PATtern (default value is zero). To add/remove one task to/from the task stack coverage, you can either call the TASK.STacK.ADD rsp. TASK.STacK.ReMove commands with the task magic number as parameter, or omit the parameter and select from the task list window. It is recommended, to display only the tasks, that you are interested in, because the evaluation of the used stack space is very time consuming and slows down the debugger display. RTXC Quadros maintains a kernel stack, that is intended to be used whenever no task is running. You can add the coverage of the kernel stack with the following command: TASK.STacK.ADD 1 However, it depends to the system startup, if this stack is used, and if it is initialized with a pattern. If one of these prerequisites is not given, the stack coverage for the kernel stack will fail. Please check accordingly. Task Related Breakpoints Any breakpoint set in the debugger can be restricted to fire only, if a specific task hits that breakpoint. This is especially useful, when debugging code which is shared between several tasks. To set a task related breakpoint, use the command: Break.Set <address> <range> [/<option>] /TASK <task> Use a task magic, ID or name for <task>. This task related breakpoint is implemented by a conditional breakpoint inside the debugger. I.e., the target will always halt at that breakpoint, but the debugger immediately resumes execution, if the current running task is not equal to the specified task. Please note, that this feature impacts the real-time behavior of the application. For a general description of the Break.Set command please see its documentation. RTOS Debugger for RTXC Quadros 8 Features

Task Context Display You are able to switch the whole viewing context to a currently not executing task. This means, that all register and stack related information (such as Register, Data.List, Frame etc.) will be shown according to this task. Be aware that this is only for displaying information. When continuing debugging the application (Step or Go), the debugger will switch back to the current context. For displaying a specific task context, use the command: Frame.TASK [<task>] Display task context. Specify a task magic or a task name (in double quotes) as parameter. To switch back to the current context, omit all parameters. For displaying the call stack of a specific task, you can use the following command: Frame /Task <task> Display call stack of a task. If you d like to see the application code, where the task was preempted, execute the command Frame /Caller /Task <task> to open a window of the same name. Double click on the line showing the OS service call. Dynamic Task Performance Measurement The debugger may execute a dynamic performance measurement by evaluating the current running task in changing time intervals. Start the measurement with the commands PERF.Mode TASK and PERF.Arm, and view the contents with PERF.ListTASK. The evaluation is done by reading the magic location (= current running task) in memory. This memory read may be non-intrusive or intrusive, depending on the PERF.METHOD used. If PERF collects the PC for function profiling of processes in MMU based operating systems (SYStem.Option MMUSPACES ON), then you need to set PERF.MMUSPACES, too. For a general description of the PERF command, refer to General Commands Reference Guide P (general_ref_p.pdf). RTOS Debugger for RTXC Quadros 9 Features

Task Runtime Statistics NOTE: This feature is only available, if your debugger equipment is able to trace task switches (see below). Out of the recordings done by the Trace (if available), the debugger is able to evaluate the time spent in a task and display it statistically and graphically. To do this, the debugger must be able to detect the task switches out of the trace, i.e. the task switches need to be recorded. Usually, there s a variable in the system that holds the current running task. By recording the accesses to this memory location (aka magic location), the debugger detects a task switch by a change of this variable. Please note, that the debugger equipment must be able to trace memory data accesses in this case, program flow trace is not sufficient. If a hardware trace solution is available, that provides a so-called context ID (e.g. ARM11 ETM), and if this context ID is served by the operating system, it is sufficient to enable the recording of the context ID (owner cycle); no data trace is needed. To do a selective recording on task switches with state analyzers (ICE and FIRE), use the following PRACTICE commands: ; Mark the magic location with an Alpha breakpoint Break.Set TASK.CONFIG(magic)++(TASK.CONFIG(magicsize)-1) /Alpha ; Program the Analyzer to record only task switches Analyzer.ReProgram ( Sample.Enable if AlphaBreak&&Write ) To do a selective recording on task switches with flow traces (ICD, e.g. ETM and NEXUS trace), based on the data accesses, use the following PRACTICE command: ; Enable tracing only on the magic location Break.Set TASK.CONFIG(magic) /TraceEnable To do a selective recording on task switches with flow traces, based on the context ID, use the following PRACTICE command: ; Enable tracing of the context ID (e.g. 32bit) ETM.ContextID 32 RTOS Debugger for RTXC Quadros 10 Features

To evaluate the contents of the trace buffer, use these commands: Trace.List List.TASK DEFault Trace.STATistic.TASK Trace.Chart.TASK Trace.PROfileSTATistic.TASK Trace.PROfileChart.TASK Trace.FindAll Address task.config(magic) Trace.FindAll CYcle owner OR CYcle context Display trace buffer and task switches Display task runtime statistic evaluation Display task runtime timechart Display task runtime within fixed time intervals statistically Display task runtime within fixed time intervals as colored graph Display all data access records to the magic location Display all context ID records The start of the recording time, when the calculation doesn t know, which task is running, is calculated as (unknown). Function Runtime Statistics NOTE: This feature is only available, if your debugger equipment is able to trace memory data accesses (program flow trace is not sufficient). All function related statistic and timechart evaluations can be used with task specific information. The function timings will be calculated dependent on the task, that called this function. To do this, additionally to the function entries and exits, the task switches must be recorded. To do a selective recording on task related function runtimes with state analyzers (ICE and FIRE), use the following PRACTICE commands: ; Mark the magic location with an Alpha breakpoint Break.Set TASK.CONFIG(magic)++(TASK.CONFIG(magicsize)-1) /Alpha ; Mark the function entries/exits with Alpha/Beta breakpoints Break.SetFunc ; Program the Analyzer to record function entries/exits and task switches Analyzer.ReProgram ( Sample.Enable if AlphaBreak BetaBreak Mark.A if AlphaBreak Mark.B if BetaBreak ) RTOS Debugger for RTXC Quadros 11 Features

To do a selective recording on task related function runtimes with flow traces (ICD, e.g. ETM and NEXUS trace), based on the data accesses, use the following PRACTICE command: ; Enable flow trace an accesses to the magic location Break.Set TASK.CONFIG(magic) /TraceData To do a selective recording on task related function runtimes with flow traces, based on the context ID, user the following PRACTICE command: ; Enable flow trace with context ID (e.g. 32bit) ETM.ContextID 32 To evaluate the contents of the trace buffer, use these commands: Trace.ListNesting Trace.STATistic.Func Trace.STATistic.TREE Trace.STATistic.sYmbol /SplitTASK Trace.Chart.Func Trace.Chart.sYmbol /SplitTASK Display function nesting Display function runtime statistic Display functions as call tree Display flat runtime analysis Display function timechart Display flat runtime timechart The start of the recording time, when the calculation doesn t know, which task is running, is calculated as (unknown). Task State Analysis NOTE: This feature is only available, if your debugger equipment is able to trace memory data accesses (program flow trace is not sufficient). The time different tasks are in a certain state (running, ready, suspended or waiting) can be evaluated statistically or displayed graphically. This feature needs recording of all accesses to the status words of all tasks. Additionally, the accesses to the current task pointer (=magic) are needed. Adjust your trace logic to record all data write accesses, or limit the recorded data to the area where all TCBs are located (plus the current task pointer). To do a selective recording on task states with state analyzers (ICE or FIRE), use TASK.TASKState, if available, to mark the status words with Alpha breakpoints. Run the following PRACTICE script: RTOS Debugger for RTXC Quadros 12 Features

; Mark the magic location with an Alpha breakpoint Break.Set task.config(magic)++(task.config(magicsize)-1) /Alpha ; Mark all task state words with Alpha breakpoints TASK.TASKState ; Program the Analyzer to record task state transitions Analyzer.ReProgram ( Sample.Enable if AlphaBreak&&Write ) To do a selective recording on task states with flow traces (ICD, e.g. ETM and NEXUS trace), just enable the recording of all data write cycles. To evaluate the contents of the trace buffer, use these commands: Trace.STATistic.TASKState Trace.Chart.TASKState Display task state statistic Display task state timechart The start of the recording time, when the calculation doesn t know, which task is running, is calculated as (unknown). All kernel activities up to the task switch are added to the calling task. RTOS Debugger for RTXC Quadros 13 Features

RTXC Quadros specific Menu The file quadros.men contains an alternate menu with RTXC Quadros specific topics. Load this menu with the MENU.ReProgram command. You will find a new pull-down menu called Quadros. The Display topics launch the kernel resource display windows. The Stack Coverage submenu starts and resets the RTXC Quadros specific stack coverage, and provides an easy way to add or remove tasks from the stack coverage window. The Trace pull-down menu is extended. In the List submenu, you can choose for an trace list window showing only task switches (if any) or task switches together with default display. The 'Perf' menu contains additional submenus for task runtime statistics and statistics on task states. RTOS Debugger for RTXC Quadros 14 Features

RTXC Quadros Commands TASK.ALaRm Display alarms TASK.ALaRm [<alarm>] Displays the alarm table of RTXC Quadros or detailed information about one specific alarm. Without any arguments, a table with all created alarms will be shown. Specify an alarm name, ID or magic number to display detailed information on that alarm. B::TASK.ALaRm magic # name state counter remain initial cyclic waiters action 004010D8 1. SALARM1 active COUNTER1 12500. 25000. 0. 1. <no action> 00401118 2. SALARM2 active COUNTER1 500. 500. 500. 0. ScheduleThread 00401158 3. SALARM3 active COUNTER1 2500. 5000. 0. 1. <no action> B::TASK.ALaRm 0x4010D8 magic # name state counter remain initial cyclic waiters action 004010D8 1. SALARM1 active COUNTER1 12500. 25000. 0. 1. <no action> waiting tasks 0040081C EXAMPLE2 expired semaphore: aborted semaphore: magic is a unique ID, used by the RTOS Debugger to identify a specific alarm (address of the alarm control structure). The fields magic and waiting tasks are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 15 RTXC Quadros Commands

TASK.CouNTer Display counters TASK.CouNTer [<counter>] Displays the counter table of RTXC Quadros or detailed information about one specific counter. Without any arguments, a table with all created counters will be shown. Specify a counter name, ID or magic number to display detailed information on that counter. B::TASK.CouNTer magic # name accumulator event src count modulus 0040100C 1. COUNTER1 58000. EVNTSRC1 1. 1. 00401030 2. COUNTER2 29000. EVNTSRC1 2. 2. 00401054 3. COUNTER3 0. EVNTSRC2 1. 1. 00401078 4. COUNTER4 0. EVNTSRC2 2. 2. B::TASK.CouNTer "COUNTER1" magic # name accumulator event src count modulus 0040100C 1. COUNTER1 58000. EVNTSRC1 1. 1. alarm object remain initial cyclic action waiters 00401118 SALARM2 500. 500. 500. ScheduleThread 00401158 SALARM3 2500. 5000. 0. <no action> 004010D8 SALARM1 12500. 25000. 0. <no action> magic is a unique ID, used by the RTOS Debugger to identify a specific counter (address of the counter control structure). The fields magic and alarm are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 16 RTXC Quadros Commands

TASK.EVenT Display event sources TASK.EVenT [<event>] Displays the event source table of RTXC Quadros or detailed information about one specific event source. Without any arguments, a table with all created event sources will be shown. Specify a event source name, ID or magic number to display detailed information on that event source. B::TASK.EVenT magic # name accumulator 00400FA4 1. EVNTSRC1 58000. 00400FB0 2. EVNTSRC2 0. 00400FBC 3. <not in use> B::TASK.EVenT "EVNTSRC1" magic # name accumulator 00400FA4 1. EVNTSRC1 58000. counter name accumulator count modulus 0040100C COUNTER1 58000. 1. 1. 00401030 COUNTER2 29000. 2. 2. magic is a unique ID, used by the RTOS Debugger to identify a specific event source (address of the event source control structure). The fields magic and counter are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. TASK.EXCeption Display exceptions TASK.EXCeption Displays a table with all created exceptions of RTXC Quadros. B::TASK.EXCeption magic # name level vector previous 00401284 1. TMR0ISR 2. 119. 00000000 00401290 2. UART0ISR 1. 77. 00000000 0040129C 3. <not in use> magic is a unique ID, used by the RTOS Debugger to identify a specific exception (address of the exception control structure). RTOS Debugger for RTXC Quadros 17 RTXC Quadros Commands

TASK.LeVeL Display levels TASK.LeVeL [<level>] Displays the level table of RTXC Quadros or detailed information about one specific level. Without any arguments, a table with all created levels will be shown. Specify a level name, ID or magic number to display detailed information on that level. B::TASK.LeVeL magic # name static dynamic method 004005BC 1. LEVEL1 3. 0. priority 004005D8 2. LEVEL2 3. 0. priority B::TASK.LeVeL "LEVEL1" magic # name static dynamic method 004005BC 1. LEVEL1 3. 0. priority curr thread : level : order <none> scheduled threads : level : order magic is a unique ID, used by the RTOS Debugger to identify a specific level (address of the level control structure). The fields magic and thread are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 18 RTXC Quadros Commands

TASK.MailBoX Display mailboxes TASK.MailBoX [<mailbox>] Displays the mailbox table of RTXC Quadros or detailed information about one specific mailbox. Without any arguments, a table with all created mailboxes will be shown. Specify a mailbox name, ID or magic number to display detailed information on that mailbox. B::TASK.MailBoX magic # name current order usage waiters 00400C30 1. SMBOX1 1. prio 29. 0. B::TASK.MailBoX "SMBOX1" magic # name current order usage waiters 00400C30 1. SMBOX1 1. prio 29. 0. message prio task state address message urgent EXAMPLE3 0. 00400044 Message from Exa waiting tasks magic is a unique ID, used by the RTOS Debugger to identify a specific mailbox (address of the mailbox control structure). The fields magic, address and waiting tasks are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. TASK.MuTeX Display mutex TASK.MuTeX [<mutex>] Displays the mutex table of RTXC Quadros or detailed information about one specific mutex. Without any arguments, a table with all created mutexes will be shown. Specify a mutex name, ID or magic number to display detailed information on that mutex. B::TASK.MuTeX magic # name level order invers owner usage conflicts waiters 00400DB4 1. CONAMUTX 0. prio no 00000000 139. 0. 0. 00400DD8 2. CONBMUTX 0. prio no 00000000 0. 0. 0. 00400DFC 3. <not in use> 00400E20 4. <not in use> magic is a unique ID, used by the RTOS Debugger to identify a specific mutex (address of the mutex control structure). The fields magic, owner and waiting tasks are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 19 RTXC Quadros Commands

TASK.PaRTition Display partitions TASK.PaRTition [<partition>] Displays the partition table of RTXC Quadros or detailed information about one specific partition. Without any arguments, a table with all created partitions will be shown. Specify a partition name, ID or magic number to display detailed information on that partition. B::TASK.PaRTition magic # name address avail total bsize order usage worst waiters 00400C78 1. SPART1 00400044 1. 2. 00000020 prio 1. 29. 0. magic is a unique ID, used by the RTOS Debugger to identify a specific partition (address of the partition control structure). The fields magic, address and waiting tasks are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. TASK.PIPe Display pipes TASK.PIPe [<pipe>] Displays the pipe table of RTXC Quadros or detailed information about one specific pipe. Without any arguments, a table with all created pipes will be shown. Specify a pipe name, ID or magic number to display detailed information on that pipe. B::TASK.PIPe magic # name full empty nbufs bsize worst usage 004011D0 1. SPIPE1 0. 2. 2. 8. 0. 0. 00401210 2. SPIPE2 0. 2. 2. 16. 0. 0. B::TASK.PIPe "SPIPE1" magic # name full empty nbufs bsize worst usage 004011D0 1. SPIPE1 0. 2. 2. 8. 0. 0. put full action: put free action: TS Sched <no action> full buffers size free buffers 004000D4 004000DC magic is a unique ID, used by the RTOS Debugger to identify a specific pipe (address of the pipe control structure). The fields magic, full buffers and free buffers are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 20 RTXC Quadros Commands

TASK.QUEue Display queues TASK.QUEue [<queue>] Displays the queue table of RTXC Quadros or detailed information about one specific queue. Without any arguments, a table with all created queues will be shown. Specify a queue name, ID or magic number to display detailed information on that queue. < B::TASK.QUEue magic # name address current depth width order usage worst waiters 00400CCC 1. CONAIQ 00402770 0. 16. 1. prio 0. 0. 1. 00400CFC 2. CONAOQ 00402730 0. 64. 1. prio 0. 4973. 1. 00400D2C 3. CONBIQ 00402720 0. 16. 1. prio 0. 0. 0. 00400D5C 4. CONBOQ 004026E0 0. 64. 1. prio 0. 0. 0. magic is a unique ID, used by the RTOS Debugger to identify a specific queue (address of the queue control structure).< The fields magic, address and waiting tasks are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. TASK.SEMaphore Display semaphores TASK.SEMaphore [<semaphore>] Displays the semaphore table of RTXC Quadros or detailed information about one specific semaphore. Without any arguments, a table with all created semaphores will be shown. Specify a semaphore name, ID or magic number to display detailed information on that semaphore. B::TASK.SEMaphore magic # name state count sig type order usage waiters 00400A3C 4. CONBOSEM pend 0. single prio 0. 0. 00400A58 5. EXAMSEM0 pend 0. single prio 1. 0. 00400A74 6. EXAMSEM1 pend 0. single prio 1. 0. 00400A90 7. EXAMSEM2 pend 0. single prio 0. 0. 00400AAC 8. EXAMSEM3 pend 0. single prio 1. 0. 00400AC8 9. <not in use> B::TASK.SEMaphore 0x4009E8 magic # name state count sig type order usage waiters 004009E8 1. CONAISEM wait 0. single prio 0. 1. waiting tasks 00400948 CONITASK magic is a unique ID, used by the RTOS Debugger to identify a specific semaphore (address of the semaphore control structure). The fields magic and waiting tasks are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 21 RTXC Quadros Commands

TASK.TaSK Display tasks TASK.TaSK [<task>] Displays the task table of RTXC Quadros or detailed information about one specific task. Without any arguments, a table with all created tasks will be shown. Specify a task name, ID or magic number to display detailed information on that task. B::TASK.TaSK magic # name prio entry arg addr state 004007E0 1. EXAMPLE1 5. 000201A8 00000000 ready 0040081C 2. EXAMPLE2 6. 00020254 00000000 alarm 00400858 3. EXAMPLE3 7. 000202DC 00000000 acknowledge 00400894 4. EXAMPLE4 8. 00020324 00000000 sleep 004008D0 5. EXAMPLE5 9. 00020384 00000000 alarm 0040090C 6. ECHOTASK 10. 00020430 00000000 queue 00400948 7. CONITASK 3. 00023608 00000000 semaphore 00400984* 8. CONOTASK 4. 00023634 00000000 current B::TASK.TaSK "EXAMPLE4" magic # name prio entry arg addr state 00400894 4. EXAMPLE4 8. 00020324 00000000 sleep task abort semaphore EXAMSEM2 magic is a unique ID, used by the RTOS Debugger to identify a specific task (address of the task control structure). The fields magic, entry and arg addr are mouse sensitive, double clicking on them opens appropriate windows. Right clicking on them will show a local menu. Pressing the context button (if available) changes the register context to this task. current resets it to the current context. See Task Context Display. RTOS Debugger for RTXC Quadros 22 RTXC Quadros Commands

TASK.THRead Display threads TASK.THRead [<thread>] Displays the thread table of RTXC Quadros or detailed information about one specific thread. Without any arguments, a table with all created threads will be shown. Specify a thread name, ID or magic number to display detailed information on that thread. B::TASK.THRead magic # name currlvl baselvl order runs entry 00400640 1. THREAD1 1. 1. 1. 116. 00020144 00400670 2. THREAD2 1. 1. 2. 116. 0002015C 004006A0 3. THREAD3 1. 1. 3. 0. 0002016C 004006D0 4. THREAD4 2. 2. 1. 0. 00020174 00400 00400 B::TASK.THRead "THREAD5" magic # name currlvl baselvl order runs entry 00400700 5. THREAD5 2. 2. 2. 0. 0002017C argument addr environment addr 00000000 00000000 gate key preset 00000000 00000000 magic is a unique ID, used by the RTOS Debugger to identify a specific thread (address of the thread control structure). The fields magic, entry and addr are mouse sensitive. Double-clicking on them opens appropriate windows. Right clicking on them will show a local menu. RTOS Debugger for RTXC Quadros 23 RTXC Quadros Commands

RTXC Quadros PRACTICE Functions There are special definitions for RTXC Quadros specific PRACTICE functions. TASK.CONFIG(magicms) TASK.CONFIG(magicss) TASK.CONFIG(magic) Returns the address for the multi-stack magic (= address of the current running task) Returns the address for the single-stack magic (= address of the current running thread) If the application is a multi-stack or dual-mode system, the multi-stack magic is returned, otherwise the singlestack magic is returned. TASK.CONFIG(magicsize) Returns the size of the magic number (1, 2 or 4) TASK.VERSION(<item>) TASK.VERSION(rtos) TASK.VERSION(cpufamily) TASK.VERSION(date) Reports awareness version information Returns the OS name this awareness is for Returns the CPU family name this awareness is for Returns the compile date of this awareness TASK.TASK.LIST(<taskmagic>) TASK.TASK.NAME(<taskmagic>) TASK.TASK.ID2MAGIC(<taskid>) Returns the next magic in the task list. Specify zero for the first task. Returns zero in no further task is available. Returns the name of the specified task Returns the magic of a given task ID TASK.THREAD.LIST(<threadmagic>) TASK.THREAD.NAME(<thrmagic>) TASK.THREAD.ID2MAGIC(<thrid>) Returns the next magic in the thread list. Specify zero for the first thread. Returns zero in no further thread is available. Returns the name of the specified thread Returns the magic of a given thread ID RTOS Debugger for RTXC Quadros 24 RTXC Quadros PRACTICE Functions

TASK.SEMAPHORE.LIST (<magic>) TASK.SEMAPHORE.NAME(<magic>) TASK.SEMAPHORE.ID2MAGIC(<id>) TASK.SEMAPHORE.STATE (<magic>) TASK.SEMAPHORE.COUNT (<magic>) TASK.SEMAPHORE.WAITERS. COUNT(<magic>) TASK.SEMAPHORE.WAITERS. LIST(<magic>,<taskmagic>) Returns the next magic in the semaphore list. Specify zero for the first semaphore. Returns zero in no further semaphore is available. Returns the name of the specified semaphore Returns the magic of a given semaphore ID Returns the state of the semaphore Returns the count of the semaphore Returns the number of tasks waiting on this semaphore Returns the next task s magic in the waiting list TASK.MUTEX.LIST (<magic>) TASK.MUTEX.NAME(<magic>) TASK.MUTEX.ID2MAGIC(<id>) TASK.MUTEX.WAITERS.COUNT (<magic>) TASK.MUTEX.WAITERS.LIST (<magic>,<taskmagic>) Returns the next magic in the mutex list. Specify zero for the first mutex. Returns zero in no further mutex is available. Returns the name of the specified mutex Returns the magic of a given mutex ID Returns the number of tasks waiting on this mutex Returns the next task s magic in the waiting list TASK.QUEUE.LIST (<magic>) TASK.QUEUE.NAME(<magic>) TASK.QUEUE.ID2MAGIC(<id>) TASK.QUEUE.WAITERS.COUNT (<magic>) TASK.QUEUE.WAITERS.LIST (<magic>,<taskmagic>) Returns the next magic in the queue list. Specify zero for the first queue. Returns zero in no further queue is available. Returns the name of the specified queue Returns the magic of a given queue ID Returns the number of tasks waiting on this queue Returns the next task s magic in the waiting list RTOS Debugger for RTXC Quadros 25 RTXC Quadros PRACTICE Functions

TASK.PIPE.LIST (<magic>) TASK.PIPE.NAME(<magic>) TASK.PIPE.ID2MAGIC(<id>) Returns the next magic in the pipe list. Specify zero for the first pipe. Returns zero in no further pipe is available. Returns the name of the specified pipe Returns the magic of a given pipe ID Frequently-Asked Questions No information available RTOS Debugger for RTXC Quadros 26 Frequently-Asked Questions