ICE/FIRE Analyzer Programming Dialog

Similar documents
ARM-ETM Programming Dialog

TRACE32 Getting Started... ICD In-Circuit Debugger Getting Started... ICD Introduction... 1

TRACE32 Debugger Getting Started... ICD Tutorial About the Tutorial... 2

An Introduction to Komodo

_ V Renesas R8C In-Circuit Emulation. Contents. Technical Notes

TRACE32 Documents... ICD In-Circuit Debugger... Processor Architecture Manuals... NS NS32000 Monitor... 1

Chapter 12 Visual Program Debugger

Training Simulator and Demo Software

Renesas 78K/78K0R/RL78 Family In-Circuit Emulation

Changing the Embedded World TM. Module 3: Getting Started Debugging

Freescale Semiconductor, Inc.

NEW CEIBO DEBUGGER. Menus and Commands

Integration for CodeWright

ICE Performance Analyzer User s Guide

AN1369 APPLICATION NOTE

Application Note for the SNOOPer Trace

NEC 78K0- Family On-Chip Emulation

MPLAB SIM. MPLAB IDE Software Simulation Engine Microchip Technology Incorporated MPLAB SIM Software Simulation Engine

Trace Getting Started V8.02

file://c:\documents and Settings\degrysep\Local Settings\Temp\~hh607E.htm

TDT 1.2 Release Notes and FAQ March 2002

Integration for CodeBlocks

Programming in the MAXQ environment

The following content has been imported from Legacy Help systems and is in the process of being checked for accuracy.

H8 C-SPY. User Guide WINDOWS WORKBENCH VERSION

SMT107 User Manual User Manual (QCF42); Version 3.0, 8/11/00; Sundance Multiprocessor Technology Ltd. 1999

Introduction. This tutorial introduces the following SingleStep features:

Lab 3-2: Exploring the Heap

MCUez MMDS or MMEVS for HC05/08 ezstart GUIDE

ADS MultiTrace Tutorial v2.0

This document describes support for OSEK operating system used with winidea.

Table of Contents. Table of Contents... I. Table of Figures... III. Tutorial VIII-A Nesting Branch General Example...4

Section 1 AVR Studio User Guide

ZCRMZNICE01ZEMG Crimzon In-Circuit Emulator

F²MC-8FX FAMILY MB95100 SERIES EMULATOR HW SETUP 8-BIT MICROCONTROLLER APPLICATION NOTE. Fujitsu Microelectronics Europe Application Note

Quick-Start Guide. BNS Solutions. QSK62P Plus

MULTIPROG QUICK START GUIDE

Using the KD30 Debugger

Lab 8: Debugging Embedded Devices and Software

KIT-VR7701-TP. User's Manual(Rev.1.00) RealTimeEvaluator

DOMAIN TECHNOLOGIES. Getting Started Guide Version 1.1. BoxView IDE. Integrated Development Environment

Assembly Programming in Atmel Studio 7 Step by Step Tutorial

_ V ST STM8 Family On-Chip Emulation. Contents. Technical Notes

ASSIGNMENT ECE514 (COMPUTER ORGANIZATION) ASSIGNMENT NO. 3

Hello and welcome to this Renesas Interactive module that provides an overview of the RX DMA Controller

ZAP Cross Debuggers for Motorola Microcontrollers

JCreator. Starting JCreator

embos Real-Time Operating System embos plug-in for IAR C-Spy Debugger Document: UM01025 Software Version: 3.0 Revision: 0 Date: September 18, 2017

PCAN-Explorer 6. Tel: Professional Windows Software to Communicate with CAN and CAN FD Busses. Software >> PC Software

Profiling Applications and Creating Accelerators

IAR C-SPY Hardware Debugger Systems User Guide. for Renesas E30A/E30 Emulators

Barracuda I and II Chips (I mask is OK36N and II mask is OK79X) PC9S12DP256

User Manual. LPC-StickView V3.0. for LPC-Stick (LPC2468) LPC2478-Stick LPC3250-Stick. Contents

KIT-VR5500-TP. User's Manual(Rev.2.02) RealTimeEvaluator

This chapter introduces how to use the emulator of TOPICE quickly.

Advanced Debugging using the Ashling MPC5500 tools

DDDA User Guide Version 1.5

In-Circuit Emulator. UNetICE for ARM

IN-CIRCUIT DEBUG (ICD) USER GUIDE

ICE Port Analyzer User s Guide

Getting Started in C Programming with Keil MDK-ARM Version 5

FR Family MB Emulator System Getting Started Guide

Repetition and Loop Statements Chapter 5

