TRACE32 Training... Training FIRE Emulator... Training FIRE Basics... 1

Transcription

1 Training FIRE Basics TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Training... Training FIRE Emulator... Training FIRE Basics... 1 System Architecture... 5 Host Interfaces 6 Parallel Interface 6 USB Interface 6 PODBUS Interface (PODBUS Ethernet Interface) 7 Starting-up the TRACE32-FIRE... 8 System Settings 8 Mapper 15 Initialize the Special Function Registers 22 Download the Program 22 Initialize the Registers 22 Start-Up File 23 TRACE32 GUI Main Menu Bar and Accelerators 26 Main Tool Bar 27 Window Area 28 Command Line 31 Command Structure 31 Command Examples 32 The Online Help for a specific Command 33 Standard Parameter Syntax 34 Message Line 35 Softkeys 36 State Line 37 Registers Display the CPU Registers 38 Colored Display of changed Registers 39 Modify the Contents of a CPU Register 40 Display the Special Function Registers 41 Tree Display 41 Full Display 42 Training FIRE Basics 1

2 Details about a Single SFR 43 The PER Definition File 44 Modify a Special Function Register 45 Data and Program Memory Run-time Memory Access 46 Display a Hex Dump 47 Data Dump Dialog Box 51 Dump Window 53 Indirect Dump 56 Modify Memory 57 Display a Source Listing 58 Changing Code Lines 60 Breakpoints Implementation 61 Software Breakpoints 61 On-chip Breakpoints 62 On-chip Breakpoints (Overview) 64 Hardware Breakpoints 65 Breakpoint Types 66 Program Breakpoints 66 Read/Write/Access Breakpoints as Onchip 67 Read/Write/Access Breakpoints as Hardware 68 Auto Implementation of Breakpoints 69 How to use the different Breakpoint Implementations Software Breakpoints 70 Hardware Breakpoint/Address Selectors 70 On-chip Breakpoints 71 Breakpoint Handling Break.Set Dialog Box 72 The HLL Check Box 73 Implementations 75 Actions 76 Options 80 Data Breakpoints 83 Advanced Breakpoints 85 Counter 86 Condition 88 CMD 90 TASK 93 Display a List of all Set Breakpoints 95 Delete Breakpoints 96 Enable/Disable Breakpoints 96 Training FIRE Basics 2

3 Store Breakpoint Settings 97 Debugging Basic Debug Control 98 Flag Memory Read Flag 101 Write Flag 103 Document your Results Print your Results 105 Save your Results to a File 107 Training FIRE Basics 3

4 Training FIRE Basics Version 22-Mar-2018 Training FIRE Basics 4

5 System Architecture FIRE System Controller provides the connection to the host system (LPT, ISA-Card, Ethernet, USB) runs the FIRE system software FIRE Port Analyzer allows to sample the port states and to trigger on the port states provides 64 k trace memory, 64 channels, 20 ns time stamp state mode, latch mode, timing mode, transient mode FIRE Emulation Controller provides all CPU indepenent emulator functions (VCO, Pulse Generator, Universal Counter) provides the trace memory (64 k frames) provides the trigger unit FIRE Emulation Memory 1, 2 or 4 MByte dual-ported emulation memory 1, 2 or 4 MByte address selector/flags memory FIRE Probe provides the CPU dependent debugger, trace and trigger features Mapper, Dualport Controller Target Adapter BGA/QFP adapter Training FIRE Basics 5

6 Host Interfaces Parallel Interface The software runs on PC. Symbol and debug information is handled on the PC. Executable T32m<cpu>.exe (e.g. t32m166.exe) PC Printer Port (LPTx:) standard parallel cable parallel Parallel Interface TRACE32-FIRE USB Interface The software runs on PC. Symbol and debug information is handled on the PC. Executable T32m<cpu>.exe (e.g. t32m166.exe) PC USB Connector standard USB cable USB Interface TRACE32-FIRE Training FIRE Basics 6

7 PODBUS Interface (PODBUS Ethernet Interface) The software can run in the PODETH box. Symbol and debug information is handled in the PODETH box. The main task of the host is to display the information and to accept the commands. Executable T32win.exe (former t32w95.exe). on the host system. Symbol and debug informtion is handled on the host. Requires Bootflash V4.0. Executable T32m<cpu>.exe. Ethernet 10/100 BaseT, Twisted Pair Ethernet HUB PC or Workstation PODETH PODBUS PODBUS Interface TRACE32-FIRE Training FIRE Basics 7

8 Starting-up the TRACE32-FIRE Starting up the RISC emulator is done in the following steps: 1. Set the system settings and activate the emulator 2. Configure the mapper 3. Download the program 4. (Set PC and SP) System Settings Select the used CPU SYStem.CPU Select CPU access mode Training FIRE Basics 8

9 Select the System Mode AloneInt Emulator is working in stand-alone mode. The internal (emulator) clock is used and all lines to the target are blocked. Command: SYStem.Mode AloneInt Is also used as Standalone Reset: AloneExt The emulator is working in stand-alone mode. The external (target) clock is used and all lines to the target are blocked. EmulInt EmulExt The emulator works with access to the target system and uses the internal (emulator) clock. Command: SYStem.Mode EmulInt The emulator works with access to the target system and uses the external (target) clock. Command: SYStem.Mode EmulExt Is also used as In Target Reset: SYStem.ModeI <mode> Select operation mode Training FIRE Basics 9

