2 _dnl__ Copyright (c) 1990 1991 1992 Free Software Foundation, Inc.
3 _dnl__ This file is part of the source for the GDB manual.
4 _dnl__ M4 FRAGMENT $Id$
5 _dnl__ This text diverted to "Remote Debugging" section in general case;
6 _dnl__ however, if we're doing a manual specifically for one of these, it
7 _dnl__ belongs up front (in "Getting In and Out" chapter).
9 @subsection The _GDBN__ remote serial protocol
11 @cindex remote serial debugging, overview
12 To debug a program running on another machine (the debugging
13 @dfn{target} machine), you must first arrange for all the usual
14 prerequisites for the program to run by itself. For example, for a C
19 A startup routine to set up the C runtime environment; these usually
20 have a name like @file{crt0}. The startup routine may be supplied by
21 your hardware supplier, or you may have to write your own.
24 You probably need a C subroutine library to support your program's
25 subroutine calls, notably managing input and output.
28 A way of getting your program to the other machine---for example, a
29 download program. These are often supplied by the hardware
30 manufacturer, but you may have to write your own from hardware
34 The next step is to arrange for your program to use a serial port to
35 communicate with the machine where _GDBN__ is running (the @dfn{host}
36 machine). In general terms, the scheme looks like this:
40 _GDBN__ already understands how to use this protocol; when everything
41 else is set up, you can simply use the @samp{target remote} command
42 (@pxref{Targets,,Specifying a Debugging Target}).
45 you must link with your program a few special-purpose subroutines that
46 implement the _GDBN__ remote serial protocol. The file containing these
47 subroutines is called a @dfn{debugging stub}.
50 The debugging stub is specific to the architecture of the remote
51 machine; for example, use @file{sparc-stub.c} to debug programs on
54 @cindex remote serial stub list
55 These working remote stubs are distributed with _GDBN__:
57 @c FIXME! verify these...
61 For @sc{sparc} architectures.
65 For Motorola 680x0 architectures.
69 For Intel 386 and compatible architectures.
72 The @file{README} file in the _GDBN__ distribution may list other
76 * stub contents:: What the stub can do for you
77 * bootstrapping:: What you must do for the stub
78 * debug session:: Putting it all together
79 * protocol:: Outline of the communication protocol
83 @subsubsection What the stub can do for you
85 @cindex remote serial stub
86 The debugging stub for your architecture supplies these three
90 @item handle_exception
91 @kindex handle_exception
92 @cindex remote serial stub, main routine
93 This is the central workhorse, but your program never calls it
94 explicitly---the setup code arranges for @code{handle_exception} to
95 run when a trap is triggered.
97 @code{handle_exception} takes control when your program stops during
98 execution (for example, on a breakpoint), and mediates communications
99 with _GDBN__ on the host machine. This is where the communications
100 protocol is implemented; @code{handle_exception} acts as the _GDBN__
101 representative on the target machine; it begins by sending summary
102 information on the state of your program, then continues to execute,
103 retrieving and transmitting any information _GDBN__ needs, until you
104 execute a _GDBN__ command that makes your program resume; at that point,
105 @code{handle_exception} returns control to your own code on the target
108 @item set_debug_traps
109 @kindex set_debug_traps
110 @cindex remote serial stub, initialization
111 You must call this subroutine explicitly near the beginning of your
112 program. This is the routine that arranges to transfer control to
113 @code{handle_exception} when your program stops.
116 @cindex @code{breakpoint} subroutine, remote
117 Use this auxiliary subroutine to make your program contain a
118 breakpoint. Depending on the particular situation, this may be the only
119 way for _GDBN__ to get control. For instance, if your target
120 machine has some sort of interrupt button, you won't need to call this;
121 pressing the interrupt button will transfer control to
122 @code{handle_exception}---in efect, to _GDBN__. On some machines,
123 simply receiving characters on the serial port may also trigger a trap;
124 again, in that situation, you don't need to call @code{breakpoint} from
125 your own program---simply running @samp{target remote} from the host
126 _GDBN__ session will get control.
128 Call @code{breakpoint} if none of these is true, or if you simply want
129 to make certain your program stops at a predetermined point for the
130 start of your debugging session.
134 @subsubsection What you must do for the stub
136 @cindex remote stub, support routines
137 The debugging stubs that come with _GDBN__ are set up for a particular
138 chip architecture, but they have no information about the rest of your
139 debugging target machine. To allow the stub to work, you must supply
140 three special low-level subroutines, and make sure one library routine
144 @item int getDebugChar()
146 Write this subroutine to read a single character from the serial port.
147 It may be identical to @code{getchar} for your target system; a
148 different name is used to allow you to distinguish the two if you wish.
150 @item void putDebugChar(int)
152 Write this subroutine to write a single character to the serial port.
153 It may be identical to @code{putchar} for your target system; a
154 different name is used to allow you to distinguish the two if you wish.
156 @item void flush_i_cache()
157 @kindex flush_i_cache
158 Write this subroutine to flush the instruction cache, if any, on your
159 target machine. If there is no instruction cache, this subroutine may
162 On target machines that have instruction caches, _GDBN__ requires this
163 function to make certain that the state of your program is stable.
165 @item void *memset(void *, int, int)
167 This is the standard library function @code{memset} that sets an area of
168 memory to a known value. If you have one of the free versions of
169 @code{libc.a}, @code{memset} can be found there; otherwise, you must
170 either obtain it from your hardware manufacturer, or write your own.
173 If you do not use the GNU C compiler, you may also need other standard
174 library subroutines; this will vary from one stub to another, but in
175 general the stubs are likely to use any of the common library
176 subroutines which @code{gcc} generates as inline code.
180 @subsubsection Putting it all together
182 @cindex remote serial debugging summary
183 In summary, when your program is ready to debug, you must follow these
188 Make sure you have the supporting low-level routines:
189 @code{getDebugChar}, @code{putDebugChar}, @code{flush_i_cache},
193 Insert these lines near the top of your program:
201 Compile and link together: your program, the _GDBN__ debugging stub for
202 your target architecture, and the supporting subroutines.
205 Make sure you have a serial connection between your target machine and
206 the _GDBN__ host, and identify the serial port used for this on the host.
209 Download your program to your target machine (or get it there by
210 whatever means the manufacturer provides), and start it.
213 To start remote debugging, run _GDBN__ on the host machine, and specify
214 as an executable file the program that is running in the remote machine.
215 This tells _GDBN__ how to find your program's symbols and the contents
218 Then establish communication using the @code{target remote} command.
219 Its argument is the name of the device you're using to control the
220 target machine. For example:
223 target remote /dev/ttyb
227 if the serial line is connected to the device named @file{/dev/ttyb}.
229 @c this is from the old text, but it doesn't seem to make sense now that I've
230 @c seen an example... pesch 4sep1992
231 This will stop the remote machine if it is not already stopped.
236 Now you can use all the usual commands to examine and change data and to
237 step and continue the remote program.
239 To resume the remote program and stop debugging it, use the @code{detach}
243 @subsubsection Outline of the communication protocol
245 @cindex debugging stub, example
246 @cindex remote stub, example
247 @cindex stub example, remote debugging
248 The stub files provided with _GDBN__ implement the target side of the
249 communication protocol, and the _GDBN__ side is implemented in the
250 _GDBN__ source file @file{remote.c}. Normally, you can simply allow
251 these subroutines to communicate, and ignore the details. (If you're
252 implementing your own stub file, you can still ignore the details: start
253 with one of the existing stub files. @file{sparc-stub.c} is the best
254 organized, and therefore the easiest to read.)
256 However, there may be occasions when you need to know something about
257 the protocol---for example, if there is only one serial port to your
258 target machine, you might want your program to do something special if
259 it recognizes a packet meant for _GDBN__.
261 @cindex protocol, _GDBN__ remote serial
262 @cindex serial protocol, _GDBN__ remote
263 @cindex remote serial protocol
264 All _GDBN__ commands and responses (other than acknowledgements, which
265 are single characters) are sent as a packet which includes a
266 checksum. A packet is introduced with the character @samp{$}, and ends
267 with the character @samp{#} followed by a two-digit checksum:
270 $@var{packet info}#@var{checksum}
273 @cindex checksum, for _GDBN__ remote
275 @var{checksum} is computed as the modulo 256 sum of the @var{packet
278 When either the host or the target machine receives a packet, the first
279 response expected is an acknowledgement: a single character, either
280 @samp{+} (to indicate the package was received correctly) or @samp{-}
281 (to request retransmission).
283 The host (_GDBN__) sends commands, and the target (the debugging stub
284 incorporated in your program) sends data in response. The target also
285 sends data when your program stops.
287 Command packets are distinguished by their first character, which
288 identifies the kind of command.
290 These are the commands currently supported:
294 Requests the values of CPU registers.
297 Sets the values of CPU registers.
299 @item m@var{addr},@var{count}
300 Read @var{count} bytes at location @var{addr}.
302 @item M@var{addr},@var{count}:@dots{}
303 Write @var{count} bytes at location @var{addr}.
307 Resume execution at the current address (or at @var{addr} if supplied).
311 Step the target program for one instruction, from either the current
312 program counter or from @var{addr} if supplied.
315 Kill the target program.
318 Report the most recent signal. To allow you to take advantage of the
319 _GDBN__ signal handling commands, one of the functions of the debugging
320 stub is to report CPU traps as the corresponding POSIX signal values.
323 @kindex set remotedebug
324 @kindex show remotedebug
325 @cindex packets, reporting on stdout
326 @cindex serial connections, debugging
327 If you have trouble with the serial connection, you can use the command
328 @code{set remotedebug}. This makes _GDBN__ report on all packets sent
329 back and forth across the serial line to the remote machine. The
330 packet-debugging information is printed on the _GDBN__ standard output
331 stream. @code{set remotedebug off} turns it off, and @code{show
332 remotedebug} will show you its current state.
336 @node i960-Nindy Remote
337 @subsection _GDBN__ with a Remote i960 (Nindy)
341 @dfn{Nindy} is a ROM Monitor program for Intel 960 target systems. When
342 _GDBN__ is configured to control a remote Intel 960 using Nindy, you can
343 tell _GDBN__ how to connect to the 960 in several ways:
347 Through command line options specifying serial port, version of the
348 Nindy protocol, and communications speed;
351 By responding to a prompt on startup;
354 By using the @code{target} command at any point during your _GDBN__
355 session. @xref{Target Commands, ,Commands for Managing Targets}.
360 * Nindy Startup:: Startup with Nindy
361 * Nindy Options:: Options for Nindy
362 * Nindy reset:: Nindy Reset Command
366 @subsubsection Startup with Nindy
368 If you simply start @code{_GDBP__} without using any command-line
369 options, you are prompted for what serial port to use, @emph{before} you
370 reach the ordinary _GDBN__ prompt:
373 Attach /dev/ttyNN -- specify NN, or "quit" to quit:
377 Respond to the prompt with whatever suffix (after @samp{/dev/tty})
378 identifies the serial port you want to use. You can, if you choose,
379 simply start up with no Nindy connection by responding to the prompt
380 with an empty line. If you do this, and later wish to attach to Nindy,
381 use @code{target} (@pxref{Target Commands, ,Commands for Managing Targets}).
384 @subsubsection Options for Nindy
386 These are the startup options for beginning your _GDBN__ session with a
387 Nindy-960 board attached:
391 Specify the serial port name of a serial interface to be used to connect
392 to the target system. This option is only available when _GDBN__ is
393 configured for the Intel 960 target architecture. You may specify
394 @var{port} as any of: a full pathname (e.g. @samp{-r /dev/ttya}), a
395 device name in @file{/dev} (e.g. @samp{-r ttya}), or simply the unique
396 suffix for a specific @code{tty} (e.g. @samp{-r a}).
399 (An uppercase letter ``O'', not a zero.) Specify that _GDBN__ should use
400 the ``old'' Nindy monitor protocol to connect to the target system.
401 This option is only available when _GDBN__ is configured for the Intel 960
405 @emph{Warning:} if you specify @samp{-O}, but are actually trying to
406 connect to a target system that expects the newer protocol, the connection
407 will fail, appearing to be a speed mismatch. _GDBN__ will repeatedly
408 attempt to reconnect at several different line speeds. You can abort
409 this process with an interrupt.
413 Specify that _GDBN__ should first send a @code{BREAK} signal to the target
414 system, in an attempt to reset it, before connecting to a Nindy target.
417 @emph{Warning:} Many target systems do not have the hardware that this
418 requires; it only works with a few boards.
422 The standard @samp{-b} option controls the line speed used on the serial
427 @subsubsection Nindy Reset Command
432 For a Nindy target, this command sends a ``break'' to the remote target
433 system; this is only useful if the target has been equipped with a
434 circuit to perform a hard reset (or some other interesting action) when
442 @subsection _GDBN__ with a Remote EB29K
445 @cindex running 29K programs
447 To use _GDBN__ from a Unix system to run programs on AMD's EB29K
448 board in a PC, you must first connect a serial cable between the PC
449 and a serial port on the Unix system. In the following, we assume
450 you've hooked the cable between the PC's @file{COM1} port and
451 @file{/dev/ttya} on the Unix system.
454 * Comms (EB29K):: Communications Setup
455 * _GDBP__-EB29K:: EB29K cross-debugging
456 * Remote Log:: Remote Log
460 @subsubsection Communications Setup
462 The next step is to set up the PC's port, by doing something like the
463 following in DOS on the PC:
466 C:\> MODE com1:9600,n,8,1,none
470 This example---run on an MS DOS 4.0 system---sets the PC port to 9600
471 bps, no parity, eight data bits, one stop bit, and no ``retry'' action;
472 you must match the communications parameters when establishing the Unix
473 end of the connection as well.
474 @c FIXME: Who knows what this "no retry action" crud from the DOS manual may
475 @c mean? It's optional; leave it out? ---pesch@cygnus.com, 25feb91
477 To give control of the PC to the Unix side of the serial line, type
478 the following at the DOS console:
485 (Later, if you wish to return control to the DOS console, you can use
486 the command @code{CTTY con}---but you must send it over the device that
487 had control, in our example over the @file{COM1} serial line).
489 From the Unix host, use a communications program such as @code{tip} or
490 @code{cu} to communicate with the PC; for example,
493 cu -s 9600 -l /dev/ttya
497 The @code{cu} options shown specify, respectively, the linespeed and the
498 serial port to use. If you use @code{tip} instead, your command line
499 may look something like the following:
506 Your system may define a different name where our example uses
507 @file{/dev/ttya} as the argument to @code{tip}. The communications
508 parameters, including which port to use, are associated with the
509 @code{tip} argument in the ``remote'' descriptions file---normally the
510 system table @file{/etc/remote}.
511 @c FIXME: What if anything needs doing to match the "n,8,1,none" part of
512 @c the DOS side's comms setup? cu can support -o (odd
513 @c parity), -e (even parity)---apparently no settings for no parity or
514 @c for character size. Taken from stty maybe...? John points out tip
515 @c can set these as internal variables, eg ~s parity=none; man stty
516 @c suggests that it *might* work to stty these options with stdin or
517 @c stdout redirected... ---pesch@cygnus.com, 25feb91
520 Using the @code{tip} or @code{cu} connection, change the DOS working
521 directory to the directory containing a copy of your 29K program, then
522 start the PC program @code{EBMON} (an EB29K control program supplied
523 with your board by AMD). You should see an initial display from
524 @code{EBMON} similar to the one that follows, ending with the
525 @code{EBMON} prompt @samp{#}---
530 G:\> CD \usr\joe\work29k
532 G:\USR\JOE\WORK29K> EBMON
533 Am29000 PC Coprocessor Board Monitor, version 3.0-18
534 Copyright 1990 Advanced Micro Devices, Inc.
535 Written by Gibbons and Associates, Inc.
537 Enter '?' or 'H' for help
539 PC Coprocessor Type = EB29K
541 Memory Base = 0xd0000
543 Data Memory Size = 2048KB
544 Available I-RAM Range = 0x8000 to 0x1fffff
545 Available D-RAM Range = 0x80002000 to 0x801fffff
548 Register Stack Size = 0x800
549 Memory Stack Size = 0x1800
552 Am29027 Available = No
553 Byte Write Available = Yes
558 Then exit the @code{cu} or @code{tip} program (done in the example by
559 typing @code{~.} at the @code{EBMON} prompt). @code{EBMON} will keep
560 running, ready for _GDBN__ to take over.
562 For this example, we've assumed what is probably the most convenient
563 way to make sure the same 29K program is on both the PC and the Unix
564 system: a PC/NFS connection that establishes ``drive @code{G:}'' on the
565 PC as a file system on the Unix host. If you do not have PC/NFS or
566 something similar connecting the two systems, you must arrange some
567 other way---perhaps floppy-disk transfer---of getting the 29K program
568 from the Unix system to the PC; _GDBN__ will @emph{not} download it over the
572 @subsubsection EB29K cross-debugging
574 Finally, @code{cd} to the directory containing an image of your 29K
575 program on the Unix system, and start _GDBN__---specifying as argument the
576 name of your 29K program:
583 Now you can use the @code{target} command:
586 target amd-eb /dev/ttya 9600 MYFOO
587 @c FIXME: test above 'target amd-eb' as spelled, with caps! caps are meant to
588 @c emphasize that this is the name as seen by DOS (since I think DOS is
589 @c single-minded about case of letters). ---pesch@cygnus.com, 25feb91
593 In this example, we've assumed your program is in a file called
594 @file{myfoo}. Note that the filename given as the last argument to
595 @code{target amd-eb} should be the name of the program as it appears to DOS.
596 In our example this is simply @code{MYFOO}, but in general it can include
597 a DOS path, and depending on your transfer mechanism may not resemble
598 the name on the Unix side.
600 At this point, you can set any breakpoints you wish; when you are ready
601 to see your program run on the 29K board, use the _GDBN__ command
604 To stop debugging the remote program, use the _GDBN__ @code{detach}
607 To return control of the PC to its console, use @code{tip} or @code{cu}
608 once again, after your _GDBN__ session has concluded, to attach to
609 @code{EBMON}. You can then type the command @code{q} to shut down
610 @code{EBMON}, returning control to the DOS command-line interpreter.
611 Type @code{CTTY con} to return command input to the main DOS console,
612 and type @kbd{~.} to leave @code{tip} or @code{cu}.
615 @subsubsection Remote Log
617 @cindex log file for EB29K
619 The @code{target amd-eb} command creates a file @file{eb.log} in the
620 current working directory, to help debug problems with the connection.
621 @file{eb.log} records all the output from @code{EBMON}, including echoes
622 of the commands sent to it. Running @samp{tail -f} on this file in
623 another window often helps to understand trouble with @code{EBMON}, or
624 unexpected events on the PC side of the connection.
629 @subsection _GDBN__ and VxWorks
632 _GDBN__ enables developers to spawn and debug tasks running on networked
633 VxWorks targets from a Unix host. Already-running tasks spawned from
634 the VxWorks shell can also be debugged. _GDBN__ uses code that runs on
635 both the UNIX host and on the VxWorks target. The program
636 @code{_GDBP__} is installed and executed on the UNIX host.
638 The following information on connecting to VxWorks was current when
639 this manual was produced; newer releases of VxWorks may use revised
642 The remote debugging interface (RDB) routines are installed and executed
643 on the VxWorks target. These routines are included in the VxWorks library
644 @file{rdb.a} and are incorporated into the system image when source-level
645 debugging is enabled in the VxWorks configuration.
648 If you wish, you can define @code{INCLUDE_RDB} in the VxWorks
649 configuration file @file{configAll.h} to include the RDB interface
650 routines and spawn the source debugging task @code{tRdbTask} when
651 VxWorks is booted. For more information on configuring and remaking
653 VxWorks, see the manufacturer's manual.
656 VxWorks, see the @cite{VxWorks Programmer's Guide}.
659 Once you have included the RDB interface in your VxWorks system image
660 and set your Unix execution search path to find _GDBN__, you are ready
661 to run _GDBN__. From your UNIX host, type:
667 _GDBN__ will come up showing the prompt:
674 * VxWorks connection:: Connecting to VxWorks
675 * VxWorks download:: VxWorks Download
676 * VxWorks attach:: Running Tasks
679 @node VxWorks connection
680 @subsubsection Connecting to VxWorks
682 The _GDBN__ command @code{target} lets you connect to a VxWorks target on the
683 network. To connect to a target whose host name is ``@code{tt}'', type:
686 (_GDBP__) target vxworks tt
689 _GDBN__ will display a message similar to the following:
692 Attaching remote machine across net... Success!
695 _GDBN__ will then attempt to read the symbol tables of any object modules
696 loaded into the VxWorks target since it was last booted. _GDBN__ locates
697 these files by searching the directories listed in the command search
698 path (@pxref{Environment, ,Your Program's Environment}); if it fails
699 to find an object file, it will display a message such as:
702 prog.o: No such file or directory.
705 This will cause the @code{target} command to abort. When this happens,
706 you should add the appropriate directory to the search path, with the
707 _GDBN__ command @code{path}, and execute the @code{target} command
710 @node VxWorks download
711 @subsubsection VxWorks Download
713 @cindex download to VxWorks
714 If you have connected to the VxWorks target and you want to debug an
715 object that has not yet been loaded, you can use the _GDBN__ @code{load}
716 command to download a file from UNIX to VxWorks incrementally. The
717 object file given as an argument to the @code{load} command is actually
718 opened twice: first by the VxWorks target in order to download the code,
719 then by _GDBN__ in order to read the symbol table. This can lead to
720 problems if the current working directories on the two systems differ.
721 It is simplest to set the working directory on both systems to the
722 directory in which the object file resides, and then to reference the
723 file by its name, without any path. Thus, to load a program
724 @file{prog.o}, residing in @file{wherever/vw/demo/rdb}, on VxWorks type:
727 -> cd "wherever/vw/demo/rdb"
733 (_GDBP__) cd wherever/vw/demo/rdb
734 (_GDBP__) load prog.o
737 _GDBN__ will display a response similar to the following:
740 Reading symbol data from wherever/vw/demo/rdb/prog.o... done.
743 You can also use the @code{load} command to reload an object module
744 after editing and recompiling the corresponding source file. Note that
745 this will cause _GDBN__ to delete all currently-defined breakpoints,
746 auto-displays, and convenience variables, and to clear the value
747 history. (This is necessary in order to preserve the integrity of
748 debugger data structures that reference the target system's symbol
752 @subsubsection Running Tasks
754 @cindex running VxWorks tasks
755 You can also attach to an existing task using the @code{attach} command as
759 (_GDBP__) attach @var{task}
763 where @var{task} is the VxWorks hexadecimal task ID. The task can be running
764 or suspended when you attach to it. If running, it will be suspended at
765 the time of attachment.
769 @node Hitachi H8/300 Remote
770 @subsection _GDBN__ and the Hitachi H8/300
771 _GDBN__ needs to know these things to talk to your H8/300:
775 that you want to use @samp{target hms}, the remote debugging
776 interface for the H8/300 (this is the default when
777 GDB is configured specifically for the H8/300);
780 what serial device connects your host to your H8/300 (the first serial
781 device available on your host is the default);
784 @c this is only for Unix hosts, not currently of interest.
786 what speed to use over the serial device.
791 @cindex serial device for H8/300
793 @c only for Unix hosts
794 Use the special @code{gdb83} command @samp{device @var{port}} if you
795 need to explicitly set the serial device. The default @var{port} is the
796 first available port on your host. This is only necessary on Unix
797 hosts, where it is typically something like @file{/dev/ttya}.
800 @cindex serial line speed for H8/300
801 @code{gdb83} has another special command to set the communications speed
802 for the H8/300: @samp{speed @var{bps}}. This command also is only used
803 from Unix hosts; on DOS hosts, set the line speed as usual from outside
804 GDB with the DOS @kbd{mode} command (for instance, @w{@samp{mode
805 com2:9600,n,8,1,p}} for a 9600 bps connection).
808 _GDBN__ depends on an auxiliary terminate-and-stay-resident program
809 called @code{asynctsr} to communicate with the H8/300 development board
810 through a PC serial port. You must also use the DOS @code{mode} command
811 to set up the serial port on the DOS side.
813 The following sample session illustrates the steps needed to start a
814 program under _GDBN__ control on your H8/300. The example uses a sample
815 H8/300 program called @file{t.x}.
817 First hook up your H8/300 development board. In this example, we use a
818 board attached to serial port @code{COM2}; if you use a different serial
819 port, substitute its name in the argument of the @code{mode} command.
820 When you call @code{asynctsr}, the auxiliary comms program used by the
821 degugger, you give it just the numeric part of the serial port's name;
822 for example, @samp{asyncstr 2} below runs @code{asyncstr} on
826 (eg-C:\H8300\TEST) mode com2:9600,n,8,1,p
828 Resident portion of MODE loaded
830 COM2: 9600, n, 8, 1, p
832 (eg-C:\H8300\TEST) asynctsr 2
836 @emph{Warning:} We have noticed a bug in PC-NFS that conflicts with
837 @code{asynctsr}. If you also run PC-NFS on your DOS host, you may need to
838 disable it, or even boot without it, to use @code{asynctsr} to control
842 Now that serial communications are set up, and the H8/300 is connected,
843 you can start up _GDBN__. Call @code{_GDBP__} with the name of your
844 program as the argument. @code{_GDBP__} prompts you, as usual, with the
845 prompt @samp{(_GDBP__)}. Use two special commands to begin your debugging
846 session: @samp{target hms} to specify cross-debugging to the Hitachi board,
847 and the @code{load} command to download your program to the board.
848 @code{load} displays the names of the
849 program's sections, and a @samp{*} for each 2K of data downloaded. (If
850 you want to refresh _GDBN__ data on symbols or on the executable file
851 without downloading, use the _GDBN__ commands @code{file} or
852 @code{symbol-file}. These commands, and @code{load} itself, are
853 described in @ref{Files,,Commands to Specify Files}.)
856 (eg-C:\H8300\TEST) _GDBP__ t.x
857 GDB is free software and you are welcome to distribute copies
858 of it under certain conditions; type "show copying" to see
860 There is absolutely no warranty for GDB; type "show warranty"
862 GDB _GDB_VN__, Copyright 1992 Free Software Foundation, Inc...
864 Connected to remote H8/300 HMS system.
866 .text : 0x8000 .. 0xabde ***********
867 .data : 0xabde .. 0xad30 *
868 .stack : 0xf000 .. 0xf014 *
871 At this point, you're ready to run or debug your program. From here on,
872 you can use all the usual _GDBN__ commands. The @code{break} command
873 sets breakpoints; the @code{run} command starts your program;
874 @code{print} or @code{x} display data; the @code{continue} command
875 resumes execution after stopping at a breakpoint. You can use the
876 @code{help} command at any time to find out more about _GDBN__ commands.
878 Remember, however, that @emph{operating system} facilities aren't
879 available on your H8/300; for example, if your program hangs, you can't
880 send an interrupt---but you can press the @sc{reset} switch!
882 Use the @sc{reset} button on the H8/300 board
885 to interrupt your program (don't use @kbd{ctl-C} on the DOS host---it has
886 no way to pass an interrupt signal to the H8/300); and
889 to return to the _GDBN__ command prompt after your program finishes
890 normally. The communications protocol provides no other way for _GDBN__
891 to detect program completion.
894 In either case, _GDBN__ will see the effect of a @sc{reset} on the
895 H8/300 board as a ``normal exit'' of your program.