bdi
GDB
for GNU Debugger, BDI2000 (ARM11 / Cortex)
User Manual
21
© Copyright 1997-2014 by ABATRON AG Switzerland
V 1.21
3 Using bdiGDB
3.1 Principle of operation
The firmware within the BDI handles the GDB request and accesses the target memory or registers
via the JTAG interface. There is no need for any debug software on the target system. After loading
the code via TFTP debugging can begin at the very first assembler statement.
Whenever the BDI system is powered-up the following sequence starts:
3.2 Configuration File
The configuration file is automatically read by the BDI2000 after every power on.
The syntax of this file is as follows:
; comment
[part name]
core# identifier parameter1 parameter2 ..... parameterN ; comment
core# identifier parameter1 parameter2 ..... parameterN
.....
[part name]
core# identifier parameter1 parameter2 ..... parameterN
core# identifier parameter1 parameter2 ..... parameterN
.....
etc.
Numeric parameters can be entered as decimal (e.g. 700) or as hexadecimal (0x80000).
The core# is optional. If not present the BDI assume core #0. See also chapter "Multi-Core Support".
Power On
initial
configuration
valid?
Get configuration file
via TFTP or from Flash
Reset System and
Power OFF
activate BDI2000 loader
Power OFF
no
yes
Process target init list
Process GDB requests
Process Telnet commands