10 Set-up the Realtime Memory Access The realtime memory access allows access to the memory while the CPU is executing the program. The main advantages of the realtime memory access on TRACE32-FIRE are: to read memory/variables while the program is running to write memory/variables while the program is running to set trigger programs while the program is running to display the flag memory while the program is running But this memory accesses should not have an effect on the realtime behavior. Training FIRE Basics 10

11 Dual-port Access Via the FIRE controller the memories within the FIRE can be read or written to while the CPU is executing the program. This means for the user: Read and write access to the emulation memory Trigger programming Read access to the flag memory There is no effect on the realtime behavior or the effect is very small. FIRE Controller Flag Memory Address Selector Memory Emulation Memory Dual-port access Debug Monitor/ On-Chip Debug Support Emulation CPU Target Internal/External Mapping Dualport Controller TimeRequest Timeout for the dualport access. After the specified time the attempt to do a dualport access will be aborted and an error message will be displayed. Training FIRE Basics 11

12 Access via the CPU Support Some CPUs supports memory read and write while the CPU is executing the program (SH7055, ST10, MCS12). Memory access via on-chip debug support FIRE Controller Dual-port access to Address-Selector and Flag Memory Debug Monitor/ On-Chip Debug Support Flag Memory Address Selector Memory Emulation Memory Emulation CPU Target Internal/External Mapping Dualport Controller Via the CPU support, the target/emulation memory can be read or written to while the CPU is executing the program. Trigger Programming and the read access to the Flag Memory are done via the dual-port access. This means for the user: Read and write access to the target/emulation memory Trigger programming Read access to the flag memory while the CPU is executing the program. The effect on the realtime behavior is very small. Advantages: small effect to the real-time behavior, access to the target memory. Training FIRE Basics 12

13 CPU Access For the CPU access the program execution is stopped for a moment to read or write to memory. Memory access via short CPU stop FIRE Controller Address Selector Memory Dual-port access to Address-Selector Memory Debug Monitor/ On-Chip Debug Support Emulation CPU Target Internal/External Mapping Dualport Controller This means the user has: Read and write access to the target memory Trigger Programming via CPU access while the CPU is executing the program. The effect on the realtime behavior is big and depends on the CPU. Advantages: access to the target memory, higher speed SYStem.CpuAccess SYStem.MemoryAccess Select CPU access mode Select memory access mode Both access modes are independent from each other. If both access modes are enabled, TRACE32-FIRE selects always the less intrusive one. Training FIRE Basics 13

14 For all CPU specific settings refer to Help FIRE Target Manual. System Settings should be done in a batch job on command level. STORE <filename> SYSTEM automatically converts the setting in the System window to a batch file. Training FIRE Basics 14

15 Mapper Memory Usage The FIRE-RAM is a 64-bit memory. For a 32-bit CPU there a 2 different ways to use this memory: 32-bit emulation/overlay memory 32-bit address selector memory 32-bit emulation/overlay memory 32-bit flag memory Memory Size The block size for the mapper depends on the size of the FIRE-SRAM/ZRAM: Module Size 1M + 1M 2M + 2M 4M + 4M 8M + 8M 16M + 16M Block Size 256K 256K 512K 1M 2M The FIRE-ARAM supports only 1 block: Module Size 1M + 1M 4M + 4M Block Size 1M 4M Training FIRE Basics 15

16 1 MByte block 0x0--0xffff 1 MByte block 0x x11ffff 1 MByte block 0x x22ffff 1 MByte block 0x x33ffff MAP.state State display Access time of the emulation memory Type of the emulation memory Number of used blocks Number of available blocks Size of the used address selector/flag memory Size of the available address selector/flag memory Size of the used address emulation memory Size of the available emulation memory Training FIRE Basics 16

17 Activate the Memory By default (no mapping is done or after MAP.RESET) the emulator always sees the target memory. Commands for Memory Allocation: MAP.RESet Resets the mapper MAP.Ram [<range>] [/<option>] Allocate emulation memory MAP.ReadFlag [<range>] [/<option>] MAP.WriteFlag [<range>] [/<option>] MAP.NoFlag [<range>] [/<option>] Allocate flag memory for read accesses Allocate flag memory for write accesses Free flag memory For some CPUs the on-chip ROM/FLASH or on-chip RAM is automatically replaced by emulation memory (e.g. H8S). In this case Address Selector Memory/Flag Memory is also available. For more information refer to your target guide Help FIRE Target Manual. If Address Selector Memory is used, the complete memory can only be used as Address Selector Memory. If Flag Memory is used, the complete memory can only be used as Flag Memory. Memories can not be mapped independently. If emulation memory is mapped, address selector or flag memory can only be mapped for the same memory range. Training FIRE Basics 17

18 After the memory allocation you have to decide where you want to use emulation memory and where you want to use target memory. MAP.Intern [<range>] MAP.Extern [<range>] Use emulation memory Use target memory - default If emulation memory is mapped, the emulation memory will be located parallel to the target memory. Emulation CPU Emulation Memory Target Memory Memory Write Cycles Emulation CPU At memory read cycles the mapper decides which data are used by the CPU Emulation Memory Target Memory Memory Read Cycles Training FIRE Basics 18

