RealView ® Debugger TargetConfiguration Guide

Version 1.8


Table of Contents

Preface
About this book
Intended audience
Examples
Using this book
Typographical conventions
Further reading
Feedback
Feedback on RealView Debugger
Feedback on this book
1. Introduction
1.1. About target connections and configuration
1.1.1. Comparing target connection and targetconfiguration
1.1.2. Connection Control window
1.1.3. Connection Propertieswindow
1.2. Viewing board file properties
1.2.1. Connection Properties window
1.2.2. Connection entries
1.2.3. Configuration entries
1.3. Configuration files
1.3.1. What the configuration files contain
1.3.2. Finding configuration files
2. Connecting to Targets
2.1. Working with the Connection Controlwindow
2.1.1. Groups in the Connection Control window
2.1.2. Using the Connection Control window
2.1.3. Changing your board file
2.2. Managing connections
2.2.1. Working with target vehicles
2.2.2. Working with access-providers
2.2.3. Working with endpoint connections
2.3. Connecting to a target
2.3.1. Connections in single processor debuggingmode
2.3.2. Using the Connection Control window
2.3.3. Setting connect mode
2.3.4. Connecting to multiple targets
2.3.5. Including the connection in the workspace
2.3.6. Using CLI commands
2.4. Failing to make a connection
2.4.1. Troubleshooting
2.5. Disconnecting from a target
2.5.1. Disconnect behavior in RealView Debugger
2.5.2. Using auto-disconnect
2.5.3. Using the Target menu
2.5.4. Using the Connection Control window
2.5.5. Setting disconnect mode
2.5.6. Disconnecting by exiting
2.5.7. Using the CLI
3. Configuring Custom Targets
3.1. About target configuration
3.1.1. Target configuration settings
3.1.2. Default configuration files
3.1.3. How configuration filesare linked together
3.1.4. Board file contents
3.2. The supplied target description (.bcd)files
3.2.1. Summary of supplied target descriptionfiles
3.2.2. Board, chip, and component groups
3.2.3. Using the supplied target descriptions
3.3. Linking a board, chip, or componentto a connection
3.3.1. Avoiding conflicts between linkedboard groups
3.3.2. Linking one board group to one connection
3.3.3. Linking several boardgroups to one connection
3.3.4. Linking one or moreboard groups to another board group
3.3.5. Linking one or more board groups tomultiple processor connections
3.4. Creating new target descriptions
3.4.1. Using the examples
3.4.2. Creating a new .bcd file
3.4.3. Creating and naming a board, chip,or component
3.4.4. Creating multiple board groups andlinking to another board group
3.4.5. Managing configuration settings
3.5. Using RealMonitor
3.5.1. Using RealMonitor with RealView ICE
3.5.2. Using RealMonitor with Multi-ICE
3.5.3. Working with RealMonitor
3.6. Example descriptions
3.6.1. Setting up an Integrator board andcore module
3.6.2. Specifying connect and disconnectmode
3.6.3. Configuring a memory map
3.6.4. Setting up a custom register
3.6.5. Setting up memory blocks
3.6.6. Setting top of memory
3.6.7. Flash programming
3.6.8. Restoring your .brd file
3.6.9. Troubleshooting
4. Programming Flash with RealView Debugger
4.1. Introduction to Flash programmingwith RealView Debugger
4.1.1. Summary of files used to program Flashfor the supported platforms
4.1.2. Summary of files used to program supportedFlash types on custom platforms
4.1.3. Summary of files usedto program custom Flash types on custom platforms
4.2. RealView Debugger files used for Flash programming
4.2.1. Evaluator-7T example
4.2.2. Flash-level code
4.2.3. Board-level code
4.2.4. ASCII MEthod file
4.2.5. Flash MEthod file
4.2.6. Board Chip Definition file
4.3. Using the pakflash utility
4.3.1. Command syntax
4.4. Programming Flash on the ARM boards
4.4.1. About the Integrator/AP board
4.4.2. Assigning a BCD file to your connection
4.4.3. Reviewing the information containedin the Integrator/AP BCD file
4.4.4. Displaying the memory map in the ProcessControl pane
4.4.5. Programming an imageinto Flash on the Integrator/AP
4.5. Programming Flash for a custom developmentplatform
4.5.1. Third-party support for ARM core-baseddevelopment platforms
4.5.2. Programming a Flash type supportedby RealView Debugger
4.5.3. Programming a custom Flash type
4.6. Gathering information about your target
4.6.1. Evaluator-7T example
4.7. Creating algorithmsfor a Flash type supported by RealView Debugger
4.7.1. Editing b_flashwrapper.s
4.7.2. Settings for the Evaluator-7T
4.8. Creating algorithms for a Flash typenot provided with RealView Debugger
4.9. Creating the Flash-level and board-levelAME files
4.9.1. Flash-level AME file format
4.9.2. Board-level AME fileformat
4.10. Generating the FME file
4.10.1. Locating the source and AME filesrequired
4.10.2. Creating a Standard RealView Debugger project
4.10.3. Specifying the compiler settings
4.10.4. Specifying the assembler settings
4.10.5. Specifying the linkersettings
4.10.6. Running the pakflash utility
4.10.7. Building the project
4.11. Checking the FME file with the dispflashutility
4.11.1. Evaluator-7T example
4.12. Creating a BCD file
4.12.1. Copying and renaming an existing BCDfile
4.12.2. Deleting any existing Board/Chip definitions
4.12.3. Creating a new board group in theBCD file
4.12.4. Describing the memorymap
4.12.5. Assigning your BCD file to a targetconnection
4.13. Programming an image into Flash
4.13.1. Writing the image to Flash
4.13.2. Using CLI commands to program Flash
4.13.3. Checking the contents of Flash
4.14. Troubleshooting
5. Configuring Custom Connections
5.1. Working with connection properties
5.1.1. Connection entries in the ConnectionControl window
5.1.2. Enabling or disabling a board fileentry
5.1.3. Changing entries containing user-informationvalues
5.1.4. Restoring board file entry defaults
5.2. Working with RealView ICE targets
5.2.1. Creating a new RealView ICE connection
5.2.2. Configuring a RealView ICE interfaceunit
5.3. Working with RDI targets
5.3.1. The RDI Target Listdialog box
5.3.2. Adding and configuring RDI targets
5.3.3. Configuring RealView ARMulator ISS
5.3.4. Configuring Remote_A
5.3.5. Configuring ARM Multi-ICE
5.3.6. Configuring ARM Agilent Debug Interface
5.3.7. Configuring ARM RealMonitor
5.4. Working with Simulator Broker connections
5.4.1. Connecting to RealView ARMulator ISS
5.4.2. Configuring RealView ARMulator ISS
5.4.3. Configuring a new simulator connection
5.5. Working with JTAG files
5.5.1. Editing JTAG files
5.5.2. Configuring a new DSP connection withMulti-ICE direct connect
6. Working with Remote Targets
6.1. Accessing remote targets with RealViewICE and Multi-ICE
6.2. Working with RealView Network Broker
6.2.1. Accessing remote targets using RealViewNetwork Broker
6.2.2. Specifying a remote host simulator
6.2.3. Using the examples
6.3. Connecting to a remote host simulator
6.3.1. Configuring the new target
6.3.2. Connecting to the newtarget
6.3.3. Viewing remote simulatorconnections
6.4. Connecting to a remote host emulator
6.4.1. Preparing the remote target
6.4.2. Configuring the new target
6.4.3. Connecting to the newtarget
6.5. Using a hosts file
6.5.1. Creating a local hosts file
6.5.2. Configuring a local hosts file
6.5.3. Connecting using a local hosts file
6.5.4. Using multiple connections in a localhosts file
6.5.5. Using a network hosts file
6.6. Disconnecting remote connections
A. Configuration Settings Reference
A.1. About this appendix
A.2. Target configuration and connections
A.2.1. Types of entry
A.3. Generic groups and settings
A.4. Target configuration reference
A.4.1. The Advanced_Information block
A.4.2. BOARD, CHIP, and COMPONENT groups
A.5. Custom connection reference
A.5.1. CONNECTION groups
A.5.2. DEVICE groups
A.5.3. RVBROKER groups
A.5.4. Working with JTAG configuration files
A.5.5. Working with ARM RDI configurationfiles
Glossary

