General Commands Reference Guide G

Transcription

1 General Commands Reference Guide G TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents... General Commands... General Commands Reference Guide G... 1 History... 3 GLOBALON... 4 GLOBALON Global event-controlled PRACTICE script execution 4 Go... 9 Debug Control for Debuggers and ROM Monitors 9 Program Execution 9 Debug Control for TRACE32-ICE 10 Real-Time Emulation 10 Single Step 10 Cycle Step 10 High-Level Language Debugging 10 Multitask Debugging 10 Go.Asm Assembler realtime execution 11 Go.Back Go back in program (CTS) 12 Go.BackEntry Re-run the program back to function entry (CTS) 12 Go.BackGround Start background program 12 Go.BackTillWarning Re-run program until warning (CTS) 13 Go.Change Realtime execution till expression changes 14 Go.direct Start the program execution 15 Go.Hll HLL realtime execution 16 Go.Java Java realtime execution 16 Go.Mix MIX realtime execution 17 Go.MONitor Activate foreground monitor 17 Go.Next Continue program 18 Go.NoBreak Emulation breakpoints disabled 18 Go.Return Complete HLL function 19 Go.Till Realtime emulation till expression true 19 Go.TillWarning Re-run program until warning (CTS) 20 Go.Up Go up in function nesting 21 GROUP GROUP Group functions, modules or tasks 22 General Commands Reference Guide G 1

2 Features 22 GROUP.COLOR Define color for group indicator 26 GROUP.Create Create a new group 27 GROUP.CreateFunctions Pool functions to group 29 GROUP.CreateLabels Use labels to pool address ranges to group 30 GROUP.CreateModules Pool modules to group 31 GROUP.CreatePrograms Pool programs group 32 GROUP.CreateSources Pool source files to group 33 GROUP.CreateTASK Pool tasks to group 34 GROUP.Delete Delete the specified group 35 GROUP.DISable Disable a group 36 GROUP.ENable Enable a group 36 GROUP.HIDE Hide group from debugging 37 GROUP.List List all specified groups 37 GROUP.Merge Merge group members in statistic 38 GROUP.RESet Clear all group specifications 38 GROUP.SEParate Separate group members in statistic 39 GROUP.SHOW Show group for debugging 39 Usage: (B) command only available for ICD (E) command only available for ICE (F) command only available for FIRE General Commands Reference Guide G 2

3 General Commands Reference Guide G Version 18-Apr-2016 History 28-Jul-15 Description for GROUP command group updated. General Commands Reference Guide G 3 History

4 GLOBALON GLOBALON Global event-controlled PRACTICE script execution GLOBALON <event> [<action>] <event>: <device_specific> <PRACTICE_specific> <CPU_specific> <device_ specific>: ABREAK BREAK CORESWITCH GO HALT PBREAK PBREAKAT <address> POWERDOWN POWERUP RESET SYSDOWN SYSUP TRIGGER <action>: DO <filename> The GLOBALON command enables the automatic start or branching of the PRACTICE programs controlled by several events. In order for events and their actions to be available, they need to be registered in TRACE32. To register events and their actions, you can: Run the GLOBALON commands via the TRACE32 command line. Include the GLOBALON commands in the t32.cmm start-up script (location: C:\T32\t32.cmm). As a result, they are automatically registered when you start TRACE32. Include the GLOBALON commands in any other script. As a result, they are only registered when you run that script. Registered actions remain stored on the global PRACTICE stack frame. Therefore, the actions are valid for the entire duration of the TRACE32 session, or until removed manually. General Commands Reference Guide G 4 GLOBALON

