Albatron Technology ARM11/Cortex-A8 user manual Multi-Core Support

Page 47

bdiGDB for GNU Debugger, BDI2000 (ARM11/Cortex-A8)

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 Cortex-A8 core even if they are located on the same scan chain.

© Copyright 1997-2007 by ABATRON AG Switzerland

V 1.04

Image 47
Contents BdiGDB BDI2000 BDI Configuration InstallationUsing bdiGDB IntroductionAppendices Troubleshooting Maintenance TrademarksBDI2000 IntroductionBDI Configuration For BDI Main / Target a connector signals see table on next InstallationConnecting the BDI2000 to Target Jtag Test Reset BDI Main / Target a Connector SignalsChanging Target Processor Type Adaptive Clocking For Target B connector signals see table on nextReturned Jtag Test Clock BDI Target B Connector SignalsExternal power supply Target system Please switch on the system in the following sequence142 Power Supply from Target SystemBuilt in LED indicates the following BDI states Status LED «MODE»RS232 Connector Name Description BASE-T ConnectorEthernet communication PC HostActivating Bootp Installation of the Configuration SoftwareOverview of an installation / configuration process Following the steps to bring-up a new BDI2000 Build the setup toolLoad/Update the BDI firmware/logic 1 Configuration with a Linux / Unix hostFor more information about Tftp use man tftpd Check configuration and exit loader modeTransmit the initial configuration parameters file name without any pathOry / programmable logic 2 Configuration with a Windows hostReassemble the unit as described in Appendix «Maintenance» Recover procedureTftp server for Windows NT Testing the BDI2000 to host connectionPrinciple of operation Using bdiGDBConfiguration File Part Init BdiGDB for GNU Debugger, BDI2000 ARM11/Cortex-A8 Format Coff Using a startup program to initialize the target systemROM on the target, select ROM as the format Format COFF, SREC, AOUT, BIN, ELF or ROM ExamplePushpull Part TargetCputype ARM1136 NoneLoadonly HaltStop RUNCore SoftHard Breakmode HardDaisy chained Jtag devices Low level Jtag scan chain configuration Part Host Dump filename Prompt ARM11Part Flash BLOCK, CHIP, Unlock AM29BX8 MIRRORX8, I28BX8 STRATAX8, AT49X8 Supported Flash MemoriesTor. In other words, this is the size of one sector in bytes Or use the Telnet unlock commandPart Regs Register definition file Example for a register definitionEntry in the configuration file Debugging with GDB Target setupConnecting to the target Breakpoint Handling GDB monitor commandTarget serial I/O via BDI Target DCC I/O via BDI Telnet Interface Dump Command listCP15 Invalidate I cache line CRn = 7, opcode2 = 1, CRm = CPxx RegistersSome examples CP15 ID register CRn = 0, opcode2 = CP15 Cache Type CRn = 0, opcode2 =Multi-Core Support BASE-T SpecificationsDeclaration of Conformity CE Environmental noticeWarranty Possible reasons TroubleshootingProblem firmware can not be loadedUnplug the cables MaintenanceReinstallation All trademarks are property of their respective holders Trademarks