List of Figures

1.1. Connection Control window
1.2. Connection Properties window
1.3. Viewing .bcd files in the ConnectionProperties window
2.1. Connection Control window
2.2. Groups in the Connection Controlwindow
2.3. Connect Mode selection box
2.4. Failing to make a connection
2.5. Disconnect Mode selection box
2.6. Disconnect confirmation
2.7. Disconnect reconfiguration or retry
3.1. Configuration files in the boardfile
3.2. Referencing two .bcd files in theConnection Properties window
3.3. Linking one connection to one board
3.4. RealView-ICE connection properties
3.5. Linking a board
3.6. New BoardChip_name setting in connectionproperties
3.7. Linking one connection to two boards
3.8. Linking a second board
3.9. Board and chip groups for the Evaluator-7T
3.10. Linking one board into another board
3.11. Board and chip groups for the EtherRouter
3.12. Linking one board into other boards
3.13. Configuring a two processor target
3.14. Saving an existing .bcd file witha new name
3.15. Viewing the new group in the .bcdfile
3.16. Setting up EtherRouter
3.17. Setting up EtherRouter
3.18. RealView ICE in the Connection Controlwindow
3.19. RealView ICE connection properties
3.20. RealMonitor in the Connection Controlwindow
3.21. RealMonitor connection properties
3.22. Creating a new connection
3.23. Displaying the new MP3Player connectionproperties
3.24. Board groups linked to the new connection
3.25. Connecting to the new target
3.26. AP tab in the Register pane
3.27. Viewing the contents of the new group
3.28. New memory map in the Process Controlpane
3.29. Configuring REGS
3.30. Creating enumerations
3.31. Creating bit field descriptions
3.32. The MYREG group
3.33. MYREG in the Register pane
3.34. Creating a new memory block
3.35. Creating a map rule
3.36. Settings for the second map rule
3.37. New memory block in the Map tab
3.38. Relating top_of_memory to singlesection program layout
4.1. New memory map in the Process Controlpane
4.2. The Flash Memory Control dialog box
4.3. Flash programming complete
5.1. Connection properties entries inthe Connection Control window
5.2. RealView ICE targets in the ConnectionControl window
5.3. Specifying a new CONNECTION group
5.4. Configuring a RealView ICE interfaceunit
5.5. Recommended settings for an ARM Integratorboard
5.6. Specifying a CONNECTION group
5.7. RDI Target List dialog box
5.8. Create New RDI Target dialog box
5.9. ARMulator Configuration dialog box
5.10. Remote_A connection dialog box
5.11. Multi-ICE DLL configuration dialogbox
5.12. ARMulator configuration dialog box
5.13. Specifying a new CONNECTION group
5.14. Connecting to a new simulator
5.15. Simulator details in the Output pane
5.16. Device JTAG-File Editor dialog box
5.17. JTAG chain ordering
5.18. Specifying a CONNECTION group
6.1. Remote connections in the ConnectionProperties window
6.2. Creating a new connection
6.3. Displaying the new Remote_Debugconnection properties
6.4. Specifying a remote host
6.5. Remote target in the Connection Controlwindow
6.6. Remote connections in the ConnectionControl window
6.7. Displaying the new Remote_MICE connectionproperties
6.8. Specifying a remote host
6.9. Remote target in the Connection Controlwindow
6.10. Hosts file in the Connection Controlwindow
6.11. Configuring a hosts file
6.12. Remote target in the Connection Controlwindow
6.13. Multiple remote targets in the ConnectionControl window
6.14. Network hosts file in the ConnectionControl window
A.1. How connections, boards, and chipsfit together
A.2. Viewing generic settings

