General Commands Reference Guide R - · PDF fileGeneral Commands Reference Guide R ... MIPS32/MIPS64/NEC-VR Program Counter, Status register and Config register are set to their initial

General Commands Reference Guide R

TRACE32 Online Help

TRACE32 Directory

TRACE32 Index

TRACE32 Documents ......................................................................................................................

General Commands ......................................................................................................................

General Commands Reference Guide R .................................................................................. 1

REFresh .................................................................................................................................... 4

Function 4

REFresh.Address Refresh address range 5

REFresh.CYcle Access mode 5

REFresh.Inc Address distance 5

REFresh.OFF Switch off 6

REFresh.RESet Reset command 6

REFresh.StandBy Standby mode 7

REFresh.state Status display 7

REFresh.Time Refresh rate 8

Register .................................................................................................................................... 9

Register Processor registers 9

Register.Init Initialize the processor registers 9

Register.LOG Log registers 13

Register.REFRESH Refresh register window 14

Register.RELOAD Reload the compiler register settings 14

Register.Set Modify register contents 15

Register.StackTop Define stack top address 16

Register.view Display registers 17

RESet ........................................................................................................................................ 20

RESet Reset all commands 20

RTP ........................................................................................................................................... 21

RTP.CLEAR Clear tracebuffer 21

RTP.DirectDataMode tbd. 21

RTP.DirectDataMode.Mode Direct data mode read/write 21

RTP.HaltOnOverflow Halt system on RTP FIFO overflow 21

RTP.Mode Selects the trace mode 21

RTP.OFF Disables the RTP module 21

RTP.ON Activates the RTP module 21

RTP.PortClock Configure RTPCLK 22

RTP.PortSize Size of RTP data port 22

General Commands Reference Guide R 1 ©1989-2017 Lauterbach GmbH

RTP.Register Display the RTP register 22

RTP.RESet Resets RTP settings 22

RTP.state Display RTP setup 22

RTP.TraceMode Trace mode 22

RTP.TraceMode.RAM<x>.SECTion<y> Configures a trace region 22

RTP.TraceMode.TraceExclude Invert all trace regions 22

RTS ........................................................................................................................................... 23

RTS Real-time profiling (RTS) 23

RTS.COVerage Code coverage (out of operation) 24

RTS.FILE Set the name for the RTS file (out of operation) 24

RTS.FileCompression Set compression level for the RTS (out of operation) 24

RTS.FileLimit Set size limit for the RTS file (out of operation) 24

RTS.FileMode Select the data to write to the RTS file (out of operation) 25

RTS.Init Initialize RTS 25

RTS.ISTATistic Statistics regarding instruction execution (out of operation) 25

RTS.List List recorded trace data (out of operation) 25

RTS.ListNesting Display function call nesting (out of operation) 26

RTS.LOAD Mount a file as trace source (out of operation) 26

RTS.NestingMode Set type of program flow analysis (out of operation) 26

RTS.OFF Deactivate real-time profiling 27

RTS.ON Activate real-time profiling 27

RTS.PROfile Display performance characteristics charts 28

RTS.RESet Restore default settings and initialize RTS 29

RTS.state Open status and control window 30

RTS.STATistic Statistics regarding function invocations 32

RTS.StopOnError Configure behavior regarding minor errors 32

RTS.StopOnFifofull Configure behavior regarding FIFO overflows 33

RTS.TASKMode Configure task analysis 34

RTS.TImeMode Configure analysis of program execution timing 35

RunTime ................................................................................................................................... 36

RunTime Runtime measurement 36

Overview RunTime 36

Runtime Measurements Using the Debugger 36

Runtime Measurements Using TRACE32-ICE / TRACE32-FIRE 38

Functions related to RunTime 38

RunTime.Init Clear timers 39

RunTime.refA Set reference 39

RunTime.refB Set reference 39

RunTime.RESet Reset values to zero 40

RunTime.state Display results 40


Usage:

(B) command only available for ICD(E) command only available for ICE(F) command only available for FIRE


General Commands Reference Guide R

Version 06-Nov-2017

REFresh

Function

The refresh function has to be activated, when a dynamic RAM is on the target system and is refreshed by the CPU. The refresh function uses burst read cycles for refreshing target memory. Address range and storage class may be defined.

StandBy

On StandBy mode the refresh burst is forced while no emulation is running.

NOTE: This command is for refreshing target DRAMs only, when having dynamic emulation memory, it is automatically refreshed by dual-port access.

//////////////////ref.burst ref.burst realtime emulation ref.burst ref.burst


REFresh.Address Refresh address range

Defines the address range, which is touched by refresh cycles.

If the REF.Inc value is set to zero, the address range will be define the length of the refresh burst to a single memory address.

See also

■ REFresh.state

▲ ’Refresh Generator’ in ’ICE User’s Guide’

ICE only

REFresh.CYcle Access mode

If on 16 bit CPUs the access type is LONG, refresh is made by 2 refresh cycles. If on 8 bit CPUs the option WORD or LONG is selected, 2 or 4 cycles are used for one refresh cycle.

