Commit | Line | Data |
---|---|---|
920dae64 AT |
1 | .TH simulate 1 "Sept 18, 2007" "" "SAM system simulator" |
2 | .SH NAME | |
3 | simulate - run SAM with a particular system configuration | |
4 | .SH SYNOPSIS | |
5 | simulate [-p | |
6 | .I processor] | |
7 | -c | |
8 | .I config | |
9 | [-w | |
10 | .I workers] | |
11 | [-sav] | |
12 | [-f | |
13 | .I cmd_file] | |
14 | [-l | |
15 | .I log_file] | |
16 | [-I | |
17 | .I system] | |
18 | [-C | |
19 | .I system] | |
20 | [-L | |
21 | .I image] | |
22 | [-D | |
23 | .I define] | |
24 | [-V | |
25 | .I veracity-script -b] | |
26 | ||
27 | simulate [-p | |
28 | .I processor] | |
29 | -c | |
30 | .I config | |
31 | [-w | |
32 | .I workers] | |
33 | [-ra] | |
34 | [-f | |
35 | .I cmd_file] | |
36 | [-l | |
37 | .I log_file] | |
38 | [-I | |
39 | .I system] | |
40 | [-C | |
41 | .I system] | |
42 | [-L | |
43 | .I image] | |
44 | [-D | |
45 | .I define] | |
46 | [-V | |
47 | .I veracity-script -b] | |
48 | ||
49 | simulate [-p | |
50 | .I processor] | |
51 | -c | |
52 | .I config | |
53 | -d | |
54 | [-w | |
55 | .I workers] | |
56 | [-f | |
57 | .I cmd_file] | |
58 | [-l | |
59 | .I log_file] | |
60 | [-I | |
61 | .I system] | |
62 | [-C | |
63 | .I system] | |
64 | [-L | |
65 | .I image] | |
66 | [-D | |
67 | .I define] | |
68 | ||
69 | simulate -p | |
70 | .I processor | |
71 | -R | |
72 | .I chkpnt | |
73 | [-f | |
74 | .I cmd_file] | |
75 | [-I | |
76 | .I system] | |
77 | [-D | |
78 | .I define] | |
79 | [-l | |
80 | .I log_file] | |
81 | ||
82 | ||
83 | .SH DESCRIPTION | |
84 | .PP | |
85 | Simulate is a wizard script that is used to run SAM | |
86 | with a SAM configuration (rc-file) that was generated | |
87 | on the fly. The script generates the file sam.rc. | |
88 | After generating the file it invokes sam -c sam.rc | |
89 | ||
90 | The simulate wizard expects that the collection of binaries | |
91 | needed to run RUST or Solaris is present in the current | |
92 | working directory. Simulate expects a known collection | |
93 | of filenames to be present there. Use the getrust(1) and | |
94 | getsolaris(1) wizards to get a working starting set of files. | |
95 | ||
96 | Simulate is best used in conjunction with the getrust(1) | |
97 | and getsolaris(1) wizards. The get wizards getrust(1) | |
98 | and getsolaris(1) create a directory outside the current | |
99 | working directory. Change directory into that created | |
100 | directory and invoke the simulate wizard there. | |
101 | ||
102 | The simulate wizard is not a one for all solution. The | |
103 | sam.rc file that it generates can always be taken and | |
104 | modified for a special need. After the modification, | |
105 | invoke SAM directly: sam -c modifiedsam.rc, see sam(1). | |
106 | ||
107 | .SH OPTIONS | |
108 | .TP | |
109 | .B -h | |
110 | Help | |
111 | .TP | |
112 | .BI -p " processor" | |
113 | Be a wizard for | |
114 | .I processor | |
115 | and create a sam.rc file that resembles a system for this | |
116 | processor. | |
117 | The | |
118 | .I processor | |
119 | can be one of: n2, depending on the SAM release | |
120 | that is being used. | |
121 | .TP | |
122 | .BI -c " config" | |
123 | .I config | |
124 | = 1c1t 1up 1c2t 1g2p 1g4p 1g16p 1g32p 8c8t ... | |
125 | .br | |
126 | The configuration is a machine description. Usually for | |
127 | Solaris and RUST you will find | |
128 | .I config-md.bin | |
129 | and | |
130 | .I config-hv.bin | |
131 | files. simulate will err and exit if it can't find the | |
132 | specified configuration. | |
133 | .TP | |
134 | .BI -w " workers" | |
135 | .I workers | |
136 | = 1 2 3 4 ... | |
137 | .br | |
138 | The number of workers (worker-threads) to create. A number >1 causes | |
139 | the simulator to run MP on MP if a configuration with more | |
140 | then one strand is used. | |
141 | .TP | |
142 | .B -s | |
143 | Boot Solaris. See getsolaris(1) on how to get Solaris binaries. | |
144 | The -s option cannot be used in conjunction with the | |
145 | -r, -d, or -R options. | |
146 | .TP | |
147 | .B -r | |
148 | Run RUST. See getrust(1) on how to get RUST binaries. | |
149 | The -r option cannot be used in conjunction with the | |
150 | -s, -d, or -R options. | |
151 | .TP | |
152 | .B -d | |
153 | Run a diag. The -d option cannot be used in conjunction | |
154 | with the -s, -r, or -R options. | |
155 | .TP | |
156 | .B -a | |
157 | Auto boot OBP followed by Solaris or RUST. This option | |
158 | causes the file nvram1-auto to be loaded instead of the | |
159 | file nvram1. In non autoboot mode, the user is expected to know | |
160 | what to type at the OBP ok prompt. For solaris this | |
161 | usually is | |
162 | .I boot disk | |
163 | , for RUST this usually is | |
164 | .I go. | |
165 | The -a option is only compatible with -r or -s. | |
166 | .TP | |
167 | .B -v | |
168 | Verbose boot Solaris. This option uses a Solaris | |
169 | disk image (disk1.verbose) that has a modified | |
170 | /etc/system file. The line | |
171 | .I set moddebug=0x80000000 | |
172 | was added. The -v option is only compatible with -s. | |
173 | .TP | |
174 | .BI -I " system" | |
175 | This option is for including extra rc files in the generated | |
176 | sam.rc file. This is useful for example to extend say a bare bone | |
177 | N2 system (Huron) with devices connected to the pcie bus. | |
178 | .TP | |
179 | .BI -C " system" | |
180 | This option is for advanced users that want to modify the | |
181 | system setup. The default system setup | |
182 | .IR processor .rc | |
183 | (here | |
184 | .I processor | |
185 | is the same as provided with the -p option) | |
186 | is in the etc directory of the release. | |
187 | .TP | |
188 | .BI -R " chkpnt" | |
189 | Start SAM from a dump that is in | |
190 | .I chkpnt. | |
191 | A dump is generated at the SAM prompt with the | |
192 | .BI dump " chkpnt" | |
193 | command. | |
194 | The -R option cannot be used in conjunction with the | |
195 | -s, -r, or -d options. | |
196 | .TP | |
197 | .BI -L " image" | |
198 | The | |
199 | .I image | |
200 | argument can be of the form | |
201 | .I filename,address | |
202 | which means load binary file | |
203 | .I filename | |
204 | into memory at | |
205 | .I address. | |
206 | If there is no comma character in the | |
207 | .I image | |
208 | argument, or image has a trailing comma, then | |
209 | .I image | |
210 | is a file that is expected to be in the cpu and system | |
211 | verilog memory image format. This file-format is usually | |
212 | produced by the Midas tool. For the -s and -r option the | |
213 | .I image | |
214 | files are loaded after the standard set of files that are loaded | |
215 | in these run modes. | |
216 | The -L can be used to override memory with user specific | |
217 | values. | |
218 | The simulate wizard accepts multiple -L options. The | |
219 | .I image | |
220 | files are loaded into memory in the order they appear on | |
221 | the command line. | |
222 | .TP | |
223 | .BI -D " define" | |
224 | This option is for advanced users that want to tightly control | |
225 | the system setup. The -D option passes | |
226 | .I define | |
227 | on to the m4 tool that preprocesses the system rc file before it | |
228 | is added to sam.rc. A common | |
229 | .I define | |
230 | is | |
231 | .I -Dpop= | |
232 | which disables popping the xterm when used in conjunction with | |
233 | the -r or -s option. | |
234 | .TP | |
235 | .BI -V " veracity-script" | |
236 | Runs veracity with | |
237 | .I veracity-script | |
238 | as an argument. simulate will create a veracity script to start up | |
239 | RUST or Solaris, depending on whether | |
240 | .B -r | |
241 | or | |
242 | .B -s | |
243 | is present. The start-up script will be called | |
244 | .B start_rust.ver | |
245 | or | |
246 | .B start_solaris.ver | |
247 | respectively which can be included by | |
248 | .I veracity-script | |
249 | to perform standard initialization. | |
250 | .TP | |
251 | .B -b | |
252 | Used with the | |
253 | .B -V | |
254 | flag, this runs veracity in batch mode, directing all serial console | |
255 | output to | |
256 | .B stdout. | |
257 | .TP | |
258 | .BI -f " cmd_file" | |
259 | Run SAM UI commands from file <cmd_file> before returning to UI prompt. | |
260 | .TP | |
261 | .BI -l " log_file" | |
262 | Turn on output logging to file <log_file>. | |
263 | .SH EXAMPLES | |
264 | .LP | |
265 | The example processor here is n2. The available processor depend | |
266 | on the SAM release. | |
267 | .LP | |
268 | Run Solaris on one strand, autoboot, and in verbose mode. | |
269 | .IP | |
270 | .B "simulate -p n2 -c 1c1t -s -a -v" | |
271 | .LP | |
272 | Run Solaris on two strands, autoboot and use two workers. | |
273 | .IP | |
274 | .B "simulate -p n2 -c 1c2t -w2 -s -a" | |
275 | .LP | |
276 | Run RUST on one strand, autoboot. | |
277 | .IP | |
278 | .B "simulate -p n2 -c 1c1t -r -a" | |
279 | .LP | |
280 | Run RUST on two strands, autoboot and use two workers. | |
281 | .IP | |
282 | .B "simulate -p n2 -c 1c2t -w 2 -r -a" | |
283 | .LP | |
284 | Run Solaris on one strand, loading one extra binary file into memory. | |
285 | .IP | |
286 | .B "simulate -pn2 -c1c1t -sa -Lmyreset.bin,0xff0000000" | |
287 | .LP | |
288 | Run a diag on one strand, loading one verilog memory image file into memory. | |
289 | .IP | |
290 | .B "simulate -pn2 -c1c1t -d -Lmem.image" | |
291 | .LP | |
292 | Run Solaris and do not pop up the console xterms | |
293 | .IP | |
294 | .B "simulate -pn2 -c1c2t -w2 -sa -Dpop=" | |
295 | .SH BUGS | |
296 | .PP | |
297 | The config -c option in combination with -s or -r option is at the | |
298 | mercy of the available machine description files. | |
299 | .SH SEE ALSO | |
300 | .BR getsolaris (1), | |
301 | .BR sam (1), | |
302 | .BR m4 (1) | |
303 | .SH AUTHORS | |
304 | .nf | |
305 | Wizard and manual page by SUN | |
306 | .f |