FAQs for TRACE32 Software

ON|GLOBALON <event> <action>

ON|GLOBALON <event> inherit

GLOBALON PBREAK DO myscript.cmm

ON ERROR CONTinue

ON POWERUP GOSUB powerup_handler

General Commands Reference Guide G
General Commands Reference Guide O

PER , "Nested Vectored Interrupt Controller,Interrupt Enable Registers"

• The user can define the STL container type using the sYmbol.AddInfo.Type
• New entry "View Object in Window" is added then to the variable pull down menu
• Var.OBJECT can display the container in a human readable form
• Added type information could be more complicated with if/else/while expressions
• Refer for more information to demo/etc/stl

Data.SAVE.IntelHex dump.hex 0xA0000000--0xA0003fff /TYPE4

SCREEN=
INVISIBLE

SCREEN=OFF

SCREEN=
VICON

TRACE32 Installation Guide

GO sYmbol.EXIT(myfunc)   // go to return statement of myfunc
PRINT Var.VALUE(return)  // get the return value

Var.NEWLOCAL \x        // create artificial variable on the PRACTICE stack
Var.set \x=func3(5,3)  // execute func3() with arguments 5 and 3 on your CPU
PRINT Var.VALUE(\x)    // get the return value

Break.Set \"c:\t32\myproject\myfile.c"\42

Break.Set \myfile\42

• Using the TRACE32 Remote API.
  To launch some scripts or execute some simple commands from a bash shell, you can use the command line tool t32rem from the <T32>/bin/<os> folder. This tool uses the TRACE32 Remote API to send TRACE32 commands to open TRACE32 GUIs.
  For more complex remote control of TRACE32 (e.g. from a Python script) you should have a look at "API for Remote Control and JTAG Access" and "Controlling TRACE32 via Python 3". and the examples at <t32>/demo/api.
• TRACE32 PowerView implements a GDB stub functionality. This provides an interface to any application using the GDB Remote Serial Protocol (RSP) to control TRACE32 PowerView via TCP or UDP.
• Using the Target Communication Framework (TCF), which can be used to access the TRACE32 debug functionality from within Eclipse.

API for Remote Control and JTAG Access
Controlling TRACE32 via Python 3
TRACE32 as GDB Back-End
TRACE32 as TCF Agent

• The object file is corrupted. Please try to re-compile the file.
• The object file has been compiled for a different architecture that the one started with TRACE32 PowerView. You get this error message e.g. if you are loading an ELF file compiled for x86 on TRACE32 PowerView for ARM.
• The file has a format which is not supported by your TRACE32 version. This can happen e.g. if you are using a compiler version newer that the used TRACE32 software. Please try to update to latest TRACE32 release available on the web site or request an interim software update from support@lauterbach.com.
• The object file has a format which is not yet supported by TRACE32 PowerView. Please contact the Lauterbach support and include the object file if possible.

  typedef struct {
      int a;
      int b;
      int d;
  } myStruct_t;

  volatile myStruct_t *dummy;

  gcc  typedef.c  -g  -o typedef.elf  -nostartfiles -nodefaultlibs

  Data.LOAD.Elf typedef.elf /NoClear /NoCODE

• OS.Area <cmdline> : Output in AREA window (blocking)
• OS.Window <cmdline> : Output in "OS.Window" window (blocking) inside PowerView
• OS.screen <cmdline> : On Windows the command gets directly executed without a shell. The output of a console application is shown in a temporary command window. On Linux the output is in the shell, which started the TRACE32 GUI (non-blocking)
• OS.Hidden <cmdline> : No output anywhere (blocking)
• OS.Command <cmdline> : Output in system shell, which allows redirects (non-blocking on Windows / blocking on Linux unless you add an ampersand &)

PowerView Function Reference

• There is more than one location for a variable. This can happen with enabled compiler optimizations. If you open the sYmbol.INFO window for such an optimized variable you can see the various locations of the variable together with a program address range. (When the program counter is inside that program address range, the related location is valid for the variable.)
• At least one of the location descriptions can't be resolved to an address, a general-purpose register, or a stack-frame offset.

• If your ARM debug cable has a serial number starting with "C18" or higher, it is the new "ARM Debug Cable V5" (shipped since 2018). Please ensure you use TRACE32 version R.2017.02 or higher.
• If you use the Automotive PRO cable (LA-2707), ensure you use TRACE32 R.2018.02 or higher.

1. TRACE32 first executes the file autostart.cmm from the TRACE32 system directory (usually C:\T32).
2. autostart.cmm normally starts then the following scripts:
   • system-settings.cmm (from the TRACE32 system directory)
   • user-settings.cmm (from the user settings directory (on Windows %APPDATA%\TRACE32 or ~/.trace32 otherwise))
   • work-settings.cmm (from the current working directory)
3. Finally TRACE32 executes additionally the file specified on the command line (or in T32Start).