RTOS Debugger for RTX-ARM

embos Real-Time Operating System embos plug-in for IAR C-Spy Debugger Document: UM01025 Software Version: 3.1 Revision: 0 Date: May 3, 2018

TRACE32 Documents... ICD In-Circuit Debugger... Processor Architecture Manuals... TriCore... TriCore Monitor... 1

ZAP Cross Debuggers for STMicroelectronics Microcontrollers

1 Introduction to MARS

EMUL-AVR-PC. User Guide

KIT-VR4120-TP. User's Manual (Rev.1.01) RealTimeEvaluator

Getting Started in C Programming with Keil MDK-ARM Version 5

A Quick Introduction to MPLAB SIM

Getting Started in C Programming with Keil MDK-ARM Version 5

Lab 0 Introduction to the MSP430F5529 Launchpad-based Lab Board and Code Composer Studio

Lab 2: Basic Assembly Programming and Debugging using AVR Studio. Due: December 13, 2011

XDS560 Trace. Technology Showcase. Daniel Rinkes Texas Instruments

Digital Electronics & Computer Engineering (E85)

RTE-V850E/GP1-IE USER'S MANUAL (REV.1.01) RealTimeEvaluator

IP Routing Lab Assignment Configuring Basic Aspects of IP IGP Routing Protocols

Getting Started. In This Chapter

CFC. Special functions from SIMATIC S7 CFC V7.0 SP1 onwards

4 DEBUGGING. In This Chapter. Figure 2-0. Table 2-0. Listing 2-0.

TREX Set-Up Guide: Creating a TREX Executable File for Windows

Support for RISC-V. Lauterbach GmbH. Bob Kupyn Lauterbach Markus Goehrle - Lauterbach GmbH

Figure 1. JTAGAVRU1 application The JTAGAVRU1 is supported by AVR Studio. Updated versions of AVR Studio is found on

OS Awareness Manual Sciopta

EMUL-PPC-PC. Getting Started Guide. Version 1.0

KIT-V850E2/MN4-TP-H. User s Manual (Rev. 1.01) RealTimeEvaluator

W7100A / W7100. Version WIZnet Co., Inc. All Rights Reserved. For more information, visit our website at

DOMAIN TECHNOLOGIES INC. Users Guide Version 2.0 SB-USB2. Emulator

Hands-on CUDA exercises

Stimuli Generator User s Guide

System Messages - Numerical List

A & A Library - Network Install

CodeWarrior. Microcomputer Architecture and Interfacing Colorado School of Mines Professor William Hoff

Megawin 8051 OCD ICE

3 TUTORIAL. In This Chapter. Figure 1-0. Table 1-0. Listing 1-0.

Development Tools. 8-Bit Development Tools. Development Tools. AVR Development Tools

Application Note for the Trace.Find Command

As CCS starts up, a splash screen similar to one shown below will appear.

Transcription:

ICE/FIRE Analyzer Programming Dialog TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents... FIRE In-Circuit Emulator... ICE Analyzer System... FIRE Analyzer Programming... ICE/FIRE Analyzer Programming Dialog... 1 Introduction... 2 How to Start 2 Programming... 3 Elements in the Dialog Box 3 Actions 4 Conditions 6 Levels 7 Load, Save and Clear 7 Definitions 9 Address/Range Definition 9 Data Definition 12 Counter Definition 15 Examples 18 Example 1: Selective Trace on a Single Address 18 Example 2: Selective Trace on a Symbol 19 Example 3: Selective Trace on an Address Range 21 Example 4: Selective Trace on an Address Range defined through a Symbol 22 Example 5: Selective Trace on Write Access to a Symbol 24 Example 6: Selective Trace on Value on Data Bus 26 Example 7: Trace all and mark with Label A beginning from 2 µs 28 Example 8: Trace all, mark the Cycles executed in Function Sieve with Label B and mark the Entrance of Function Sieve with Label A 30 Example 9: Trace all, when Function Sieve is reached goto Level 1 and stop Sampling and Debugging after 5 Cycles 31 ICE/FIRE Analyzer Programming Dialog 1

ICE/FIRE Analyzer Programming Dialog Version 14-Nov-2018 Introduction How to Start The Analyzer Programming Dialog can be found on any TRACE32 CD dated May 1999 and later. To start select under the menu Analyzer the option Trigger Definition > Dialog. An empty dialog box will appear. Please go on reading this manual to get an overview on the functionality of the dialog. ICE/FIRE Analyzer Programming Dialog 2

