RealView ® Debugger TargetConfiguration Guide

Version 3.0


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 configuration
1.1.1. What is target configuration?
1.1.2. Target configuration board files
1.1.3. Connection Properties window
1.2. Viewing board file properties
1.2.1. Displaying the Connection Propertieswindow
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. Configuring Custom Targets
2.1. About target configuration
2.1.1. Target configuration settings
2.1.2. Default configuration files
2.1.3. How configuration files are linkedtogether
2.1.4. Board file contents
2.2. The supplied target description (.bcd)files
2.2.1. Summary of supplied target descriptionfiles
2.2.2. Board, chip, and component groups
2.2.3. Using the supplied target descriptions
2.3. Linking a board, chip, or componentto a connection
2.3.1. Avoiding conflicts between linkedboard groups
2.3.2. Linking one board group to one connection
2.3.3. Linking several boardgroups to one connection
2.3.4. Linking one or moreboard groups to another board group
2.3.5. Linking one or more board groups tomultiple processor connections
2.4. Creating new target descriptions
2.4.1. Using the examples
2.4.2. Creating a new .bcd file
2.4.3. Creating and naming a board, chip,or component
2.4.4. Creating multiple board groups andlinking to another board group
2.4.5. Managing configuration settings
2.5. Loading a different board file
2.5.1. Manually loading a board file
2.5.2. Forcing the load ofa specific board file on startup
2.6. Using RealMonitor
2.6.1. Using RealMonitor with RealView ICE
2.6.2. Using RealMonitor with Multi-ICE
2.6.3. Working with RealMonitor
2.7. Examples of configuring settings atthe CONNECTION level
2.7.1. Changing connection settings
2.7.2. Changing a connection setting backto the default value
2.7.3. Changing the order of settings thathave multiple values
2.7.4. Setting up an Integrator board andcore module
2.7.5. Specifying connect and disconnectmode
2.7.6. Setting top of memory
2.7.7. Configuring vector catch
2.7.8. Flash programming
2.7.9. Restoring your .brd file
2.7.10. Troubleshooting
2.8. Examples of configuring memory mapsettings in a BCD file
2.8.1. Creating a blank BCD file
2.8.2. Creating a memory map block
2.8.3. Setting up a custom memory mappedregister
2.8.4. Setting up memory blocksthat depend on a custom register value
2.8.5. Creating a concatenated register
3. Configuring Custom Connections
3.1. About configuring custom connections
3.1.1. Relationship betweenconnections and connection properties
3.2. Enabling or disabling a board fileentry
3.2.1. Procedure
3.3. Changing entries containing user-informationvalues
3.4. Restoring board file entry defaults
3.4.1. Procedure
3.5. Creating new Target Access configurations
3.5.1. Creating a new Target Access configuration
3.5.2. Copying a Target Access configuration
3.6. Configuring RealView ICE connections
3.6.1. Creating a new RealView ICE TargetAccess
3.6.2. Creating a new Target Access fromthe Connection Properties window
3.6.3. Changing the connection properties
3.6.4. Configuring a RealView ICE TargetAccess
3.7. Configuring RDI targets
3.7.1. The RDI Target Listdialog box
3.7.2. Adding and configuring RDI targets
3.7.3. Configuring Remote_A
3.7.4. Configuring ARM Multi-ICE
3.7.5. Configuring ARM Agilent Debug Interface
3.7.6. Configuring ARM RealMonitor
3.8. Configuring RealView Simulator Brokerconnections
3.8.1. Connections to RealView ARMulatorISS
3.8.2. Configuring RealView ARMulator ISS
3.8.3. Configuring a new RealView SimulatorBroker connection
3.9. Configuring ISSM connections
3.9.1. Configuring an ISSM Target Access
3.9.2. Creating a new ISSM Target Access
3.10. Using the Thumb-2EE helper macro
3.11. Configuring connections that use JTAGfiles
3.11.1. Editing JTAG files
4. Working with Remote Targets
4.1. Accessing remote targets with RealViewICE and Multi-ICE
4.2. Working with RealView Simulator Broker
4.2.1. Accessing remote targets using RealViewSimulator Broker
4.2.2. Specifying a remote host simulator
4.2.3. Using the examples
4.3. Connecting to a remote host simulator
4.3.1. Configuring a Target Access to theremote target
4.3.2. Connecting to the new remote target
4.3.3. Viewing remote simulatorconnections
4.4. Defining remote targets in a hostsfile
4.4.1. How RealView Debugger searches for the rvbroker.brdfile
4.4.2. Creating a local hosts file
4.4.3. Configuring a local hosts file
4.4.4. Connecting using a local hosts file
4.4.5. Using multiple connections in a localhosts file
4.4.6. Using a network hosts file
4.5. Disconnecting remote connections
5. Programming Flash with RealView Debugger
5.1. Introduction to Flash programmingwith RealView Debugger
5.1.1. Summary of files used to program Flashfor the supported platforms
5.1.2. Summary of files used to program supportedFlash types on custom platforms
5.1.3. Summary of files usedto program custom Flash types on custom platforms
5.2. RealView Debugger files used for Flash programming
5.2.1. Evaluator-7T example
5.2.2. Flash-level code
5.2.3. Board-level code
5.2.4. ASCII MEthod file
5.2.5. Flash MEthod file
5.2.6. Board Chip Definition file
5.3. Using the pakflash utility
5.3.1. Command syntax
5.4. Programming Flash on the ARM boards
5.4.1. About the Integrator/AP board
5.4.2. Assigning a BCD file to your connection
5.4.3. Reviewing the information containedin the Integrator/AP BCD file
5.4.4. Displaying the memory map in the ProcessControl pane
5.4.5. Programming an imageinto Flash on the Integrator/AP
5.5. Programming Flash for a custom developmentplatform
5.5.1. Third-party support for ARM core-baseddevelopment platforms
5.5.2. Programming a Flash type supportedby RealView Debugger
5.5.3. Programming a custom Flash type
5.6. Gathering information about your target
5.6.1. Evaluator-7T example
5.7. Creating algorithmsfor a Flash type supported by RealView Debugger
5.7.1. Editing b_flashwrapper.s
5.7.2. Settings for the Evaluator-7T
5.8. Creating algorithms for a Flash typenot provided with RealView Debugger
5.9. Creating the Flash-level and board-levelAME files
5.9.1. Flash-level AME file format
5.9.2. Board-level AME fileformat
5.10. Generating the FME file
5.10.1. Locating the source and AME filesrequired
5.10.2. Specifying the compiler options
5.10.3. Specifying the assembler options
5.10.4. Specifying the linker options
5.10.5. Running the pakflash utility
5.11. Checking the FME file with the dispflashutility
5.11.1. Evaluator-7T example
5.12. Creating a BCD file
5.12.1. Copying and renaming an existing BCDfile
5.12.2. Deleting any existing Board/Chip definitions
5.12.3. Creating a new board group in theBCD file
5.12.4. Describing the memorymap
5.12.5. Assigning your BCD file to a targetconnection
5.13. Programming an image into Flash
5.13.1. Writing the image to Flash
5.13.2. Using CLI commands to program Flash
5.13.3. Checking the contents of Flash
5.14. Troubleshooting
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. Advanced_Information block CONNECTIONlevel settings
A.4.2. Advanced_Information block Memorymap settings
A.4.3. 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
B. ISSM Model Configuration Reference
B.1. Cortex-A8 model configuration
B.1.1. Summary of supported features
B.1.2. Cortex-A8 configurationparameters
B.1.3. Cortex-A8 memory map
B.1.4. Cortex-A8 peripheralregister mapping
B.2. Cortex-M3 model configuration
B.2.1. Summary of supported features
B.2.2. Cortex-M3 configurationparameters
B.2.3. Cortex-M3 memory map
B.2.4. Cortex-M3 peripheral register mapping