See also

■ REFresh.state


Format: REFresh.Address <address_range>

ref.inc 0x1ref.a ud:0x10000--0x100ff ; Refresh on USERDATA area

ref.inc 0x0ref.c wordref.a sd:0x1000++0x0ff ; Refresh burst with 128 words on

; address 1000h

Format: REFresh.CYcle <width>

<width>: ByteWordLong


ICE only

REFresh.Inc Address distance

Defines the address increment used in the refresh access loop.

See also

■ REFresh.state


ICE only

REFresh.OFF Switch off

Refresh function is switched to OFF automatically, when the refresh parameters don't fit e.g. an odd address range together with word size.

See also

■ REFresh.state


Format: REFresh.Inc <inc>

<inc>: 1. …

; force refresh with 256 cycles

ref.t 4.msref.a ud:0x0--0x03ffref.c longref.i 0x4ref.on

; cycle time 4 ms; address range 0 to 03ffh; long word; increment 4; switch on refresh operation

; standby refresh on address 1000H

ref.a ud:0x1000++0x0ref.c bref.standby

; address 1000H; byte access; switch refresh on

Format: REFresh.OFF


ICE only

REFresh.RESet Reset command

The refresh system is switched to OFF and all refresh parameters are initialized.

See also

■ REFresh.state


ICE only

REFresh.StandBy Standby mode

Refresh cycles will be executed, if real-time emulation is not active. Refresh command may be activated only when all refresh parameters are correct.

See also

■ REFresh.state


Format: REFresh.RESet

Format: REFresh.StandBy


ICE only

REFresh.state Status display

Displays the current setup of the refresh function.

See also

■ REFresh.Address ■ REFresh.CYcle ■ REFresh.Inc ■ REFresh.OFF ■ REFresh.RESet ■ REFresh.StandBy ■ REFresh.Time


ICE only

REFresh.Time Refresh rate

Will define the refresh time, if cyclic refresh is selected. This field has no effect on standby-refresh.

See also

■ REFresh.state


Format: REFresh.state

Format: REFresh.Time <time>

<time>: 1.0ms … 1.0s

ref.t 4.0ms ; refresh burst every 4 ms

E68::w.refmode

OFFON

StandByAddress

UD:0000000000FFCycle

BYTEInc000001


Register

Register Processor registers

The Register command group is used to control the processor registers. In case of subprocessors (e.g., FPU) extra commands are provided.

Register values can be returned by the function Register(<register_name>):

See also

■ Register.Init ■ Register.LOG ■ Register.REFRESH ■ Register.RELOAD ■ Register.Set ■ Register.StackTop ■ Register.view ❏ PP() ❏ Register() ❏ Register.LIST()

▲ ’Release Information’ in ’Release History’

Register.Init Initialize the processor registers

Sets the registers to the same state as after the processor reset. Registers which are undefined after RESET are set to zero.

PRINT Register(D0) ; print the contents of the ; register D0 in the message line

Register.Set D1 Register(D0) ; set register D1 to the contents; of register D0

Format: Register.Init [/<option>]Register.RESet (deprecated)

<option>: ForeGroundSet | BackGroundSet | SystemSet | TemporarySetCORE <number>REGSET <number> | Current | PreviousTASK <magic_number> | <task_id> | <task_name>

<option> For information about the options, see Register.view.


B:: ; example for the debugger

…

SYStem.Up ; establish the communication between the; processor and the debugger

Register.Init ; initialize the general purpose registers

…

CPU Behavior of Register.Init

ARC STATUS <= 0x02000000STATUS32 <= 0x00000001DEBUG <= 0x11000000IRQ_LV12 <= 0x00000002 (Resets any interrupt flags)IENABLE <= 0xffffffffSEMAPHORE <= 0x00000000

All other registers are set to zero.

If SYStem.Option ResetDetection is used with a semaphore bit (Sem0...Sem3), Register.Init sets the corresponding semaphore bit in the SEMAPHORE register.

ARM, Cortex, XScale ARM7/9/10/11, Cortex-A/R, XScale:Rx = 0SPSRx = 0x10CPSR = 0xd3 (ARM7/9/10, XScale), 0x1d3 (ARM11, Cortex-A/R)R15 (PC) = 0, 0xffff0000 if high exception vectors selected

Cortex-M:Rx = 0R15 (PC) = [vector table base + 4]xPSR = 0x01000000MSP = [vector table base + 0]PSP = 0R13 (SP) = MSP or PSP depending on the mode

C166 The CP is set to 0xFC00. The sixteen registers R0 - R15 are set to 0x0. DPP0 = 0x0, DPP1 = 0x1, DPP2 = 0x2 and DPP3 = 0x3.Stack registers STKUN is set to 0xFC00 and STKOV is set to 0xFA00.The Stack Pointer SP is set to 0xFC00The Instruction Pointer IP is set to zero.The Code Segment Pointer CSP and the VECSEG are set to the initial value after SYStem.Up.All other registers are set to zero.

CEVA-X MODA and MODA shadow register are set to 0x1E.All other registers are set to zero.


