General Commands Reference Guide G

(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

(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

(3)

General Commands Reference Guide G

Version 18-Apr-2016

History

(4)

GLOBALON

Global event-controlled PRACTICE script execution

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.

Format: 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>

(5)

The currently active actions can be viewed with the PMACRO command. The outermost frame is the global PRACTICE stack frame, as shown below.

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:

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

Descriptions

ABREAK (E) The analyzer mode changed to the break state.

BREAK (E) ICE/FIRE: The trigger system changed to BREAK state.

CORESWITCH SMP-Debugging: The currently displayed context changed to a different core or thread.

GO The target program started.

HALT (E) ICE/FIRE: Emulation CPU is in HALT state (H in the state line). Global PRACTICE stack frame

with GLOBALON actions

TRACE32 executes the SYStem.Up command.

TRACE32 detects the SYSUP event.

TRACE32 executes the <action>.

(6)

<actions>

One of the following actions can be defined for any of the above events:

POWERUP Target power is switched on.

RESET A target reset was detected.

SYSDOWN 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.

SYSUP 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>

For a description of the PRACTICE specific events, refer to GLOBALON in the ”PRACTICE Script Language Reference Guide” (practice_ref.pdf). <CPU_specific_

events>

Debuggers providing CPU specific events are listed in the See also block at the end of this command description.

Actions Descriptions

no action specified

An already defined action for a particular global event will be removed from the global PRACTICE stack frame. See “Unregistering GLOBALON Actions”.

DO If the event occurs, the specified PRACTICE script file will be executed automatically.

Device-specific Events

(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

globalon_sysdown.cmm

2. Register the events and their actions in TRACE32.

The path prefix ~~/ works on Windows and Linux and expands to the system directory of TRACE32, by default C:\T32 for Windows.

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

PRINT "System down at " Clock.Time()

AREA ; Display the message in the AREA window ; ...

ENDDO

; 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:

(8)

Unregistering GLOBALON Actions

You can unregister all GLOBALON actions or just a selected GLOBALON action.

• To unregister all GLOBALON actions, type at the TRACE32 command line:

• To unregister just a selected GLOBALON action, type at the TRACE32 command line:

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.

See also

■ END _■ ON _■ PMACRO.RESet

▲ ’CPU specific Events for the ON and GLOBALON Command’ in ’Intel x86/x64 Debugger’

NOTE: Unregistering all GLOBALON actions from the global PRACTICE stack frame also deletes all global PRACTICE macros (variables).

END ; Ends all active PRACTICE scripts

PMACRO.RESet ; Unregisters all GLOBALON actions and

; deletes all global PRACTICE macros (variables)

END ; Ends all active PRACTICE scripts

; Unregisters the action for the SYSDOWN event

(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 .

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.

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.

(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 level language code. As compared to software supported high-level language debuggers, real-time characteristics are not changed. In order to handle high-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).

(11)

Go.Asm

Assembler realtime execution

The same as the Go command, except that simultaneous switching into assembler mode takes place.

See also

■ Go.direct

▲ ’Realtime Emulation’ in ’ICE User’s Guide’

Format: Go.Asm [<address> [/<break> …]] …

<break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll

(12)

Go.Back

Go back in program (CTS)

The virtual program is executed backwards.

See also

■ Go.direct

▲ ’Release Information’ in ’Release History’

Go.BackEntry

Re-run the program back to function entry (CTS)

Re-run the recorded program flow backwards until the function entry.

See also

■ Go.direct

Format: Go.Back [<address> [/<break> …]] …

Go.Back 0x1000 ; go back until address 0x1000

(13)

ICE only

Go.BackGround

Start background program

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.

See also

■ Go.direct

Go.BackTillWarning

Re-run program until warning (CTS)

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.

See also ■ CTS.state ■ Go.direct Format: Go.BackGround 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

(14)

Go.Change

Realtime execution till expression changes

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.

See also

■ Go.direct

Format: Go.Change <expression>

Break.Set 0x100 Break.Set 0x200

Go.Change Register(i) ; starts the emulation and restarts, if the

(15)

Go.direct

Start the program execution

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..

See also

■ 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()

Format: Go.direct [<address> [/<break> …]] …

Go ; start program execution

Go func0 func12 ; set temporary breakpoints to the entry of

; function func0 and func12 and then start the ; program execution

(16)

Go.Hll

HLL realtime execution

The same as the Go command, except that simultaneous switching into high-level language mode takes place.

See also

■ Go.direct

Go.Java

Java realtime execution

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.

See also

■ Go.direct

Format: Go.Hll [<address> [/<break> …]] …

<break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll Format: Go.Java

(17)

Go.Mix

MIX realtime execution

The same as the Go command, except that simultaneous switching into mixed language mode takes place.

See also

■ Go.direct

Go.MONitor

Activate foreground 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).

See also

■ Go.direct

Format: Go.Mix [<address> [/<break> …]] …

<break>: Program Hll Spot Read Write Alpha Beta Charly Data DEFault ALL AllNotHll Format: Go.MONitor

(18)

Go.Next

Continue program

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. See also the command Step.Over.

See also

■ Go.direct

ICE only

Go.NoBreak

Emulation breakpoints disabled

Same as the command Go, but program breakpoints are disabled.

See also

■ Go.direct

Format: Go.Next

(19)

Go.Return

Complete HLL function

The command sets a temporary breakpoint to the last instruction of a function and starts the program.

See also

■ Go.direct

Go.Till

Realtime emulation till expression true

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.

See also

■ Go.direct

Format: Go.Return 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

Format: Go.Till <boolean_expression>

Break.Set 0x100 Break.Set 0x200

Go.Till Register(i)==7 ; starts the emulation and restarts if the

(20)

Go.TillWarning

Re-run program until warning (CTS)

Re-run the recorded program flow until the next warning. An explanation for the warning is given in the message area.

See also

■ CTS.state ■ Go.direct

Format: Go.TillWarning

AREA.view ; open message area

CTS.GOTO -17281536. ; display the target´s context as

; it was when record -17281536. was ; recorded (activate CTS)

CTS.state ; open the CTS state window and

; and check the warnings

Trace.GOTO -200000000. ; move the cursor to the start of

; the trace (just use a big number)

Go.TillWarning ; re-run the recorded program

(21)

Go.Up

Go up in function nesting

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.

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.

See also

■ Go.direct

Format: Go.Up [<level> | <address>]

Go.Up ; returns from the current function

Go.Up 3 ; returns three levels

Go.Up main ; returns from functions, till the program is in the

(22)

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.

See also

■ 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:

(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 Group-based run-time analysis. Trace.Chart.GROUP Group time chart.

Trace.PROfileChart.GROUP Group profile chart. MIPS.STATistic.GROUP MIPS statistic for groups. MIPS.PROfileChart.GROUP MIPS profile chart for groups.

(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.

(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).

(26)

GROUP.COLOR

Define color for group indicator

Define the color that is used to mark the group members.

Lauterbach scripts use the following color convention:

See also

■ GROUP ■ GROUP.Create

▲ ’Screen Display’ in ’IDE User’s Guide’

Format: GROUP.COLOR <group_name> <color>

<color>: NONE BLACK MAROON GREEN OLIVE NAVY PURPLE TEAL SILVER GREY RED LIME YELLOW BLUE FUCHSIA AQUA WHITE

GROUP.COLOR "Layer 1" FUCHSIA ; Specify color

RED To mark the OS kernel.

YELLOW To mark kernel drivers and libraries.

BLUE To mark virtual machine byte code e.g. Android/Dalvik.

(27)

GROUP.Create

Create a new group

The command GROUP.Create allows to create a new group. Group members can be defined by module name, function name, etc.

Options:

Format: GROUP.Create [<group_name> {<group_member>}] [/<option>]

<group_ member>:

<address_range> | <function> | <module> | <program> | <source>

<option>: ENable | DISable SHOW | HIDE SEParate | Merge

<color>

GROUP.Create ; open GROUP.Create dialog window.

ENable

(default)

Enable the GROUP features.

DISable Disable the GROUP features.

SHOW

(default)

Display the instructions of the GROUP members together with the GROUP indicator (COLOR).

HIDE 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.

SEParate

(default)

Display the measurement results separately for each group member if a trace analysis command is used.

Merge The group represents its members in all trace analysis windows. No details about group members are displayed.

(28)

See also

■ <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

GROUP.Create "kernel" \os_module1 \os_module2 \os_scheduler GROUP.Create "Layer 1" 0x3F0000--0x3FA533 /LIME

(29)

GROUP.CreateFunctions

Pool functions to group

Pool the functions to groups.

Format: GROUP.CreateFunctions <group_name> <pattern>|<function> [{/<option>}]

<option>: ENable | DISable SHOW | HIDE SEParate | Merge DIALOG

<color>

; 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

(30)

GROUP.CreateLabels

Use labels to pool address ranges to group

Pool address ranges to groups. Each address range starts at a label and ends at the next label.

The options are described in detail with the GROUP.Create command.

See also

■ GROUP _■ GROUP.Create

Format: GROUP.CreateLabels <group_name> <pattern> | <label> [{/<option>}]

<option>: ENable | DISable SHOW | HIDE SEParate | Merge DIALOG

<color>

; 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

(31)

GROUP.CreateModules

Pool modules to group

Pool modules to group.

Format: GROUP.CreateModules <group_name> <pattern | module> [{/<option>}]

<color>

; 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

(32)

GROUP.CreatePrograms

Pool programs group

Pool the programs that correspond to the specified name pattern to a new group.

See also

Format: GROUP.CreatePrograms <group_name> <pattern>|<program> [{/<option>}]

<color>

; 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

(33)

GROUP.CreateSources

Pool source files to group

Pool the source files that correspond to the specified name pattern to a new group.

See also

Format: GROUP.CreateSources <group_name> <pattern>|<source> [{/<option>}]

<color>

; 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

(34)

GROUP.CreateTASK

Pool tasks to group

Pool tasks to group. The grouping of tasks affects only the following commands:

Example for Linux:

Format: GROUP.CreateTASK <group_name> {<task>} [{/<option>}]

<task>: <task_name> | <magic> | <task_id>

<option>: ENable | DISable SEParate | Merge

<color>

Trace.STATistic.TASK Display task activity statistic. Trace.Chart.TASK Display a task activity chart. Trace.PROfileChart.TASK Display a task activity graph.

MIPS.STATistic.TASK Display the MIPS per task numerically. MIPS.PROfileChart.TASK Display the MIPS per task graphically.

; 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"

(35)

See also

GROUP.Delete

Delete the specified group

Delete the specified GROUP. If no group is specified all GROUPs are deleted.

See also

; pool specified tasks to group "spi_tasks" ; use <magic> to specify tasks

GROUP.CreateTASK "spi_tasks" 0xDC1EF540 0xDC1FAA40 0xDC1F2040 /LIME

; pool specified tasks to group "spi_tasks" ; use <task-ID> to specify tasks

GROUP.CreateTASK "spi_tasks" 652. 654. 656. /LIME

GROUP.List

Format: GROUP.Delete [<string> | <range> | <address>]

GROUP.Delete "kernel" ; delete the "kernel" group

(36)

GROUP.DISable

Disable a group

Disables a group.

See also

GROUP.ENable

Enable a group

Enables a group. For details, refer to Features.

See also

Format: GROUP.DISable [<string> | <range> | <address>]

GROUP.DISable "kernel"

GROUP.DISable 0x3F0000--0x3FA533

Format: GROUP.ENable [<string> | <range> | <address>]

GROUP.ENable "kernel"

(37)

GROUP.HIDE

Hide group from debugging

Hides a group. For details, refer to Features.

See also

GROUP.List

List all specified groups

Show all group definitions.

See also

Format: GROUP.HIDE [<string> | <range> | <address>]

GROUP.HIDE "kernel" Trace.List

GROUP.SHOW "kernel"

(38)

GROUP.Merge

Merge group members in statistic

Merge group members in all trace analysis windows. For details, refer to Features.

See also

GROUP.RESet

Clear all group specifications

Reset all group settings to default.

See also

Format: GROUP.Merge <name>

GROUP.Merge "layer 1" Trace.STATistic.Func GROUP.SEParate "layer 1"

Format: GROUP.RESet

(39)

GROUP.SEParate

Separate group members in statistic

Display details about group members in all trace analysis windows (default). For details, refer to Features.

See also

GROUP.SHOW

Show group for debugging

Shows a group. For details, refer to Features.

See also

Format: GROUP.SEParate <name>

GROUP.SEParate "layer 1" Trace.STATistic.Func GROUP.Merge "layer 1"

Format: GROUP.SHOW [<string> | <range> | <address>]

GROUP.SHOW "kernel" Trace.List