Troubleshooting, Problem | Albatron Technology ARM11/Cortex-A8

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

User Manual 51

Appendices

A Troubleshooting

Problem

The ﬁrmware can not be loaded.

Possible reasons

•The BDI is not correctly connected with the target system (see chapter 2).

•The power supply of the target system is switched off or not in operating range (4.75 VDC ... 5.25 VDC) --> MODE LED is OFF or RED

•The built in fuse is damaged --> MODE LED is OFF

•The BDI is not correctly connected with the Host (see chapter 2).

•A wrong communication port (Com 1...Com 4) is selected.

Problem

No working with the target system (loading ﬁrmware is ok).

Possible reasons

•Wrong pin assignment (BDM/JTAG connector) of the target system (see chapter 2).

•Target system initialization is not correctly --> enter an appropriate target initialization list.

•An incorrect IP address was entered (BDI2000 conﬁguration)

•BDM/JTAG signals from the target system are not correctly (short-circuit, break, ...).

•The target system is damaged.

Problem

Network processes do not function (loading the ﬁrmware was successful)

Possible reasons

•The BDI2000 is not connected or not correctly connected to the network (LAN cable or media converter)

•An incorrect IP address was entered (BDI2000 conﬁguration)

© Copyright 1997-2007 by ABATRON AG Switzerland

V 1.04

Image 51

Albatron Technology ARM11/Cortex-A8 user manual Troubleshooting, Problem, ﬁrmware can not be loaded, Possible reasons

Contents

BdiGDB BDI2000 BDI Conﬁguration InstallationUsing bdiGDB Introduction Appendices Troubleshooting Maintenance Trademarks BDI2000 Introduction BDI Conﬁguration Installation Connecting the BDI2000 to TargetFor BDI Main / Target a connector signals see table on next Jtag Test Reset BDI Main / Target a Connector Signals Changing Target Processor Type Adaptive Clocking For Target B connector signals see table on next Returned Jtag Test Clock BDI Target B Connector Signals External power supply Target system Please switch on the system in the following sequence 142 Power Supply from Target System Built in LED indicates the following BDI states Status LED «MODE» RS232 Connector Name Description BASE-T ConnectorEthernet communication PC Host Installation of the Conﬁguration Software Overview of an installation / conﬁguration processActivating Bootp Following the steps to bring-up a new BDI2000 Build the setup toolLoad/Update the BDI ﬁrmware/logic 1 Conﬁguration with a Linux / Unix host For more information about Tftp use man tftpd Check conﬁguration and exit loader modeTransmit the initial conﬁguration parameters ﬁle name without any path Ory / programmable logic 2 Conﬁguration with a Windows host Reassemble the unit as described in Appendix «Maintenance» Recover procedure Tftp server for Windows NT Testing the BDI2000 to host connection Principle of operation Using bdiGDB Conﬁguration 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 Example Pushpull Part TargetCputype ARM1136 None Loadonly HaltStop RUN Core SoftHard Breakmode Hard Daisy chained Jtag devices Low level Jtag scan chain conﬁguration Part Host Dump ﬁlename Prompt ARM11 Part Flash BLOCK, CHIP, Unlock AM29BX8 MIRRORX8, I28BX8 STRATAX8, AT49X8 Supported Flash Memories Tor. In other words, this is the size of one sector in bytes Or use the Telnet unlock command Part Regs Example for a register deﬁnition Entry in the conﬁguration ﬁleRegister deﬁnition ﬁle Target setup Connecting to the targetDebugging with GDB Breakpoint Handling GDB monitor command Target serial I/O via BDI Target DCC I/O via BDI Telnet Interface Dump Command list CP15 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 Speciﬁcations Declaration of Conformity CE Environmental notice Warranty Possible reasons TroubleshootingProblem ﬁrmware can not be loaded Unplug the cables Maintenance Reinstallation All trademarks are property of their respective holders Trademarks