DSP56K Family 56000 and 56100The eight 16-bit modifier registers M[0-7] are set to 0xFFFF. This specifies linear arithmetic as the default type for address register update calculations.The Operating Mode Register (OMR) is set to the initial value after SYStem.Up. Values of bits MA, MB and MC of the OMR register are preserved.The program counter is set to zero. All interrupts are masked by setting the Status Register (SR) to 0x300.

Family 56300 and 56720 DualcoreThe eight 24-bit modifier registers M[0-7] are set to 0xFFFFFF. This specifies linear arithmetic as the default type for address register update calculations. The Operating Mode Register (OMR) is set to the initial value after SYStem.Up. Values of bits MA, MB, MC and MD of the OMR register are preserved. All interrupts are masked by setting Status Register (SR) to 0x300. The program counter is set to zero.

Family 56800 and 56800EThe eight 16-bit modifier registers M[0-7] are set to 0xFFFF. This specifies linear arithmetic as the default type for address register update calculations. The Operating Mode Register (OMR) is set to the initial value after SYStem.Up. Values of bits MA and MB of the OMR register are preserved. All interrupts are masked by setting Status Register (SR) to 0x300. The program counter is set to zero.

HCS08 The Program Counter is set to the value read at 0xFFFE. The Stack Pointer SP is set to 0xFF and the CCR is set to 0x68. All other registers are set to zero.

HC11 The Program Counter is set to the value read at 0xFFFE. The Stack Pointer SP is set to a default value dependent on the derivative. The CCR is set to 0xD8. All other registers are set to zero.

HC12/S12/S12X The Program Counter is set to the value read at 0xFFFE. The CCR is set to 0xD8. All other registers are set to zero.

MIPS32/MIPS64/NEC-VR Program Counter, Status register and Config register are set to their initial values after reset (read during SYStem.Up). PRID and Cause register are updated, all other registers are set to zero.

MMDSP Sets all registers to their initial value after a reset. This is done via a soft reset of the core. NOTE: This may have effects besides updating the contents of architectural registers.

PowerPC Program counter and MSR are set to their initial values after reset (read during SYStem.Up). GPRs and SPR appearing in the Register window are set to zero.

Microblaze All registers are set to zero.

PCP All registers are set to zero.



See also

■ Register ■ Register.view

▲ ’Register and Peripherals’ in ’ICE User’s Guide’

Teak MOD0 and MOD0S registers SATA bit is set. MOD1 and MOD1S regsiters CMD bit is set. MOD3 and MOD3S registers CREP, CPC and CCNTA bits are set.All other registers are set to zero.

Teaklite/Teaklite-II/Oak All registers are set to zero.

Teaklite-III MOD2 register SATA and SATP bits are set.All other registers are set to zero.

x86 EDX is set to a cpu specific value defining the family/model/stepping of the core if a SYStem.Up has been executed at some point before, otherwise EDX is set to 0.EAX,EBX,ECX,ESI,EDI,ESP,EBP are set to 0.EIP is set to 0xFFF0 and EFLAGS to 2.CR0 is set to 0x60000010 and CR2-4 to 0.DR0-3 are set to 0. DR6 to 0xFFFF0FF0 and DR7 to 0x400.IDT and GDT: Base = 0 and Limit = 0xFFFF.LDT and TR: Selector = 0, Base = 0, Limit = 0xFFFF, Access = 0x82.CS: Selector = 0xF000, Base = 0xFFFF0000, Limit = 0xFFFF, Access = 0x93.DS,ES,FS,GS,SS: Selector = 0, Base = 0, Limit = 0xFFFF, Access = 0x93.NOTE: In a multicore system the above holds for the main bootstrap processor. For the other processors the following differences apply: EIP is set to 0x10000 and CR0 to 0x10.

TMS320 All registers except SSR, IER and TSR are set to zero.

TriCore All registers are set to zero with the following exceptions:The initial values for registers PC, PSW, ISP and BTV are read from the CPU at SYStem.Up.If this is not possible the following default values are assumed:PC=0xA0000020 (AURIX and later), 0xA0000000 (otherwise)PSW=0x00000B80BTV=0xA0000100ISP=0x00000100

XTENSA All registers are set to zero.

ZSP All registers are set to zero.



Register.LOG Log registers

Writes the selected registers to the AREA window whenever the program execution stops. The output can be redirected to any named AREA window. The output of any AREA windows can also be redirected to a file.

See also


Format: Register.LOG [<set>] …[/<option>]

<set>: ALL

<option>: AREA <name>

AREA.Create REG_LOG ; set up an AREA window named; REG_LOG

AREA.OPEN REG_LOG regfile.log ; write all outputs to the; AREA window REG_LOG also to the ; file regfile.log

AREA.view REG_LOG ; display the AREA window REG_LOG; in TRACE32

Register.LOG ALL /AREA REG_LOG ; log the contents of all registers; at every program stop to the; AREA window REG_LOG

…

Register.LOG ; end the register logging

AREA.CLOSE REG_LOG ; close the file regfile.log