19 Examples Examples 1 (PowerPC860) MAP.RESet MAP.Ram 0x0--0xfffff MAP.Intern 0x0--0xfffff ; reset mapper ; allocate emulation memory ; memory accesses in the range from ; 0x0--0xfffff are done to overlay/ ; emulation memory Examples 2 (H8S) MAP.RESet MAP.Ram 0x0--0x3ffff MAP.Ram 0x x3ffff MAP.Intern 0x0--0x3ffff MAP.Intern 0x x3ffff ; reset mapper ; allocate emulation memory ; memory accesses in the range from ; 0x0--0x3ffff and 0x x3ffff ; are done to overlay/emulation memory Overlay/emulation memory is automatically mapped for the on-chip memory Training FIRE Basics 19

20 Examples 3 (ARM7) MAP.RESet MAP.Ram 0x0--0x1ffff MAP.Ram 0x xffff MAP.Ram 0xA xffff MAP.Ram 0xB xffff MAP.Ram 0xC xffff MAP.Ram 0xD xffff MAP.Ram 0xE xffff MAP.Ram 0xF xffff ; reset mapper ; allocate emulation memory For the complete address range the target memory is valid memory. The emulation memory exists parallel to the target memory. All write accesses to the target memory are also visible in the emulation memory. This mapping provides: Memory/variable read access via the dual-port access Trigger programming via the dual-port access Access to the Flag memory via the dual-port access while the CPU is executing the program Realtime write accesses are only possible by using CPUAccess Mode. Training FIRE Basics 20

21 Examples 4 (PowerPC860) MAP.RESet MAP.Ram 0x0--0xfffff MAP.ReadFlag 0x0--0xfffff MAP.Intern 0x0--0xfffff ; reset mapper ; allocate emulation memory ; allocate flag memory ; memory accesses in the range from ; 0x0--0xfffff are done to overlay/ ; emulation memory Examples 5 (PowerPC860) MAP.RESet MAP.Ram 0x0--0xfffff MAP.WriteFlag 0x0--0xfffff MAP.Intern 0x0--0xfffff ; reset mapper ; allocate emulation memory ; allocate flag memory ; memory accesses in the range from ; 0--0fffff are done to overlay/ ; emulation memory Training FIRE Basics 21

22 Examples 6 (H8S) MAP.RESet MAP.Ram 0x0--0x3ffff MAP.Ram 0x x3ffff MAP.Intern 0x0--0x3ffff MAP.Intern 0x x3ffff MAP.ReadFlag 0x0--0x3ffff MAP.ReadFlag 0x x3ffff MAP.ReadFlag 0xffdc00--0xfffbff ; reset mapper ; allocate emulation memory ; memory accesses in the range from ; 0--0fffff are done to overlay/ ; emulation memory ; allocate flag memory ; allocate flag memory for on-chip ; memory Initialize the Special Function Registers Main task of this step is to prepare the memories, so that the program can be loaded with the next step. Data.Set [<address> <range>] %<format> /<option> Initialize SFRs Download the Program Data.LOAD.<subcommand> <filename> </option> Compiler specific load command Compiler-specific load command can be found in the FIRE Target Guide. Menu: Help FIRE Target Guide, section Compiler. Initialize the Registers Register.Set <register> <value> Set register Training FIRE Basics 22

23 Start-Up File It is recommanded to write a batch job to setup the RISC emulator TRACE32-FIRE to guarantee a proper start-up sequence. Default extension for a batch job is.cmm. Example for H8S: SYStem.RESet MAP.RESet MAP.Ram 0x0--0x3ffff MAP.Ram 0x x3ffff MAP.Intern 0x0--0x3ffff MAP.Intern 0x x3ffff SYStem.CPU H8S2338 SYStem.CPU EXP16M16 SYStem.Mode AloneInt ; Reset system settings and mapper ; Allocate emulation memory ; memory accesses in the range from ; 0x0--0x3ffff and ; 0x x3ffff are done ; to overlay/emulation memory ; Select CPU and CPU mode ; Activate the emulator in ; stand-alone mode Data.Set 0x0fffed1 0x0fc Data.LOAD.Ubrof iarh8s.dbg WinPOS 0% 0% 100% 50% Data.List WinPOS 0% 50% 50% 50% Var.Frame /Locals /Caller WinPOS 50% 50% 50% 50% Var.Watch Var.AddWatch ast Var.AddWatch flags ; Load the user program ; Open a few windows ENDDO A first example for a start up batch job can be found in the FIRE Target Guide. Menu: Help FIRE Target Guide, section Quick Start. Training FIRE Basics 23

24 Run the Start-up File DO <filename> [<parlist>] Start a batch file If a batch file t32.cmm exists, this batch file is automatically executed, when the TRACE32 software is started. The software looks for this file in: the working directory the system directory Training FIRE Basics 24

25 TRACE32 GUI Main Menu Bar + Accelerators Main Tool Bar Local Buttons Local Popup Menu The structure and functionality of the GUI is defined by the file t32.men in the TRACE32 system directory. TRACE32 allows you to modify the GUI so it will better fit to your requirements. Training FIRE Basics 25

26 Main Menu Bar and Accelerators The main menu bar provides all important TRACE32 functions sorted by groups. For often used commands accelerators are defined. Accelerators A user specific menu can be defined very easily: MENU.AddMenu <name> <command> MENU.RESet Add a user menu Reset menu to default Menu.AddMenu "Set PC to main" "Register.Set pc main" Menu.AddMenu "Set PC to main, ALT+F10" "Register.Set pc main" ; User menu with accelerator User Menu For more complex changes to the main menu bar refer to the training section: Menu Programming Training FIRE Basics 26