5 The currently active actions can be viewed with the PMACRO command. The outermost frame is the global PRACTICE stack frame, as shown below. Global PRACTICE stack frame with GLOBALON actions Let s assume that an action has been registered for the SYSUP event. When a SYStem.Up command is initiated (via the TRACE32 PowerView GUI or the command line or via another PRACTICE script), then TRACE32 responds as illustrated in the figure below: TRACE32 executes the SYStem.Up command. TRACE32 detects the SYSUP event. TRACE32 executes the <action>. Next: Description of <events> Description of <actions> Creating Actions for GLOBALON Events - Example Unregistering GLOBALON Actions <events> The following table focuses on the device-specific GLOBALON events and tells you where to find the descriptions of the PRACTICE-specific and CPU-specific events. Device-specific Events ABREAK (E) BREAK (E) CORESWITCH GO HALT (E) PBREAK PBREAKAT POWERDOWN Descriptions The analyzer mode changed to the break state. ICE/FIRE: The trigger system changed to BREAK state. SMP-Debugging: The currently displayed context changed to a different core or thread. The target program started. ICE/FIRE: Emulation CPU is in HALT state (H in the state line). The target program stopped. The target program stopped at a specific address. Target power is switched off. General Commands Reference Guide G 5 GLOBALON

6 Device-specific Events POWERUP RESET SYSDOWN SYSUP Descriptions Target power is switched on. A target reset was detected. System mode changed to Down or NoDebug. The event is also triggered if the debugger is in system mode StandBy and the target power is switched off. System mode changed to Up. The event is also triggered if the debugger is in system mode StandBy and the target power is switched on. TRIGGER Debugger: A podbus trigger occurred (internal or external source can be selected via TRIGGER window). ICE/FIRE: The trigger system changed from ARM to TRIGGER state. <PRACTICE_specific _events> <CPU_specific_ events> For a description of the PRACTICE specific events, refer to GLOBALON in the PRACTICE Script Language Reference Guide (practice_ref.pdf). Debuggers providing CPU specific events are listed in the block at the end of this command description. <actions> One of the following actions can be defined for any of the above events: Actions no action specified DO Descriptions An already defined action for a particular global event will be removed from the global PRACTICE stack frame. See Unregistering GLOBALON Actions. If the event occurs, the specified PRACTICE script file will be executed automatically. General Commands Reference Guide G 6 GLOBALON

7 Creating Actions for GLOBALON Events - Example 1. Develop the action (PRACTICE script *.cmm) you want to be executed automatically whenever the desired event occurs. For demo purposes, we will use two simple scripts for the events SYSUP and SYSDOWN so that you can reproduce the example right away. globalon_sysup.cmm PRINT "System up at " Clock.Time() AREA ; Display the message in the AREA window ; Other commands such as Data.Set, PER.Set to disable an ; external watchdog ;... ENDDO globalon_sysdown.cmm PRINT "System down at " Clock.Time() AREA ; Display the message in the AREA window ;... ENDDO 2. Register the events and their actions in TRACE32. ; At the global PRACTICE stack frame, the following ; device-specific events are registered: SYSUP and SYSDOWN ; On SYSUP, this PRACTICE script file (*.cmm) is called: GLOBALON SYSUP DO "~~/globalon_sysup.cmm" ; On SYSDOWN, this PRACTICE script file (*.cmm) is called: GLOBALON SYSDOWN DO "~~/globalon_sysdown.cmm The path prefix ~~/ works on Windows and Linux and expands to the system directory of TRACE32, by default C:\T32 for Windows. General Commands Reference Guide G 7 GLOBALON

8 Unregistering GLOBALON Actions You can unregister all GLOBALON actions or just a selected GLOBALON action. NOTE: Unregistering all GLOBALON actions from the global PRACTICE stack frame also deletes all global PRACTICE macros (variables). To unregister all GLOBALON actions, type at the TRACE32 command line: END ; Ends all active PRACTICE scripts PMACRO.RESet ; Unregisters all GLOBALON actions and ; deletes all global PRACTICE macros (variables) To unregister just a selected GLOBALON action, type at the TRACE32 command line: END ; Ends all active PRACTICE scripts ; Unregisters the action for the SYSDOWN event GLOBALON SYSDOWN ; Do not include the DO <action> here! Result: The respective line or lines are no longer displayed in global PRACTICE stack frame of the PMACRO.list window. Thus the global action can no longer be executed. END ON PMACRO.RESet CPU specific Events for the ON and GLOBALON Command in Intel x86/x64 Debugger General Commands Reference Guide G 8 GLOBALON

