| 1 |
578 |
markom |
.\" t
|
| 2 |
|
|
.\" The above line must be present to tell man to process through tbl.
|
| 3 |
|
|
.\" @(#)dosudi.5 2.2, AMD
|
| 4 |
|
|
.\"Copyright (c) 1989, 1990, 1991 by Advanced Micro Devices, Inc.
|
| 5 |
|
|
.\"All rights reserved. No part of this publication may be reproduced,
|
| 6 |
|
|
.\"stored in a retrieval system, or transmitted in any form or by any
|
| 7 |
|
|
.\"means, electronic, mechanical, photocopying, recording or otherwise,
|
| 8 |
|
|
.\"without the prior written permission of Advanced Micro Devices, Inc.
|
| 9 |
|
|
.\"
|
| 10 |
|
|
.\"You must change the date in these files for a release!
|
| 11 |
|
|
.\"The commands used to generate output from this input are:
|
| 12 |
|
|
.\" tbl udi.1 | nroff -man - > filename (Goes to a unix file)
|
| 13 |
|
|
.\" tbl udi.1 | ptroff -man - (Goes to PostScript printer)
|
| 14 |
|
|
.\"
|
| 15 |
|
|
.TH UDI 5 "27 Jan. 1992" "UDI Configuration Files for DOS hosts"
|
| 16 |
|
|
.UC 4
|
| 17 |
|
|
.SH NAME
|
| 18 |
|
|
\fBudi\fP \- UDI Configuration Files for DOS hosts.
|
| 19 |
|
|
.sp
|
| 20 |
|
|
.sp
|
| 21 |
|
|
.SH DESCRIPTION
|
| 22 |
|
|
A UDI conformant Debugger Front End (DFE) specifies the Target
|
| 23 |
|
|
Interface Process (TIP) that it wishes to connect to and
|
| 24 |
|
|
the options that it wishes to pass to that TIP by referencing
|
| 25 |
|
|
a configuration in the "UDI configuration file".
|
| 26 |
|
|
This man page explains the format of the UDI Configuration file
|
| 27 |
|
|
for DOS hosts.
|
| 28 |
|
|
.sp
|
| 29 |
|
|
The search rules that the DFE uses to locate the UDI Configuration
|
| 30 |
|
|
file are:
|
| 31 |
|
|
.IP
|
| 32 |
|
|
the complete filename specified by the environment variable, UDICONF.
|
| 33 |
|
|
.IP
|
| 34 |
|
|
the file udiconfs.txt in the current directory.
|
| 35 |
|
|
.IP
|
| 36 |
|
|
the file udiconfs.txt in each of the directories specified by the PATH environment
|
| 37 |
|
|
variable.
|
| 38 |
|
|
.sp
|
| 39 |
|
|
.LP
|
| 40 |
|
|
Each line of the udiconfs.txt file consists of the following fields:
|
| 41 |
|
|
.IP
|
| 42 |
|
|
tip_config_name tip_executable [tip_options]
|
| 43 |
|
|
.TP 10
|
| 44 |
|
|
.I tip_config_name
|
| 45 |
|
|
An arbitrary name which the DFE will use to refer to this configuration.
|
| 46 |
|
|
Each line in the udiconfs.txt file must have a different tip_config_name field.
|
| 47 |
|
|
.TP
|
| 48 |
|
|
.I tip_executable
|
| 49 |
|
|
The name of the TIP executable file. The DFE will
|
| 50 |
|
|
use the tip_executable filename to spawn
|
| 51 |
|
|
the TIP if the TIP is not already running. If a full pathname is
|
| 52 |
|
|
not specified, the PATH environment variable
|
| 53 |
|
|
is used to locate the executable file.
|
| 54 |
|
|
.sp
|
| 55 |
|
|
.TP
|
| 56 |
|
|
.I tip_options
|
| 57 |
|
|
The rest of the line after the tip_executable name is passed
|
| 58 |
|
|
to the TIP at connect time.
|
| 59 |
|
|
.sp
|
| 60 |
|
|
.SH EXAMPLES OF UDI CONFIGURATION FILE ENTRIES
|
| 61 |
|
|
.sp
|
| 62 |
|
|
The following is an exampleare examples of entries in the UDI configuration
|
| 63 |
|
|
file for DOS hosts.
|
| 64 |
|
|
.sp
|
| 65 |
|
|
\fB iss050 isstip.exe -29050 -r osboot \fR
|
| 66 |
|
|
.sp
|
| 67 |
|
|
The above entry associates the TIP configuration name "iss050" with the
|
| 68 |
|
|
\fBisstip.exe\fR executable with the parameters
|
| 69 |
|
|
"-29050 -r osboot" being passed to isstip.exe
|
| 70 |
|
|
when it is invoked. If isstip.exe is not already running and
|
| 71 |
|
|
needs to be spawned, the PATH environment variable will be used to
|
| 72 |
|
|
locate the file isstip.exe.
|
| 73 |
|
|
.sp
|
| 74 |
|
|
.SH TRADEMARKS
|
| 75 |
|
|
AMD is a registered trademark of Advanced Micro Devices, Inc.
|
| 76 |
|
|
MiniMON29K, 29K, Am29000, Am29005, Am29030, Am29035, Am29200,
|
| 77 |
|
|
and Am29050 are trademarks of Advanced Micro Devices, Inc.
|