27 Main Tool Bar The main tool bar provides fast access to often used commands. The user can add his own buttons very easily: MENU.AddTool <tooltip text> <tool image> <command> MENU.RESet Add a button to the toolbar Reset menu to default MENU.AddTool "Set PC to main" "PM,X" "Register.Set PC main" User specific button Information on the <tool image> can be found in Help -> TRACE32 Documents -> IDE User Interface -> -> IDE Reference Guide -> MENU -> Programming Commands -> TOOLITEM. For more complex changes to the main tool bar refer to the training section: Menu Programming Training FIRE Basics 27

28 Window Area Save Page Layout No information about the page layout is saved when you exit TRACE32. To save the window layout use the Store Window to command in the Window menu. Store Windows to generates a batchfile, that allows you to reactivate the current page- and window-configuration at any time. Batchfile for page- and window-configuration: ; And Mon Jan 19 13:06: B:: TOOLBAR ON STATUSBAR ON WINPAGE.RESET WINPAGE.CREATE P000 WINCLEAR WINPOS W000 B::d.l WINPOS W001 B::v.f /l /c WINPOS W002 B::v.l %m %r %t WINPAGE.CREATE P001 WINCLEAR WINPOS W005 B::A.T d.0--7 WINPOS W004 B::T.L WINPAGE.SELECT P000 ENDDO Training FIRE Basics 28

29 Training FIRE Basics 29 Run the batchfile to reactivate the stored page- and window-configuration

30 Modify Window The Window Header displays the command which was executed to open the window By clicking with the right mouse button to the window header, the command which was executed to open the window is re-displayed in the command line and can be modified there Training FIRE Basics 30

31 Command Line Command line Command Structure Device Prompt Selects the command set used by the TRAC32: no device prompt E:: B:: F:: TRACE32-IDE command set for TRACE32-ICE command set for TRACE32-ICD (Debugger) command set for TRACE32-FIRE (RISC Emulator) Training FIRE Basics 31

32 Command Examples Data Data.dump Data.List Data.LOAD Command group to display, modify memory Displays a hex dump Displays a source listing Loads code to the target memory Break Break.Set Break.List Break.Delete Command group to set, list, delete breakpoints Sets a breakpoint Lists all set breakpoint Deletes a breakpoint Each command can be abbreviated. The significant letters are always written in upper case letters. Data.dump 0x x2000 /Byte Option Subcommand Command group Parameter Training FIRE Basics 32

33 The Online Help for a specific Command Enter the command to the command line. Add one blank. Push F1 to get the on-line help for the specified command. Training FIRE Basics 33

34 Standard Parameter Syntax RADIX.<mode> Define parameter syntax The RADIX defines the input format for numeric values. RADIX.Decimal RADIX.Hex Number base is decimal and C-like operators are used Number base is hex and C-like operators are used (default) Examples: Decimal Hex Data.dump d 100h Data.dump d 100d Data.dump 0x h 100h To see the currently used parameter syntax, enter RADIX. to the command line. Training FIRE Basics 34

35 Message Line Message Area Message Line Message line for system and error messages Message Area window for the display of the last system and error messages Training FIRE Basics 35

36 Softkeys The softkey line allows to enter a specific command step by step. Select the command group Select the subcommand Angle brackets request an entry from the user. Here e.g. the entry of an <address> or a <range>. Get a display of all options Select an option Training FIRE Basics 36

37 State Line Symbolic and absolute address at the blue cursor State of the system Debug mode Training FIRE Basics 37

38 Registers Display the CPU Registers Training FIRE Basics 38

39 Colored Display of changed Registers Register.view /SpotLight The registers changed by the last step are marked in dark red. The registers changed by the step before the last step are marked a little bit lighter. This works up to a level of 4. If SpotLight is ON, the SpotLight feature is automatically on for: 1.) all Variable windows 2.) the Register window this includes also register bits 3.) the Peripheral window 4.) the hll stack frame 5.) all Data.dump windows The SpotLight feature will be only valid for windows, which will be opend after activating this feature. Register.view [/<option>] SETUP.Var %SpotLight Display CPU registers Switch the option SpotLight on for all Variable windows, the Register window, the Peripheral window, the HLL Stack Frame window and all Data.dump windows Training FIRE Basics 39

40 Modify the Contents of a CPU Register By double clicking to the register contents a Register.Set command is automatically displayed in the command line. Enter the new value and press Return to modify the register contents. Register.Set <register> <value> Modify CPU register Training FIRE Basics 40

41 Display the Special Function Registers TRACE32 supports a free configurable window to display/manipulate configuration registers and the on-chip peripheral registers at a logical level. Predefined peripheral windows are available for most standard CPUs. Tree Display The individual configuration registers/on-chip peripherals are organized by TRACE32 in a tree structure. On demand, details about a selected register can be displayed. Training FIRE Basics 41

42 Full Display Sometimes it might be useful to expand the tree structure from the start. Use the right mouse and select Show all PER.View, "Clocks and Power Control" PER.View, "*" ; Display the functional unit ; "Clocks and Power Control" in ; expanded mode ; Display all functional units in ; expanded mode The following command sequence can be used to save the contents of all configuration registers/on-chip peripheral registers to a file. PRinTer.FileType ASCIIE PRinTer.FILE Per.lst WinPrint.Per.view, "*" ; Select ASCII ENHANCED as output ; format ; Define Per.lst as output file ; Save contents of all ; configuration registers/on-chip ; periperal registers to the ; specified file Training FIRE Basics 42

43 Details about a Single SFR The address, bit position and the full name of the selected item are displayed in the state line; the full name of the selected item is taken from the CPU manual. Training FIRE Basics 43