9 Go Debug Control for Debuggers and ROM Monitors Program Execution. Go starts the program execution on the chip/core. By default the program is executed in real-time, but there are features within TRACE32 PowerView that suspend the real-time execution. Examples are: Intrusive breakpoint Performance analysis via StopAndGo NOTE: Go is not equivalent to the SYStem.Mode Go command. SYStem.Mode Go resets the processor/chip, enables the on-chip debug logic and then starts the program execution. Go command in the toolbar Restarting from Breakpoint When interrupts are pending and the program execution is started from a breakpoint, it is possible that the processor/core executes the interrupt service routine and returns to the same breakpoint location afterward. The debugging seem to stick on the breakpoints. To avoid this behavior, TRACE32 executes a single step when the program execution is started on a breakpoint if required. Unfortunately, this strategy does not solve the problem completely. To completely solve the issue, you have to disable the interrupts will single stepping on assembler level with the TRACE32 command SYStem.Option IMASKASM ON. SYStem.Option IMASKASM ON is not a default setting, because it may disturb debugging part of the program (e.g. a boot loader) that enable/disable interrupts. General Commands Reference Guide G 9 Go

10 Debug Control for TRACE32-ICE Real-Time Emulation The target program executes all emulation commands in real time. There is no discrepancy in the time response compared to the original CPU. During real-time emulation all commands can be sent to the development system just as before. Single Step Single-stepping is controlled via hardware. A program break results after the execution of an assembler command, or after the execution of the next line of high-level language code. Cycle Step In addition to real-time execution it is also possible to do cyclical program emulation. The emulation CPU can be halted either by a WAIT or a DMA request. When using a WAIT request the cycle is extended indefinitely with all CPU signals becoming statically. In the case of single cycle execution via a BUS (DMA) request, the cycle is executed in real time. High-Level Language Debugging The TRACE32 Development System features a hardware supported high-level language debugger. Each line of high-level language code loaded to the system is flagged in break memory. During high-level language single-stepping, or by program break via the keyboard, these breakpoints are initialized, and the program interrupts at the next line of high-level language code. As compared to software supported highlevel language debuggers, real-time characteristics are not changed. In order to handle high-level debugging the system must contain an ample amount of breakpoint memory. Multitask Debugging In addition to the foreground program, a second program can be activated. This program can be executed whenever no additional task (background program) is available to the emulator. This allows to handle various tasks such as single-stepping interrupt-handling, multitask kernel activation, or watchdog operations. The background program needs its own interrupt stack. All system hardware (breakpoint, trigger, flag, runtime) is solely tied to the foreground program. This means that in the case of routines which have common breakpoints, only the foreground program is interrupted. The background program is stopped when the emulation controller sends a request to the emulation system. However, special background program breakpoints can be set (see Break.SELect BACK). General Commands Reference Guide G 10 Go

11 Go.Asm Assembler realtime execution Go.Asm [<address> [/<break> ]] <break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll The same as the Go command, except that simultaneous switching into assembler mode takes place. Go.direct Realtime Emulation in ICE User s Guide General Commands Reference Guide G 11 Go

12 Go.Back Go back in program (CTS) Go.Back [<address> [/<break> ]] <break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll The virtual program is executed backwards. Go.Back 0x1000 ; go back until address 0x1000 Go.direct Release Information in Release History Go.BackEntry Re-run the program back to function entry (CTS) Go.BackEntry Re-run the recorded program flow backwards until the function entry. Go.direct Release Information in Release History General Commands Reference Guide G 12 Go

13 Go.BackGround ICE only Start background program Go.BackGround The background program is always executed, when the emulation is stopped. The purpose of this program can be to maintain interrupts, refresh memory or trigger watchdogs in the target. r.s pc 0x1000 /t bg r.s ssp 0x2000 /t bg g.bg ; Define program counter ; Define stack ; Start background program b.bg ; Break background program Go.direct Release Information in Release History Go.BackTillWarning Re-run program until warning (CTS) Go.BackTillWarning Re-run the recorded program flow until the previous warning. An explanation for the warning is given in the message area. A full example is give at Go.TillWarning. CTS.state Go.direct General Commands Reference Guide G 13 Go

