Abatron BDI2000 User manual

bdi
SCI
JTAG debug interface for SeeCode™ Debugger
XScale
User Manual
Manual Version 1.00 for BDI2000
© 1999-2003 ABATRON AG

bdi
SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 2
© Copyright 1999-2003 by ABATRON AG V 1.00
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 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 Debug Handler.....................................................................................................................17
4.2 Startup Mode.......................................................................................................................18
4.2.1 Startup mode RESET ................................................................................................18
4.2.2 Startup Mode STOP...................................................................................................18
4.2.3 Startup mode RUN.....................................................................................................18
5 Working with SeeCode..............................................................................................................19
5.1 Starting SeeCode................................................................................................................19
5.2 Properties............................................................................................................................20
5.3 Direct Commands................................................................................................................21
5.3.1 Target.Reset...............................................................................................................21
5.3.2 Flash.Setup................................................................................................................21
5.3.3 Flash.Erase................................................................................................................22
5.3.4 Flash.Load .................................................................................................................22
5.3.5 Flash.Idle....................................................................................................................22
5.4 Download to Flash Memory.................................................................................................23
6 Telnet Interface ..........................................................................................................................25
7 Specifications............................................................................................................................26
8 Environmental notice................................................................................................................27
9 Declaration of Conformity (CE)................................................................................................27
10 Warranty...................................................................................................................................28
Appendices
A Troubleshooting........................................................................................................................29
B Maintenance..............................................................................................................................30
C Trademarks................................................................................................................................32

bdi SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 3
© Copyright 1999-2003 by ABATRON AG V 1.00
1 Introduction
The BDI2000 adds JTAG based debug features to Metaware’s Seecode debugger.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 SeeCode debugger.
1.1 BDI2000
The BDI2000 is a processor system in a small box. It implements the interface between the BDM/
JTAG 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 implementa-
tion of lasted technology, the BDI2000 is optimally prepared for further enhancements.The firmware
and the programmable logic of the BDI2000 can be updated by the user with a simple Windows
based configuration program. The BDI2000 supports 1.8 – 5.0 Volts target systems (3.0 – 5.0 Volts
target systems with Rev.A/B).
PC Host
SeeCode
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
JTAG Interface
Ethernet (10 BASE-T)
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
JTAG Interface
RS232
XScale XScale