44 The PER Definition File The layout of the PER window is described by a PER definition file. The definition can be changed to fit to your requirements using the PER command group. The path and the version of the actual PER definition file can be displayed by using: VERSION.SOFTWARE PER.view <filename> [<tree-search-item>] Display the configuration registers/on-chip peripherals PER.view C:\T32\perarm9t.per ; Use the peripheral file perarm9t.per ; instead of the default PER definition ; file Training FIRE Basics 44

45 Modify a Special Function Register You can modify the contents of a configuration/on-chip peripheral register: By pressing the right mouse button and selecting one of the predefined values from the pulldown menu. By a double-click to a numeric value. A PER.Set command to change the contents of the selected register is displayed in the command line. Enter the new value and confirm it with return. PER.Set.simple <address> <range> [<%format>] <string> Data.Set <address> <range> [<%format>] <string> Modify configuration register/on-chip peripheral Modify memory PER.Set.simple D:0xF87FFF10 %Long 0x00000b02 Training FIRE Basics 45

46 Data and Program Memory Depending on the setting of the mapper target memory or emulation memory is displayed and can be modified. Run-time Memory Access TRACE32-FIRE allows display and modification of memory, while the CPU is executing the program. The way the memory access is done depends on the settings in the system window: Training FIRE Basics 46

47 Display a Hex Dump Address Training FIRE Basics 47

48 Address Range If you enter an address range, only the specified address range will be displayed. This is useful if a memory area close to an I/O area should be displayed and you do not want the development tool to generate read cycles for the I/O area. Conventions for address ranges: <start address>--<end address> <start address>..<end address> <start address>++<offset_in_byte> Training FIRE Basics 48

49 Symbol or Label Use i to select any symbol name or label from the internal symbol data base. By default an oriented display is used (line break at 2 x ). A small arrow indicates, where the selected dump area starts. Training FIRE Basics 49

50 HLL Expression If HLL is ON and the entered variable is a pointer the address range where the pointer is pointing to is displayed Training FIRE Basics 50

51 Data Dump Dialog Box Display Width Default is the data bus width of the CPU Run-time Update default: the Dump window is only updated, when the program execution is stopped Realtime update of the Dump window is switched ON. Realtime update is done depending on the settings of MemAccess and CPUAccess in the System window If CPUAccess is used the red S in the state line indicates, that the system is no longer running in realtime (each update takes between 1-100ms) Training FIRE Basics 51

52 Other Options Other options Track: (see section Indirect dump) Oriented: By default an oriented display is used (line break at 2 x ). If Orient is OFF, the Dump window starts at the given address. Oriented display No oriented display Ascii: By default ASCII characters are displayed together with the hex. memory contents. Spotlight: The option Spotlight can be used to highlight the memory locations that changed while single stepping. The memory location changed by the last step is marked in dark red. The memory location changed by the step before the last step is marked a little bit lighter. This works up to a level of 4. Training FIRE Basics 52

53 Dump Window Find With the Find button a Find in Memory Dialog Box is opened, that allows to search a specific data in a specified memory range. Training FIRE Basics 53

54 Modify With the Modify Button a Modify Memory Dialog Box is opened, that provides a number of operations to modify or test memory. Operation Fill Pattern Test Copy Compare Sum Fill the specified memory range with the user defined data (see also Data.Set command). Fill the specified memory range with a predefined pattern (see also Data.PATTERN command). Test the specified memory range (see also Data.Test command). Copy data from one memory range to another (see also Data.COPY command). Compare the specified memory ranges (see also Data.ComPare command). Build the checksum over the specified memory range (see also Data.SUM command). Training FIRE Basics 54

55 Display Width Check Boxes Switch ON/OFF the run-time memory access Switch ON/OFF the track option Switch the hex display ON/OFF Switch the ASCII display ON/OFF Training FIRE Basics 55

56 Indirect Dump Indirect dump indexed by register R1 With the track option the address indexed by the current contents of register R1/SP is always displayed in the middle of the window and is highlighted Data.dump [<address> <range>] [/<option> ] Data.View %<format> [<address> <range>] [/<option>] Display a memory dump Display a detailed dump Training FIRE Basics 56

57 Modify Memory By double clicking to a data field a Data.Set command is automatically displayed in the command line, you can enter the new value and confirm it with return. Data.Set [<address> <range>] %<format> /<option> Modify memory Training FIRE Basics 57

58 Display a Source Listing Displays Source listing around the PC If the debug mode Mixed is active a mixed source listing is displayed. If the HLL mode is active only the hll lines are displayed. Training FIRE Basics 58

59 Displays Source listing of the selected Function Select the function you want to display Data.List [<address>] [/<option>] Data.ListAsm [<address>] [/<option>] Data.ListHll [<address>] [/<option>] Data.ListMix [<address>] [/<option>] Display source listing Display source listing in assembler Display source listing in hll Display source listing in assembler and hll Training FIRE Basics 59

60 Changing Code Lines TRACE32 provides its own assembler. Use Assemble here to enter new assembler code Use Modify here to modify the current assembler code Data.Assemble [<address>] <mnemonic> Assemble code line Training FIRE Basics 60

61 Breakpoints Implementation Software Breakpoints The original instruction at the breakpoint address is patched by a special instruction (usually TRAP) to stop the program and return the control to the Debug Monitor or BDM/JTAG interface. This method requires RAM/emulation memory at the break positions.the number of software breakpoints is unlimited. Training FIRE Basics 61