14 Go.Change Realtime execution till expression changes Go.Change <expression> The emulation is started and after each emulation stop the given expression is evaluated. If the expression has not changed, the emulation is started again. Break.Set 0x100 Break.Set 0x200 Go.Change Register(i) ; starts the emulation and restarts, if the ; register i has not changed Go.direct Realtime Emulation in ICE User s Guide General Commands Reference Guide G 14 Go

15 Go.direct Start the program execution Go.direct [<address> [/<break> ]] <break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll Up to 256 temporary breakpoints can be set with the GO command simultaneously. All temporary breakpoints are automatically deleted when the program execution stops the next time.. Go Go func0 func12 ; start program execution ; set temporary breakpoints to the entry of ; function func0 and func12 and then start the ; program execution Go.Asm Go.Back Go.BackEntry Go.BackGround Go.BackTillWarning Go.Change Go.Hll Go.Java Go.Mix Go.MONitor Go.Next Go.NoBreak Go.Return Go.Till Go.TillWarning Go.Up Register.view RUN() Release Information in Release History General Commands Reference Guide G 15 Go

16 Go.Hll HLL realtime execution Go.Hll [<address> [/<break> ]] <break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll The same as the Go command, except that simultaneous switching into high-level language mode takes place. Go.direct Realtime Emulation in ICE User s Guide Go.Java Java realtime execution Go.Java The same as the Go command with breakpoints set to stop the target before the next byte code is executed. This command requires that the debugger is configured for the virtual java machine. Go.direct General Commands Reference Guide G 16 Go

17 Go.Mix MIX realtime execution Go.Mix [<address> [/<break> ]] <break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll The same as the Go command, except that simultaneous switching into mixed language mode takes place. Go.direct Realtime Emulation in ICE User s Guide Go.MONitor Activate foreground monitor Go.MONitor The same as the Go command, but also activates the foreground monitor. The next target stop will use the foreground monitor. This command requires other configuration commands to work (memory access modes, breakpoints, loading a monitor program). Go.direct General Commands Reference Guide G 17 Go

18 Go.Next Continue program Go.Next Like the command Go with a temporary breakpoint set to the next assembler command or next HLL line. This command can be used to overstep a subroutine call instruction or to leave a loop. the command Step.Over. Go.direct Realtime Emulation in ICE User s Guide Go.NoBreak ICE only Emulation breakpoints disabled Go.NoBreak [<address>] Same as the command Go, but program breakpoints are disabled. Go.direct Realtime Emulation in ICE User s Guide General Commands Reference Guide G 18 Go

19 Go.Return Complete HLL function Go.Return The command sets a temporary breakpoint to the last instruction of a function and starts the program. Go func0 Step.single Step.single Go.Return Var.Local Step.single ; run to function start ; step inside function ; go to function end ; inspect return value ; leave function Go.direct Realtime Emulation in ICE User s Guide Go.Till Realtime emulation till expression true Go.Till <boolean_expression> The emulation is started and after each emulation stop the given boolean expression is evaluated. If the expression is false, the emulation is started again. Break.Set 0x100 Break.Set 0x200 Go.Till Register(i)==7 ; starts the emulation and restarts if the ; register i has not the value 7 Go.direct Realtime Emulation in ICE User s Guide General Commands Reference Guide G 19 Go

20 Go.TillWarning Re-run program until warning (CTS) Go.TillWarning Re-run the recorded program flow until the next warning. An explanation for the warning is given in the message area. AREA.view CTS.GOTO CTS.state Trace.GOTO Go.TillWarning ; open message area ; display the target s context as ; it was when record was ; recorded (activate CTS) ; open the CTS state window and ; and check the warnings ; move the cursor to the start of ; the trace (just use a big number) ; re-run the recorded program ; until the next warning CTS.state Go.direct General Commands Reference Guide G 20 Go

