ARM DS-5 Using the Debug Hardware Configuration Utilities

Configuring debug hardware for GDB9.23 Multiprocessor debugging with GDB and debug hardwareDebug hardware is capable of simultaneously and synchronously debugging multiple targets.However, GDB does not support multiprocessor debugging directly.NoteAlthough multiprocessor debugging is possible using GDB, it is recommended that you debugmultiple processors using higher level tools.9.23.1 How connections to multiple processors are allocatedWhen you make connections to multiple target processors, the connections on ports 5000,5001,... are allocated by debug hardware, that is, redirected virtual DCC is allocated a port foreach device in a similar way to GDB halt-mode debugging. The port range starts from port 5000,so virtual Ethernet or raw redirected DCC for the first device appears on port 5000, the seconddevice on port 5001, and this continues in the same way.9.23.2 Considerations when debugging multiple targets with GDBBe aware of the following if you are debugging multiple targets with GDB:• Multiprocessor debugging with GDB requires that you open multiple command windows(such as Xterms). You must have one GDB session for each target processor to which youwant to connect.• If you have multiple targets on the debug hardware scan chain, then:— the target processors are numbered consecutively, starting at one— the available bandwidth over DCC is shared between all target processors— communications to all target processors are through a single JTAG chain.9.23.3 See alsoTasks• Preparing your debug hardware for remote GDB connections on page 9-21• Loading and booting a complete system on page 9-26.Concepts• About configuring debug hardware for debugging with GDB on page 9-3• Methods of connecting from remote GDB sessions on page 9-9.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 9-34ID021112Non-Confidential