62 On-chip Breakpoints Most CPUs have an onchip trigger unit, that provides on-chip breakpoints. TRACE32-FIRE uses by default software breakpoints on instructions. The on-chip breakpoints can be used to: To set breakpoints to ROM, FLASH or EEPROM. This is only necessary if the target memory is not replaced by emulation memory. To set an on-chip breakpoint to an instruction you can change the default implementation for a specific memory range to onchip MAP.BOnchip <address_range> To set an on-chip breakpoint to an instruction you can select the implementation Onchip explicitly. Training FIRE Basics 62

63 To set breakpoints on Read/Write Accesses Training FIRE Basics 63

64 On-chip Breakpoints (Overview) The following list gives an overview of the usage of the on-chip breakpoints by TRACE32-FIRE: CPU Family On-chip breakpoints: Total amount of available on-chip breakpoints. Instruction breakpoints: Number of on-chip breakpoints that can be used to set program and spot breakpoints into ROM/FLASH/EEPROM. Read/Write breakpoints: Number of on-chip breakpoints that can be used as read or write breakpoints. Data breakpoint: Number of onchip data breakpoints that can be used to stop the program when a specific data value is written to an address or when a specific data value is read from an address. CPU Family On-chip Breakpoints Instruction Breakpoints Read/Write Breakpoints Data Breakpoints MPC800/500 4 Instruction / 2 Data ARM7 2 (Reduced to 1 if software breakpoints are used) 2/1 2/1 2 H8S SH MCS Training FIRE Basics 64

65 Hardware Breakpoints Hardware breakpoints are memory based breakpoints. They use the address selector memory and can be used to set Read/Write breakpoints. Training FIRE Basics 65

66 Breakpoint Types Breakpoint Type Program Read, Write, ReadWrite Implementation Software (Default) Onchip Onchip (Default) Hardware Program Breakpoints Set a program breakpoint by double clicking with the left mouse button to the instruction The program stops before the instruction marked by the breakpoint is executed. Disable the program breakpoint by a double click to the red program breakpoint indicator. The program breakpoint indicator becomes grey. Training FIRE Basics 66

67 Read/Write/Access Breakpoints as Onchip The number of on-chip breakpoints is always limited. CPU stops shortly after the write access Advantages: Read/Write/Access breakpoints can be set to address ranges, even if it is not possible to map Address Selector Memory to this locations (e.g. ports) Training FIRE Basics 67

68 Read/Write/Access Breakpoints as Hardware Read/Write/Access breakpoints should be used as hardware breakpoints: if the number of on-chip breakpoints is exceeded if the on-chip breakpoints are not suitable (e.g. no exact range possible) Read/Write/Access breakpoints as hardware breakpoints requires address selector memory at the break location. Implementation Hardware has to be selected Training FIRE Basics 68

69 Auto Implementation of Breakpoints Program Breakpoint Software Breakpoint On-chip Breakpoint (after MAP.BOnchip <range>) Read/Write/Access Breakpoint On-chip Breakpoint Hardware The auto implementation can be changed by Break.SELect <brktype> <impl> Breakpoint implementation The implementation of the Read and Write Breakpoints is changed to Hardware Training FIRE Basics 69

70 How to use the different Breakpoint Implementations Software Breakpoints Program Realization: The original instruction at the breakpoint address is patched by a special instruction to stop the program and to return control to the Debug Monitor or BDM/JTAG interface. This method requires RAM/emulation memory at the break position. Advantage: unlimited number of breakpoints Hardware Breakpoint/Address Selectors Read Write Realization: These breakpoints are realized by programming the FIRE trigger unit. Break.Program IF ReadBreak&&Read Break.Program IF WriteBreak&&Write for the Read breakpoint for the Write breakpoint This means, that Read and Write breakpoints can only be set, if it is possible to map address selector memory to the break address. These trigger programs are not visible for the user. Advantage: unlimited number of single breakpoints and breakpoint ranges Training FIRE Basics 70

71 On-chip Breakpoints Program Realization: The onchip trigger unit is programmed to set these breakpoints. Advantage: program breakpoints to ROM/FLASH Disadvantage: limited number of breakpoints Read Write Realization: The onchip trigger unit is programmed to set these breakpoints. Advantage: easy combination of read/write breakpoints and data in the Break dialog box Advantage: read/write breakpoints can also be set to addresses where it is not possible to map address selector memory e.g. ports (CPU specific) Disadvantage: limited number of breakpoints Training FIRE Basics 71

72 Breakpoint Handling Break.Set Dialog Box or Training FIRE Basics 72

73 The HLL Check Box (asm breakpoint) HLL The entered address/label is marked by the selected breakpoint. The address range used by the entered HLL expression is marked by the selected breakpoint. Single Address HLL check box OFF Training FIRE Basics 73

74 Complete Variable HLL check box ON HLL-Expression HLL check box ON Training FIRE Basics 74

75 Implementations Implementation Implementation Auto Soft HARD On-chip Use predefined implementation for the breakpoint. Implement breakpoint as software breakpoint. Implement breakpoint as hardware breakpoint. The resources for the hardware breakpoints are provided by the TRACE32 development tool. Hardware breakpoints are not available for most CPUs. Implement breakpoint as on-chip breakpopint. The resources for onchip breakpopints are provided by the CPU. Training FIRE Basics 75