ProprietaryNotice

Words and logos marked with ® or ™ are registered trademarks or trademarksowned by ARM Limited. Other brands and names mentioned herein maybe the trademarks of their respective owners.

Neither the whole nor any part of the information containedin, or the product described in, this document may be adapted orreproduced in any material form except with the prior written permissionof the copyright holder.

The product described in this document is subject to continuousdevelopments and improvements. All particulars of the product andits use contained in this document are given by ARM in good faith.However, all warranties implied or expressed, including but notlimited to implied warranties of merchantability, or fitness forpurpose, are excluded.

This document is intended only to assist the reader in theuse of the product. ARM Limited shall not be liable for any lossor damage arising from the use of any information in this document,or any error or omission in such information, or any incorrect useof the product.

ConfidentialityStatus

This document is Non-Confidential. The right to use, copyand disclose this document may be subject to license restrictionsin accordance with the terms of the agreement entered into by ARMand the party that ARM delivered this document to.

Product Status

The information in this document is final, that is for a developedproduct.

Revision History
Revision A April2002 RealView Debugger v1.5 release
Revision B September2002 RealView Debugger v1.6 release
Revision C February2003 RealView Debugger v1.6.1 release
Revision D September2003 RealView Debugger v1.6.1 release for RVDSv2.0
Revision E January2004 RealView Debugger v1.7 release for RVDS v2.1
Revision F December2004 RealView Debugger v1.8 release for RVDS v2.2
Revision G May2005 RealView Debugger v1.8 SP1 release for RVDSv2.2 SP1
Copyright © 2002-2005 ARM Limited. All rights reserved. ARM DUI 0182G
Non-Confidential