ARM DS-5 Using the Debug Hardware Configuration Utilities

More documents

Recommendations

Info

Configuring debug hardware for GDB9.4 Debug hardware TCP/IP port numberingTo use the debug hardware Command Monitor and debug your target with GDB, the debughardware unit uses the TCP/IP ports described in the following table:Table 9-1 Debug hardware TCP/IP portsPortsDescription4000 series This port range is used to connect to a target from GDB, and to performhalt-mode debugging.Each device on the JTAG scan chain, or behind a CoreSight DAP, isallocated a TCP/IP port number for connection from GDB. Ports areallocated in sequence, with port 4000 connected to the first device in the scanchain. Synchronized start and step are not supported.NoteAny attempt to connect to a non-processor device fails, but the port numberis still reserved for that device.5000 series This port range is used for Monitor-mode debugging and other VirtualEthernet/TTY mode connections.NoteTo use these ports you must set the DCC mode to a non-zero value.9.4.1 See alsoTasks• Connecting to targets from GDB through debug hardware on page 9-22.Reference• DCC modes on page 9-7.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-6ID021112Non-Confidential
Configuring debug hardware for GDB9.5 DCC modesIf your target application communicates using DCC, you must configure the DCC mode. Youcan set the following DCC modes:Mode 0: raw DCCRaw, unprocessed, data is fed to the client through the DCC register on the target.Mode 1: redirected raw DCCIn this mode, the data is fed over TCP/IP ports starting at 5000. Data is sent fromthe host to the target 4 bytes at a time. If fewer than 4 bytes are available, the datais padded with 0 bytes until it is 4 bytes long. Data from the target to the host isreceived 4 bytes at a time, and no padding or trimming is performed.NoteIt is recommended that you use the Virtual Ethernet/TTY mode (mode 2).However, if the Virtual Ethernet/TTY mode is unsuitable for your application,then you can use mode 1 DCC but you must also implement a suitablecommunications protocol.Mode 2: Virtual Ethernet/TTY modeVirtual Ethernet/TTY is used for providing virtual serial and Ethernetconnections to the target. As far as the debug host and the target are concerned,Virtual Ethernet/TTY mode is a debug hardware feature that provides:• A virtual Ethernet feature using the DCC channel and a collection ofsoftware tools in debug hardware and the host PC. It enables TCP/IP to beused to the target as though the target has an Ethernet port of its own.• A virtual serial port feature using the DCC channel and a collection ofsoftware tools in debug hardware and the host PC.9.5.1 See alsoTasks• Connecting to targets from GDB through debug hardware on page 9-22.Concepts• Setting DCC parameters on page 9-23• DCC and interrupts on page 9-25.Reference• Debug hardware TCP/IP port numbering on page 9-6• rvigdbconfig command syntax on page 9-27• rviload command syntax on page 9-28.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-7ID021112Non-Confidential
Page 1 and 2:
®ARMDS-5Version 5.9Using the Debug
Page 3 and 4:
Conformance NoticesThis section con
Page 5 and 6:
Contents4.6 Restarting the debug ha
Page 7 and 8:
Contents10.6 Auto Configure button
Page 9 and 10:
Conventions and feedback• the ser
Page 11 and 12:
Getting started with the debug hard
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Chapter 3Configuring network settin
Page 21 and 22:
Configuring network settings for yo
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Managing the firmware on your debug
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Chapter 5Creating debug hardware ta
Page 45 and 46:
Creating debug hardware target conf
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Configuring CoreSight systems6.1 Ab
Page 99 and 100:
Configuring CoreSight systems6.3 Co
Page 101 and 102:
Configuring CoreSight systems6.5 Ab
Page 103 and 104:
Configuring CoreSight systems6.7 Fo
Page 105 and 106: Configuring CoreSight systems2. Loc
Page 107 and 108: Configuring CoreSight systems• To
Page 109 and 110: Configuring CoreSight systems6.10.1
Page 111 and 112: Configuring CoreSight systemsName=T
Page 113 and 114: Configuring CoreSight systemsName=T
Page 115 and 116: Configuring CoreSight systems6.13.1
Page 117 and 118: Configuring CoreSight systems6.15 C
Page 123 and 124: Chapter 7Using TraceThe following t
Page 125 and 126: Using Trace7.2 Trace hardware captu
Page 127 and 128: Using TraceConcepts• About using
Page 129 and 130: Chapter 8Debugging with your debug
Page 131 and 132: Debugging with your debug hardware
Page 151 and 152: Chapter 9Configuring debug hardware
Page 153 and 154: Configuring debug hardware for GDB9
Page 155: Configuring debug hardware for GDB9
Page 179 and 180: Configuring debug hardware for GDBO
Page 181 and 182: Configuring debug hardware for GDBR
Page 183 and 184: Configuring debug hardware for GDB
Page 185 and 186: Chapter 10Troubleshooting your debu
Page 187 and 188: Troubleshooting your debug hardware
Page 199: Troubleshooting your debug hardware
show all

ARM DS-5 Using the Debug Hardware Configuration Utilities

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?