bdi
Wind
for Tornado™, BDI2000 (MPC8xx/MPC5xx)
User Manual
22
© Copyright 1997-2007 by ABATRON AG Switzerland
V 1.38
3.2.2 Part [TARGET]
The part [TARGET] defines some target specific values.
CPUTYPE type
This value gives the BDI information about the connected CPU:
type
The CPU type from the following list:
MPC500 or MPC800
Example: CPUTYPE
MPC500
CPUCLOCK value
The BDI needs to know how fast the target CPU runs after processing the
init list. The BDM communication speed is selected based on this value. If
this value defines a clock rate that is higher than the real clock, BDM com-
munication may fail. When defining a clock rate slower than possible, BDM
communication still works but not as fast as possible.
Important: When programming the MPC555 internal flash, this value is
used to calculate the appropriate timing parameters.
value
the CPU clock in hertz
Example:
CPUCLOCK 25000000 ; CPU clock is 25.0MHz
BDIMODE mode [param] This parameter selects the BDI debugging mode. The following modes are
supported:
LOADONLY
Loads and starts the VxWorks core. No debugging via
BDM.
GATEWAY
After loading and starting the VxWorks core. The BDI es-
tablishes a communication channel between the target
server on the host and the target agent on the target.
The second parameter (UART | HDLC) defines the seri-
al communication protocol. If no second parameter is
present, normal BDM communication is used.
This mode supports task level debugging.
AGENT
The debug agent runs within the BDI. There is no need
for any debug software on the target. This mode accepts
a second parameter. If RUN is entered as a second pa-
rameter, the loaded application will be started immedi-
ately, otherwise only the PC is set and BDI waits for
WDB requests.
Example:
BDIMODE AGENT RUN
BDIMODE GATEWAY HDLC
STARTUP mode [runtime] This parameter selects the target startup mode. The following modes are
supported:
RESET
This default mode forces the target to debug mode im-
mediately out of reset. No code is executed after reset.
STOP
In this mode, the BDI lets the target execute code for
"runtime" milliseconds after reset. This mode is useful
when monitor code should initialize the target system.
RUN
After reset, the target executes code until stopped by the
Telnet "halt" command.
Example:
STARTUP STOP 3000 ; let the CPU run for 3 seconds