21 Go.Up Go up in function nesting Go.Up [<level> <address>] The command returns to the caller function. Without arguments it returns to the function, that called the current function (level 1). With a level argument several levels can be skipped (see also command Frame.view). The command can also be executed by clicking with the mouse to the function name in the Var.Frame window. With an address argument it returns to the first function on the stack, which includes the given address. The address can be defined symbolically, by the name of the function, or by a line number within the function. Go.Up Go.Up 3 Go.Up main ; returns from the current function ; returns three levels ; returns from functions, till the program is in the ; 'main' function The method used for this command is to search back in the stack frame for the target function. A temporary breakpoint is then set directly behind the call command. The program is then executed. An extra high-level step is executed, if running in high-level mode and the program has not stopped on a HLL line. Go.direct Realtime Emulation in ICE User s Guide General Commands Reference Guide G 21 Go

22 GROUP GROUP Group functions, modules or tasks The GROUP command group allows to structure application programs consisting of a huge number of functions/modules/tasks to ease the evaluation of the trace contents and the debugging process. GROUP.COLOR GROUP.Create GROUP.CreateFunctions GROUP.CreateLabels GROUP.CreateModules GROUP.CreatePrograms GROUP.CreateSources GROUP.CreateTASK GROUP.Delete GROUP.DISable GROUP.ENable GROUP.HIDE GROUP.List GROUP.Merge GROUP.RESet GROUP.SEParate GROUP.SHOW GROUP.EXIST() Features ENable TRACE32 PowerView provides the following features if a group is enabled: The source code of all group members is marked with the color assigned to the group. General Commands Reference Guide G 22 GROUP

23 The trace information recorded for the group members is marked with the color assigned to the group. All group members are marked with the color assigned to the group in all trace analysis windows. Additional group-based trace analyses commands are provided. Trace.STATistic.GROUP Trace.Chart.GROUP Trace.PROfileChart.GROUP MIPS.STATistic.GROUP MIPS.PROfileChart.GROUP Group-based run-time analysis. Group time chart. Group profile chart. MIPS statistic for groups. MIPS profile chart for groups. General Commands Reference Guide G 23 GROUP

24 Merge If a group is enabled, the following features are added by checking merge: The group represents its members in all trace analysis windows. No details about group members are displayed. General Commands Reference Guide G 24 GROUP

25 Hide If a group is enabled, the following features are added by checking hide: The trace information recorded for the group members is hidden. The group represents its members in all trace analysis windows. No details about group members are displayed (same as merge). Step over group members during hll single stepping. General Commands Reference Guide G 25 GROUP

26 GROUP.COLOR Define color for group indicator GROUP.COLOR <group_name> <color> <color>: NONE BLACK MAROON GREEN OLIVE NAVY PURPLE TEAL SILVER GREY RED LIME YELLOW BLUE FUCHSIA AQUA WHITE Define the color that is used to mark the group members. GROUP.COLOR "Layer 1" FUCHSIA ; Specify color Lauterbach scripts use the following color convention: RED YELLOW BLUE GREEN To mark the OS kernel. To mark kernel drivers and libraries. To mark virtual machine byte code e.g. Android/Dalvik. To mark the application/application processes. GROUP GROUP.Create Screen Display in IDE User s Guide General Commands Reference Guide G 26 GROUP

27 GROUP.Create Create a new group GROUP.Create [<group_name> {<group_member>}] [/<option>] <group_ member>: <address_range> <function> <module> <program> <source> <option>: ENable DISable SHOW HIDE SEParate Merge <color> The command GROUP.Create allows to create a new group. Group members can be defined by module name, function name, etc. GROUP.Create ; open GROUP.Create dialog window. Options: ENable (default) DISable SHOW (default) HIDE SEParate (default) Merge DIALOG <color> Enable the GROUP features. Disable the GROUP features. Display the instructions of the GROUP members together with the GROUP indicator (COLOR). Suppress the display of the instructions of the GROUP members in the trace listing and step over the instructions of the GROUP members during hll single stepping. The group represents its members in all trace analysis windows. Display the measurement results separately for each group member if a trace analysis command is used. The group represents its members in all trace analysis windows. No details about group members are displayed. Deprecated. Define the color for the GROUP indicator. General Commands Reference Guide G 27 GROUP