76 Actions By default the program execution is stopped when a breakpoint is hit (action stop). TRACE32 provides the following additional reactions on a breakpoint hit: Action (debugger) stop Spot Alpha Beta Charly Delta Echo Stop program execution (default). If a breakpoint is combined with the action Spot, the program execution is stopped shortly at a breakpoint hit to update the screen. As soon as the screen is updated, the program execution continues. Set an Alpha breakpoint. Set a Beta breakpoint. Set a Charly breakpoint. Set a Delta breakpoint. Set an Echo breakpoint. Training FIRE Basics 76

77 Alpha, Beta, Charly, Delta and Echo breakpoint are only used in very special cases. For this reason no description is given in the general part of the training material. Training FIRE Basics 77

78 Example for the Action Spot The information displayed on the screen is by default only updated, when the CPU stops the program execution and switches to the debug mode. The action spot can be used to turn a breakpoint into a watchpoint. The CPU stops the program execution at the watchpoint, switches to debug mode, updates the screen and restarts the program execution automatically. This takes ms depending on the speed of the debug interface and the amount of information displayed on the screen. Example 1: Update the screen whenever the program executes the instruction sieve\17. A spotpoint is active and the system is no longer running in realtime Training FIRE Basics 78

79 Example 2: Update the screen whenever the program writes to flags[3] A spotpoint is active and the system is no longer running in realtime Training FIRE Basics 79

80 Options Options Temporary DISable DISableHIT ON: Set a temporary breakpoint. All temporary breakpoints are deleted the next time the CPU stops the program execution. OFF: Set a permanent breakpoint (default). OFF: Breakpoint is enabled (default). ON: Set breakpoint, but disabled. ON: Disable the breakpoint when the breakpoint is hit. Training FIRE Basics 80

81 Example for the Option Temporary Sets a temporary breakpoint Start the program with Go All temporary breakpoints are automatically deleted after the next program stop Training FIRE Basics 81

82 Example for the Option DISableHit Disable the program breakpoint at the function entry to sieve, after the breakpoint was hit. As soon as the breakpoint is hit, it is disabled Training FIRE Basics 82

83 Data Breakpoints The DATA field offers the possibility to combine a Read/Write breakpoint with a specific data value. This is only possible if your CPU provides data breakpoints. Example: Stop the program execution if a 1 is written to flags[3]. Training FIRE Basics 83

84 If a HLL expression is used TRACE32 gets the information if the data is written via a byte, word or long access from the symbol information. If an address or symbol is used the user has to specify the access width. Training FIRE Basics 84

85 Advanced Breakpoints If the advanced button is pushed additional input field are appended to the Break.Set dialog box to provide advanced breakpoint features Advanced breakpoint input fields Training FIRE Basics 85

86 Counter Allows to stop the program execution on the n th hit of a breakpoint. Software Counter If the CPU does not provide debug counters, the counter is implemented as a software counter. Example: Stop the program execution after the function sieve was entered times. Training FIRE Basics 86

87 The Counter is implemented by software. When the breakpoint is reached, the CPU is stopped for a moment to increment the counter. The current counter value is visible in the Break.List window. If the counter has reached its final value the program execution is permanently The red S indicates, that the system is no longer running in realtime Training FIRE Basics 87

88 Condition The program execution is stopped at the breakpoint only if the defined condition is true. Example: Stop the program execution on a write to flags[3] only if flags[12] is equal to 0 when the breakpoint is hit. When the breakpoint is reached, the CPU is stopped for a moment, the condition is checked and the program execution continues when the condition is not true. Due to this the program is not longer running in real time. The red S indicates, that the program is no longer running in realtime Training FIRE Basics 88

89 Conditions not in HLL Syntax It is also possible to write register-based or memory-based conditions. Examples: Stop the program executions on a write to address flags if Register R11 is equal to 1. Switch HLL OFF ; stop the program execution at a write to the address flags if the ; register R11 is equal to 1 Break.Set flags /Write /CONDition Register(R11)==1 ; stop program execution at a write to the address flags if the long ; at address D:1000 is larger then Break.Set flags /Write /CONDition Data.Long(D:1000)>12345 Training FIRE Basics 89

90 CMD The field CMD allows to specify 1 or more commands that are executed when the breakpoint is hit. Example: Write the contents of flags[12] to a file whenever the write breakpoint at flags[12] is hit. OPEN #1 outflags.txt /Create ; open the file for writing The specified command(s) is executed whenever the breakpoint is hit. With RESUME ON the program execution will continue after the execution of the command(s) is finished. The cmd field in the Break.List window informs the user which command(s) is associated with the breakpoint. R indicates It is recommanded to set RESUME to OFF, if CMD starts a PRACTICE script with the command DO commands are used that open processing windows like Trace.STATistic.Func, Trace.Chart.sYmbol or CTS.List because the program execution is restarted before these commands are finished. Training FIRE Basics 90

91 The state of the debugger toggles between going and stopped close #1 ; close the file when you are done Display the result: Training FIRE Basics 91

92 Example for Data, Condition and CMD It is also possible to combine the advanced features. Example: Write the contents of flags[3] to a file when a 0 is written to flags[3] when flags[12] is equal to 1. Training FIRE Basics 92

93 TASK The program execution is stopped at the breakpoint only if the specified task is running. Example: Stop the program execution at thread_0_entry\16 only if thread0 is running. When the breakpoint is hit, the CPU is stopped for a moment to check if the specified task s running. If not, the program execution continues.if yes, the program execution is stopped. Due to this the program is no longer running in real time. Training FIRE Basics 93

94 The red S indicates, that the program is no longer running in realtime Training FIRE Basics 94

