You are on page 1of 12

XCP Debug Back-End

TRACE32 Online Help
TRACE32 Directory
TRACE32 Index
TRACE32 Documents ......................................................................................................................

Debug Back-Ends ..........................................................................................................................

XCP Debug Back-End ................................................................................................................

1

Introduction .............................................................................................................................

2

Related Documents

2

Contacting Support

3

Supported Tools ......................................................................................................................

4

PowerView System Configurations .......................................................................................

5

Configuring XCP ......................................................................................................................

8

Reducing XCP Traffic ..............................................................................................................

9

Command Reference ..............................................................................................................
SYStem.CONFIG XCP

10

XCP specific settings

10

Network address

10

Products ...................................................................................................................................

11

SYStem.CONFIG XCP.SLAVE

Product Information

11

Back-End

11

Front-End

11

Order Information

12

Back-End

12

Front-End

12

©1989-2016 Lauterbach GmbH

XCP Debug Back-End

1

and software-only debug environments. host computer JTAG DAP XCP over TCP (network cable) TCP TRACE32 TCP The figure below shows a typical configuration.pdf) ©1989-2016 Lauterbach GmbH XCP Debug Back-End 2 Introduction . TRACE32 is running on a host computer. please refer to: ”Software-only Debugging (Host MCI)” (app_t32start. Instead of sending debugging commands directly to the target CPU. The 3rd party system translates the XCP commands back into a low-level debug protocol. These XCP commands are then send over the host computers TCP stack and a network cable to the 3rd party system. For more information about software-only debug environments. Typical examples are JTAG and DAP for INFINEON TriCore CPUs. The protocol supports different transport layers. It is standardized by the ASAM e. The 3rd party system can consist of multiple physical components.. e. CPU 3rd party system This document describes how to set up and configure debugging over XCP.V. Some of these measurement and calibration tools implement extensions to the XCP protocol that allow debugging of the target CPU in cooperation with TRACE32. TCP/IP.g.XCP Debug Back-End Version 24-May-2016 Introduction The XCP protocol family allows to control measurement and calibration tools of various vendors. Related Documents For Windows only .The T32Start application assists you in setting up multicore/multiprocessor debug environments. all debugging commands are encoded into XCP commands.

By filling out the system information form completely and with correct data.html or http://www. 1. ©1989-2016 Lauterbach GmbH XCP Debug Back-End 3 Introduction .lauterbach.lauterbach. Preferred: click Save to File. Click Save to Clipboard.com/report. 2. and then paste the system information into your e-mail.com/tsupport.html Here you’ll find local and special support addresses. NOTE: Please help to speed up processing of your support request.com General support address where your request will be answered within a short time if it is a basic support request or redirected to the appropriate address.Contacting Support LAUTERBACH GmbH Altlaufstrasse 40 85635 Hoehenkirchen-Siegertsbrunn Germany Phone (+49) 8102-9876-555 Fax (+49) 8102-9876-187 Internet http://www. 3. To generate a system information report. E-mail support@lauterbach. and send the system information as an attachment to your e-mail. Be sure to include detailed system information about your TRACE32 configuration. choose TRACE32 > Help > Support > Systeminfo. you minimize the number of additional questions and clarification request e-mails we need to resolve your problem.

Supported Tools Vendor Tool Transport ETAS ES592 TCP/IP Comments ©1989-2016 Lauterbach GmbH XCP Debug Back-End 4 Supported Tools .

2. 1. Multiple TRACE32 PowerView instances run on the same host as the back-end. 3. the back-end runs on another host. The dedicated communication process is used when TRACE32 PowerView runs on another hosts in the network or it can be used to run multiple TRACE32 PowerView instances on the back-end host. see Setup 2. Setup 1 Setup with a single TRACE32 PowerView instance running on the same host as the back-end:  .PowerView System Configurations The TRACE32 PowerView instances can be set up in different ways. see Setup 3. too. A single TRACE32 PowerView instance runs on the same host as the back-end.so (back-end) can either run in a dedicated communication process t32mciserver or can be integrated into the TRACE32 PowerView process. The library hostmci. see Setup 1. The TRACE32 PowerView instances run on a dedicated workstation. This configuration can’t handle AMP debug scenarios.

t32 file as follows: PBI=MCILIB .so ©1989-2016 Lauterbach GmbH XCP Debug Back-End 5 PowerView System Configurations .           Modify the config. configure system to use hostmci.

Setup 2 Setup with multiple TRACE32 PowerView instances (AMP) running on the same host as the back-end:  .

set up the usage of hostmci.                Modify the config. server at 30000 for the first instance. consecutive number of instance or AUTO ©1989-2016 Lauterbach GmbH XCP Debug Back-End 6 PowerView System Configurations .t32 as follows: PBI=MCISERVER PORT=30000 INSTANCE=AUTO . .so and open .

Setup 3 Setup with multiple TRACE32 PowerView instances (AMP) running on another host: .

  .

      .

.1 at port 30000 consecutive number of instances avoid to fall into Setup2 case To start TRACE32 PowerView with a specific config file.1 PORT=30000 INSTANCE=AUTO DEDICATED .: bin/pc_linux/t32marm -c config. use e.t32 ©1989-2016 Lauterbach GmbH XCP Debug Back-End 7 PowerView System Configurations . .0.168. .          Start t32mciserver on the simulation host: .168. set up connection to t32mciserver connect to IP 192./t32mciserver port=30000 .t32 file as follows: PBI=MCISERVER NODE=192.g. . start t32mciserver at port 30000 Modify the config.0.

1) and port (12345) of XCP slave SYStem. set IP-Address (192.Configuring XCP A typical start sequence is shown below. select XCP as back-end SYStem.1 12345.CONFIG XCP.168. .168.DEBUGPORT XCP0 . continue with CPU configuration SYStem.cmm) and executed with the command DO <filename>. select CPU SYStem. RESet . This sequence can be written to a PRACTICE script file (*.CONFIG.Attach . connect to XCP slave and CPU ©1989-2016 Lauterbach GmbH XCP Debug Back-End 8 Configuring XCP .0.CPU TC277T .SLAVE 192.0.

read memory of regions .Access VM . TRACE32 has several configuration options that allow adoption to this situation by reducing the amount of generated XCP traffic.ELF *. copy it to VM: Data. VM: memory Onchip.URATE 10s • .List VM: . Therefore. SETUP.Load.elf file is being loaded. MAP.Reducing XCP Traffic Compared to a direct debug connection using a PowerDebug module. the code needs to be copied to the virtual memory when an *. but use . download code to target and . Data. screen will be updated every 10s The command MAP.UpdateOnce can be used to read memory regions only one time after a break is detected.UpdateOnce 0x0++0x1000 • . This can cause longer execution times for polling the CPUs system state or commands executed in PowerView. use VM memory for trace analysis ©1989-2016 Lauterbach GmbH XCP Debug Back-End 9 Reducing XCP Traffic .elf /CopyVM . 0x0--0x1000 . • The most important setting is SETUP.UpdateRATE to configure the update rate of the TRACE32 windows. only one time after break For analysis and data display purposes it is recommended that you use the code from the TRACE32 virtual memory (VM:) instead of the code from the target memory. open source window. The processors state is also polled by this rate. the XCP debug connection shows significantly higher latency.

SLAVE Format: Network address SYStem.SLAVE <address> [<port>] <address> IP address or network name of XCP slave.CONFIG XCP. <port> Parameter Type: Hex value or integer. Port used by XCP slave.CONFIG XCP.CONFIG XCP XCP specific settings SYStem.Command Reference SYStem. ©1989-2016 Lauterbach GmbH XCP Debug Back-End 10 Command Reference .

other platforms on request floating license via RLM (Reprise License Manager) Please add the RLM HostID of the license server to your order (please see our FAQ) ©1989-2016 Lauterbach GmbH XCP Debug Back-End 11 Products .) . Linux or Solaris. Windows64...Products Product Information Back-End OrderNo Code Text LA-9010L 1 User Float. Linux32.virtual prototypes/simulators (VAST..third-party target server (GDB server .) supports TriCore and PCP for Windows32. other platforms on request Front-End OrderNo Code Text LA-8893L 1 User Floating License TriCore Front-End FRONTEND-TC-FL TRACE32 Front-End connecting to . Linux64 and Solaris. CoWare . Lic XCP TriCore Debug Back-End BE-XCP-TC-FL License for debugging the TriCore architecture via Etas XCP for Windows and Linux floating license via RLM (Reprise License Manager) Please add the RLM HostID of the license server to your order (please see our FAQ) Requires RLM floating license server running on Windows..

Code Text LA-9010L BE-XCP-TC-FL 1 User Float. Code Text LA-8893L FRONTEND-TC-FL 1 User Floating License TriCore Front-End ©1989-2016 Lauterbach GmbH XCP Debug Back-End 12 Products .Order Information Back-End Order No. Lic XCP TriCore Debug Back-End Additional Options LA-8893L FRONTEND-TC-FL 1 User Floating License TriCore Front-End Front-End Order No.