Register.REFRESH Refresh register window

Forces the debugger to re-read all processor registers from the target and refresh the Register.view window.

Use this command, if your registers might have changed. The timebase registers of the PowerPC processors for example change permanently even when the program execution is stopped.

See also


Register.RELOAD Reload the compiler register settings

Re-writes the initialization values of the last Data.LOAD command into the appropriate processor registers.

See also



Format: Register.REFRESH

NOTE: Whenever the program execution is stopped, the Register.view window is refreshed automatically.

Format: Register.RELOAD


Register.Set Modify register contents

Sets <register> to the specified <value>.

The Register.Set command is also invoked by a double click to the register contents or by choosing Set … in the Register popup menu.

See also

■ Register ■ Register.view ❏ Register()

▲ ’Register and Peripherals’ in ’ICE User’s Guide’▲ ’Release Information’ in ’Release History’▲ ’Registers’ in ’Debugger Basics - Training’▲ ’Registers’ in ’Training FIRE Basics’▲ ’Registers’ in ’Training ICE Basics’

Format: Register.Set <register> [<value>] [/<option>]

<register>: D0 | D1 | D2 | D3 | …

<option>: TASK <magic_number> | <task_id> | <task_name>

<option> For information about the options, see Register.view.

Register.Set PC start ; set the Program Counter to the label; start

Register.Set D0 Register(D0)+1 ; increment register contents


Register.StackTop Define stack top address

Limits the display of the stack in the register window. When the stack is below or equal to this address its contents will not be displayed.

See also

■ Register ■ Register.view ❏ Register()

Format: Register.StackTop <address>

Register.StackTop 0x14000 ; limit the stack display in the; register window to address; 0x14000


Register.view Display registers

Display the general purpose registers. For some CPUs additional information is displayed if the Register.view window is dragged to its full size.

Format: Register.view [/<option>]

<display_option>:

SpotLightStack

<context_option>:

CORE <number>REGSET <number> | Current | PreviousSystemSet | TemporarySetTASK <magic_number> | <task_id>. | "<task_name>"MACHINE <machine_number> [/VCPU <vcpu_number>]

(TRACE32-ICE only)ForeGroundSet | BackGroundSet

SpotLight Highlight changed registers.

Registers changed by the last program run/single step are marked in dark red. Registers changed by the second to last program run/single step are marked a little bit lighter. This works up to a level of 4.

Register.view /SpotLight

Default display

Full display


Stack With Stack: The stack display [A] is shown.Without Stack: The stack display is hidden.

[B] Toggle between:• S = Addresses relative to the stack pointer• F = Addresses relative to the frame pointer• C = Addresses relative to the canonical frame address[C] Clicking the Stack button in the Register.view window lets you show/hide the stack display on the fly.

ForeGroundSet (TRACE32-ICE only)Display the registers of the application program.

TRACE32-ICE allows to run a background program. The background program is always executed, when the execution of the application program stopped. The purpose of the background program can be to maintain interrupts, refresh memory or trigger watchdogs in the target.

BackGroundSet (TRACE32-ICE only)Display the registers of the background program.

SystemSet The TRACE32-internal register set is a temporary buffer within TRACE32. This buffer is used to hold a copy of the CPU registers. Commands like Register.Copy, Register.SWAP are using this TRACE32-internal register set.

Register.COPY ; copy general purpose registers into the; TRACE32-internal register set

Go ; start program execution

Break ; stop program execution

Register.view /SystemSet ; display TRACE32-internal register set

TemporarySet (diagnosis purpose only)

C

A B


See also

■ Register ■ Register.Init ■ Register.LOG ■ Register.REFRESH ■ Register.RELOAD ■ Register.Set ■ Register.StackTop ■ Go.direct ❏ PP() ❏ Register() ❏ Register.LIST()

▲ ’CPU specific Implementations’ in ’MIPS Debugger and Trace’▲ ’Register and Peripherals’ in ’ICE User’s Guide’▲ ’Release Information’ in ’Release History’

CORE <number> (SMP debugging only)The TRACE32 GUI displays the context (registers, cache, memory …) of the currently selected core if SMP debugging is performed. The option CORE allows to display the register set of another core.

CORE.select CORE 1 ; advise TRACE32 to display the ; context of core 1

Register.view ; display the registers of the ; current context

Register.view /CORE 0 ; display the registers for core 0

REGSET <number> (processor-specific)MIPS architecture: Display the specified shadow register set.SH2A architecture: Display the specified register bank.

TASK <magic_number> | <task_id>. | "<task_name>"

Display the register set of the specified task.For information about the parameters, see “What to know about Magic Numbers, Task IDs and Task Names” (general_ref_t.pdf).

Register.view /TASK 0x41498 ; <magic_number>

; <task_id>

Register.view /TASK "thread 0" ; <task_name>

MACHINE <machine_number>VCPU <vcpu_number>

Display the current register set for the specified machine and/or VCPU (only available with SYStem.Option MACHINESPACES ON).


RESet

Resets all commands.

RESet Reset all commands

