Abatron BDI2000 User manual

bdiGDB
JTAG debug interface for GNU Debugger
PowerPC 7440 / 7450 / 86xx
User Manual
Manual Version 1.13 for BDI2000
©1997-2015 by Abatron AG

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 2
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
1 Introduction ................................................................................................................................. 3
1.1 BDI2000................................................................................................................................. 3
1.2 BDI Configuration ..................................................................................................................4
2 Installation ................................................................................................................................... 5
2.1 Connecting the BDI2000 to Target ........................................................................................5
2.1.1 Changing Target Processor Type ................................................................................7
2.2 Connecting the BDI2000 to Power Supply ............................................................................ 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 Initial configuration of the bdiGDB system...........................................................................12
2.5.1 Configuration with a Linux / Unix host........................................................................13
2.5.2 Configuration with a Windows host ............................................................................15
2.5.3 Recover procedure.....................................................................................................16
2.6 Testing the BDI2000 to host connection..............................................................................17
2.7 TFTP server for Windows....................................................................................................17
3 Using bdiGDB ............................................................................................................................ 18
3.1 Principle of operation...........................................................................................................18
3.2 Configuration File.................................................................................................................20
3.2.1 Part [INIT]...................................................................................................................21
3.2.2 Part [TARGET] ...........................................................................................................23
3.2.3 Part [HOST]................................................................................................................ 28
3.2.4 Part [FLASH] ..............................................................................................................30
3.2.5 Part [REGS] ............................................................................................................... 34
3.3 Debugging with GDB ...........................................................................................................36
3.3.1 Target setup ...............................................................................................................36
3.3.2 Connecting to the target.............................................................................................36
3.3.3 Breakpoint Handling...................................................................................................37
3.3.4 GDB monitor command..............................................................................................37
3.3.5 Target serial I/O via BDI.............................................................................................38
3.3.6 Embedded Linux MMU Support .................................................................................39
3.4 Telnet Interface....................................................................................................................41
3.5 Dual-Core Support for MPC8641D......................................................................................43
4 Specifications ............................................................................................................................ 45
5 Environmental notice................................................................................................................ 46
6 Declaration of Conformity (CE)................................................................................................ 46
7 Warranty..................................................................................................................................... 47
Appendices
A Troubleshooting ....................................................................................................................... 48
B Maintenance .............................................................................................................................. 49
C Trademarks ............................................................................................................................... 51

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 3
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
1 Introduction
bdiGDB enhances the GNU debugger (GDB), with JTAG/COP debugging for PowerPC 7440/7450/
86xx based targets. With the built-in Ethernet interface you get a very fast code download speed. No
target communication channel (e.g. serial line) is wasted for debugging purposes. Even better, you
can use fast Ethernet debugging with target systems without network capability. The host to BDI
communication uses the standard GDB remote protocol.
An additional Telnet interface is available for special debug tasks (e.g. force a hardware reset,
program flash memory).
The following figure shows how the BDI2000 interface is connected between the host and the target:
1.1 BDI2000
The BDI2000 is the main part of the bdiGDB system. This small box implements the interface be-
tween the JTAG pins of the target CPU and a 10Base-T Ethernet connector. The firmware and the
programmable logic of the BDI2000 can be updated by the user with a simple Windows based con-
figuration program. The BDI2000 supports 1.8 – 5.0 Volts target systems (3.0 – 5.0 Volts target sys-
tems with Rev. B).
GNU Debugger
(GDB)
BDI2000
Target System
COP Interface
Ethernet (10 BASE-T)
PPC
7450

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 4
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
1.2 BDI Configuration
As an initial setup, the IP address of the BDI2000, the IP address of the host with the configuration
file and the name of the configuration file is stored within the flash of the BDI2000.
Every time the BDI2000 is powered on, it reads the configuration file via TFTP.
Following an example of a typical configuration file:
;bdiGDB configuration file for Sandpoint 7450 evaluation system
;--------------------------------------------------------------
;
[INIT]
; init core register
;WREG MSR 0x00000000 ;clear MSR
; init memory controller (based on DINK32)
WM32 0xFEC00000 0x80000080 ;select MSAR1
WM32 0xFEE00000 0x00204060 ;
WM32 0xFEC00000 0x84000080 ;select MSAR2
WM32 0xFEE00000 0x80a0c0e0 ;
WM32 0xFEC00000 0x90000080 ;select MEAR1
WM32 0xFEE00000 0x1f3f5f7f ;
WM32 0xFEC00000 0x94000080 ;select MEAR2
WM32 0xFEE00000 0x9fbfdfff ;
WM32 0xFEC00000 0xa0000080 ;select MBEN
WM8 0xFEE00000 0x03 ;
WM32 0xFEC00000 0xa0000080 ;select MPM
WM8 0xFEE00003 0x32 ;
WM32 0xFEC00000 0xf0000080 ;select MCCR1
WM32 0xFEE00000 0x0000e075 ;do not set MEMGO
WM32 0xFEC00000 0xf4000080 ;select MCCR2
WM32 0xFEE00000 0xcc044004 ;
WM32 0xFEC00000 0xf8000080 ;select MCCR3
WM32 0xFEE00000 0x00004078 ;
WM32 0xFEC00000 0xfc000080 ;select MCCR4
WM32 0xFEE00000 0x39323235 ;
WM32 0xFEC00000 0xf0000080 ;select MCCR1
WM32 0xFEE00000 0x0000e875 ;now set MEMGO
;
WM32 0xFEC00000 0x78000080 ;select EUMBBAR
WM32 0xFEE00000 0x000000fc ;Embedded utility memory block at 0xFC000000
;
WM32 0xFEC00000 0xa8000080 ;select PICR1
WM32 0xFEE00000 0x901014ff ;enable flash write (Flash on processor bus)
;
[TARGET]
CPUTYPE 7450 ;the CPU type (7450)
JTAGCLOCK 1 ;use 8 MHz JTAG clock
WORKSPACE 0x00000000 ;workspace in target RAM for data cache flush and L3PM access
BDIMODE AGENT ;the BDI working mode (LOADONLY | AGENT | GATEWAY)
BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC hardware breakpoint
DCACHE NOFLUSH ;data cache flushing (FLUSH | NOFLUSH)
[HOST]
IP 151.120.25.115
FILE E:\cygnus\root\usr\demo\mpc7450\vmlinux
FORMAT IMAGE
LOAD MANUAL ;load code MANUAL or AUTO after reset
Based on the information in the configuration file, the target is automatically initialized after every re-
set.

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 5
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2 Installation
2.1 Connecting the BDI2000 to Target
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
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

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 6
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
BDI TARGET B Connector Signals:
Pin Name Describtion
1 TDO JTAG Test Data Out
This input to the BDI2000 connects to the target TDO pin.
2QACK QACK
This output of the BDI2000 connects to the target QACK pin. By default this pin is not driven
by the BDI2000. With an entry in the configuration file it can be forced low.
3 TDI JTAG Test Data In
This output of the BDI2000 connects to the target TDI pin.
4TRST JTAG Test 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 JTAG Test Clock
This output of the BDI2000 connects to the target TCK pin.
8 <reseved>
9 TMS JTAG Test 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

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 7
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2.1.1 Changing Target Processor Type
Before you can use the BDI2000 with an other target processor type (e.g. CPU32 <--> PPC), a new
setup has to be done (see chapter 2.5). 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.
!

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 8
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
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

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 9
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
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

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 10
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2.4 Connecting the BDI2000 to Host
2.4.1 Serial line communication
Serial line communication is only used for the initial configuration of the bdiGDB system.
The host is connected to the BDI through the serial interface (COM1...COM4). The communication
cable (included) between BDI and Host is a serial cable. There is the same connector pinout for the
BDI and for the Host side (Refer to Figure below).
RS232 Connector
(for PC host)
BDI2000
Target System
RS232
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

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 11
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
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 When this LED light BLINKS, data is being transmitted through 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 / Unix
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
RS232 POWER LI TX RX 10 BASE-T
18 PPC

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 12
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2.5 Initial configuration of the bdiGDB system
On the enclosed diskette you will find the BDI configuration software and the firmware / logic required
for the BDI2000. For Windows users there is also a TFTP server included.
The following files are on the diskette.
b20pwsgd.exe Windows Configuration program
b20pwsgd.xxx Firmware for the BDI2000
copjed20.xxx JEDEC file for the BDI2000 (Rev. B) logic device when working with a COP target
copjed21.xxx JEDEC file for the BDI2000 (Rev. C) logic device when working with a COP target
tftpsrv.exe TFTP server for Windows (WIN32 console application)
*.cfg Configuration files
*.def Register definition files
bdisetup.zip ZIP Archive with the Setup Tool sources for Linux / UNIX hosts.
Overview of an installation / configuration process:
• Create a new directory on your hard disk
• Copy the entire contents of the enclosed diskette into this directory
• Linux only: extract the setup tool sources and build the setup tool
• Use the setup tool to load/update the BDI firmware/logic
Note: A new BDI has no firmware/logic loaded.
• Use the setup tool to transmit the initial configuration parameters
- IP address of the BDI.
- IP address of the host with the configuration file.
- Name of the configuration file. This file is accessed via TFTP.
- Optional network parameters (subnet mask, default gateway).
Activating BOOTP:
The BDI can get the network configuration and the name of the configuration file also via BOOTP.
For this simple enter 0.0.0.0 as the BDI’s IP address (see following chapters). If present, the subnet
mask and the default gateway (router) is taken from the BOOTP vendor-specific field as defined in
RFC 1533.
With the Linux setup tool, simply use the default parameters for the -c option:
[root@LINUX_1 bdisetup]# ./bdisetup -c -p/dev/ttyS0 -b57
The MAC address is derived from the serial number as follows:
MAC: 00-0C-01-xx-xx-xx , repace the xx-xx-xx with the 6 left digits of the serial number
Example: SN# 93123457 ==>> 00-0C-01-93-12-34

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 13
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2.5.1 Configuration with a Linux / Unix host
The firmware / logic update and the initial configuration of the BDI2000 is done with a command line
utility. In the ZIP Archive bdisetup.zip are all sources to build this utility. More information about this
utility can be found at the top in the bdisetup.c source file. There is also a make file included.
Starting the tool without any parameter displays information about the syntax and parameters.
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).
Following the steps to bring-up a new BDI2000:
1. Build the setup tool:
The setup tool is delivered only as source files. This allows to build the tool on any Linux / Unix host.
To build the tool, simply start the make utility.
[root@LINUX_1 bdisetup]# make
cc -O2 -c -o bdisetup.o bdisetup.c
cc -O2 -c -o bdicnf.o bdicnf.c
cc -O2 -c -o bdidll.o bdidll.c
cc -s bdisetup.o bdicnf.o bdidll.o -o bdisetup
2. Check the serial connection to the BDI:
With "bdisetup -v" you may check the serial connection to the BDI. The BDI will respond with infor-
mation about the current loaded firmware and network configuration.
Note: Login as root, otherwise you probably have no access to the serial port.
[root@LINUX_1 bdisetup]# ./bdisetup -v -p/dev/ttyS0 -b57
BDI Type : BDI2000 Rev.C (SN: 92152150)
Loader : V1.05
Firmware : unknown
Logic : unknown
MAC : 00-0c-01-92-15-21
IP Addr : 255.255.255.255
Subnet : 255.255.255.255
Gateway : 255.255.255.255
Host IP : 255.255.255.255
Config : ??????????????????
3. Load/Update the BDI firmware/logic:
With "bdisetup -u" the firmware is loaded and the CPLD within the BDI2000 is programmed. This con-
figures the BDI for the target you are using. Based on the parameters -a and -t, the tool selects the
correct firmware / logic files. If the firmware / logic files are in the same directory as the setup tool,
there is no need to enter a -d parameter.
[root@LINUX_1 bdisetup]# ./bdisetup -u -p/dev/ttyS0 -b57 -aGDB -tMPC7450
Connecting to BDI loader
Erasing CPLD
Programming firmware with ./b20pwsgd.100
Programming CPLD with ./copjed21.102
!

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 14
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
4. Transmit the initial configuration parameters:
With "bdisetup -c" the configuration parameters are written to the flash memory within the BDI.
The following parameters are used to configure the BDI:
BDI IP Address The IP address for the BDI2000. Ask your network administrator for as-
signing an IP address to this BDI2000. Every BDI2000 in your network
needs a different IP address.
Subnet Mask The subnet mask of the network where the BDI is connected to. A subnet
mask of 255.255.255.255 disables the gateway feature. Ask your network
administrator for the correct subnet mask. If the BDI and the host are in
the same subnet, it is not necessary to enter a 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.
Config - Host IP Address Enter the IP address of the host with the configuration file. The configura-
tion file is automatically read by the BDI2000 after every start-up.
Configuration file Enter the full path and name of the configuration file. This file is read via
TFTP. Keep in mind that TFTP has it’s own root directory (usual /tftpboot).
You can simply copy the configuration file to this directory and the use the
file name without any path.
For more information about TFTP use "man tftpd".
[root@LINUX_1 bdisetup]# ./bdisetup -c -p/dev/ttyS0 -b57 \
> -i151.120.25.101 \
> -h151.120.25.118 \
> -fppc750.cnf
Connecting to BDI loader
Writing network configuration
Writing init list and mode
Configuration passed
5. Check configuration and exit loader mode:
The BDI is in loader mode when there is no valid firmware loaded or you connect to it with the setup
tool. While in loader mode, the Mode LED is flashing. The BDI will not respond to network requests
while in loader mode. To exit loader mode, the "bdisetup -v -s" can be used. You may also power-off
the BDI, wait some time (1min.) and power-on it again to exit loader mode.
[root@LINUX_1 bdisetup]# ./bdisetup -v -p/dev/ttyS0 -b57 -s
BDI Type : BDI2000 Rev.C (SN: 92152150)
Loader : V1.05
Firmware : V1.00 bdiGDB for MPC7450
Logic : V1.02 PPC6xx/PPC7xx
MAC : 00-0c-01-92-15-21
IP Addr : 151.120.25.101
Subnet : 255.255.255.255
Gateway : 255.255.255.255
Host IP : 151.120.25.118
Config : sp7450.cnf
The Mode LED should go off, and you can try to connect to the BDI via Telnet.
[root@LINUX_1 bdisetup]# telnet 151.120.25.101

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 15
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2.5.2 Configuration with a Windows host
First make sure that the BDI is properly connected (see Chapter 2.1 to 2.4).
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).
dialog box «BDI2000 Update/Setup»
Before you can use the BDI2000 together with the GNU debugger, you must store the initial config-
uration parameters in the BDI2000 flash memory. The following options allow you to do this:
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.
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
displayed.
Update This button is only active if there is a newer firmware or logic version pres-
ent in the execution directory of the bdiGDB setup software. Press this but-
ton to write the new firmware and/or logic into the BDI2000 flash memory
/ programmable logic.
!

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 16
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
BDI IP Address Enter the IP address for the BDI2000. Use the following format:
xxx.xxx.xxx.xxx e.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..
Config - Host IP Address Enter the IP address of the host with the configuration file. The configura-
tion file is automatically read by the BDI2000 after every start-up.
Configuration file Enter the full path and name of the configuration file.
e.g. D:\gnu\config\bdi\ads8260bdi.cnf
For information about the syntax of the configuration file see the bdiGDB
User manual. This name is transmitted to the TFTP server when reading
the configuration file.
Transmit Click on this button to store the configuration in the BDI2000 flash
memory.
2.5.3 Recover procedure
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

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 17
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
2.6 Testing the BDI2000 to host connection
After the initial setup is done, you can test the communication between the host and the BDI2000.
There is no need for a target configuration file and no TFTP server is needed on the host.
• If not already done, connect the BDI2000 system to the network.
• Power-up the BDI2000.
• Start a Telnet client on the host and connect to the BDI2000 (the IP address you entered dur-
ing initial configuration).
• If everything is okay, a sign on message like «BDI Debugger for Embedded PowerPC» and
a list of the available commands should be displayed in the Telnet window.
2.7 TFTP server for Windows
The bdiGDB system uses TFTP to access the configuration file and to load the application program.
Because there is no TFTP server bundled with Windows, Abatron provides a TFTP server application
tftpsrv.exe. This WIN32 console application runs as normal user application (not as a system ser-
vice).
Command line syntax: tftpsrv [p] [w] [dRootDirectory]
Without any parameter, the server starts in read-only mode. This means, only read access request
from the client are granted. This is the normal working mode. The bdiGDB system needs only read
access to the configuration and program files.
The parameter [p] enables protocol output to the console window. Try it.
The parameter [w] enables write accesses to the host file system.
The parameter [d] allows to define a root directory.
tftpsrv p Starts the TFTP server and enables protocol output
tftpsrv p w Starts the TFTP server, enables protocol output and write accesses are
allowed.
tftpsrv dC:\tftp\ Starts the TFTP server and allows only access to files in C:\tftp and its
subdirectories. As file name, use relative names.
For example "bdi\mpc750.cfg" accesses "C:\tftp\bdi\mpc750.cfg"
You may enter the TFTP server into the Startup group so the server is started every time you login.

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 18
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
3 Using bdiGDB
3.1 Principle of operation
The firmware within the BDI handles the GDB request and accesses the target memory or registers
via the JTAG interface. There is no need for any debug software on the target system. After loading
the code via TFTP, debugging can begin at the very first assembler statement.
Whenever the BDI system is powered-up the following sequence starts:
Power On
initial
configuration
valid?
Get configuration file
via TFTP
Process target init list
via TFTP and set the PC
Load program code
Process GDB request
Power OFF
activate BDI2000 loader
Power OFF
no
yes
RUN selected?
Start loaded program code

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 19
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
Breakpoints:
There are two breakpoint modes supported. One of them (SOFT) is implemented by replacing appli-
cation code with a TRAP instruction. The other (HARD) uses the built in breakpoint logic. If HARD is
used, only 1 breakpoint can be active at the same time.
The following example selects SOFT as the breakpoint mode:
BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC hardware breakpoints
All the time the application is suspended (i.e. caused by a breakpoint) the target processor remains
freezed.

bdiGDBfor BDI2000 (PowerPC 7440/7450/86xx) User Manual 20
© Copyright 1997-2015 by ABATRON AG Switzerland V 1.13
3.2 Configuration File
The configuration file is automatically read by the BDI after every power on.
The syntax of this file is as follows:
; comment
[part name]
identifier parameter1 parameter2 ..... parameterN ; comment
identifier parameter1 parameter2 ..... parameterN
.....
[part name]
identifier parameter1 parameter2 ..... parameterN
identifier parameter1 parameter2 ..... parameterN
..... etc.
Numeric parameters can be entered as decimal (e.g. 700) or as hexadecimal (0x80000).
Note about how to enter 64bit values:
The syntax for 64 bit parameters is : [<high word>_]<low word>
The "high word" (optional) and "low word" can be entered as decimal or hexadecimal. They are han-
dled as two separate values concatenated with an underscore.
Examples:
0x01234567_0x89abcdef =>> 0x0123456789abcdef
1_0 =>> 0x0000000100000000
256 =>> 0x0000000000000100
3_0x1234 =>> 0x0000000300001234
0x80000000_0 =>> 0x8000000000000000