Abatron 7440 User manual

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

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) 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.3 Status LED «MODE».............................................................................................................8
2.4 Connecting the BDI2000 to the Host.....................................................................................9
2.4.1 Serial line communication............................................................................................9
2.4.2 Ethernet communication ............................................................................................10
2.5 Installation of the Configuration Software............................................................................11
2.6 Configuration .......................................................................................................................12
2.6.1 BDI2000 Setup/Update..............................................................................................12
3 Init List........................................................................................................................................14
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 SeeCode..............................................................................................................18
5.1 Starting SeeCode................................................................................................................18
5.2 Properties............................................................................................................................19
5.3 Direct Commands................................................................................................................20
5.3.1 Target.Reset...............................................................................................................20
5.3.2 Flash.Setup................................................................................................................20
5.3.3 Flash.Erase................................................................................................................21
5.3.4 Flash.Load .................................................................................................................21
5.3.5 Flash.Idle....................................................................................................................21
5.4 Download to Flash Memory.................................................................................................22
6 Telnet Interface ..........................................................................................................................24
7 Specifications............................................................................................................................25
8 Environmental notice................................................................................................................26
9 Declaration of Conformity (CE)................................................................................................26
10 Warranty...................................................................................................................................27
Appendices
A Troubleshooting........................................................................................................................28
B Maintenance..............................................................................................................................29
C Trademarks................................................................................................................................31

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) 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 JTAG
pins of the target CPU and a 10Base-T Ethernet / RS232 connector.The firmware and the program-
mable 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. 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)
PPC
7450
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
JTAG Interface
MPC
7450
RS232

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 4
© Copyright 1999-2003 by ABATRON AG V 1.00
2 Installation
2.1 Connecting the BDI2000 toTarget
The cable to the target system is a 16 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 PowerPC COP connector 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 TARGET B connector signals see table on next page.
!
COP/JTAG Connector
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
Target System
PPC 1 15
16
2
The green LED «TRGT» marked light up when target is powered up
BDI TRGT MODE TARGET A TARGET B
15 1
16 2
1 - TDO
2 - QACK
3 - TDI
4 - TRST
5 - HALTED
6 - Vcc Target
7 - TCK
8 - NC (RXD)
9 - TMS
10 - NC (TXD)
11 - SRESET
12 - GROUND
13 - HRESET
14 - NC (key)
15 - CKSTP_OUT
16 - GROUND

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 5
© Copyright 1999-2003 by ABATRON AG V 1.00
BDITARGET B Connector Signals:
Pin Name Describtion
1 TDO JTAGTest Data Out
This input to the BDI2000 connects to the target TDO pin.
2 IO0 General purpose I/O
This output of the BDI2000 connects to the target QACK pin. Currently not used.
3 TDI JTAGTest Data In
This output of the BDI2000 connects to the target TDI pin.
4 TRST JTAGTest Reset
This output of the BDI2000 resets the JTAG TAP controller on the target.
5 IN0 General purpose Input
This input to the BDI2000 connects to the target HALTED pin. Currently not used.
6 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. 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.
7 TCK JTAGTest Clock
This output of the BDI2000 connects to the target TCK pin.
8 <reseved>
9 TMS JTAGTest Mode Select
This output of the BDI2000 connects to the target TMS line.
10 <reseved>
11 SRESET Soft-Reset
This open collector output of the BDI2000 connects to the target SRESET pin.
12 GROUND System Ground
13 HRESET Hard-Reset
This open collector output of the BDI2000 connects to the target HRESET pin.
14 <reseved>
15 IN1 General purpose Input
This input to the BDI2000 connects to the target CKSTP_OUT pin. Currently not used.
16 GROUND System Ground

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) 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. ARM <--> 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 (Version A) or via the POWER connector (Version B). 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 debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 7
© Copyright 1999-2003 by ABATRON AG V 1.00
2.2 Connecting the BDI2000 to Power Supply
The BDI2000 needs to be supplied with 5 Volts (max. 1A) via the POWER connector.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 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

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 8
© 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 TARGET A TARGET B

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 9
© Copyright 1999-2003 by ABATRON AG V 1.00
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
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
RS232 POWER LI TX RX 10 BASE-T
54321
9876
PPC

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 10
© 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,dataisbeingtransmittedthroughthe 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
BDI2000
AA
AAbb bbaa aattttrr rroo oonn nn AA AAGG GG SS
SSww wwiiiiss ssss ss MM MMaa aadd ddeeee
RS232 POWER LI TX RX 10 BASE-T
18 PPC

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 11
© 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:
b20pws.exe Configuration program
b20pws.hlp Helpfile for the configuration program
b20pws.cnt Help contents file
b20pwsfw.xxx Firmware for BDI2000 for COP targets (PPC7450)
copjed20.xxx JEDEC file for BDI2000 (Rev. B) logic device programming
copjed21.xxx JEDEC file for BDI2000 (Rev. C) logic device programming
bdiifc32.dll BDI Interface DLL for the configuration program
ppcbdi.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 b20cop.exe configuration program.
• Copy ppcbdi.dll to the SeeCode \bin directory

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 12
© 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.
!

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 13
© 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

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 14
© 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.
You may also use the debuggers feature to setup the hardware (chip initialization file).

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 15
© Copyright 1999-2003 by ABATRON AG V 1.00
Special BDI Configuration Registers:
In order to change some special configuration parameters of the BDI, the SPR entry in the init list is
used. Normal PPC SPR's covers a range from 0 to 1023. Other SPR's are used to set BDI internal
registers:
8001 For slow memory it may be necessary to increase the number of clocks used to execute a
memory access cycle. If for example you cannot access boot ROM content with the default
configuration of your memory controller, define additional memory access clocks with this
SPR number in the init list.Usual values are in the range 1000 - 4000 (0x400 - 0x1000).
8002 Defines an alternate boot address. Normally a PPC boots from 0xFFF00100. A MPC8260
has also the option to boot from 0x00000100.The BDI needs to know the boot address in
order to set the correct hardware breakpoint during startup.
8003 Defines the base address of the L3 cache private memory.Because L3 cache private mem-
ory cannot be accessed directly via JTAG, the BDI loads some support code into the work-
space and uses it to access this memory range. Therefore a workspace is necessary to
access this memory range.
8004 Defines the size of the L3 cache private memory in bytes (e.g. 0x100000 for 1Mbyte).
8006 Write tothis special registera valueof 1 ifthe BDI shoulduse the alternatesinglestep mode.
The alternate mode does not use the trace bit (MSR[SE]) to implement single stepping. It
uses always a hardware breakpoint (via IABR) on the next instruction to implement single
stepping.
8007 Write to this special register a value of 1 if the BDI must not use burst reads when reading
memory via COP. This will slow down memory read performance dramatically. Disabling
burst reads maybe necessary if the memory controller does not support misaligned burst
accesses.
8009 This entry in the init list allows to define a delay time (in ms) the BDI inserts between releas-
ing the COP-HRESET line and starting communicating with the target.This init list entry may
be necessary if COP-HRESET is delayed on its way to the PowerPC reset pin.

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) 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.
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.
CPU Type Select the CPU family type of the target system.
JTAG Clock This option allows to select the used JTAG clock rate.
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.
Workspace In order to speed up code download, enter the address of a free 256 byte
RAM area.The BDI will install there some code that supports faster pro-
gram download.A value of 0xFFFFFFFF disables the workspace.The BDI
also needs this workspace to flush the data cache and to access L2 pri-
vate memory.
Catch exceptions Check this switch if the BDI should catch unhandled exception. Catching
exceptions is only possible if the memory at address 0x00000100 to
0x00001FFF is writable and the vector table is mapped to 0x00000000
(MSR[IP] = 0).
Flush L3 cache Check this switch if the BDI should flush the target cache before accessing
memory.This is mainly useful if there is an enabled L3 cache.If this switch
is not set, the BDI uses L1/L2 cache coherent read and write accesses to
target memory. Coherent access means, that the L1/L2 cache is directly
read or written via COP if the appropriate cache line is valid. In order to
flush the cache, the BDI needs some workspace in target RAM to execute
the flush code.
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
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 17
© Copyright 1999-2003 by ABATRON AG V 1.00
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.
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 begins executing application code.
• After a delay (Run Time), the target is forced into debug mode.
• The BDI works through the initialization list.
4.1.3 Startup mode RUN
This mode is used to debug an application which is already stored in ROM.The application is started
normally and will be 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 begins executing application code.
• The application runs until it is stopped by the debugger.

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 18
© 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.
scppc -DLL=ppcbdi -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:
scppc -DLL=ppcbdi -io=COM1,57600 a.out
scppc -DLL=ppcbdi -io=191.23.34.56
scppc -DLL=ppcbdi -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:
scppc
For more information about debugger startup, consult SeeCode documentation.

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 19
© 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.
PPC_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=ppcbdi.log
prop BDI_PRELOAD=c:\myproject\preload.cmd
prop BDI_PRELOAD=c:\myproject\postload.cmd
prop PPC_RESET
prop BDI_BREAK=HARD
prop BDI_VERIFY=FIRST
...

