bdiGDB for GNU Debugger, BDI2000 | User Manual 47 |
3.5 Multi-Core Support
The bdiGDB system supports concurrent debugging of up to 4 ARM cores (same family) connected to the same JTAG scan chain. For every core you can start its own GDB session. The default port numbers used to attach the remote targets are 2001 ... 2004. In the Telnet you switch between the cores with the command "select <0..3>". In the configuration file, simply begin the line with the ap- propriate core number. If there is no #n in front of a line, the BDI assumes core #0.
The following example defines two cores on the scan chain.
[TARGET] |
|
|
|
|
CLOCK | 1 |
|
| ;JTAG clock (0=Adaptive, 1=8MHz, 2=4MHz, 3=2MHz) |
WAKEUP | 1000 |
| ;wakeup time after reset | |
#0 CPUTYPE |
| ARM1136 |
| |
#0 SCANPRED |
| 0 | 0 | ;JTAG devices connected before this core |
#0 SCANSUCC |
| 1 | 4 | ;JTAG devices connected after this core |
#0 VECTOR |
| CATCH | ;catch unhandled exceptions | |
#0 BREAKMODE | SOFT | ;SOFT or HARD | ||
#0 DCC |
| 8 |
| ;DCC I/O via TCP port 8 |
#1 CPUTYPE |
| ARM1136 |
| |
#1 SCANPRED |
| 1 | 4 | ;JTAG devices connected before this core |
#1 SCANSUCC |
| 0 | 0 | ;JTAG devices connected after this core |
#1 VECTOR |
| CATCH | ;catch unhandled exceptions | |
#1 BREAKMODE | SOFT | ;SOFT or HARD | ||
#1 DCC |
| 7 |
| ;DCC I/O via TCP port 7 |
Note:
It is not possible to concurrent debug an ARM11 and a
© Copyright | V 1.04 |