(E) All commands of the emulator are reset to their default state.

(B) (BDM Debugger) All commands of the BDM-debugger are reset to their default state.

(B) (ROM Monitor) Switches off the EPROM simulator and resets the mapping system to its default state.

The target CPU is reset only if the RES pin of one adapter is connected and adapted to the target CPU.

See also

■ SYStem.RESet

▲ ’RESET’ in ’EPROM/FLASH Simulator’

Format: RESet


RTP

RTP.CLEAR Clear tracebuffer

See command RTP.CLEAR in 'RAM Trace Port' (trace_rtp.pdf, page 7).

RTP.DirectDataMode tbd.

See command RTP.DirectDataMode in 'RAM Trace Port' (trace_rtp.pdf, page 8).

RTP.DirectDataMode.Mode Direct data mode read/write

See command RTP.DirectDataMode.Mode in 'RAM Trace Port' (trace_rtp.pdf, page 8).

RTP.HaltOnOverflow Halt system on RTP FIFO overflow

See command RTP.HaltOnOverflow in 'RAM Trace Port' (trace_rtp.pdf, page 9).

RTP.Mode Selects the trace mode

See command RTP.Mode in 'RAM Trace Port' (trace_rtp.pdf, page 9).

RTP.OFF Disables the RTP module

See command RTP.OFF in 'RAM Trace Port' (trace_rtp.pdf, page 9).

RTP.ON Activates the RTP module

See command RTP.ON in 'RAM Trace Port' (trace_rtp.pdf, page 10).


RTP.PortClock Configure RTPCLK

See command RTP.PortClock in 'RAM Trace Port' (trace_rtp.pdf, page 11).

RTP.PortSize Size of RTP data port

See command RTP.PortSize in 'RAM Trace Port' (trace_rtp.pdf, page 10).

RTP.Register Display the RTP register

See command RTP.Register in 'RAM Trace Port' (trace_rtp.pdf, page 10).

RTP.RESet Resets RTP settings

See command RTP.RESet in 'RAM Trace Port' (trace_rtp.pdf, page 11).

RTP.state Display RTP setup

See command RTP.state in 'RAM Trace Port' (trace_rtp.pdf, page 12).

RTP.TraceMode Trace mode

See command RTP.TraceMode in 'RAM Trace Port' (trace_rtp.pdf, page 13).

RTP.TraceMode.RAM<x>.SECTion<y> Configures a trace region

See command RTP.TraceMode.RAM<x>.SECTion<y> in 'RAM Trace Port' (trace_rtp.pdf, page 13).

RTP.TraceMode.TraceExclude Invert all trace regions

See command RTP.TraceMode.TraceExclude in 'RAM Trace Port' (trace_rtp.pdf, page 14).


RTS

RTS Real-time profiling (RTS)

Real-time profiling (RTS) is a trace mode that allows to process the trace data while the target is running.

Direct processing is possible for the following command groups:

• COVerage.List*

• ISTATistic.List*

• RTS.PROfile

By default the trace data is discarded after processing, but enabling the Trace.Mode STREAM allows to obtain the trace data for a later analysis.

RTS is currently supported for the following processor architecture/trace protocols:

• ARM ETMv3 and ARM ETMv4

• Nexus for MPC5xxx and QorIQ

• TriCore MCDS

See also

■ RTS.COVerage ■ RTS.FILE ■ RTS.FileCompression ■ RTS.FileLimit ■ RTS.FileMode ■ RTS.Init ■ RTS.ISTATistic ■ RTS.List ■ RTS.ListNesting ■ RTS.LOAD ■ RTS.NestingMode ■ RTS.OFF ■ RTS.ON ■ RTS.PROfile ■ RTS.RESet ■ RTS.state ■ RTS.STATistic ■ RTS.StopOnError ■ RTS.StopOnFifofull ■ RTS.TASKMode ■ RTS.TImeMode ■ COVerage ❏ RTS.ERROR() ❏ RTS.RECORDS()

▲ ’RTS Functions’ in ’General Functions’▲ ’Release Information’ in ’Release History’


RTS.COVerage Code coverage (out of operation)

See also

■ RTS ■ RTS.state

RTS.FILE Set the name for the RTS file (out of operation)

See also


RTS.FileCompression Set compression level for the RTS (out of operation)

See also


RTS.FileLimit Set size limit for the RTS file (out of operation)

See also


Format: RTS.COVerage(command is out of operation)

Format: RTS.FILE <file> (command is out of operation)

Format: RTS.FileCompression OFF | LOW | MID | HIGH(command is out of operation)

Format: RTS.FileLimit <+/- limit_in_bytes>(command is out of operation)


RTS.FileMode Select the data to write to the RTS file (out of operation)

See also


RTS.Init Initialize RTS

Initializes RTS by clearing the RTS data base. Thereupon, all windows showing RTS results are cleared.

See also


RTS.ISTATistic Statistics regarding instruction execution (out of operation)

See also


RTS.List List recorded trace data (out of operation)

See also


Format: RTS.FileMode OFF | Summary | Tasks | FULL (command is out of operation)