bdi SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 4
© Copyright 1999-2003 by ABATRON AG V 1.00
2 Installation
2.1 Connecting the BDI2000 toTarget
The enclosed target cable is designed for the Intel recommended 20pin JTAG connector. In case
where the target system has an appropriate connector, the cable can be directly connected.The pin
assignment is in accordance with the Intel specification.
In order to ensure reliable operation of the BDI (EMC, runtimes, etc.) the target cable length must not
exceed 20 cm (8").
!
BDI TRGT MODE BDI MAIN BDI OPTION
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
9 1
10 2
The green LED «TRGT» marked light up when target is powered up
Rev. A 1 19
20
2
1 - Vcc Target
2 - NC
3 - TRST
4 - NC
5 - TDI
6 - NC
7 - TMS
8 - GROUND
9 - TCK
10 - GROUND
11 - NC
12 - NC
13 - TDO
14 - NC
15 - RESET
16 - NC
17 - NC
18 - NC
19 - NC
20 - NC
20 pin JTAG
Connector
XScale
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
The green LED «TRGT» marked light up when target is powered up
BDI TRGT MODE TARGET A TARGET B
9 1
10 2
Rev. B/C
1 - Vcc Target
2 - NC
3 - TRST
4 - NC
5 - TDI
6 - NC
7 - TMS
8 - GROUND
9 - TCK
10 - GROUND
11 - NC
12 - NC
13 - TDO
14 - NC
15 - RESET
16 - NC
17 - NC
18 - NC
19 - NC
20 - NC
20 pin JTAG
Connector
1 19
20
2
XScale

bdi SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 5
© Copyright 1999-2003 by ABATRON AG V 1.00
BDI MAIN /TARGET A Connector Signals
Note:
The BDI actively drives TRST.It does not require any special power-up circuitry. Simply, the require-
ment is that TRST is weakly pulled down at the processor. It is suggested that the value of the pull-
down resistor is 10k or greater.
Pin Name Describtion
1 reserved This pin is currently not used.
2 TRST
JTAGTest Reset
This output of the BDI2000 resets the JTAGTAP controller on the target.
3+5 GND System Ground
4 TCK JTAGTest Clock
This output of the BDI2000 connects to the target TCK line.
6 TMS JTAGTest Mode Select
This output of the BDI2000 connects to the target TMS line.
7 RESET This open collector output of the BDI2000 is used to reset the target system.
8 TDI JTAGTest Data In
This output of the BDI2000 connects to the target TDI line.
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 connected to 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 TDO JTAGTest Data Out
This input to the BDI2000 connects to the target TDO line.

bdi SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 6
© Copyright 1999-2003 by ABATRON AG V 1.00
2.1.1 ChangingTarget ProcessorType
Before you can use the BDI2000 with an other target processor type (e.g.XScale <--> 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 SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 7
© Copyright 1999-2003 by ABATRON AG V 1.00
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 - BREAK-ENA
6 - GROUND
7 - NOT USED
8 - GROUND
9 - BREAK-A
10 - GROUND
11 - BREAK-B
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 SCI
JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 8
© Copyright 1999-2003 by ABATRON AG V 1.00
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 - BREAK-ENA
6 - GROUND
7 - NOT USED
8 - GROUND
9 - BREAK-A
10 - GROUND
11 - BREAK-B
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

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 9
© Copyright 1999-2003 by ABATRON AG V 1.00
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

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 10
© Copyright 1999-2003 by ABATRON AG V 1.00
2.4 Connecting the BDI2000 to 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
Rev. A
XScale
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
Rev. B/C
RS232 POWER LI TX RX 10 BASE-T
54321
9876
XScale

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 11
© Copyright 1999-2003 by ABATRON AG V 1.00
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 XScale

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 12
© Copyright 1999-2003 by ABATRON AG V 1.00
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:
b20xsc.exe Configuration program
b20xsc.hlp Helpfile for the configuration program
b20xscfw.xxx Firmware for BDI2000 for XScale targets
xscjed20.xxx JEDEC file for the BDI2000 (Rev. A/B) logic device programming
xscjed21.xxx JEDEC file for the BDI2000 (Rev. C) logic device programming
bdiifc32.dll BDI Interface DLL for configuration program
armbdi.dll BDI Target Interface DLL for SeeCode debugger
*.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 b20xsc.exe configuration program.
• Copy armbdi.dll to the SeeCode \bin directory

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 13
© Copyright 1999-2003 by ABATRON AG V 1.00
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.
!

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 14
© Copyright 1999-2003 by ABATRON AG V 1.00
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

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 15
© Copyright 1999-2003 by ABATRON AG V 1.00
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.
CPx register number:
The register number is used to build the appropriate MCR or MRC instruction.
+-----+-+-------+-----+-+-------+
|opc_2|0| CRm |opc_1|0| nbr |
+-----+-+-------+-----+-+-------+
CP15 : ID register (CRn = 0, opcode_2 = 0) 0x0000
CP15 : Cache Type (CRn = 0, opcode_2 = 1) 0x2000
CP15 : Invalidate I cache line (CRn = 7, opcode_2 = 1, CRm = 5) 0x2507
Special BDI Configuration Registers:
In order to change some special configuration parameters of the BDI, the GPR entry in the init list is
used. Normal ARM GPR's covers a range from 0 to 15. Other GPR's are used to set BDI internal
registers:
8006 When this entry is present, the BDI fills the default vector table in the Mini IC (except the
debug/reset vector) with the requested opcode. Also the vector table in the Mini IC will not
be updated each time before the target is restarted.:
8007 When this entry is present, the BDI fills the relocated vector table in the Mini IC (except the
debug/reset vector) with the requested opcode. Also the vector table in the Mini IC will not
be updated each time before the target is restarted.

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 16
© Copyright 1999-2003 by ABATRON AG V 1.00
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 breakpoints are implemented. When Soft-
ware is selected (default), Breakpoints are set by replacing program code
in target memory.When Hardware is selected, the built-in breakpoint logic
of the target CPU is used to implement Breakpoints.In this mode, only up
to 2 Breakpoints are available. This mode may be used when debugging
code already stored in a ROM.
CPU Type Select the CPU type of the target system.
JTAG Clock This option allows to select the used JTAG clock rate.
Debug Handler This parameter defines the base address of the debug handler.The debug
handler code (and the override vector tables) are loaded into the mini in-
struction cache during reset processing. See also XScale core manual
chapter "Software Debug".The entered value has to be 2k aligned in the
range 0x00000000 ...0x01FEF800 or 0xFE000800 ... 0xFFFFF800.
Run Time When startup mode STOP is selected, this option allows to set the run
time after reset in milliseconds until the target CPU is stopped. Values
from 100 (0.1 sec) till 32000 (32 sec) are accepted.
Trap Exceptions Select the exceptions that should lead to debug mode entry instead of en-
tering the normal exception handler. Maybe overridden by the debugger.
Big Endian... Check this switch if the target memory uses Big Endian format.

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 17
© Copyright 1999-2003 by ABATRON AG V 1.00
JTAG Scan Chain The BDI can also handle systems with multiple devices connected to the
JTAG scan chain.In order to put the other devices into BYPASS mode and
to count for the additional bypass registers, the BDI needs some informa-
tion about the scan chain layout. Enter the number and total instruction
register (IR) length of the devices present before the XScale chip (Prede-
cessor). Enter the appropriate information also for the devices following
the XScale chip (Successor).
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.
4.1 Debug Handler
The XScale variant of debugging via JTAG depends on a debug handler running on the target.This
handler communicates with the BDI via the JTAG interface.This debug handler is loaded into the mini
instruction cache via JTAG during reset processing.Please read also the chapter "Software Debug"
in the XScale manual. It is also necessary that the reset vectors at 0x00000000 and 0xFFFF0000
are overridden.
Because it is not possible to override only the reset vector, all vectors are overridden by a valid entry
in the mini IC.A code fetch always accesses the vector table in the mini IC loaded via JTAG.The mini
IC is never updated from memory, it can only be loaded via JTAG.
Always before the target exits debug mode, the BDI reads back the vector tables from memory and
updates the mini IC accordingly.This works fine when the vector table is only updated while the target
is in debug mode (e.g. via application download). If the application updates the vector table on the
fly, this will not change the mini IC and the old vectors will still be used until the target enters/exits
debug mode at least once.Therefore it is recommended that the vector table itself is not change dy-
namically. A second table outside the mini IC addresses may be used to change exception handler
addresses on the fly.
In order to force an enter/exit debug mode sequence, a "bkpt #1" instruction maybe added after the
vector tables are updated.The BDI recognizes this "bkpt #1" instruction and immediately restarts the
target.

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 18
© Copyright 1999-2003 by ABATRON AG V 1.00
4.2 Startup Mode
Startup mode defines how the BDI interacts with the target system after a reset or power up
sequence.
4.2.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:
• RESET is activated on the target system and the mini IC is loaded with the debug handler.
• RESET 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.2.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:
• RESET is activated on the target system and the mini IC is loaded with the debug handler.
• RESET is deactivated and the target starts executing application code.
• After a delay of RUNTIME seconds, the target is forced into debug mode.
• The BDI works through the initialization list and writes the corresponding addresses.
4.2.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:
• RESET is activated on the target system and the mini IC is loaded with the debug handler.
• RESET is deactivated and the target starts executing application code.
• The application runs until it is stopped by the debugger.

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 19
© Copyright 1999-2003 by ABATRON AG V 1.00
5Working with SeeCode
5.1 Starting SeeCode
In order to use the BDI as the target interface, use the following command to start SeeCode.
scarm -DLL=armbdi -io=port[,baud] [program [arguments]]
port Specifies the IP address of the BDI2000 or the serial communication port
where the BDI is connected. If a name is used for the IP address, there
must be an appropriate entry in the
hosts file.
COM1 = the BDI is serial connected to the COM1 connector
151.120.25.102 = the IP address of the BDI
BDI2000 = the name for the BDI in the
hosts file
baud If the BDI is serial connected, this second parameter defines the used
baudrate (e.g. 115200). If the BDI2000 is connected via ethernet, do not
enter any value as second parameter.
Some examples:
scarm -DLL=armbdi -io=COM1,57600 a.out
scarm -DLL=armbdi -io=191.23.34.56
scarm -DLL=armbdi -io=BDI2000
When using the debugger in GUI mode, you may also use the debuggers Option dialog to select the
appropriate BDI communication parameters.This way you can simply start SeeCode as follows:
scarm
For more information about debugger startup, consult SeeCode documentation.

bdiSCI JTAG interface for SeeCode™ Debugger, BDI2000 (XScale) User Manual 20
© Copyright 1999-2003 by ABATRON AG V 1.00
5.2 Properties
The BDI target interface supports the following properties.You may use it interactively via the debug-
ger command line or within a chip initialization file.
BDI_RESET This property forces a target hardware reset.You may use this property in
the chip initialization file to bring the target in a defined state before pro-
cessing other chip initialization functions.
BDI_DC=direct-commandWith this property you can execute a so called BDI direct command. BDI
direct commands are mainly used to erase and program flash memories.
They also allows a direct download to flash via SeeCode.
BDI_PRELOAD=name With this property you define the name of a BDI command file that should
be executed before program download begins.
By default preload.cmd in the default directory is used.
BDI_POSTLOAD=name With this property you define the name of a BDI command file that should
be executed after program download.
By default postload.cmd in the default directory is used.
BDI_LOG=name If this property is used, all calls to the BDI interface are recorded in a file.
The recorded calls are not useful for SeeCode user but may be used by
Abatron to solve interface problems between the SeeCode debugger and
the BDI.
BDI_BREAK=[soft|hard] This selects how instruction breakpoints are implemented. This property
is only useful if the target CPU has built-in breakpoint logic.Use this prop-
erty to switch to hardware breakpoints. Do not change breakpoint mode
when there are already breakpoints set.
If you select "soft", the BDI will still use hardware breakpoints for memory
areas defined as readonly (See chapter "Chip Initialization File" in See-
Code User’s Guide).
BDI_VERIFY=[no|first|all|only] This selects how writing to target memory is verified during program
download.
no : No verify at all (default)
first :Verify the first byte of every download block
all :Verify every downloaded byte
only : Do only verify, no write to memory
Example of a chip initialization file:
...
prop BDI_LOG=bdi.log
prop BDI_PRELOAD=c:\myproject\preload.cmd
prop BDI_PRELOAD=c:\myproject\postload.cmd
prop BDI_RESET
prop BDI_VERIFY=FIRST
...