List of Figures

1.1. Connection Properties window
1.2. Viewing .bcd files in the ConnectionProperties window
2.1. Configuration files in the boardfile
2.2. Referencing two .bcd files in theConnection Properties window
2.3. Linking one connection to one board
2.4. RealView-ICE connection properties
2.5. New BoardChip_name setting in connectionproperties
2.6. Linking one connection to two boards
2.7. Linking a second board
2.8. Board and chip groups for the Evaluator-7T
2.9. Linking one board into another board
2.10. Board and chip groups for the EtherRouter
2.11. Linking one board into other boards
2.12. Configuring a two processor target
2.13. Saving an existing .bcd file witha new name
2.14. Viewing the new group in the .bcdfile
2.15. Setting up EtherRouter
2.16. Setting up EtherRouter
2.17. RealView ICE in the Connection Controlwindow
2.18. RealView ICE connection properties
2.19. RealMonitor in the Connection Controlwindow
2.20. RealMonitor connection properties
2.21. Creating a new connection
2.22. Displaying the new MP3Player connectionproperties
2.23. Board groups linked to the new connection
2.24. Connecting to the new target
2.25. AP tab in the Registers pane
2.26. Relating top_of_memory to singlesection program layout
2.27. Connection Properties window
2.28. Viewing the contents of the new group
2.29. New memory map in the Process Controlpane
2.30. Memory map with image loaded
2.31. Configuring REGS
2.32. Creating enumerations
2.33. Creating bit field descriptions
2.34. The MYREGS group
2.35. MYREGS in the Registers pane
2.36. Creating a new memory block
2.37. Creating a map rule
2.38. Settings for the second map rule
2.39. MYREGS tab in the Registers pane
2.40. New memory block in the Map tab
2.41. Activated ROM memory block in theMap tab
2.42. Concat_reg tab in Registers pane
2.43. User view showing concatenated register
3.1. Connection properties entries inthe Connection Control window
3.2. Create Configuration dialog box
3.3. Create Configuration dialog box
3.4. RealView ICE targets in the ConnectionControl window
3.5. Specifying a new CONNECTION group
3.6. Specifying a CONNECTION group
3.7. RDI Target List dialog box
3.8. Create New RDI Target dialog box
3.9. Remote_A connection dialog box
3.10. Multi-ICE DLL configuration dialogbox
3.11. ARMulator configuration dialog box
3.12. Specifying a new CONNECTION group
3.13. Connecting to a new simulator
3.14. Simulator details in the Output pane
3.15. Connection Control window with ISSMTarget Access
3.16. MxDI Configuration Utility dialogbox
3.17. Create Configuration dialog box
3.18. Device JTAG-File Editor dialog box
3.19. JTAG chain ordering
4.1. Remote connections in the ConnectionProperties window
4.2. Creating a new connection
4.3. Displaying the new Remote_Debugconnection properties
4.4. Specifying a remote host
4.5. Remote target in the Connection Controlwindow
4.6. Remote connections in the ConnectionControl window
4.7. Hosts file in the Connection Controlwindow
4.8. Configuring a hosts file
4.9. Remote target in the Connection Controlwindow
4.10. Multiple remote targets in the ConnectionControl window
4.11. Network hosts file in the ConnectionControl window
5.1. New memory map in the Process Controlpane
5.2. The Flash Memory Control dialog box
5.3. Flash programming complete
A.1. How connections, boards, and chipsfit together
A.2. Viewing generic settings
B.1. Cortex-A8 memory map
B.2. Cortex-M3 memory map

Proprietary Notice

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
Revision H March2006 RealView Debugger v3.0 release for RVDS v3.0
Copyright © 2002-2006 ARM Limited. All rights reserved. ARM DUI 0182H
Non-Confidential