Format: RTS.Init

Format: RTS.ISTATistic <view_option> | <modification_option> (command is out of operation)

Format: RTS.List <option> (command is out of operation)


RTS.ListNesting Display function call nesting (out of operation)

See also


RTS.LOAD Mount a file as trace source (out of operation)

See also


RTS.NestingMode Set type of program flow analysis (out of operation)

See also


Format: RTS.ListNesting <option> (command is out of operation)

Format: RTS.LOAD [<file_name>] (command is out of operation)

Format: RTS.NestingMode FLAT | TREE(command is out of operation)


RTS.OFF Deactivate real-time profiling

Ends an RTS session and stops recording new data.

If used with an RTS file (see RTS.FileMode), flushes pending data and processing results to disk. This may require some time to complete.

See also


RTS.ON Activate real-time profiling

Enables real-time profiling and prepares the debugger for processing trace data. The command RTS.ON should be invoked before starting the target so the debugger can synchronize to the beginning of the trace data stream.

If the option RTS.FileMode is enable, the command creates the RTS file. The name of the RTS file is set using RTS.FILE. By convention the file name should end with the extension “.RTS”.

If necessary, RTS.ON creates a backup of a previous file with the same name by changing the extension to *.bak.

Regarding information how to use the file, see RTS.LOAD and the“ARM-ETM RTS User’s Guide” (rts_user.pdf).

See also


Format: RTS.OFF

NOTE: When the RTS file does not contain sensible data (e.g. in the case of an RTS.ON followed immediately by RTS.OFF without processing any data), RTS.OFF deletes the superfluous RTS file. This avoids overwriting an older, potentially important *.bak file at the next RTS.ON.

Generally for important data, it is advisable to make a copy of the last RTS file or rename it immediately after ending the RTS sessions.

Format: RTS.ON


RTS.PROfile Display performance characteristics charts

Displays a window charting the occurrence of events on the vertical axis versus the elapsed time on the horizontal axis. If no <event_option> is specified the following events are displayed: MIPS, READS, WRITES. The default update time is 0.1s.

The events are assigned colors according to their position:

• 1st parameter : red

• 2nd parameter : green

• 3rd parameter : blue

Format: RTS.PROfile [{<event_option>}] [<time>]

<event_option>:

MIPSREADSWRITESTaskSwitches

<time>: 0.1s | 1.0s | 10.s


The following table explains the event options:

See also


RTS.RESet Restore default settings and initialize RTSARM ETMv3, ARM ETMv4, MPC5xxx Nexus, QorIQ Nexus, TriCore MCDS

RTS.RESet restores the default settings and similar to RTS.Init clears the result data base and re-initializes RTS by resetting all internal data structures.

See also


MIPS Number of instructions executed.

READS Number of memory read operations executed by the core.

WRITES Number of memory write operations executed by the core.

TaskSwitches Number of task switches performed.

RTS.PROfile 1.s ; update chart every second

RTS.PROfile READS 10.s ; display chart only for reads; update chart every 10 seconds

Format: RTS.RESet


RTS.state Open status and control windowARM ETMv3, ARM ETMv4, MPC5xxx Nexus, QorIQ Nexus, TriCore MCDS

Opens the RTS status and control window. This window displays the current status of the RTS system, allows to configure the most important options and gives access to various analysis options through the buttons at the left side.

In the following we only describe the fields of the box “utilization”. The fields under utilization have the following meaning:

• The progress bar represents the “fill level” of the buffer holding of data awaiting processing. When the buffer overflows, processing will fail. The number is the amount of pending data in MBs.

• state: the state of RTS (yellow: waiting for synchronization pattern in the trace data stream; green: recording and analyzing trace data; red: an error occurred; blue: not tracing)

• data size: the amount of processed trace data

The field errors displays type of the latest error in plain text and the total accumulated number of errors of any type. The following errors are handled:

• no access to code : the decoder failed to read the opcodes necessary for decoding the trace

Format: RTS.state

A For descriptions of the commands in the RTS.state window, please refer to the RTS.* commands in this chapter. Example: For information about RTS.ON, see RTS.ON.

A


data. Usually this is caused by not copying a range of program code to the debugger’s VM.

• out of memory

• stack overflow, stack underflow : when tracking the program’s calling hierarchy (using RTS.NestingMode.TREE), the debugger maintains information about invocations on an internal stack. The error message is output, when this stack overflows or underflows.

• illegal cancel : a cancel message was found in the trace data stream that should not be there. Applicable only for the ETMV3 protocol.

• flow error : the trace data does not match the executed program. This can be caused by physical transmission errors of the trace data (bad signal quality on the trace port) or because some executed code is missing in the debugger’s VM. Even a single missing or incorrect opcode can cause this problem.

• vtrace error :

• fatal error :

See also