Programming Elements in the Dialog Box Remark The intension of the Analyzer Programming Dialog Window is to provide an intuitive and easy to use interface to program the Analyzer Trigger Unit. The Analyzer Programming Dialog Window does not represent the full functionality of the Analyzer Trigger Unit. Overview Address definition Data definition Count definition Condition Pannel to controll the programming ICE/FIRE Analyzer Programming Dialog 3

Actions Actions ICE/FIRE Analyzer Programming Dialog 4

An Analyzer Trigger Program executes ACTIONS depending on the current situation of the user program/target hardware. Sample Stop Analyzer Stop CPU&Analyzer Mark A Mark B Mark C Inc Count0 Inc Count1 Restart Count0 Restart Count1 Goto Level0 Goto Level1 Goto Level2 Samples only the specified CPU cycles (Selective Tracing) Stops tracing Stops CPU and tracing Put a marker with label A, B or C to the line in the trace output Increment the counter identified by the label COUNT0 or COUNT1. Set the counter identified by the label COUNT0 or COUNT1 to zero. Go on tracing according to the actions defined under Level0, Level1 or Level2. ICE/FIRE Analyzer Programming Dialog 5

Conditions One situation of the user program/target system is described by different characteristics. Different characteristics combinded throught LOGICAL AND form a definite condition. An action will only be carried out if the program/target system reaches the situation defined through the condition. The characteristics are: Address/Range RD/WR Data Count Address or address range To be defined in the address definition fields A-Range, B-Range or C-Range CPU cycle type READ, WRITE or ACCESS (READ or WRITE) CPU data To be defined in the data definition fields DATA0 or DATA1 Counter or Time Counter To be defined in the count definition fields COUNT0 or COUNT1 If no characteristic is chosen the action is carried out at every CPU cycle. ICE/FIRE Analyzer Programming Dialog 6

Levels Three different levels can be used to define a set of actions. The levels can be referenced by the logical names Level0, Level1 and Level2. At any time only one of this sets of actions can be carried out. Use the action Goto Level1 to let the system carry out only the actions under Level1 beginning from a definite condition. For this example all CPU cycles are collected and marked with label A in the output until the address A- Range is reached. From that time on all CPU cycles are collected and marked with label B in the output. Load, Save and Clear At the bottom of the dialog you find the buttons to controll where your dialog will be stored. Use the button CLEAR to reset the dialog window if you want to begin from the scratch. With the button LOAD an analyzer program can be read into the dialog window. Only analyzer programs written with the Analyzer Dialog can be loaded into the dialog again. Press the button VIEW and you will see the contents of the dialog written down in statements of the analyzer programming language. Use this button now and then to learn the basics of the analyzer programming language. ICE/FIRE Analyzer Programming Dialog 7

Program Analyzer will write the contents of the dialog to the file which is specified under Actual used file:. After that the analyzer will be programmed. If no file name is given you will be asked to define one. The analyzer is successfully programmed if you get the message Otherwise a message box shows the error. Special for C166 Before the analyzer is programmed you will be asked Press OK if you want to go on programming the analyzer. But be aware that all breakpoints you set before will be deleted. Program Analyzer & Close works the same as Program Analyzer except that the dialog will be closed after the analyzer is programmed successfully. ICE/FIRE Analyzer Programming Dialog 8

Definitions Address/Range Definition Up to three diffent address areas can be defined in this part of the dialog. This areas are later referenced by the logical names A-Range, B-Range or C-Range. The logical name AB-Range defines an area declared throught the area A-Range combined with the area B-Range by LOGICAL AND. Each area e.g. A-Range allows to define the address space throught tree different singular address parts. One of this part can hold a single address or an address range. All three singular address parts are combinded throught LOGICAL OR to form the charcteristic named A-Range. If you don t know how to specify an address or an address range just click the V button. With the appearing subdialog a single address or any kind of range can be defined easily. ICE/FIRE Analyzer Programming Dialog 9

As you are familiar with the syntax of defining an address in TRACE32 just fill out the dialog. The defined address area will be used to define the condition for carrying out an action in the main dialog. If not address area is defined at the time you want to choose an address area name you will be asked to do so. ICE/FIRE Analyzer Programming Dialog 10

ICE/FIRE Analyzer Programming Dialog 11

Data Definition Two different data values can be used to observe the data on the databus. The data values are later referenced by the labels DATA0 and DATA1. The data is defined through the value and the type. If you don t know how to specify a data value just click the V button. With the appearing subdialog a single data, a data range or a mask can be defined easily. ICE/FIRE Analyzer Programming Dialog 12

