Drivers series SIGNUM SYSTEMS CORPORATION RDI Drivers for Third Party ARM Debuggers with JTAGjet Installation Instructions
COPYRIGHT NOTICE Copyright (c) 2007 by Signum Systems Corporation. All rights are reserved worldwide. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of Signum Systems.
This document describes the installation process for the RDI, or Remote Debug Interface, driver used with the Signum emulators for the ARM processors. Outlined are the software configuration processes for several popular ARM debuggers. (Other RDI compatible debuggers should be configured similarly.) Purpose Installing the Driver 1. Insert the Development Tools for Microsoft Windows CD into the CD-ROM drive. In the Master Setup dialog box, select Drivers/Arm/RDI Driver for Signum Emulators (Figure 1).
SI GNUM 2. S YS TE MS When the Setup program starts, select the program folder for the program icons and the destination folder for the RDI driver to be installed in. FIGURE 2 Selecting the folder for the driver.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 3 Confirming the driver location. 3. Connect the emulator JTAG cable to the JTAG connector on your ARM system or evaluation board. Use either the 20-pin or the 14-pin JTAG connector, depending on your target board. For examples of connecting the emulator with selected target boards, see the ARM Board Setup User Guide. Turn the emulator on first, and then turn on your target board.
SI GNUM • • • • • • • • • • S YS TE MS ARM Ltd. RealView Debugger ARM Lt. AXD, SDT and ADS Debuggers eSol eBinder GNU gdb Debugger Green Hills Software Multi-2000 Debugger IAR Software Embedded Workbench for ARM (EWARM) Keil uVision3 Mentor Graphics XRAY Metrowerks CodeWarrior Palm Software Universal Debugger (PUD) p. 4 p. 7 p. 9 p. 10 p. 12 p. 13 p. 15 p. 16 p. 19 p. 20 ARM Ltd. RealView Debugger Note: RealView Debugger version 3.1 no longer supports RDI connections (http://www.arm.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 5 The Connection Control dialog box. 3. The RDI Target List dialog box appears. Press the Add DLL button (Figure 6) and browse for the driver file SigJdsDI.dll found in typical installations in the \Signum\RDI folder. FIGURE 6 The RDI Target List dialog box. 4. Enter a name and description for the new target connection (Figure 7). Click OK.
SI GNUM S YS TE MS FIGURE 7 Naming and describing the new target connection. 5. Make sure that the new target entry appears in the RDI target list (Figure 8) and close the RDI Target List dialog box. FIGURE 8 The augmented target list. 6. 6 In the Connection Control dialog box, right-click the new connection entry and select Configure Device Info from the popup menu (Figure 9).
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 9 The augmented target list. When the RDI Configuration dialog box appears, proceed to section Configuring the Connection on p. 22 to complete the system configuration process. ARM Ltd. AXD, SDT and ADS Debuggers The ARM RDI driver for Signum emulators is compatible with all the ARM debuggers that conform to the RDI specification, including: • • • ARM extended Debugger (AXD) for Windows, ARM Debugger for Windows SDT 2.
SI GNUM S YS TE MS FIGURE 10 Selecting the driver DLL. 3. 8 Press the Add button. In the Windows Open dialog, navigate to the ARM RDI driver file. If you accepted the defaults from the Installing the Driver section, the path to the driver file should be C:\Signum\RDI\SigJdsRDI.dll. Click the Open button. The driver is now listed in the Choose Target dialog box.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 11 The RDI driver for the Signum emulator is now available. Press the Configure button to configure the connection between your debugger and the Signum emulator. Proceed to section Configuring the Connection on p. 22. eSOL eBinder The eBinder Development Suite is provided with a Board Support Package (BSP) for a specific platform.
SI GNUM 2. S YS TE MS Proceed to section Configuring Note: To set a system variable on a the Connection on p. 22, keeping Windows XP system, click Start | in mind that semihosting should Control Panel | Systems | Advanced be turned off (see Figure 28 | Environment Variables. For later in the text). Whenever you information about other systems, load an application program to please refer to the documentation of the target board from within the specific OS.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H 2. Start the gdb debugger. To establish connection with the GDBserver, run “target remote :” command, as shown in the following examples. • J T A G J E T Note: The server folder contains the cygwin1.dll library file. You may want to rename this file if it is in conflict with your version of cygwin1.dll.
SI GNUM S YS TE MS Start address 0x8000, load size 10137 Transfer rate: 81096 bits in <1 sec, 151 bytes/write. (gdb) p /x $pc $1 = 0x8000 (gdb) break main Breakpoint 1 at 0x8220: file x.c, line 34. (gdb) c Continuing. Breakpoint 1, main () at x.c:34 34 a = 0; . . . And so on Green Hills Multi2000 Debugger ! To configure the GreenHills Software Multi2000 Debugger: 1. Start the MULTI debugger. In the Target menu, select Show Connection Organizer (Figure 12).
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 13 Choosing the JTAGjet.con file in the Connection Organizer. 3. Right-click in the dialog box. From the popup menu, select Copy. Choose [User Methods] from the drop-down list Copy Selected Connections To. Click OK. Close the Connection Organizer dialog box. 4. In the Target menu, press Connect To Target. Choose the JTAGjet target and press Connect. The RDI Configuration dialog appears.
SI GNUM 5. S YS TE MS Choose Options from the Project menu. The Options for Target dialog box appears. Select the Debugger category. In the Setup tab, choose RDI as the driver (Figure 14). FIGURE 14 Selecting the driver type for C-Spy. 6. 14 Select the RDI tab. In the Manufacturer RDI Driver edit box, navigate to the SigJdsRDI.dll file in the C:\Signum\RDI directory (Figure 15).
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 15 Selecting the RDI driver DLL file for C-Spy. Press OK to close the dialog box. In the RDI menu, select Configure to open the RDI Configuration dialog. Proceed to section Configuring the Connection on p. 22. Keil uVision3 ! To configure the Keil uVisoin3 debugger: 1. From the Project menu choose Options For Target. The Options for Target dialog box appears. In the Debug tab, check Use RDI Interface Driver (Figure 16.
SI GNUM S YS TE MS FIGURE 16 Selecting the driver type for uVision3. 2. Press the Settings button. In the RDI Interface Driver Setup dialog box, navigate to the SigJdsRDI.dll file in the C:\Signum\RDI directory, (Figure 17). FIGURE 17 Selecting the RDI driver DLL file for uVision3. 3. Press the Configure RDI Driver button to open the RDI Configuration dialog. Proceed to section Configuring the Connection on p. 22. Click OK to close the dialog box.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T %XRAY_HOME%\etc\aro.brd (in default installations, the file c:\MGC\embedded\xrayose\etc\aro.brd): is + JTAGjet 0 "Signum JTAGjet" "RDI 1.5" \ { type=multi-ice:endian=little:chip=ARM7TDMI: rdilib="C:\Signum\RDI\SigJdsRDI.dll" } To avoid mistakes, you may want to copy the text from the C:\Signum\RDI\Config\XRAY\signum_aro.brd file. The leading + character instructs the debugger to connect automatically to the emulator.
SI GNUM S YS TE MS FIGURE 18 Setting up the connection between XRAY and JTAGjet manually. The JTAGjet RDI 1.5 server should appear in the Connect tab. FIGURE 19 A log of a successful connection established between the target and the emulator. Note: To modify the emulator configuration at a later time, make sure that the debugger is not running. Press the system Start button and select Signum Systems RDI from the Programs (or All Programs under Windows XP) menu.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T Metrowerks CodeWarrior ! To configure the Metrowerks CodeWarrior debugger: 1. Select Preferences form the Edit menu. The IDE Preferences dialog appears (Figure 20). Press the Add button to add (create) a new connection. FIGURE 20 The IDE Preferences dialog box. 2. In the New Connection dialog box (Figure 21): • • • • Choose a name for your connection, e.g., JTAGjet. Select ARM RDI from the Debugger drop-down list.
SI GNUM • S YS TE MS Select Configure to open the RDI Configuration dialog and proceed to section Configuring the Connection on p. 22. FIGURE 21 The IDE New Connection dialog box. Palm Universal Debugger (PUD) ! To configure the Palm Universal Debugger: 1. Select Preferences from the Edit menu. The Debugger Preferences dialog box appears. 2. In the Category pane, select ARM under the Debugger Plugins entry. In the Debugger Plugins/ARM Settings pane, select ARM RDI1.5 Protocol Plugin as the protocol.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 22 Selecting the protocol for the ARM Debugger Plugin. 3. In the Category pane, select ARM RDI 1.5 under the Protocols entry. In the Debugger Plugins/ARM Settings pane, navigate to the SigJdsRDI.dll file to set the Path to RDI DLL entry. In a standard installation, the SigJdsRDI.dll file is located in the C:\Signum\RDI folder. See Figure 23. FIGURE 23 Selecting the path to the RDI 1.5 DLL file for the ARM RDI 1.
SI GNUM S YS TE MS The debugger attempts to connect to the emulator. If the JTAGjet has not yet been configured, the RDI Configuration dialog appears. Proceed to section Configuring the Connection on p. 22. Configuring the Connection 1. In the Configuration dialog that appears, make sure that the Connection tab is selected. FIGURE 24 Configuring the emulator: the Connection tab. • 2. 22 To establish a debugger-emulator connection with minimum effort, press the Connect Automatically button.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H • J T A G J E T If your JTAG chain contains a single ARM device, select the processor from the CPU list. The name (ID) and device type, along with a short description, are displayed in the JTAG Chain group box (Figure 25): FIGURE 25 Selecting a single target CPU. • If your JTAG chain contains multiple devices, load the chain definition form your JTAG configuration file. (For a description of the file’s format, see section below).
SI GNUM S YS TE MS column, click on the device you want to debug. Note that you cannot select a bypass device (see Figure 17): FIGURE 26 Selecting a multi-device JTAG chain. • 24 Click the Advanced Parameters button. Select ARM from the Emulation Mode drop-down list for all but TI ARM925-based processors. For the TI ARM925-based devices, like OMAP1510, OMAP5910, OMAP710, OMAP310, or OMAP331, choose TI Emulation Mode (Figure 27).
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T For the XScale processor, set the JTAG Header field to the following: ARM,TRST:1. FIGURE 27 An example of selecting the emulation mode for Texas Instruments ARM925-based devices, such as OMAP1510, OMAP5910, OMAP710, OMAP310, or OMAP331. 3. Click the Board tab and select the endianness of your target board (Figure 28). In the File field, enter the name of the startup macro file.
SI GNUM S YS TE MS FIGURE 28 Configuring the emulator: the Board tab. 4. Click the Driver tab to configure driver protocol logs and error reports. • • 26 To display the driver protocol log in the Log window, select Log Enable. If you also need to store the log in a file, enter the file name in the File text box. To enable the driver to generate descriptive error messages, select Show Error Messages.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T FIGURE 29 Configuring the emulator: the Driver tab. 5. Click OK. In the Choose Target dialog box, click OK again to accept your settings and connect to the target processor. Multi Device Configuration A multi-device JTAG daisy chain is configured using an ASCII text JTAG chain configuration file with extension .cfg. With the exception of comment lines, each line in a .cfg file refers to a separate device.
SI GNUM S YS TE MS Device Description Is the type of the device, such as ARM7TDMI. Non-ARM devices should be bypassed, and specified as BYPASSxx, where xx denotes the length of the instruction register in a two-digit format. For instance, BYPASS0A denotes a bypassed device with a 10-bit (0a hex) instruction register. Is a comment text. In general, enclose in double quotes all names, words or phrases that contain non-alphanumeric characters.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H dd
dw db reset /halt pause emu = J T A G J E T Read a DWORD (32bit) from memory . Read a WORD (16bit) from memory . Read a BYTE (8bit) from memory . Reset the CPU. The /halt option stops the CPU after the reset. Pause for the number of milliseconds.SI GNUM S YS TE MS ; MyTarget.mac - RDI Startup macro for MyTarget board. ; Version 1.
RDI DRIV ERS FO R THI RD P AR TY AR M DEBUG GE RS W I T H J T A G J E T RAM memory and all flash devices you wish to load code to in the following format: RAM = @ FLASH = @ The configuration string is case insensitive. For example, RAM=2K@0x2000_0000 FLASH=cfi@0x40_0000 FLASH=str9@0x10_0000 specifies that there is 2KB RAM at address 0x2000_0000 and a CFI-compliant flash device at address 0x40_0000. RAM is to be used by the flash programmer.