95 Display a List of all Set Breakpoints address types impl action options data count condition cmd (command) R (resume) task Physical address of the breakpoint Type of the breakpoint Implementation of the breakpoint or disabled Action selected for the breakpoint Option defined for the breakpoint Data value that has to be read/written to stop the program execution by the breakpoint Current value/final value of the counter that is combined with a breakpoint Condition that has to be true to stop the program execution by the breakpoint Commands that should be executed after the breakpoint hit R ON: continue the program execution after the defined commands were executed Name of the task for a task-related breakpoint Symbolic address of the breakpoint Break.List [/<option>] List all breakpoints Training FIRE Basics 95

96 Delete Breakpoints Break.Delete <address> <address range> [/<type>] [/<implem.>] [/<option>] Var.Break.Delete <hll-expression> [/<type>] [/<implem.>] [/<option>] Delete breakpoint Delete hll breakpoint Enable/Disable Breakpoints Break.ENable [<address> <address range>] [/<option>] Break.DISable [<address> <address range>] [/<option>] Enable breakpoint Disable breakpoint Training FIRE Basics 96

97 Store Breakpoint Settings // AndT32 Fri Jul 04 13:17: B:: BREAK.RESET B.S func4 /P /DISABLEHIT B.S sieve /P V.B.S \\diabp555\global\flags[3]; /W /DATA.BYTE 0x1; ENDDO STOre <filename> Break Generate a batch for breakpoint settings Training FIRE Basics 97

98 Debugging Basic Debug Control There are local buttons in the Data.List window for all basic debug commands Step Single stepping e.g. Step 10. Over Next The Call is executed in real time but for the user it seems to be only one step over the call. Next sets a temporary breakpoint to the next assembler or hll line and starts then the program execution. This command is useful to overstep a subroutine call or to leave a loop. Program Counter With Next a temporary breakpoint is set to the next written code line, here e.g. to leave the loop Training FIRE Basics 98

99 Return Return sets a temporary breakpoint to the last instruction of a function and then starts the program execution. After pressing Return the program execution is stopped at the last instruction of the function Up This command is used to return to the function that called the current function. For this a temporary breakpoint is set at the instruction directly after the function call. Press Up to return to the function that called the current function Display the hll stack to see the function nesting Training FIRE Basics 99

100 Step <count> Step.Over Step.Change <expression> Step.Till <boolean _expression> Var.Step.Change <hll_expression> Var.Step.Till <boolean _hll_expression> Single step Step over call Step until <expression> changes Step until <boolean _expression> becomes true Step until <hll_expression> changes Step until <boolean _hll_expression> becomes true Go [<address> <label>] Go.Next Go.Return Go.Up [<level> <address>] Start program execution Run program until the next code line is reached Run program until the end of the hll function is reached Run program until it returns to the caller function Training FIRE Basics 100

101 Flag Memory Read Flag MAP.ReadFlag Map read flag MAP.RESet MAP.Ram 0--0xfffff MAP.ReadFlag 0--0xfffff MAP.Intern 0--0xfffff ; reset mapper ; allocate emulation memory ; allocate flag memory ; memory accesses in the range from ; 0--0fffff are done to overlay/ ; emulation memory The ReadFlag can be used for Code coverage: The Flag system can not decide, if a prefetched instruction is executed or not. Short skips are not detected as not executed code. Prefetches at the end of a functions sets some flag bits in the next function Training FIRE Basics 101

102 Not-fetched instructions are bold printed on a yellow background Training FIRE Basics 102

103 Write Flag MAP.WriteFlag Map write flag MAP.RESet MAP.Ram 0--0xfffff MAP.WriteFlag 0--0xfffff MAP.Intern 0--0xfffff ; reset mapper ; allocate emulation memory ; allocate flag memory ; memory accesses in the range from ; 0--0fffff are done to overlay/ ; emulation memory FLAG.ListVar [<addressrange>] [<item>] Code-coverage variables Training FIRE Basics 103

104 The Write Flag can also be used for stack depth analysis: Training FIRE Basics 104

105 Document your Results Print your Results Requires a printer configuration in the file config.t32. E.g. for Windows PRINTER=WINDOWS For other host platform refer to the host platform specific section of the Installation Guide. Print a Hardcopy of the TRACE32 Application Window Training FIRE Basics 105

106 Print the Contents of a Specific Window Select the Print item in the window manager menu to print the window contents. Print any Result To print more complex results e.g over several pages: WinPrint.<command> Pre-command for complex outputs WinPrint.Data.dump 0x x1fff WinPrint.Trace.List (-1000.)--(-500.) Training FIRE Basics 106

107 Save your Results to a File Select the Output Format for the File Switch the File radio button to ON PRinTer.FileType <format> Select file format Training FIRE Basics 107

108 Open the File for Printing Print 1 output to 1 file WinPrint.Data.dump 0x xfff Training FIRE Basics 108

109 Print n outputs to n files If the file name includes a number, this number is automatically incremented after each output. WinPrint.Data.dump 0x xfff Go Break WinPrint.Data.dump 0x xfff The number within the file name is automatically incremented Training FIRE Basics 109

110 Print n outputs to 1 file PRinTer.OPEN [<filename>] PRinTer.CLOSE Open permanent output file for results Close permanent output file for results PRinTer.OPEN outpd WinPrint.Data.dump 0x xfff Go Break WinPrint.Data.dump 0x xfff PRinTer.CLOSE Training FIRE Basics 110

111 Reset Output to Printer Switch the Printer radio button to ON Training FIRE Basics 111