With the type you specify the width of the value and the position on the databus. Depending on your CPU you have different types available. Databus 8 bit B Byte size and whole databus Databus 16 bit B B0 B1 W0 W Byte size and anywhere on the databus Byte size and at the lower byte of the data bus Byte size and at the upper byte of the data bus Word size and lower word on data bus Word size and any position on data bus Databus 32 bit B B0 B1 B2 B3 W0 W1 W2 W L0 L Byte size and anywhere on the databus Byte size and at the lower byte of the lower word on data bus Byte size and at the upper byte of the lower word on data bus Byte size and at the lower byte of the upper word on data bus Byte size and at the upper byte of the upper word on data bus Word size and lower word on data bus Word size and middle word on data bus Word size and upper word on data bus Word size and any position on data bus Double word size and lower double word on data bus Double word size and any position on data bus For details on other data types see Analyzer Programming Guide chapter Data Selectors. ICE/FIRE Analyzer Programming Dialog 13

As you are familiar with the syntax of defining data in TRACE32 just fill out the dialog. If there is no data defined at the time you want to use a data name you will be asked to do so. ICE/FIRE Analyzer Programming Dialog 14

Counter Definition For controlling the flow two different counters can be defined. For each counter you can define the maximum value and if you want to define the counter as time counter the unit. The counters are referenced in the condition of an action by the labels COUNT0 and COUNT1. If you use the COUNT0/1 in the way showed above the sampling begins when the counter COUNT0 has reached the value of 12 ks. But as there are no actions defined to set the counter COUNT0 this will never happen. To control the value of the counters the actions Inc Count0/1 and Restart Count0/1 are available. ICE/FIRE Analyzer Programming Dialog 15

Inc COUNT0/1 adds 1 to the value of the counter COUNT0/1. Restart COUNT0/1 sets the value of the counter COUNT0/1 to zero. If you don t know how to define the value of a counter just click the V button. As you are familiar with the syntax of defining counters in TRACE32 just fill out the dialog. If there is no counter defined at the time you want to use a counter name in a condition or an action you will be asked to define it. ICE/FIRE Analyzer Programming Dialog 16

ICE/FIRE Analyzer Programming Dialog 17

Examples Example 1: Selective Trace on a Single Address Click here to open the Define Address Window Enter the address and confirm with OK. ICE/FIRE Analyzer Programming Dialog 18

Example 2: Selective Trace on a Symbol Click here to open the Define Address Window Click here to browse through the symbol data base Select the symbol by a double click ICE/FIRE Analyzer Programming Dialog 19

ICE/FIRE Analyzer Programming Dialog 20

Example 3: Selective Trace on an Address Range Click here to open the Define Address Window 1. Click here to select the radio button for Range 2. Click here to choose a memory class out of the list of available classes 3. Type in the base address of the range 4. Type in the end address of the range 5. Press OK button ICE/FIRE Analyzer Programming Dialog 21

Example 4: Selective Trace on an Address Range defined through a Symbol Click here to open the Define Address Window Click here to select the radio button for HLL-Range Select the symbol by a double click Press the V button ICE/FIRE Analyzer Programming Dialog 22

ICE/FIRE Analyzer Programming Dialog 23

Example 5: Selective Trace on Write Access to a Symbol Click here to open the Define Address Window Click here to browse through the symbol data base Select the symbol by a double click ICE/FIRE Analyzer Programming Dialog 24

ICE/FIRE Analyzer Programming Dialog 25

Example 6: Selective Trace on Value on Data Bus Click here to open the Define Data Window Click here to select the width of the value Type in the value Click here to select a single value Press OK ICE/FIRE Analyzer Programming Dialog 26

ICE/FIRE Analyzer Programming Dialog 27

Example 7: Trace all and mark with Label A beginning from 2 µs Click here to open the Define Counter Window Click here to select a Time Counter Type in the value Click here to select time unit ICE/FIRE Analyzer Programming Dialog 28

ICE/FIRE Analyzer Programming Dialog 29

Example 8: Trace all, mark the Cycles executed in Function Sieve with Label B and mark the Entrance of Function Sieve with Label A Define the begin of function sieve as A-Range Define the end of function sieve as B-Range Display was cut here ICE/FIRE Analyzer Programming Dialog 30

Example 9: Trace all, when Function Sieve is reached goto Level 1 and stop Sampling and Debugging after 5 Cycles Define the begin of function sieve in A-Range Change level if sieve is reached Always set COUNT0 to zero Add one to COUNT0 every cycle Stop sampling and debugging when COUNT0 reaches 5 (decimal) ICE/FIRE Analyzer Programming Dialog 31

Debugger stops here Level is changed Sampling stops here ICE/FIRE Analyzer Programming Dialog 32