OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [insight/] [utils/] [amd-udi/] [udi/] [dosudi.cat] - Blame information for rev 1765

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 578 markom
 
2
 
3
 
4
UDI(5)                    FILE FORMATS                     UDI(5)
5
 
6
 
7
 
8
NAME
9
     udi - UDI Configuration Files for DOS hosts.
10
 
11
 
12
 
13
DESCRIPTION
14
     A UDI conformant Debugger Front End (DFE) specifies the Tar-
15
     get Interface Process (TIP) that it wishes to connect to and
16
     the options that it wishes to pass to that TIP by  referenc-
17
     ing  a  configuration in the "UDI configuration file".  This
18
     man page explains the format of the UDI  Configuration  file
19
     for DOS hosts.
20
 
21
     The search rules that the DFE uses to locate the UDI  Confi-
22
     guration file are:
23
 
24
          the complete  filename  specified  by  the  environment
25
          variable, UDICONF.
26
 
27
          the file udiconfs.txt in the current directory.
28
 
29
          the file udiconfs.txt in each of the directories speci-
30
          fied by the PATH environment variable.
31
 
32
 
33
     Each line of the udi_soc  file  consists  of  the  following
34
     fields:
35
 
36
          tip_config_name  tip_executable  [tip_options]
37
 
38
     tip_config_name
39
               An arbitrary name which the DFE will use to  refer
40
               to  this  configuration.  Each line in the udi_soc
41
               file must have a different tip_config_name field.
42
 
43
     tip_executable
44
               The name of the TIP executable file.  The DFE will
45
               use  the  tip_executable filename to spawn the TIP
46
               if the TIP is not already running. If a full path-
47
               name  is not specified, the PATH environment vari-
48
               able is used to locate the executable file.
49
 
50
 
51
     tip_options
52
               The rest of the line after the tip_executable name
53
               is passed to the TIP at connect time.
54
 
55
 
56
EXAMPLES OF UDI CONFIGURATION FILE ENTRIES
57
     The following is an exampleare examples of  entries  in  the
58
     UDI configuration file for DOS hosts.
59
 
60
 
61
 
62
 
63
UDI Configuration Files for DOS hostsLast change: 27 Jan. 1992                   1
64
 
65
 
66
 
67
 
68
 
69
 
70
UDI(5)                    FILE FORMATS                     UDI(5)
71
 
72
 
73
 
74
      iss050  isstip.exe -29050 -r osboot
75
 
76
     The  above  entry  associates  the  TIP  configuration  name
77
     "iss050"  with the isstip.exe executable with the parameters
78
     "-29050 -r osboot" being passed to  isstip.exe  when  it  is
79
     invoked.   If isstip.exe is not already running and needs to
80
     be spawned, the PATH environment variable will  be  used  to
81
     locate the file isstip.exe.
82
 
83
 
84
TRADEMARKS
85
     AMD is a registered trademark  of  Advanced  Micro  Devices,
86
     Inc.   MiniMON29K,  29K, Am29000, Am29005, Am29030, Am29035,
87
     Am29200, and Am29050 are trademarks of Advanced  Micro  Dev-
88
     ices, Inc.
89
 
90
 
91
 
92
 
93
 
94
 
95
 
96
 
97
 
98
 
99
 
100
 
101
 
102
 
103
 
104
 
105
 
106
 
107
 
108
 
109
 
110
 
111
 
112
 
113
 
114
 
115
 
116
 
117
 
118
 
119
 
120
 
121
 
122
 
123
 
124
 
125
 
126
 
127
 
128
 
129
UDI Configuration Files for DOS hosts   Last change: 27 Jan. 1992          2
130
 
131
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.