bdi
SCI
JTAG debug interface for SeeCode™ Debugger, BDI2000 (PPC744x/745x) User Manual 20
© Copyright 1999-2003 by ABATRON AG V 1.00
5.3 Direct Commands
For special functions (mainly for flash programming) the BDI supports so called «Direct Commands».
This commands can be entered in a command file (e.g. PRELOAD.CMD) or directly executed as
property in the Command Line Window.This Direct Commands are not interpreted by SeeCode but
directly sent to the BDI.After processing the command the result is displayed in the debugger’s con-
sole.
Direct Commands are ASCII - Strings with the following structure:
<Object>.<Action> [<ParName>=<ParValue>]...
Example: flash.erase addr=0x02800000
All names are case insensitive. Parameter values are numbers or strings. Numeric parameters can
be entered as decimal (e.g.700) or as hexadecimal (0x80000) values.
If the commands are entered via the SeeCode property feature, use the following syntax:
prop bdi_dc="direct-command"
Example: prop bdi_dc="flash.load addr=0x02800000 size=0x200000"
5.3.1Target.Reset
This direct command executes a real physical reset of the target system.
5.3.2 Flash.Setup
In order to support loading into flash memory, the BDI needs some information about the used flash
devices.Before any other flash related command can be used, this direct command must be execut-
ed.
Syntax: flash.setup type=am29f size=0x80000 bus=32 workspace=0x1000
type This parameter defines the type of flash used.It is used to select the correct program-
ming algorithm.The following flash types are supported:
AM29F, AM29BX8, AM29BX16, I28BX8, I28BX16, AT49, AT49X8, AT49X16,
STRATAX8, STRATAX16, MIRROR, MORRORX8, MIRRORX16,
I28BX32, AM29DX16, AM29DX32
size The size of one flash chip in bytes (e.g. AM29F010 = 0x20000).This value is used to
calculate the starting address of the current flash memory bank.
bus The width of the memory bus that leads to the flash chips. Do not enter the width of
the flash chip itself.The parameter TYPE carries the information about the number of
data lines connected to one flash chip. For example, enter 16 if you are using two
AM29F010 to build a 16bit flash memory bank.
workspace If a workspace is defined, the BDI uses a faster programming algorithm that run out of
RAM on the target system. Otherwise, the algorithm is processed within the BDI.The
workspace is used for a 1kByte data buffer and to store the algorithm code.There must
be at least 2kBytes of RAM available for this purpose.