Advertisement
Quick Links
Advertisement
Related Manuals for Lauterbach TRACE 32
Summary of Contents for Lauterbach TRACE 32
- Page 1 TRACE 32 In-Circuit Debugger Quick Installation Tutorial...
- Page 2 All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any means without the written permission of Lauterbach Datentechnik GmbH. TRACE32 is a registered trademark of Lauterbach Datentechnik GmbH. Lauterbach Datentechnik GmbH Fichtenstrasse 27...
- Page 3 Table of Contents TRACE32-ICD Preface ________________________ Page PRE-1 What is an In-Circuit Debugger? PRE-1 About this Guide PRE-2 Where to Look for More Information PRE-4 Quick Installation for TRACE32-ICD _____________ Page INST-1 About the Installation Guide INST-1 Product Overview INST-2 System Concepts INST-4 Host Interfaces...
- Page 4 Tutorial for TRACE32-ICD _____________________ Page TUT-1 About the Tutorial TUT-1 Start TRACE32-ICD TUT-2 Setup the Application Properties TUT-3 The Online Help TUT-4 Setup the Debug Environment TUT-7 Batch Jobs TUT-11 The User Interface TUT-13 How to Debug the Program TUT-15 How to Display and Modify CPU Registers TUT-25 How to Display and Modify the Special Function Registers...
- Page 5 TRACE32-ICD Preface What is an In-Circuit Debugger? Most CPUs provide an onchip debug system implemented in the CPU. Typical examples are the BDM interface from Motorola, the JTAG interface for the ARM7 or the JTAG interface for the PowerPC family. The debug interface usually requires a few CPU pins that are used for the communication between the onchip debug system and a third party development tool.
-
Page 6: About This Guide
TRACE32-ICD is part of the TRACE32 microprocessor development tool product line. This product line also includes a trace extension for some ICD-Debuggers and the full featured In-Circuit Emulators TRACE32-ICE for all CISCs and TRACE32-FIRE for the fast RISC processors. In-Circuit Debugger In-Circuit Emulator TRACE32-ICD TRACE32-ICE/FIRE... - Page 7 A simulator can run without a target processor. The work of the CPU is simulated by software. So real time debugging is not possible. You can download our simulators from our web page http://www.lauterbach.com or from our CD TRACE32 Product Information by using the link Download Demo Software in the main menu.
-
Page 8: Where To Look For More Information
Where to Look for More Information The common TRACE32 user interface contains a detailed Online-Help, that offers the most current description of all debug features. If you have installed the TRACE32 software The Online Help on how to start the Online Help. - Page 9 Reference In the Reference book you can find an alphabetical list of all debug commands for the TRACE32 development tools and a detailed description of their syntax and function. All commands not available for TRACE32-ICD are marked with (E − TRACE32-ICE only) or (F −...
- Page 10 Quick Installation for TRACE32-ICD About the Installation Guide This Installation Guide describes the basic installation and configuration for all TRACE32-ICD In-Circuit Debuggers that are implemented using their onchip debug interface. Typical examples for onchip debug interfaces are BDM, JTAG, ONCE … For the installation and configuration of the ROM monitors or for special system configurations (e.g.
-
Page 11: Product Overview
• A PODBUS interface to the host (PODPC, PODPAR or PODETH) • A Debug Module Lauterbach offers two different debug modules: the Standard Debug Module and the Power Debug Module. Both modules can be used all CPUs that are supported by TRACE32-ICD. - Page 12 • A Clock Cable By default TRACE32-ICD uses a fixed clock to run the debug interface. A clock range from 100KHz up to 5 MHz can be used. We also provide a clock cable to allow you the use of the divided CPU clock as clock for the debug interface.
-
Page 13: System Concepts
System Concepts The TRACE32 Debugger Software runs on a host (PC or workstation). The host communicates with the target via the Debug Module. • For the fast communication between the host and the debug module a special bus interface is used: PODBUS (Processor Oriented Device Bus). An advantage of the PODBUS is that your debug environment can be easily expanded by additional PODBUS devices, to provide a powerful tool configuration. - Page 14 Target clock cable DEBUG MODULE PODPC ISA card PODBUS System configuration with ISA card (PODPC) Target clock cable DEBUG standard PODPAR parallel MODULE cable Printer Port parallel (LPTx:) power trigger PODBUS supply in/out AC/DC-adapter System configuration with printer port interface (PODPAR) Quick Installation for TRACE32-ICD...
- Page 15 Target clock cable PC or Workstation DEBUG PODETH MODULE trigger PODBUS in/out AC/DC-adapter System configuration with ethernet interface (PODETH) Quick Installation for TRACE32-ICD...
- Page 16 PODPC Interface Card for ISA bus PODBUS Jumper BNC connector trigger in/out ISA BUS When a PODPC interface card is used no additional power supply is required for additional PODBUS devices. Address select jumpers on the ISA card: Address (hex) Address (dec) JP3 must always be on.
- Page 17 PODPAR Converter for Printer Port (LPTx:) Printer Port power supply trigger in/out PODBUS OUT External power supply is required for the PODPAR (Plug: 7-9V; inner negative, outer positive). Please use only the enclosed AC/DC-Adapter. The BNC connector is used to input/output a trigger signal to/from the Debug Module.For more information on this Trigger feature refer to Trigger in the ICD Users Guide .
- Page 18 PODETH Converter to Ethernet (Twisted Pair) Printer Port trigger in/out Ethernet power supply PODBUS OUT The PODBUS controller for ethernet contains both, an ethernet connector for twisted pair and a printer port interface, to provide a flexible host connection. External power supply is required for the PODETH (Plug: 7-9V; inner negative, outer positive).
- Page 19 The LEDs transmit, receive, collision, link, polarity, jabber indicate the status of the integrated Ethernet transceiver MC68160. LEDs POWER External power is supplied. ACTIVE On if device is active, flashes if device is not used. ERROR On if device is active, flashes if device is not used. In error case an error code will be pulsed.
- Page 20 The Debug Module PODBUS IN connector to host interface connector for debug cable PODBUS OUT connector for additional devices (optional) Some processor types like MPC740/750, PPC603 … require a Power Debug Module. But there is no difference in using this module. LEDs POWER Power is applied to the debug module.
Need help?
Do you have a question about the TRACE 32 and is the answer not in the manual?
Questions and answers