The next step is to set up the PC's port, by doing something like this in DOS on the PC:
C:\> MODE com1:9600,n,8,1,none
This example--run on an MS DOS 4.0 system--sets the PC port to 9600 bps, no parity, eight data bits, one stop bit, and no "retry" action; you must match the communications parameters when establishing the Unix end of the connection as well.
To give control of the PC to the Unix side of the serial line, type the following at the DOS console:
C:\> CTTY com1
(Later, if you wish to return control to the DOS console, you can use
CTTY con---but you must send it over the device that
had control, in our example over the `COM1' serial line).
From the Unix host, use a communications program such as
cu to communicate with the PC; for example,
cu -s 9600 -l /dev/ttya
cu options shown specify, respectively, the linespeed and the
serial port to use. If you use
tip instead, your command line
may look something like the following:
tip -9600 /dev/ttya
Your system may require a different name where we show
`/dev/ttya' as the argument to
tip. The communications
parameters, including which port to use, are associated with the
tip argument in the "remote" descriptions file--normally the
system table `/etc/remote'.
cu connection, change the DOS working
directory to the directory containing a copy of your 29K program, then
start the PC program
EBMON (an EB29K control program supplied
with your board by AMD). You should see an initial display from
EBMON similar to the one that follows, ending with the
EBMON prompt `#'---
C:\> G: G:\> CD \usr\joe\work29k G:\USR\JOE\WORK29K> EBMON Am29000 PC Coprocessor Board Monitor, version 3.0-18 Copyright 1990 Advanced Micro Devices, Inc. Written by Gibbons and Associates, Inc. Enter '?' or 'H' for help PC Coprocessor Type = EB29K I/O Base = 0x208 Memory Base = 0xd0000 Data Memory Size = 2048KB Available I-RAM Range = 0x8000 to 0x1fffff Available D-RAM Range = 0x80002000 to 0x801fffff PageSize = 0x400 Register Stack Size = 0x800 Memory Stack Size = 0x1800 CPU PRL = 0x3 Am29027 Available = No Byte Write Available = Yes # ~.
Then exit the
tip program (done in the example by
~. at the
running, ready for GDB to take over.
For this example, we've assumed what is probably the most convenient
way to make sure the same 29K program is on both the PC and the Unix
system: a PC/NFS connection that establishes "drive
G:" on the
PC as a file system on the Unix host. If you do not have PC/NFS or
something similar connecting the two systems, you must arrange some
other way--perhaps floppy-disk transfer--of getting the 29K program
from the Unix system to the PC; GDB does not download it over the
Go to the first, previous, next, last section, table of contents.