28 GROUP.Create "kernel" \os_module1 \os_module2 \os_scheduler GROUP.Create "Layer 1" 0x3F x3FA533 /LIME GROUP.Create "INT" symbol.secprange(\.interrupt) /MAROON /HIDE <trace>.chart.group <trace>.statistic.group GROUP GROUP.COLOR GROUP.CreateFunctions GROUP.CreateLabels GROUP.CreateModules GROUP.CreatePrograms GROUP.CreateSources GROUP.CreateTASK GROUP.Delete GROUP.DISable GROUP.ENable GROUP.HIDE GROUP.List GROUP.Merge GROUP.RESet GROUP.SEParate GROUP.SHOW General Commands Reference Guide G 28 GROUP

29 GROUP.CreateFunctions Pool functions to group GROUP.CreateFunctions <group_name> <pattern> <function> [{/<option>}] <option>: ENable DISable SHOW HIDE SEParate Merge DIALOG <color> Pool the functions to groups. ; display symbol listing for all functions symbol.list.function ; pool all functions that match the specified name pattern to the ; group "group_a" ; assign color FUCHSIA to "group_a" GROUP.CreateFunctions "group_a" jpeg_f* /FUCHSIA ; create group "group_b" that contains the function init_source GROUP.CreateFunctions "group_b" init_source ; add function term_source to the group "group_b" GROUP.CreateFunctions "group_b" term_source ; add function do_barray_io to the group "group_b" ; assign color TEAL to "group_b" GROUP.CreateFunctions "group_b" do_barray_io /TEAL ; list group definition GROUP.List The options are described in detail with the GROUP.Create command. GROUP GROUP.Create General Commands Reference Guide G 29 GROUP

30 GROUP.CreateLabels Use labels to pool address ranges to group GROUP.CreateLabels <group_name> <pattern> <label> [{/<option>}] <option>: ENable DISable SHOW HIDE SEParate Merge DIALOG <color> Pool address ranges to groups. Each address range starts at a label and ends at the next label. ; pool all address ranges that start with a label of the specified name ; pattern to the group "Init" GROUP.CreateLabels "Init" _*init* ; add address range that starts with label _start to the group "Init" ; assign color MAROON to the group "Init" GROUP.CreateLabels "Init" _start /MAROON ; list group definition GROUP.List The options are described in detail with the GROUP.Create command. GROUP GROUP.Create General Commands Reference Guide G 30 GROUP

31 GROUP.CreateModules Pool modules to group GROUP.CreateModules <group_name> <pattern module> [{/<option>}] <option>: ENable DISable SHOW HIDE SEParate Merge <color> Pool modules to group. ; display symbol listing for all functions symbol.list.module ; pool all modules that match the specified name pattern to the ; group "jd_group" GROUP.CreateModules "jd_group" jd* ; add modules jmemmgr to group "jd_group" ; assign color FUCHSIA to group "jd_group" GROUP.CreateModules "jd_group" jmemmgr /FUCHSIA ; list group definition GROUP.List The options are described in detail with the GROUP.Create command. GROUP GROUP.Create General Commands Reference Guide G 31 GROUP

32 GROUP.CreatePrograms Pool programs group GROUP.CreatePrograms <group_name> <pattern> <program> [{/<option>}] <option>: ENable DISable SHOW HIDE SEParate Merge <color> Pool the programs that correspond to the specified name pattern to a new group. ; display symbol listing for all programs symbol.list.program ; pool all programs that match the specified name pattern to the ; group "my_programs" GROUP.CreatePrograms "my_programs" j* ; add program im02_bf1x to group "my_programs" ; assign color OLIVE to group "my_programs" GROUP.CreatePrograms "my_programs" im02_bf1x /OLIVE ; list group definition GROUP.List The options are described in detail with the GROUP.Create command. GROUP GROUP.Create General Commands Reference Guide G 32 GROUP