■ RTS ■ RTS.COVerage ■ RTS.FILE ■ RTS.FileCompression ■ RTS.FileLimit ■ RTS.FileMode ■ RTS.Init ■ RTS.ISTATistic ■ RTS.List ■ RTS.ListNesting ■ RTS.LOAD ■ RTS.NestingMode ■ RTS.OFF ■ RTS.ON ■ RTS.PROfile ■ RTS.RESet ■ RTS.STATistic ■ RTS.StopOnError ■ RTS.StopOnFifofull ■ RTS.TASKMode ■ RTS.TImeMode ❏ RTS.ERROR() ❏ RTS.RECORDS()



RTS.STATistic Statistics regarding function invocations

RTS.STATistic implements the <trace>.STATistic functionality for RTS.

The <trace>.STATistic commands work on a data base recording functions calls and function execution time values (min, max). This is in contrast to the <trace>.ISTATistic commands working on the coverage information regarding individual machine instructions.

See also


RTS.StopOnError Configure behavior regarding minor errors

RTS.StopOnError (read “stop on minor errors”) controls the behavior of RTS in case of minor errors like Flow Errors or “no access to code” errors. For more serious errors (out of memory, ...) the RTS decoder always stops processing.

See also


Format: RTS.STATistic <option>(command is out of operation)

<option>: sYmbolAddressLineGROUPAddressGROUPVarDatasYmbolFuncTREEChildTREEParentTREELINKageTASKTASKKernelTASKState

Format: RTS.StopOnError [ON | OFF]


RTS.StopOnFifofull Configure behavior regarding FIFO overflows

Controls the behavior of RTS in case of overflows of the target’s FIFOs.

See also


Format: RTS.StopOnFifofull [ON | OFF]


RTS.TASKMode Configure task analysis

Defines if the analysis considers task information or not.

In the modes STATIC and DYNAMIC, the task switch information in the trace data stream is used to attribute executed opcodes to the correct task.

See also


Format: RTS.TASKMode OFF | STATIC | DYNAMIC(command is out of operation)

OFF The debugger ignores information about task switches in the trace stream.

STATIC The information regarding (all relevant) tasks is retrieved at the beginning of the analysis from the RTOS awareness. Tasks that are created later are not included in the analysis.

The feature is under development.

DYNAMIC The information regarding newly created and terminated tasks is retrieved dynamically from the RTOS awareness while the system runs.

The feature is under development.


RTS.TImeMode Configure analysis of program execution timing

Defines the type of real-time (wall-clock time) information that is gathered and analyzed:

See also


Format: RTS.TImeMode OFF | External(command is out of operation)

OFF no real-time information is generated. Use this for plain code coverage and trace functions.

Sampling Activates a coarse timestamp that is created by the Autofocus preprocessor. It generates very little overhead of trace data at the cost of a lower resolution than cycle-accurate tracing. The timestamp is created approximately every 1000 cycles of the trace clock.

CycleAccurate Uses the cycle-accurate mode of the chip (e.g. ETMV3 cycle accurate mode). If the amount of generated trace in cycle-accurate mode is too big, Sampling may be an alternative.

For using cycle accurate mode, it is necessary to inform the debugger about the targets CPU clock using the command <trace>.CLOCK.

CAVEAT: Currently sampling mode is not supported for CoreSight systems.


RunTime

RunTime Runtime measurement

See also

■ RunTime.Init ■ RunTime.refA ■ RunTime.refB ■ RunTime.RESet ■ RunTime.state ❏ RunTime.ACCURACY() ❏ RunTime.ACTUAL() ❏ RunTime.LAST() ❏ RunTime.LASTRUN() ❏ RunTime.REFA() ❏ RunTime.REFB()

▲ ’RunTime Functions’ in ’General Functions’▲ ’Release Information’ in ’Release History’

Overview RunTime

The RunTime command group and the RunTime() functions allow to measure the time that the target executed code, i.e. the so-called “runtime”. The runtime starts with the target reset and increments while the target executes program code. The target runtime is frozen while the target is stopped.

There are different methods of measuring the runtime with different accuracies. The available methods depend on the target hardware and the debug interface (debugger-based vs. trace-based or emulator-based).

Runtime Measurements Using the Debugger

The RunTime counter allows to measure the program execution times between two breakpoints. The accuracy of the measurement depends on the features provided by the debug interface. The measurement error is displayed as tooltip text.

Or by the function

RunTime.ACCURACY()


There is a number of different CPU and debugger features related to measuring runtime. The following table gives an overview. For details, see further down.

“CPU running” signal

Some processor architectures provide a “CPU running” signal within the debug interface (e.g. DBACK for ARM7/ARM9). This feature allows an exact measurement by the RunTime counter.

Debug Status Messages

Most NEXUS interfaces provide Debug Status Messages which indicate the start/stop of the program execution. The maximum measurement error is calculated as follows:

clock cycles

While MCKOFactor is the value entered via the command SYStem.Option MCKO <factor>.

Hardware signal indicating “CPU stopped”

Some processor architectures provide a “CPU stopped” signal within the debug interface (e.g. DE for the DSP56K). This feature allows an exact stop of the RunTime counter, but the start of the RunTime counter can´t be synchronized exactly with the start of the program execution.

Polling

