bdi
GDB
for GNU Debugger, BDI2000 (ARM11 / Cortex)
User Manual
26
© Copyright 1997-2014 by ABATRON AG Switzerland
V 1.21
TRST type
Normally the BDI uses an open drain driver for the TRST signal. This is in
accordance with the ARM recommendation. For boards where TRST is
simply pulled low with a weak resistor, TRST will always be asserted and
JTAG debugging is impossible. In that case, the TRST driver type can be
changed to push-pull. Then the BDI actively drives also high level.
type
OPENDRAIN (default)
PUSHPULL
Example:
TRST PUSHPULL ; Drive TRST also high
RESET type [time] [pwr] Normally the BDI drives the reset line during a reset sequence. If reset
type is NONE or SOFT, the BDI does not assert a hardware reset. If reset
type SOFT is supported depends on the connected target.
type
NONE
SOFT (soft reset via a debug register)
HARD (default)
time
The time in milliseconds the BDI assert the reset signal.
pwr
A different reset type can be defined for the initial power-
up reset (NONE, SOFT, HARD).
Example:
RESET SOFT ; reset ARM core via RCSR
RESET HARD 1000 ; assert RESET for 1 second
STARTUP mode [runtime]This parameter selects the target startup mode. The following modes are
supported:
HALT
This default mode tries to forces the target to debug
mode immediately out of reset.
STOP
In this mode, the BDI lets the target execute code for
"runtime" milliseconds after reset. This mode is useful
when boot code should initialize the target system.
RUN
After reset, the target executes code until stopped by the
Telnet "halt" command. The init list is not processed in
this mode.
WAIT
Sets the debug request bit in the target. Once the target
is released from reset it will enter debug mode.
IDLE
In this mode, the BDI does not access the target/core
until it is attached via the Telnet „attach“ command. This
is useful for cores that are not accessible after reset.
Only after the attach, the BDI starts communicating with
the debug logic of this target/core.
Example:
STARTUP STOP 3000 ; let the CPU run for 3 seconds
WAKEUP time
This entry in the init list allows to define a delay time (in ms) the BDI inserts
between releasing the reset line and starting communicating with the tar-
get. This delay is necessary when a target needs some wake-up time after
a reset.
time
the delay time in milliseconds
Example:
WAKEUP 3000 ; insert 3sec wake-up time