33 GROUP.CreateSources Pool source files to group GROUP.CreateSources <group_name> <pattern> <source> [{/<option>}] <option>: ENable DISable SHOW HIDE SEParate Merge <color> Pool the source files that correspond to the specified name pattern to a new group. ; display symbol listing for all sources symbol.list.source ; pool all sources that match the specified name pattern to the ; group "my_sources" GROUP.CreateSources "my_sources" *\mpc5xxx\mpc5646c_jpeg\jq*.c ; add all sources that match the specified name pattern to the group ; "my_sources" ; assign color LIME to group "my_sources" GROUP.CreateSources "my_sources" *\mpc5xxx\mpc5646c_jpeg\ji*.c /LIME ; list group definition GROUP.List The options are described in detail with the GROUP.Create command. GROUP GROUP.Create General Commands Reference Guide G 33 GROUP

34 GROUP.CreateTASK Pool tasks to group GROUP.CreateTASK <group_name> {<task>} [{/<option>}] <task>: <task_name> <magic> <task_id> <option>: ENable DISable SEParate Merge <color> Pool tasks to group. The grouping of tasks affects only the following commands: Trace.STATistic.TASK Trace.Chart.TASK Trace.PROfileChart.TASK MIPS.STATistic.TASK MIPS.PROfileChart.TASK Display task activity statistic. Display a task activity chart. Display a task activity graph. Display the MIPS per task numerically. Display the MIPS per task graphically. Example for Linux: ; display process list TASK.DTask ; pool specified tasks to group "spi_tasks" ; use <task_name> to specify tasks ; assign color LIME to group "spi_tasks" GROUP.CreateTASK "spi_tasks" "spi1" "spi2" "spi3" /LIME General Commands Reference Guide G 34 GROUP

35 ; pool specified tasks to group "spi_tasks" ; use <magic> to specify tasks ; assign color LIME to group "spi_tasks" GROUP.CreateTASK "spi_tasks" 0xDC1EF540 0xDC1FAA40 0xDC1F2040 /LIME ; pool specified tasks to group "spi_tasks" ; use <task-id> to specify tasks ; assign color LIME to group "spi_tasks" GROUP.CreateTASK "spi_tasks" /LIME ; list group definition GROUP.List GROUP GROUP.Create GROUP.Delete Delete the specified group GROUP.Delete [<string> <range> <address>] Delete the specified GROUP. If no group is specified all GROUPs are deleted. GROUP.Delete "kernel" GROUP.Delete 0x3F x3FA533 ; delete the "kernel" group ; delete group in the address range GROUP GROUP.Create General Commands Reference Guide G 35 GROUP

36 GROUP.DISable Disable a group GROUP.DISable [<string> <range> <address>] Disables a group. GROUP.DISable "kernel" GROUP.DISable 0x3F x3FA533 GROUP GROUP.Create GROUP.ENable Enable a group GROUP.ENable [<string> <range> <address>] Enables a group. For details, refer to Features. GROUP.ENable "kernel" GROUP.ENable 0x3F x3FA533 GROUP GROUP.Create General Commands Reference Guide G 36 GROUP

37 GROUP.HIDE Hide group from debugging GROUP.HIDE [<string> <range> <address>] Hides a group. For details, refer to Features. GROUP.HIDE "kernel" Trace.List GROUP.SHOW "kernel" GROUP GROUP.Create Release Information in Release History GROUP.List List all specified groups GROUP.List Show all group definitions. GROUP GROUP.Create General Commands Reference Guide G 37 GROUP

38 GROUP.Merge Merge group members in statistic GROUP.Merge <name> Merge group members in all trace analysis windows. For details, refer to Features. GROUP.Merge "layer 1" Trace.STATistic.Func GROUP.SEParate "layer 1" GROUP GROUP.Create GROUP.RESet Clear all group specifications GROUP.RESet Reset all group settings to default. GROUP.RESet GROUP GROUP.Create General Commands Reference Guide G 38 GROUP

39 GROUP.SEParate Separate group members in statistic GROUP.SEParate <name> Display details about group members in all trace analysis windows (default). For details, refer to Features. GROUP.SEParate "layer 1" Trace.STATistic.Func GROUP.Merge "layer 1" GROUP GROUP.Create GROUP.SHOW Show group for debugging GROUP.SHOW [<string> <range> <address>] Shows a group. For details, refer to Features. GROUP.SHOW "kernel" Trace.List GROUP.HIDE "kernel" GROUP GROUP.Create General Commands Reference Guide G 39 GROUP