For most processor architectures the RunTime counter is started/stopped by TRACE32. Thus the measurement can’t be exactly synchronized with the CPU start/stop.

The polling rate can be set with the SYStem.POLLING command. Any polling interval smaller than 1 ms is ignored.

Feature RunTime counteris started...

Runtime counter is stopped...

Accuracy

“CPU running” signal

...after detecting the “CPU running” signal

... after deassertion of the “CPU running” signal

High

NEXUS Debug Status Message

... after receiving the “Debug Mode Left”message

... after receiving the “Debug Mode Entered” message

High

“CPU stopped”signal

...by TRACE32 after starting the CPU

...with the activation of the “CPU stopped” signal

RunTime counter start is imprecise

Polling the PC ...by TRACE32 after starting the CPU

...by TRACE32 after CPU is stopped

RunTime counter start and stop are imprecise

SizeOfMessageFifo 2 MCKOFactor


Runtime Measurements Using TRACE32-ICE / TRACE32-FIRE

The runtime analyzer allows to check program execution times between two breakpoints. Therefore a independent timing analyzer is available to the user. The resolution of runtime measurement is 100 ns. Two reference points may be set in order to evaluate time differences. Total time, as well as the previous emulation command execution time, is automatically recorded. The differences between the individual reference points are displayed in tabular form. Only the execution time of the foreground program is measured. The execution time of the background program is not taken into consideration (only TRACE32-ICE).

Measurement errors due to break sequence

As a result of the break sequence of each individual emulator an absolute timing error of approximately 0.5 … 5 µs occurs. This timing error is dependent upon the CPU's clock frequency and the type of the emulation adapter used. The timing error can only precisely be determined by using time-stamp unit of the logic analyzer. For complex CPUs, additional timing errors in single-step operation can occur during cache memory fill. The timing error can be determined to some extent once a program has been executed by executing first one, and then a set of NOP commands.

Timing errors due to dual-port access

In Wait mode, dual-port access requires up to 1% of total computing time; in Request mode, this can be increased up to 3%. These values are valid for average clock frequencies and when using dynamic memory. By using static memory only, these values will be reduced to one-third. If operating in Denied or Nodelay (GAP, Refresh, Prefetch) mode, no computing will be needed for dual-port access.

Functions related to RunTime

The following functions can be used to obtain various runtime-related values. All the functions return the absolute time the target executed (the “runtime”) since the latest SYStem.Up or RunTime.Init command.

• RunTime.ACTUAL() returns the runtime elapsed until the current moment.

• RunTime.LAST() returns the time of the latest start of program execution e.g. caused by a single Step or Go command.

• RunTime.REFA() returns the reference value A. There is a homonymous command to set the value.

• RunTime.REFB() returns the reference value B. There is a homonymous command to set the value.

• RunTime.LASTRUN() returns the length of the last execution period (e.g. of a single step or the time between a Go and a Break). The value is calculated by:

• RunTime.ACCURACY() returns a measure of the inaccuracy of the runtime values (depends on the measurement method used).

&difftime=CONV.TIMEUSTOINT(RUNTIME.ACTUAL()-RUNTIME.LAST())


RunTime.Init Clear timers

Sets all timers and reference values to zero.

See also

■ RunTime ■ RunTime.state

▲ ’Emulator Functions’ in ’FIRE User’s Guide’▲ ’Execution Time Measurement’ in ’ICE User’s Guide’

RunTime.refA Set reference

Sets the reference value A to the current runtime. Typically the feature is used to record the moment of an “important event” like entering an interrupt handler etc.

The value can also be set by double-clicking the appropriate field in the RunTime.state window.

See also



RunTime.refB Set reference

Sets the reference value B to the current runtime.

The value can also be set by double-clicking the appropriate field in the RunTime.state window.

See also



Format: RunTime.Init

Format: RunTime.refA

Format: RunTime.refB


RunTime.RESet Reset values to zero

Sets all counters and reference values to zero.

See also



RunTime.state Display results

Displays the RunTime counter window with a matrix of values related to runtime measurements.

Each cell of the matrix shows the difference between the value denoted by the column header and the value denoted by the row header. As the first line’s row header is “zero”, the line shows the effective values e.g. (refA - 0), (refB - 0), ... The cell at (column refB / row ref A) shows refB - refA i.e. the runtime between both values.

Reference values can be set to the current runtime (“actual”) by double-clicking the appropriate element.

See also

■ RunTime ■ RunTime.Init ■ RunTime.refA ■ RunTime.refB ■ RunTime.RESet ❏ RunTime.ACCURACY() ❏ RunTime.ACTUAL() ❏ RunTime.LAST() ❏ RunTime.LASTRUN() ❏ RunTime.REFA() ❏ RunTime.REFB()

▲ ’Emulator Functions’ in ’FIRE User’s Guide’▲ ’Execution Time Measurement’ in ’ICE User’s Guide’▲ ’Release Information’ in ’Release History’

Format: RunTime.RESet

Format: RunTime.stateRunTime.view (deprecated)

A Total time since the last SYStem.Up or RunTime.Init

B Time since the latest program start

A

B
