OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove refs to UDI for now.

Browse Source
This commit is contained in:
Stu Grossman 1992-10-23 08:50:19 +00:00
parent 5f5be54ce8
commit 6446b7a4b2
3 changed files with 0 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
gdb/doc/gdb.texinfo
View File

@ -6583,13 +6583,6 @@ Remote PC-resident AMD EB29K board, attached over serial lines.
name of the program to be debugged, as it appears to DOS on the PC.
@xref{EB29K Remote, ,_GDBN__ with a Remote EB29K}.
@item target udi
@kindex target udi
@cindex UDI interface to 29K
@cindex AMD UDI-29K
Remote AMD 29K board, attached over the AMD ``Universal Debug
Interface'', a protocol based on TCP/IP. @xref{UDI29K Remote,,_GDBN__
and the UDI 29K protocol}.
_fi__(_AMD29K__)
_if__(_H8__)
@item target hms

1
gdb/doc/gdbinv-m.m4.in
View File

@ -10,7 +10,6 @@ _if__(_I960__)
_fi__(_I960__)
_if__(_AMD29K__)
* EB29K Remote:: _GDBN__ with a remote EB29K
* UDI29K Remote:: _GDBN__ and the UDI 29K protocol
_fi__(_AMD29K__)
_if__(_VXWORKS__)
* VxWorks Remote:: _GDBN__ and VxWorks

18
gdb/doc/gdbinv-s.m4.in
View File

@ -628,24 +628,6 @@ of the commands sent to it. Running @samp{tail -f} on this file in
another window often helps to understand trouble with @code{EBMON}, or
unexpected events on the PC side of the connection.
@node UDI29K Remote
@subsection _GDBN__ and the UDI 29K protocol
If your 29K development system supports the UDI (``Universal Debug
Interface'') protocol, using _GDBN__ is almost transparent. UDI is a
TCP/IP based protocol. On some 29K development systens that do not
support TCP/IP directly, however, the manufacturer supplies an interface
adapter daemon, which translates UDI to whatever communications
interface---typically a serial port---is available.
Please see the manufacturer's documentation for your 29K system for how
to set up the UDI connection for your hardware.
Once the UDI connection is established, use @samp{target udi} from _GDBN__
to start using it. All the usual facilities of _GDBN__ are immediately
available: use @code{load} to get your program to the board,
@code{breakpoint} to say where to stop, @code{run} to start the program,
and so on.
_fi__(_AMD29K__)
_if__(_ST2000__)