Abatron BDI2000 Installation and operation manual

bdi
CW
BDM interface for CodeWarrior™ Debugger
PowerPC MPC8xx/MPC5xx
User Manual
Manual Version 1.02 for BDI2000
© 1992-2001 ABATRON AG

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 2
© Copyright 1992-2001 by ABATRON AG V 1.02
1 Introduction .................................................................................................................................3
1.1 BDI2000.................................................................................................................................3
2 Installation ...................................................................................................................................4
2.1 Connecting the BDI2000 to Target.........................................................................................4
2.1.1 Changing Target Processor Type .................................................................................6
2.2 Connecting the BDI2000 to Power Supply.............................................................................7
2.2.1 External Power Supply.................................................................................................7
2.2.2 Power Supply from Target System...............................................................................8
2.3 Status LED «MODE».............................................................................................................9
2.4 Connecting the BDI2000 to the Host...................................................................................10
2.4.1 Serial line communication..........................................................................................10
2.4.2 Ethernet communication ............................................................................................11
2.5 Installation of the Configuration Software............................................................................12
2.6 Configuration .......................................................................................................................13
2.6.1 BDI2000 Setup/Update..............................................................................................13
3 Init List........................................................................................................................................15
4 BDI working modes...................................................................................................................16
4.1 Startup Mode.......................................................................................................................17
4.1.1 Startup mode RESET ................................................................................................17
4.1.2 Startup Mode STOP...................................................................................................17
4.1.3 Startup mode RUN.....................................................................................................17
5 Working with CodeWarrior........................................................................................................18
5.1 Setup ...................................................................................................................................18
5.2 EPPC Exceptions ................................................................................................................18
6 Specifications............................................................................................................................19
6.1 BDI2000...............................................................................................................................19
7 Environmental notice................................................................................................................20
8 Declaration of Conformity (CE)................................................................................................20
9 Warranty.....................................................................................................................................21
Appendices
A Troubleshooting........................................................................................................................22
B Maintenance..............................................................................................................................23
C Trademarks................................................................................................................................25

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 3
© Copyright 1992-2001 by ABATRON AG V 1.02
1 Introduction
The BDI2000 adds Background Debug Mode features to the CodeWarrior debugger environment
from Metrowerks.With the BDI2000, you control and monitor the microcontroller solely through the
stable on-chip debugging services.You won’t waste time and target resources with a software ROM
monitor, and you eliminate the cabling problems typical of ICE’s. This combination runs even when
the target system crashes and allows developers to continue investigating the cause of the crash.
A RS232 interface with a maximum of 115 kBaud and a 10Base-T Ethernet interface is available for
the host interface.
The configuration software is used to update the firmware and to configure the BDI2000 so it works
with the CodeWarrior debugger.
1.1 BDI2000
The BDI2000 is a processor system in a small box.It implements the interface between the BDM pins
of the target CPU and a 10Base-T Ethernet / RS232 connector.BDI2000 is powered by a MC68360,
512Kbyte RAM and a flash memory of 1024Kbyte. As a result of consistent implementation of lasted
technology, the BDI2000 is optimally prepared for further enhancements.The firmware and the pro-
grammable logic of the BDI2000 can be updated by the user with a simple Windows based configu-
ration program.The BDI2000 supports 1.8 – 5.0 Volts target systems (3.0 – 5.0Volts target systems
with Rev. A/B).
PC Host
CodeWarrior
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
BDM Interface
Ethernet (10 BASE-T)
MPC
5xx8xx
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
BDM Interface
MPC
5xx8xx
RS232

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 4
© Copyright 1992-2001 by ABATRON AG V 1.02
2 Installation
2.1 Connecting the BDI2000 toTarget
The cable to the target system is a ten pin flat ribbon cable. In case where the target system has an
appropriate connector, the cable can be directly connected.The pin assignment is in accordance with
the Motorola specification.
In order to ensure reliable operation of the BDI (EMC, runtimes, etc.) the target cable length must not
exceed 20 cm (8").
For BDI MAIN / TARGET A connector signals see table on next page.
!
BDI TRGT MODE BDI MAIN BDI OPTION
Target Connector
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
MPC
8xx
9 1
10 2
The green LED «TRGT» marked light up when target is powered up
1 - VFLS0
2 - SRESET
3 - GROUND
4 - DSCK
5 - GROUND
6 - VFLS1
7 - HRESET
8 - DSDI
9 - Vcc Target
10 - DSDO
19
210
Rev. A
«Rev. A» is the first BDI2000 version, produced until June 1999
Target Connector
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
MPC
8xx
The green LED «TRGT» marked light up when target is powered up
1 - VFLS0
2 - SRESET
3 - GROUND
4 - DSCK
5 - GROUND
6 - VFLS1
7 - HRESET
8 - DSDI
9 - Vcc Target
10 - DSDO
19
210
Rev B/C
BDI TRGT MODE TARGET A TARGET B
9 1
10 2

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 5
© Copyright 1992-2001 by ABATRON AG V 1.02
BDI MAIN /TARGET A Connector Signals:
Mention of sources used: MPC860ADS User’s Manual, Revision A
Enhanced Debug Mode Detection:
For MPC8xx and MPC555 targets, debug mode (Freeze) detection also works when the BDM con-
nector pins VFLS0 and VFLS1 are not connected to the target. If not connected to VFLSx, this BDM
connector pins should be left open or tied toVcc.The BDI uses the following algorithm to check if the
target is in debug mode (freezed):
BOOL PPC_TargetFreezed(void) {
if ((VFLS0 != 1) | (VFLS0 != 1)) return FALSE;
read debug port status;
if (status == freezed) return TRUE;
else return FALSE;
Pin Name Describtion
1 VFLS0 These pin and pin 6 (VFLS1) indicate to the debug port controller whether or not the MPC
is in debug mode.When both VFLS0 and VFLS1 are at "1", the MPC is in debug mode.
2 SRESET This is the Soft-Reset bidirectional signal of the MPC8xx. On the MPC5xx it is an output.
The debug port configuration is sampled and determined on the rising-edge of SRESET
(forboth processorfamilies).On the MPC8xxit isabidirectional signalwhichmaybe driven
externally to generate soft reset sequence.This signal is in fact redundant regarding the
MPC8xx debug port controller since there is a soft-reset signal integrated within the debug
port protocol.However, the local debug port controller uses this signal for compatibility with
MPC5xx existing boards and s/w.
3+5 GND System Ground
4 DSCK Debug-port Serial Clock
During asynchronous clock mode, the serial data is clocked into the MPC according to the
DSCK clock.The DSCK serves also a role during soft-reset configuration.
6 VFLS1 These pin and pin 1 (VFLS0) indicate to the debug port controller whether or not the MPC
is in debug mode.When both VFLS0 and VFLS1 are at "1", the MPC is in debug mode.
7 HRESET This is the Hard-Reset bidirectional signal of the MPC.When this signal is asserted (low)
the MPC enters hard reset sequence which include hard reset configuration.This signal is
made redundant with the MPC8xx debug port controller since there is a hard-reset com-
mand integrated within the debug port protocol.
8 DSDI Debug-port Serial Data In
Via the DSDI signal, the debug port controller sends its data to the MPC.The DSDI serves
also a role during soft-reset configuration.
9 Vcc Target 1.8 – 5.0V:
This is the target reference voltage.It indicates that the target has power and it is also used
to create the logic-level reference for the input comparators.It also controls the output logic
levels to the target.It is normally fed from Vdd I/O on the target board.
3.0 – 5.0V with Rev. A/B :
This input to the BDI2000 is used to detect if the target is powered up.If there is a current
limiting resistor between this pin and the target Vdd, it should be 100 Ohm or less.
10 DSDO Debug-port Serial Data Out
DSDO is clocked out by the MPC according to the debug port clock, in parallel with the
DSDI being clocked in.The DSDO serves also as "READY" signal for the debug port con-
troller to indicate that the debug port is ready to receive controller’s command (or data).

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 6
© Copyright 1992-2001 by ABATRON AG V 1.02
2.1.1 ChangingTarget ProcessorType
Before you can use the BDI2000 with an other target processor type (e.g.CPU32 <--> PPC), a new
setup has to be done (see Appendix A). During this process the target cable must be disconnected
from the target system.The BDI2000 needs to be supplied with 5 Volts via the BDI OPTION connec-
tor (Rev. A) or via the POWER connector (Rev.B/C). For more information see chapter 2.2.1
«External Power Supply».
To avoid data line conflicts, the BDI2000 must be disconnected from the target system while
programming the logic for an other target CPU.
!

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 7
© Copyright 1992-2001 by ABATRON AG V 1.02
2.2 Connecting the BDI2000 to Power Supply
2.2.1 External Power Supply
The BDI2000 needs to be supplied with 5Volts (max.1A) via the BDI OPTION connector (Rev. A) or
via POWER connector (Rev.B/C).The available power supply from Abatron (option) or the enclosed
power cable can be directly connected. In order to ensure reliable operation of the BDI2000, keep
the power supply cable as short as possible.
For error-free operation, the power supply to the BDI2000 must be between 4.75V and 5.25V DC.
The maximal tolerable supply voltage is 5.25 VDC. Any higher voltage or a wrong polarity
might destroy the electronics.
Please switch on the system in the following sequence:
• 1 --> external power supply
• 2 --> target system
!
BDI TRGT MODE BDI MAIN BDI OPTION
13
1
14 2
BDI OPTION
1 - NOT USED
2 - GROUND
3 - NOT USED
4 - GROUND
5 - NOT USED
6 - GROUND
7 - NOT USED
8 - GROUND
9 - NOT USED
10 - GROUND
11 - NOT USED
12 - Vcc (+5V)
13 - Vcc Target (+5V)
14 - Vcc (+5V)
Vcc GND
Connector
The green LED «BDI» marked light up when 5V power is connected to the BDI2000
Rev. A
BDI TRGT MODE TARGET A TARGET B
POWER
1 - Vcc (+5V)
2 - VccTGT
3 - GROUND
4 - NOT USED
Connector
The green LED «BDI» marked light up when 5V power is connected to the BDI2000
RS232 POWER LI TX RX 10 BASE-T
1 Vcc
2
GND 3
4
Rev. B Version
Rev. B/C

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 8
© Copyright 1992-2001 by ABATRON AG V 1.02
2.2.2 Power Supply fromTarget System
The BDI2000 needs to be supplied with 5 Volts (max.1A) via BDI MAIN target connector (Rev.A) or
via TARGET A connector (Rev. B/C).This mode can only be used when the target system runs with
5V and the pin «Vcc Target» is able to deliver a current up to 1A@5V. For pin description and layout
see chapter 2.1 «Connecting the BDI2000 toTarget».Insert the enclosed Jumper as shown in figure
below. Please ensure that the jumper is inserted correctly.
For error-free operation, the power supply to the BDI2000 must be between 4.75V and 5.25V DC.
The maximal tolerable supply voltage is 5.25 VDC. Any higher voltage or a wrong polarity
might destroy the electronics.
!
BDI TRGT MODE BDI MAIN BDI OPTION
13
1
14 2
BDI OPTION
Connector
The green LEDs «BDI» and «TRGT» marked light up when target is powered up
Jumper
and the jumper is inserted correctly
1 - NOT USED
2 - GROUND
3 - NOT USED
4 - GROUND
5 - NOT USED
6 - GROUND
7 - NOT USED
8 - GROUND
9 - NOT USED
10 - GROUND
11 - NOT USED
12 - Vcc (+5V)
13 - Vcc Target (+5V)
14 - Vcc BDI2000 (+5V)
Rev. A
BDI TRGT MODE TARGET A TARGET B
POWER
1 - Vcc BDI2000 (+5V)
2 - Vcc Target (+5V)
3 - GROUND
4 - NOT USED
Connector
RS232 POWER LI TX RX 10 BASE-T
1
2
3
4
The green LEDs «BDI» and «TRGT» marked light up when target is powered up
and the jumper is inserted correctly
Jumper
Rev. B/C

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 9
© Copyright 1992-2001 by ABATRON AG V 1.02
2.3 Status LED «MODE»
The built in LED indicates the following BDI states:
MODE LED BDI STATES
OFF The BDI is ready for use, the firmware is already loaded.
ON The power supply for the BDI2000 is < 4.75VDC.
BLINK The BDI «loader mode» is active (an invalid firmware is loaded or loading firmware is active).
BDI TRGT MODE BDI MAIN BDI OPTION
BDI TRGT MODE TARGET A TARGET B
Rev. A
Rev. B/C

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 10
© Copyright 1992-2001 by ABATRON AG V 1.02
2.4 Connecting the BDI2000 to the Host
2.4.1 Serial line communication
The host is connected to the BDI through the serial interface (COM1...COM4).The communication
cable between BDI and Host is a serial cable (RXD / TXD are crossed).There is the same connector
pinout for the BDI and for the Host side (Refer to Figure below).
RS232 Connector
(for PC host)
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
RS232
RS232 LI TX RX 10 BASE-T
54321
9876
PC Host
1 - NC
2 - RXD data from host
3 - TXD data to host
4 - NC
5 - GROUND
6 - NC
7 - NC
8 - NC
9 - NC
MPC
5xx8xx
Rev. A
RS232 Connector
(for PC host)
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
RS232
PC Host
1 - NC
2 - RXD data from host
3 - TXD data to host
4 - NC
5 - GROUND
6 - NC
7 - NC
8 - NC
9 - NC
MPC
5xx8xx
Rev. B/C
RS232 POWER LI TX RX 10 BASE-T
54321
9876

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 11
© Copyright 1992-2001 by ABATRON AG V 1.02
2.4.2 Ethernet communication
The BDI2000 has a built-in 10 BASE-T Ethernet interface (see figure below). Connect an UTP (Un-
shilded Twisted Pair) cable to the BD2000. For thin Ethernet coaxial networks you can connect a
commercially available media converter (BNC-->10 BASE-T) between your network and the
BDI2000. Contact your network administrator if you have questions about the network.
The following explains the meanings of the built-in LED lights:
LED Name Description
LI Link When this LED light is ON, data link is successful between the UTP
port of the BDI2000 and the hub to which it is connected.
TX Transmit WhenthisLEDlightBLINKS,dataisbeingtransmittedthrough the UTP
port of the BDI2000
RX Receive When this LED light BLINKS, data is being received through the UTP
port of the BDI2000
10 BASE-T
PC Host
Target System
Ethernet (10 BASE-T)
1 - TD+
2 - TD-
3 - RD+
4 - NC
5 - NC
6 - RD-
7 - NC
8 - NC
Connector
RS232 LI TX RX 10 BASE-T
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
18
RS232 POWER LI TX RX 10 BASE-T
Rev. A
Rev. B/C
18 MPC
5xx8xx

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 12
© Copyright 1992-2001 by ABATRON AG V 1.02
2.5 Installation of the Configuration Software
On the enclosed diskette you will find the BDI configuration software and the firmware required for
the BDI. Copy all these files to a directory on your hard disk.
The following files are on the diskette:
b20mpc.exe Configuration program
b20mpc.hlp Helpfile for the configuration program
b20mpc.cnt Help contents file
b20ppcfw.xxx Firmware for BDI2000 (Rev. A/B) for MPC8xx/MPC5xx targets
b21ppcfw.xxx Firmware for BDI2000 (Rev. C) for MPC8xx/MPC5xx targets
ppcjed20.xxx JEDEC file for the BDI logic device programming
bdiifc32.dll BDI Interface DLL
*.bdi Configuration Examples
Example of an installation process:
• Copy the entire contents of the enclosed diskette into a directory on the hard disk.
•You may create a new shortcut to the b20mpc.exe configuration program.
• Copy the BDI interface DLL to ...\CodeWarrior\Bin\Plugins\Support\Abatron\bdiifc32.dll

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 13
© Copyright 1992-2001 by ABATRON AG V 1.02
2.6 Configuration
Before you can use the BDI together with the debugger, the BDI must be configured.Use the SETUP
menu and follow the steps listed below:
• Load or update the firmware / logic, store IP address --> Firmware
• Set the communication parameters between Host and BDI --> Communication
• Setup an initialization list for the target processor --> Initlist
• Select the working mode --> Mode
• Transmit the configuration to the BDI --> Mode Transmit
For information about the dialogs and menus use the help system (F1).
2.6.1 BDI2000 Setup/Update
First make sure that the BDI is properly connected (see Chapter 2.1 to 2.4).The BDI must be con-
nected via RS232 to the Windows host.
To avoid data line conflicts, the BDI2000 must be disconnected from the target system while
programming the logic for an other target CPU (see Chapter 2.1.1).
The following dialogbox is used to check or update the BDI firmware and logic and to set the network
parameters.
dialog box «BDI2000 Update/Setup»
The following options allow you to check or update the BDI firmware and logic and to set the network
parameters:
Channel Select the communication port where the BDI2000 is connected during
this setup session.
Baudrate Select the baudrate used to communicate with the BDI2000 loader during
this setup session.
!

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 14
© Copyright 1992-2001 by ABATRON AG V 1.02
Connect Click on this button to establish a connection with the BDI2000 loader.
Once connected, the BDI2000 remains in loader mode until it is restarted
or this dialog box is closed.
Current Press this button to read back the current loaded BDI2000 software and
logic versions. The current loader, firmware and logic version will be dis-
played.
Update This button is only active if there is a newer firmware or logic version
present in the execution directory of the BDI setup software. Press this
button to write the new firmware and/or logic into the BDI2000 flash mem-
ory / programmable logic.
IP Address Enter the IP address for the BDI2000.
Use the following format: xxx.xxx.xxx.xxxe.g.151.120.25.101
Ask your network administrator for assigning an IP address to this
BDI2000. Every BDI2000 in your network needs a different IP address.
Subnet Mask Enter the subnet mask of the network where the BDI is connected to.
Use the following format: xxx.xxx.xxx.xxxe.g.255.255.255.0
A subnet mask of 255.255.255.255 disables the gateway feature.
Ask your network administrator for the correct subnet mask.
Default Gateway Enter the IP address of the default gateway.Ask your network administra-
tor for the correct gateway IP address. If the gateway feature is disabled,
you may enter 255.255.255.255 or any other value..
Transmit Click on this button to store the network configuration in the BDI2000 flash
memory.
In rare instances you may not be able to load the firmware in spite of a correctly connected BDI (error
of the previous firmware in the flash memory).Before carrying out the following procedure,check
the possibilities in Appendix «Troubleshooting». In case you do not have any success with the
tips there, do the following:
• Switch OFF the power supply for the BDI and open the unit as
described in Appendix «Maintenance»
• Place the jumper in the «INIT MODE» position
• Connect the power cable or target cable if the BDI is powered
from target system
• Switch ON the power supply for the BDI again and wait until the
LED «MODE» blinks fast
• Turn the power supply OFF again
• Return the jumper to the «DEFAULT» position
• Reassemble the unit as described in Appendix «Maintenance»
INIT MODE
DEFAULT

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 15
© Copyright 1992-2001 by ABATRON AG V 1.02
3 Init List
dialog box «Startup Init List»
In order to prepare the target for debugging, you can define an Initialization List.This list is stored in
the Flash memory of the BDI2000 and worked through every time the target comes out of reset.Use
it to get the target operational after a reset.The memory system is usually initialized through this list.
After processing the init list, the RAM used to download the application must be accessible.
Use on-line help (F1) and the supplied configuration examples on the distribution disk to get more
information about the init list.
Note:
You may also use the debuggers feature to setup the hardware. But keep in mind, that the BDI will
speed up BDM communication clock after processing its own initialization list based on the "Clock
Rate" field in the "BDIWorking Mode" dialog box (see next chapter).The "Clock Rate" value you have
to enter is therefore the value the target runs immediately after reset.
To use a BDM speed as fast as possible, you should at least speed up the target with an entry in the
BDI initialization list and set the "Clock Rate" field to the appropriate value.The rest of the initialization
(e.g.memory controller) can be done with the debugger.

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 16
© Copyright 1992-2001 by ABATRON AG V 1.02
4 BDI working modes
dialog box «BDI Working Mode»
With this dialog box you can define how the BDI interacts with the target system.
Identification Enter a text to identify this setup.This text can be read by the debugger
with the appropriate Command.
Startup Startup mode defines how the BDI interacts with the target processor after
reset or power up.The options RESET, STOP or RUN can be selected.
Breakpoint Breakpoint mode defines how instruction breakpoints are implemented.
When Software is selected (default), instruction breakpoints are set as re-
quested by the debugger (Software or Hardware breakpoints). When
Hardware is selected, the BDI uses always hardware breakpoints.This is
useful when the attached debugger does not support hardware break-
points on instruction access. For CodeWarrior, select always Software.
CPU Type Select the CPU type of the target system.
Clock Rate Enter the clock rate the target CPU runs after BDI has worked through the
init list. BDI selects the BDM communication speed based on this param-
eter. If this parameter selects a CPU clock rate that is higher than the real
clock rate, BDM communication may fail. When selecting a clock rate
slower than possible, BDM communication still works but not as fast as
possible.
Workspace In order to access the floating-point registers of a MPC5xx microproces-
sor, the BDI needs a workspace of 8 bytes in target RAM. Enter the base
address of this RAM area.This memory is used, when a floating-point reg-
ister is accessed.If there is no RAM space available for the BDI, you may
enter 0xFFFFFFFF as the workspace address but then, accessing float-
ing-point registers is not possible.
Transmit Click on this button to send the initialization list and the working mode to
the BDI. This is normally the last step done before the BDI can be used
with the debugging system.

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 17
© Copyright 1992-2001 by ABATRON AG V 1.02
4.1 Startup Mode
Startup mode defines how the BDI interacts with the target system after a reset or power up
sequence.
4.1.1 Startup mode RESET
In this mode no ROM is required on the target system.The necessary initialization is done by the BDI
with the programmed init list.The following steps are executed by the BDI after system reset or
system power up:
• HRESET is activated on the target system.
• HRESET is deactivated and the target is forced into debug mode.
• The BDI works through the initialization list and writes to the corresponding addresses.
The RESET mode is the standard working mode. Other modes are used in special cases (i.e.
applications in ROM, special requirements on the reset sequence...).
4.1.2 Startup Mode STOP
In this mode the initialization code is in a ROM on the target system.The code in this ROM handles
base initialization. At the end of the code, the initialization program enters an endless loop until it is
interrupted by the BDI.This mode is intended for special requirements on the reset sequence (e.g.
loading a RAM based programmable logic device).
In this mode the following steps are executed by the BDI after system reset or power up:
• HRESET is activated on the target system.
• HRESET is deactivated and the target is forced into debug mode.
• The target is started and begins executing application code.
• After a delay of 2 seconds, the target is forced into debug mode.
• The BDI works through the initialization list and writes the corresponding addresses.
4.1.3 Startup mode RUN
This mode is used to debug applications which are already stored in ROM.The application is started
normally and is stopped when the debugger is started.
In this mode, the following steps are executed by the BDI after system reset or power up:
• HRESET is activated on the target system.
• HRESET is deactivated and the target is forced into debug mode.
• The target is startet and begins executing application code.
• The application runs until it is stopped by the debugger.

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 18
© Copyright 1992-2001 by ABATRON AG V 1.02
5Working with CodeWarrior
5.1 Setup
Use the CodeWarrior "IDE Preferences" dialog box, section "Debugger -> Remote Connections", and
setup the appropriate communication parameters for the "AbatronTCP/IP" and "Abatron Serial" con-
nection.
Use the CodeWarrior "your project Settings" dialog box, section "Debugger -> Remote Debugging"
and select either "Abatron TCP/IP" or "Abatron Serial".
5.2 EPPC Exceptions
From the CodeWarrior menu "Edit" open "your project Settings...".
Select "Debugger - EPPC Exceptions".This opens the "EPPC Exceptions" dialog box.
Here it is possible to define which EPPC exceptions causes an entry into debug mode. Do not check
exceptions which should be handled by application code (typically External Interrupt and Decrement-
er Interrupt). Never disable Development Port and External Breakpoint. For normal debugging you
should also not disable Program, Trace, Software Emulation, Load/Store Breakpoint and Instruction
Breakpoint.

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 19
© Copyright 1992-2001 by ABATRON AG V 1.02
6 Specifications
6.1 BDI2000
Operating Voltage Limiting 5 VDC ± 0.25 V
Power Supply Current typ. 500 mA
max. 1000 mA
RS232 Interface: Baud Rates 9’600,19’200, 38’400, 57’600,115’200
Data Bits 8
Parity Bits none
Stop Bits 1
Network Interface 10 BASE-T
Serial Transfer Rate between BDI and Target up to 16 Mbit/s
Supported target voltage 1.8 – 5.0 V (3.0 – 5.0 V with Rev. A/B)
Operating Temperature + 5 °C ... +60 °C
Storage Temperature -20 °C ... +65 °C
Relative Humidity (noncondensing) <90 %rF
Size 190 x 110 x 35 mm
Weight (without cables) 420 g
Host Cable length (RS232) 2.5 m
Specifications subject to change without notice

bdi
CW
BDM interface for CodeWarrior™ Debugger, BDI2000 (MPC5xx/8xx) User Manual 20
© Copyright 1992-2001 by ABATRON AG V 1.02
7 Environmental notice
Disposal of the equipment must be carried out at a designated disposal site.
8 Declaration of Conformity (CE)