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

Subversion Repositories openrisc_me

[/] [openrisc/] [trunk/] [gnu-src/] [gdb-6.8/] [gdb/] [doc/] [or1k.info] - Blame information for rev 157

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 131 jeremybenn
This is or1k.info, produced by makeinfo version 4.13 from
2
../.././gdb/doc/or1k.texinfo.
3
 
4
INFO-DIR-SECTION Software development
5
START-INFO-DIR-ENTRY
6
* Gdb for OpenRISC 1000: (gdb for Or1K).   The GNU debugger for OpenRISC 1000.
7
END-INFO-DIR-ENTRY
8
 
9
   This file documents the GNU debugger GDB when used with OpenRISC
10
1000 processors.
11
 
12
   This is the Second Edition, of `Debugging the OpenRISC 1000 GDB' for
13
GDB Version 6.8.
14
 
15
   Copyright (C) 2008 Embecosm Limited
16
 
17
   Permission is granted to copy, distribute and/or modify this document
18
under the terms of the GNU Free Documentation License, Version 3 or any
19
later version published by the Free Software Foundation; with the
20
Front-Cover Texts being "Debugging the OpenRISC 1000 with GDB by Jeremy
21
Bennett" and with the Back-Cover Texts being "You are free to copy and
22
modify this Manual."
23
 
24

25
File: or1k.info,  Node: Top,  Next: Summary,  Prev: (dir),  Up: (dir)
26
 
27
Debugging the OpenRISC 1000 with GDB
28
************************************
29
 
30
This file describes GDB, the GNU symbolic debugger for use with the
31
OpenRISC 1000 processor architecture.
32
 
33
   This is the Second Edition, for GDB Version 6.8.
34
 
35
   Copyright (C) 2008 Embecosm Limited
36
 
37
* Menu:
38
 
39
* Summary::                         Summary of GDB with OpenRISC 1000
40
* Connecting to the Target::        Connecting to an OpenRISC 1000 Target
41
* OpenRISC 1000 Specific Commands:: Commands just for the OpenRISC 1000
42
* OpenRISC 1000 Example::           A small example
43
* OpenRISC 1000 Limitations::       Known problems
44
 
45
* Copying::                         GNU General Public License says
46
                                    how you can copy and share GDB
47
* GNU Free Documentation License::  The license for this documentation
48
* Index::                           Index
49
 
50

51
File: or1k.info,  Node: Summary,  Next: Connecting to the Target,  Prev: Top,  Up: Top
52
 
53
Summary of GDB with OpenRISC 1000
54
*********************************
55
 
56
GDB is described well in its user manual, "Debugging with GDB: The GNU
57
Source-Level Debugger".
58
 
59
   This manual describes how to use GDB to debug C programs cross
60
compiled for and running on processors using the OpenRISC 1000
61
architecture. In general GDB does not run on the actual target, but on
62
a separate host processor. It communicates with the target via the GDB
63
"Remote Serial Protocol" (RSP).
64
 
65
   For backwards compatibility, GDB for OpenRISC also supports the
66
legacy custom remote protocol, which drives the JTAG interface on the
67
OpenRISC 1000.  This is provided by adding a special target, "jtag" to
68
GDB, allowing the debugger to connect via the JTAG interface. *Note
69
Connecting to the Target: Connecting to the Target.
70
 
71
   In addition the info command is extended to allow inspection of
72
OpenRISC 1000 Special Purpose registers, and a new command "spr" is
73
added to set the value of a Special Purpose Register. *Note OpenRISC
74
1000 Specific Commands: OpenRISC 1000 Specific Commands.
75
 
76
   All the normal GDB commands should work, although hardware
77
watchpoints are not tested at present. The `info registers' command
78
will show the 32 general purpose registers, while the `info registers
79
all' command will add the program counter, supervision register and
80
exception program counter register.
81
 
82
   For those who like their debugging graphical, the `gdbtui' command is
83
available (typically as `or32-uclinux-gdbtui'). GDB for OpenRISC 1000
84
can also be run under `ddd' as follows:
85
 
86
     `ddd --debugger=or32-uclinux-gdb --gdb'
87
 
88
* Menu:
89
 
90
* Contributors::                Contributors to GDB for the OpenRISC 1000
91
 
92

93
File: or1k.info,  Node: Contributors,  Up: Summary
94
 
95
Contributors to GDB for the OpenRISC 1000
96
=========================================
97
 
98
The pantheon of contributors to GDB over the years is recorded in the
99
main user manual, `Debugging with GDB: The GNU Source-Level Debugger".
100
 
101
   There is no official history of contributors to the OpenRISC 1000
102
version. However the current author believes the original GDB 5.0 and
103
5.3 ports were the work of:
104
 
105
   * Ivan Guzvinec and Johan Rydverg at OpenCores, who wrote the Binary
106
     File Descriptor library;
107
 
108
   * Alessandro Forin at Carnegie-Mellon University and Per Bothner at
109
     the University of Wisconsin who wrote the main GDB interface; and
110
 
111
   * Mark Mlinar at Cygnus Support and Chris Ziomkowski at ASICS.ws,who
112
     wrote the OpenRISC JTAG interface.
113
 
114
   The port to GDB 6.8 is the work of Jeremy Bennett of Embecosm
115
Limited (jeremy.bennett@embecosm.com).
116
 
117
     Plea: If you know of anyone who has been omitted from this list,
118
     please email the current author, so the omission can be corrected,
119
     and credit given where it is due.
120
 
121

122
File: or1k.info,  Node: Connecting to the Target,  Next: OpenRISC 1000 Specific Commands,  Prev: Summary,  Up: Top
123
 
124
1 Connecting to an OpenRISC 1000 Target
125
***************************************
126
 
127
There are two ways to connect to an OpenRISC 1000 target with GDB.
128
 
129
  1. To hardware directly connected via a JP1 header linked to the
130
     parallel port. This uses the GDB command `target jtag'.
131
 
132
  2. Via a TCP/IP socket to a machine which has the hardware connected,
133
     or is running the architectural simulator using the standard GDB
134
     "Remote Serial Protocol". This uses the GDB commands `target
135
     remote' or `target extended-remote'.
136
 
137
  3. Via a TCP/IP socket to a machine which has the hardware connected,
138
     or is running the architectural simulator using the custom
139
     OpenRISC 1000 Remote JTAG protocol. This uses the GDB command
140
     `target jtag'.
141
 
142
          Note: This connection mechanism is deprecated. It remains for
143
          backward compatibility only.
144
 
145
 
146
     Caution: If used with version 0.2.0 of the architectural
147
     simulator, Or1ksim, GDB version 6.8 requires a patch to be applied
148
     to the architectural simulator. This should be available on the
149
     OpenCores website, or contact the author directly. Only the legacy
150
     OpenRISC 1000 Remote JTAG Protocol interface is available for this
151
     version of the architectural simualtor.
152
 
153
     The user is strongly recommended to use Or1ksim 0.3.0 or later,
154
     since this interfaces directly to GDB using the "Remote Serial
155
     Protocol".
156
 
157
* Menu:
158
 
159
* Direct JTAG Connection::            Direct connection via a JTAG JP1
160
                                      interface
161
* Remote Serial Protocol Connection:: Connection via the GDB Remote
162
                                      Serial Protocol Interface
163
* Remote JTAG Connection::            Connection via the OpenRISC 1000 Remote
164
                                      JTAG Interface
165
 
166

167
File: or1k.info,  Node: Direct JTAG Connection,  Next: Remote Serial Protocol Connection,  Up: Connecting to the Target
168
 
169
1.1 Direct connection via a JTAG JP1 Interface
170
==============================================
171
 
172
In this case the the device to which the JP1 header is connected must be
173
specifed to the `target jtag' command. Typically that will be the
174
parallel printer port, so the command would be:
175
 
176
     `target jtag /dev/lp'
177
 
178
     Caution: The current author is not aware of anyone using the JP1
179
     interface. As a result this code has not been tested in the port to
180
     GDB version 6.8. Modern hardware connections are usually via
181
     interfaces such as USB, for which the OpenRISC Remote Interface
182
     can be used (*note Remote JTAG Connection: Remote JTAG
183
     Connection.).
184
 
185

186
File: or1k.info,  Node: Remote Serial Protocol Connection,  Next: Remote JTAG Connection,  Prev: Direct JTAG Connection,  Up: Connecting to the Target
187
 
188
1.2 Connection via the GDB Remote Serial Protocol
189
=================================================
190
 
191
The usual mode of operation is through the GDB "Remote Serial Protocol"
192
(RSP). This communicates to the target through a TCP/IP socket. The
193
target must then implement the server side of the interface to drive
194
either physical hardware (for example through a USB/JTAG connector) or a
195
simulation of the hardware (such as the OpenRISC Architectural
196
Simulator).
197
 
198
   Although referred to as a _remote_ interface, the target may actually
199
be on the same machine, just running in a separate process, with its own
200
terminal window.
201
 
202
   For example, to connect to the OpenRISC 1000 Architectural
203
simulator, which is running on machine "thomas" and has been configured
204
to talk to GDB on port 51000, the following command would be used:
205
 
206
     `target remote thomas:51000'
207
 
208
   The target machine is specified as the machine name and port number.
209
If the architectural simulator was running on the same machine, its
210
name may be omitted, thus:
211
 
212
     `target remote :51000'
213
 
214

215
File: or1k.info,  Node: Remote JTAG Connection,  Prev: Remote Serial Protocol Connection,  Up: Connecting to the Target
216
 
217
1.3 Connection via the OpenRISC 1000 Remote JTAG Interface
218
==========================================================
219
 
220
Historically, GDB communicated with remote OpenRISC 1000 targets using
221
a customer protocol, the "OpenRISC 1000 Remote JTAG Interface".
222
 
223
   This protocol is maintained for backwards compatibility, but is now
224
deprecated. It communicates to the target through a TCP/IP socket. The
225
target must then implement the client side of the interface to drive
226
either physical hardware (for example through a USB/JTAG connector) or
227
a simulation of the hardware (such as the OpenRISC Architectural
228
Simulator).
229
 
230
   Although referred to as the _remote_ interface, the target may
231
actually be on the same machine, just running in a separate process,
232
with its own terminal window.
233
 
234
   For example, to connect to the OpenRISC 1000 Architectural
235
simulator, which is running on machine "thomas" and has been configured
236
to talk to GDB on port 50000, I could use the command:
237
 
238
     `target jtag jtag://thomas:50000'
239
 
240
   The target machine is specified after the jtag:// and separated from
241
the target port by a colon. If the architectural simulator was running
242
on the same machine, just locahost would suffice as the machine name,
243
thus:
244
 
245
     `target jtag jtag://localhost:50000'
246
 
247
   Unfortunately there are now two different flavours of the JTAG
248
interface used with OpenRISC 1000. The original version was created for
249
use with the OpenRISC 1000 System-on-Chip, ORPSoC. A new (smaller and
250
simpler) JTAG interface was developed by Igor Mohor in 2004, which is
251
used on some designs.
252
 
253
   The default behavior of GDB is to use the original ORPSoC version of
254
the interface for backwards compatibility. GDB can use the Igor Mohor
255
version by specifying for example:
256
 
257
     `target jtag jtag_mohor://localhost:50000'
258
 
259
   This interface is only available with remote connections using the
260
legacy OpenRISC 1000 Remote JTAG Protocol (deprecated). The direct JP1
261
interface can support only the ORPSoC version of JTAG.
262
 
263
   The recommended approach is to use the GDB "Remote Serial Protocol"
264
which interfaces directly to the simulator, and is independent of the
265
JTAG implementation used.
266
 
267
   For completeness
268
 
269
     `target jtag jtag_orpsoc://localhost:50000'
270
 
271
   is provided as a synonym for:
272
 
273
     `target jtag jtag://localhost:50000'
274
 
275
   By default, establishing a connection _does not_ reset the target.
276
This allows debugging to resume a partially complete program on
277
connection. If a reset is required, the keyworkd `RESET' (case
278
insensitive) may be added at the end of the `target' command. For
279
example:
280
 
281
     `target jtag jtag://localhost:50000 reset'
282
 
283
     Warning: The OpenRISC remote JTAG interface is not particularly
284
     robust. In particular dropping and reconnecting sessions does not
285
     seem to work well. This was a key factor in its replacement by the
286
     generic GDB Remote Serial Interface.
287
 
288

289
File: or1k.info,  Node: OpenRISC 1000 Specific Commands,  Next: OpenRISC 1000 Example,  Prev: Connecting to the Target,  Up: Top
290
 
291
2 Commands just for the OpenRISC 1000
292
*************************************
293
 
294
The OpenRISC 1000 has one particular feature that is difficult for GDB.
295
GDB models target processors with a register bank and a block of
296
memory. The internals of GDB assume that there are not a huge number of
297
registers in total.
298
 
299
   The OpenRISC 1000 Special Purpose Registers (SPR) do not really fit
300
well into this structure. There are too many of them (12 groups each
301
with 2000+ entries so far, with up to 32 groups permitted) to be
302
implemented as ordinary registers in GDB. Think what this would mean
303
for the command `info registers all'. However they cannot be considered
304
memory, since they do not reside in the main memory map.
305
 
306
   The solution is to add two new commands to GDB to see the value of a
307
particular SPR and to set the value of a particular SPR.
308
 
309
  1. `info spr' is used to show the value of a SPR or group of SPRs.
310
 
311
  2. `spr' is used to set the value of an individual SPR.
312
 
313
* Menu:
314
 
315
* Reading SPRs::            Using the ``info spr'' command
316
* Writing SPRs::            Using the spr command
317
 
318

319
File: or1k.info,  Node: Reading SPRs,  Next: Writing SPRs,  Up: OpenRISC 1000 Specific Commands
320
 
321
2.1 Using the `info spr' Command
322
================================
323
 
324
The value of an SPR is read by specifying either the unique name of the
325
SPR, or the its group and index in that group. For example the Debug
326
Reason Register (`DRR', register 21 in group 6 (Debug)) can be read
327
using any of the following commands:
328
 
329
     `info spr DRR'
330
     `info spr debug DRR'
331
     `info spr debug 21'
332
     `info spr 6 DRR'
333
     `info spr 6 21'
334
 
335
   In each case the output will be:
336
 
337
     `DEBUG.DRR = SPR6_21 = 0 (0x0)'
338
 
339
   It is also possible to inspect all the registers in a group. For
340
example to look at all the Programmable Interrupt Controller registers
341
(group 9), either of the following commands could be used:
342
 
343
     `info spr PIC'
344
     `info spr 9'
345
 
346
   And the output would be:
347
 
348
     `PIC.PICMR = SPR9_0 = 0 (0x9)'
349
     `PIC.PICSR = SPR9_2 = 0 (0x8)'
350
 
351
   Indicating that interrupts 0 and 4 are enabled and interrupt 4 is
352
pending.
353
 
354

355
File: or1k.info,  Node: Writing SPRs,  Prev: Reading SPRs,  Up: OpenRISC 1000 Specific Commands
356
 
357
2.2 Using the `spr' Command
358
===========================
359
 
360
The value of an SPR is written by specifying the unique name of the SPR
361
or its group and index in the same manner as for the `info spr'
362
command. An additional argument specifies the value to be written. So
363
for example the Programmable Interrupt Controller mask register could
364
be changed to enable interrupts 5 and 3 only by any of the following
365
commands.
366
 
367
     `spr PICMR 0x24'
368
     `spr PIC PICMR 0x24'
369
     `spr PIC 0 0x24'
370
     `spr 9 PICMR 0x24'
371
     `spr 9 2 0x24'
372
 
373

374
File: or1k.info,  Node: OpenRISC 1000 Example,  Next: OpenRISC 1000 Limitations,  Prev: OpenRISC 1000 Specific Commands,  Up: Top
375
 
376
3 A Small Example
377
*****************
378
 
379
A simple "Hello World" program (what else) is used to show the basics
380
 
381
   This is the cannonical small program. Here is the main program and
382
its two subprograms (added to demonstrate a meaningful backtrace).
383
 
384
     void level2() {
385
       simexit( 0 );
386
     }
387
 
388
     void level1() {
389
       level2();
390
     }
391
 
392
     main()
393
     {
394
       int  i;
395
       int  j;
396
 
397
       simputs( "Hello World!\n" );
398
       level1();
399
     }
400
 
401
   It is linked with a program providing the utility functions
402
`simexit', `simputc' and `simprints'.
403
 
404
     void  simexit( int  rc )
405
     {
406
       __asm__ __volatile__ ( "\tl.nop\t%0" : : "K"( NOP_EXIT ));
407
 
408
     }  /* simexit() */
409
 
410
     void  simputc( int  c )
411
     {
412
       __asm__ __volatile__ ( "\tl.nop\t%0" : : "K"( NOP_PUTC ));
413
 
414
     }  /* simputc() */
415
 
416
     void  simputs( char *str )
417
     {
418
       int  i;
419
 
420
       for( i = 0; str[i] != '\0' ; i++ ) {
421
         simputc( (int)(str[i]) );
422
       }
423
     }  /* simputs() */
424
 
425
   Finally, a small bootloader is needed, which will be placed at the
426
OpenRISC reset vector location (0x100) to set up a stack and jump to
427
the main program.
428
 
429
             .org    0x100           # The reset routine goes at 0x100
430
             .global _start
431
     _start:
432
             l.addi  r1,r0,0x7f00    # Set SP to value 0x7f00
433
             l.addi  r2,r1,0x0       # FP and SP are the same
434
             l.mfspr r3,r0,17        # Get SR value
435
             l.ori   r3,r3,0x10      # Set exception enable bit
436
             l.jal   _main           # Jump to main routine
437
             l.mtspr r0,r3,17        # Enable exceptions (DELAY SLOT)
438
 
439
             .org    0xFFC
440
             l.nop                   # Guarantee the exception vector space
441
                                     # does not have general purpose code
442
 
443
   This is compiled and linked with the OpenRISC 1000 GNU toolchain.
444
Note that the linking must specify the bootloader first and use the
445
`-Ttext 0x0' argument.
446
 
447
   The Or1ksim architectural simulator is configured with memory
448
starting at location 0x0. The debugging interface is enabled by using a
449
debug section.
450
 
451
     section debug
452
       enabled         =          1
453
       gdb_enabled     =          1
454
       server_port     =      50000
455
     end
456
 
457
   The architectural simulator is started in its own terminal window.
458
If the configuration is in `rsp.cfg', then the command might be:
459
 
460
     `or32-uclinux-sim -f rsp.cfg'
461
     Reading script file from 'rsp.cfg'...
462
     Building automata... done, num uncovered: 0/213.
463
     Parsing operands data... done.
464
     Resetting memory controller.
465
     Resetting PIC.
466
 
467
   Note that no program is specified - that will be loaded from GDB.
468
 
469
   In a separate window start up GDB.
470
 
471
     `or32-uclinux-gdb'
472
 
473
   A local copy of the symbol table is needed, specified with the `file'
474
command.
475
 
476
     Building automata... done, num uncovered: 0/216.
477
     Parsing operands data... done.
478
     GNU gdb 6.8
479
     Copyright (C) 2008 Free Software Foundation, Inc.
480
     License GPLv3+: GNU GPL version 3 or later 
481
     This is free software: you are free to change and redistribute it.
482
     There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
483
     and "show warranty" for details.
484
     This GDB was configured as "--host=i686-pc-linux-gnu --target=or32-uclinux".
485
     (gdb) `file hello'
486
     Reading symbols from /home/jeremy/svntrunk/GNU/gdb-6.8/progs_or32/hello...done.
487
     (gdb)
488
 
489
   The connection to the target (the architectural simulator) is then
490
established, using the port number given in the configuration file.
491
 
492
     (gdb) `target remote :51000'
493
     Remote debugging using :51000
494
     0x00000100 in _start ()
495
     (gdb)
496
 
497
   The program of interest can now be loaded:
498
 
499
     (gdb) `load hello'
500
     Loading section .text, size 0x1290 lma 0x0
501
     Loading section .rodata, size 0xe lma 0x1290
502
     Start address 0x100, load size 4766
503
     Transfer rate: 5 KB/sec, 238 bytes/write.
504
     (gdb)
505
 
506
   The program does not immediately start running, since on opening the
507
connection to the target, Or1ksim stalls.
508
 
509
   All the GDB commands (including the SPR commands are available). For
510
example
511
 
512
     (gdb) `bt'
513
     #0  0x00000100 in _start ()
514
     (gdb) `info spr 0 17'
515
     SYS.SR = SPR0_17 = 32769 (0x8001)
516
     (gdb)
517
 
518
   The Supervision Register shows the target is in Supervisor Mode and
519
that SPRs have User Mode read access.
520
 
521
   _Note._ The supervision register is used to provide the value for the
522
GDB `$ps' processor status variable, so can also be accessed as:
523
 
524
     (gdb) `print $ps'
525
     $1 = 32769
526
     (gdb)
527
 
528
   For this example set a breakpoint at the start of main and then
529
continue the program
530
 
531
     (gdb) `break main'
532
     Breakpoint 1 at 0x1264: file hello.c, line 41.
533
     (gdb) `continue'
534
     Continuing.
535
 
536
     Breakpoint 1, main () at hello.c:41
537
     41        simputs( "Hello World!\n" );
538
     (gdb)
539
 
540
   It is now possible to step through the code:
541
     (gdb) `step'
542
     simputs (str=0x1290 "Hello World!\n") at utils.c:90
543
     90        for( i = 0; str[i] != '\0' ; i++ ) {
544
     (gdb) `step'
545
     91          simputc( (int)(str[i]) );
546
     (gdb) `step'
547
     simputc (c=72) at utils.c:58
548
     58        __asm__ __volatile__ ( "\tl.nop\t%0" : : "K"( NOP_PUTC ));
549
     (gdb)
550
 
551
   At this point a backtrace will show where the code has reached:
552
 
553
     (gdb) `bt'
554
     #0  simputc (c=72) at utils.c:58
555
     #1  0x000011cc in simputs (str=0x1290 "Hello World!\n") at utils.c:91
556
     #2  0x00001274 in main () at hello.c:41
557
     #3  0x00000118 in _start ()
558
     (gdb)
559
 
560
   One more step completes the call to the character output routine.
561
Inspecting the terminal running the Or1ksim simulation, shows the
562
output appearing:
563
 
564
     JTAG Proxy server started on port 50000
565
     Resetting PIC.
566
     H
567
 
568
   Let the program run to completion by giving GDB the continue command:
569
     (gdb) `continue'
570
     Continuing.
571
     Remote connection closed
572
     (gdb)
573
 
574
   With completion of the program, the terminal running Or1ksim shows
575
its final output:
576
 
577
     Resetting PIC.
578
     Hello World!
579
     exit(0)
580
     @reset : cycles 0, insn #0
581
     @exit  : cycles 215892308, insn #215891696
582
      diff  : cycles 215892308, insn #215891696
583
 
584
   When execution exits (by execution of a `l.nop 1'), the connection
585
to the target is automatically broken as the simulator exits.
586
 
587

588
File: or1k.info,  Node: OpenRISC 1000 Limitations,  Next: Copying,  Prev: OpenRISC 1000 Example,  Up: Top
589
 
590
4 Known Problems
591
****************
592
 
593
There are some known problems with the current implementation
594
 
595
  1. If the OpenRISC 1000 Architecture supports hardware watchpoints,
596
     GDB will use them to implement hardware breakpoints and
597
     watchpoints. GDB is not perfect in handling of watchpoints. It is
598
     possible to allocate hardware watchpoints and not discover until
599
     running that sufficient watchpoints are not available. It is also
600
     possible that GDB will report watchpoints being hit spuriously.
601
     This can be down to the assembly code having additional memory
602
     accesses that are not obviously reflected in the source code.
603
 
604
  2. The remote JTAG connection is not robust to being interrupted, or
605
     reconnecting. If the connection is lost due to error, then you
606
     must restart GDB and the target server (for example the Or1ksim
607
     architectural simulator). Moving to the Remote Serial Protocol is
608
     intended to remedy this problem in the future.
609
 
610
  3. The OpenRISC 1000 architecture has evolved since the port of GDB
611
     5.3 in 2001. In particular the structure of the Unit Present
612
     register has changed and the CPU Configuration register has been
613
     added. The port of GDB version 6.8 uses the _current_
614
     specification of the OpenRISC 1000. This means that old clients
615
     that talk to the debugger may not work. In particular the Or1ksim
616
     Architectural simulator requires a patch to work.
617
 
618
  4. The handling of watchpoints in the Or1ksim architectural simulator
619
     was incorrect. To work with GDB 6.8, a patch is required to fix
620
     this problem. This is combined with the patch changing the
621
     structure of the Unit Present and CPU Configuration registers.
622
 
623
  5. The OpenRISC 1000 architecture uses its General Purpose Register
624
     (GPR) 2 as a frame pointer register. However the `$fp' variable in
625
     GDB is not currently implemented, and will return the value of the
626
     stack pointer (GPR 1) instead.
627
 
628
   Reports of bugs are much welcomed. Please report problems through the
629
OpenCORES tracker at `www.opencores.org/ptracker.cgi/list/or1k'.
630
 
631

632
File: or1k.info,  Node: Copying,  Next: GNU Free Documentation License,  Prev: OpenRISC 1000 Limitations,  Up: Top
633
 
634
Appendix A GNU GENERAL PUBLIC LICENSE
635
*************************************
636
 
637
                         Version 2, June 1991
638
 
639
     Copyright (C) 1989, 1991 Free Software Foundation, Inc.
640
     51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
641
 
642
     Everyone is permitted to copy and distribute verbatim copies
643
     of this license document, but changing it is not allowed.
644
 
645
Preamble
646
========
647
 
648
The licenses for most software are designed to take away your freedom
649
to share and change it.  By contrast, the GNU General Public License is
650
intended to guarantee your freedom to share and change free
651
software--to make sure the software is free for all its users.  This
652
General Public License applies to most of the Free Software
653
Foundation's software and to any other program whose authors commit to
654
using it.  (Some other Free Software Foundation software is covered by
655
the GNU Library General Public License instead.)  You can apply it to
656
your programs, too.
657
 
658
   When we speak of free software, we are referring to freedom, not
659
price.  Our General Public Licenses are designed to make sure that you
660
have the freedom to distribute copies of free software (and charge for
661
this service if you wish), that you receive source code or can get it
662
if you want it, that you can change the software or use pieces of it in
663
new free programs; and that you know you can do these things.
664
 
665
   To protect your rights, we need to make restrictions that forbid
666
anyone to deny you these rights or to ask you to surrender the rights.
667
These restrictions translate to certain responsibilities for you if you
668
distribute copies of the software, or if you modify it.
669
 
670
   For example, if you distribute copies of such a program, whether
671
gratis or for a fee, you must give the recipients all the rights that
672
you have.  You must make sure that they, too, receive or can get the
673
source code.  And you must show them these terms so they know their
674
rights.
675
 
676
   We protect your rights with two steps: (1) copyright the software,
677
and (2) offer you this license which gives you legal permission to copy,
678
distribute and/or modify the software.
679
 
680
   Also, for each author's protection and ours, we want to make certain
681
that everyone understands that there is no warranty for this free
682
software.  If the software is modified by someone else and passed on, we
683
want its recipients to know that what they have is not the original, so
684
that any problems introduced by others will not reflect on the original
685
authors' reputations.
686
 
687
   Finally, any free program is threatened constantly by software
688
patents.  We wish to avoid the danger that redistributors of a free
689
program will individually obtain patent licenses, in effect making the
690
program proprietary.  To prevent this, we have made it clear that any
691
patent must be licensed for everyone's free use or not licensed at all.
692
 
693
   The precise terms and conditions for copying, distribution and
694
modification follow.
695
 
696
    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
697
  0. This License applies to any program or other work which contains a
698
     notice placed by the copyright holder saying it may be distributed
699
     under the terms of this General Public License.  The "Program",
700
     below, refers to any such program or work, and a "work based on
701
     the Program" means either the Program or any derivative work under
702
     copyright law: that is to say, a work containing the Program or a
703
     portion of it, either verbatim or with modifications and/or
704
     translated into another language.  (Hereinafter, translation is
705
     included without limitation in the term "modification".)  Each
706
     licensee is addressed as "you".
707
 
708
     Activities other than copying, distribution and modification are
709
     not covered by this License; they are outside its scope.  The act
710
     of running the Program is not restricted, and the output from the
711
     Program is covered only if its contents constitute a work based on
712
     the Program (independent of having been made by running the
713
     Program).  Whether that is true depends on what the Program does.
714
 
715
  1. You may copy and distribute verbatim copies of the Program's
716
     source code as you receive it, in any medium, provided that you
717
     conspicuously and appropriately publish on each copy an appropriate
718
     copyright notice and disclaimer of warranty; keep intact all the
719
     notices that refer to this License and to the absence of any
720
     warranty; and give any other recipients of the Program a copy of
721
     this License along with the Program.
722
 
723
     You may charge a fee for the physical act of transferring a copy,
724
     and you may at your option offer warranty protection in exchange
725
     for a fee.
726
 
727
  2. You may modify your copy or copies of the Program or any portion
728
     of it, thus forming a work based on the Program, and copy and
729
     distribute such modifications or work under the terms of Section 1
730
     above, provided that you also meet all of these conditions:
731
 
732
       a. You must cause the modified files to carry prominent notices
733
          stating that you changed the files and the date of any change.
734
 
735
       b. You must cause any work that you distribute or publish, that
736
          in whole or in part contains or is derived from the Program
737
          or any part thereof, to be licensed as a whole at no charge
738
          to all third parties under the terms of this License.
739
 
740
       c. If the modified program normally reads commands interactively
741
          when run, you must cause it, when started running for such
742
          interactive use in the most ordinary way, to print or display
743
          an announcement including an appropriate copyright notice and
744
          a notice that there is no warranty (or else, saying that you
745
          provide a warranty) and that users may redistribute the
746
          program under these conditions, and telling the user how to
747
          view a copy of this License.  (Exception: if the Program
748
          itself is interactive but does not normally print such an
749
          announcement, your work based on the Program is not required
750
          to print an announcement.)
751
 
752
     These requirements apply to the modified work as a whole.  If
753
     identifiable sections of that work are not derived from the
754
     Program, and can be reasonably considered independent and separate
755
     works in themselves, then this License, and its terms, do not
756
     apply to those sections when you distribute them as separate
757
     works.  But when you distribute the same sections as part of a
758
     whole which is a work based on the Program, the distribution of
759
     the whole must be on the terms of this License, whose permissions
760
     for other licensees extend to the entire whole, and thus to each
761
     and every part regardless of who wrote it.
762
 
763
     Thus, it is not the intent of this section to claim rights or
764
     contest your rights to work written entirely by you; rather, the
765
     intent is to exercise the right to control the distribution of
766
     derivative or collective works based on the Program.
767
 
768
     In addition, mere aggregation of another work not based on the
769
     Program with the Program (or with a work based on the Program) on
770
     a volume of a storage or distribution medium does not bring the
771
     other work under the scope of this License.
772
 
773
  3. You may copy and distribute the Program (or a work based on it,
774
     under Section 2) in object code or executable form under the terms
775
     of Sections 1 and 2 above provided that you also do one of the
776
     following:
777
 
778
       a. Accompany it with the complete corresponding machine-readable
779
          source code, which must be distributed under the terms of
780
          Sections 1 and 2 above on a medium customarily used for
781
          software interchange; or,
782
 
783
       b. Accompany it with a written offer, valid for at least three
784
          years, to give any third party, for a charge no more than your
785
          cost of physically performing source distribution, a complete
786
          machine-readable copy of the corresponding source code, to be
787
          distributed under the terms of Sections 1 and 2 above on a
788
          medium customarily used for software interchange; or,
789
 
790
       c. Accompany it with the information you received as to the offer
791
          to distribute corresponding source code.  (This alternative is
792
          allowed only for noncommercial distribution and only if you
793
          received the program in object code or executable form with
794
          such an offer, in accord with Subsection b above.)
795
 
796
     The source code for a work means the preferred form of the work for
797
     making modifications to it.  For an executable work, complete
798
     source code means all the source code for all modules it contains,
799
     plus any associated interface definition files, plus the scripts
800
     used to control compilation and installation of the executable.
801
     However, as a special exception, the source code distributed need
802
     not include anything that is normally distributed (in either
803
     source or binary form) with the major components (compiler,
804
     kernel, and so on) of the operating system on which the executable
805
     runs, unless that component itself accompanies the executable.
806
 
807
     If distribution of executable or object code is made by offering
808
     access to copy from a designated place, then offering equivalent
809
     access to copy the source code from the same place counts as
810
     distribution of the source code, even though third parties are not
811
     compelled to copy the source along with the object code.
812
 
813
  4. You may not copy, modify, sublicense, or distribute the Program
814
     except as expressly provided under this License.  Any attempt
815
     otherwise to copy, modify, sublicense or distribute the Program is
816
     void, and will automatically terminate your rights under this
817
     License.  However, parties who have received copies, or rights,
818
     from you under this License will not have their licenses
819
     terminated so long as such parties remain in full compliance.
820
 
821
  5. You are not required to accept this License, since you have not
822
     signed it.  However, nothing else grants you permission to modify
823
     or distribute the Program or its derivative works.  These actions
824
     are prohibited by law if you do not accept this License.
825
     Therefore, by modifying or distributing the Program (or any work
826
     based on the Program), you indicate your acceptance of this
827
     License to do so, and all its terms and conditions for copying,
828
     distributing or modifying the Program or works based on it.
829
 
830
  6. Each time you redistribute the Program (or any work based on the
831
     Program), the recipient automatically receives a license from the
832
     original licensor to copy, distribute or modify the Program
833
     subject to these terms and conditions.  You may not impose any
834
     further restrictions on the recipients' exercise of the rights
835
     granted herein.  You are not responsible for enforcing compliance
836
     by third parties to this License.
837
 
838
  7. If, as a consequence of a court judgment or allegation of patent
839
     infringement or for any other reason (not limited to patent
840
     issues), conditions are imposed on you (whether by court order,
841
     agreement or otherwise) that contradict the conditions of this
842
     License, they do not excuse you from the conditions of this
843
     License.  If you cannot distribute so as to satisfy simultaneously
844
     your obligations under this License and any other pertinent
845
     obligations, then as a consequence you may not distribute the
846
     Program at all.  For example, if a patent license would not permit
847
     royalty-free redistribution of the Program by all those who
848
     receive copies directly or indirectly through you, then the only
849
     way you could satisfy both it and this License would be to refrain
850
     entirely from distribution of the Program.
851
 
852
     If any portion of this section is held invalid or unenforceable
853
     under any particular circumstance, the balance of the section is
854
     intended to apply and the section as a whole is intended to apply
855
     in other circumstances.
856
 
857
     It is not the purpose of this section to induce you to infringe any
858
     patents or other property right claims or to contest validity of
859
     any such claims; this section has the sole purpose of protecting
860
     the integrity of the free software distribution system, which is
861
     implemented by public license practices.  Many people have made
862
     generous contributions to the wide range of software distributed
863
     through that system in reliance on consistent application of that
864
     system; it is up to the author/donor to decide if he or she is
865
     willing to distribute software through any other system and a
866
     licensee cannot impose that choice.
867
 
868
     This section is intended to make thoroughly clear what is believed
869
     to be a consequence of the rest of this License.
870
 
871
  8. If the distribution and/or use of the Program is restricted in
872
     certain countries either by patents or by copyrighted interfaces,
873
     the original copyright holder who places the Program under this
874
     License may add an explicit geographical distribution limitation
875
     excluding those countries, so that distribution is permitted only
876
     in or among countries not thus excluded.  In such case, this
877
     License incorporates the limitation as if written in the body of
878
     this License.
879
 
880
  9. The Free Software Foundation may publish revised and/or new
881
     versions of the General Public License from time to time.  Such
882
     new versions will be similar in spirit to the present version, but
883
     may differ in detail to address new problems or concerns.
884
 
885
     Each version is given a distinguishing version number.  If the
886
     Program specifies a version number of this License which applies
887
     to it and "any later version", you have the option of following
888
     the terms and conditions either of that version or of any later
889
     version published by the Free Software Foundation.  If the Program
890
     does not specify a version number of this License, you may choose
891
     any version ever published by the Free Software Foundation.
892
 
893
 10. If you wish to incorporate parts of the Program into other free
894
     programs whose distribution conditions are different, write to the
895
     author to ask for permission.  For software which is copyrighted
896
     by the Free Software Foundation, write to the Free Software
897
     Foundation; we sometimes make exceptions for this.  Our decision
898
     will be guided by the two goals of preserving the free status of
899
     all derivatives of our free software and of promoting the sharing
900
     and reuse of software generally.
901
 
902
                                NO WARRANTY
903
 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
904
     WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
905
     LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
906
     HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
907
     WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
908
     NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
909
     FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE
910
     QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
911
     PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
912
     SERVICING, REPAIR OR CORRECTION.
913
 
914
 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
915
     WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
916
     MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
917
     LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
918
     INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
919
     INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
920
     DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
921
     OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
922
     OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
923
     ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
924
 
925
                      END OF TERMS AND CONDITIONS
926
How to Apply These Terms to Your New Programs
927
=============================================
928
 
929
If you develop a new program, and you want it to be of the greatest
930
possible use to the public, the best way to achieve this is to make it
931
free software which everyone can redistribute and change under these
932
terms.
933
 
934
   To do so, attach the following notices to the program.  It is safest
935
to attach them to the start of each source file to most effectively
936
convey the exclusion of warranty; and each file should have at least
937
the "copyright" line and a pointer to where the full notice is found.
938
 
939
     ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
940
     Copyright (C) YEAR  NAME OF AUTHOR
941
 
942
     This program is free software; you can redistribute it and/or modify
943
     it under the terms of the GNU General Public License as published by
944
     the Free Software Foundation; either version 2 of the License, or
945
     (at your option) any later version.
946
 
947
     This program is distributed in the hope that it will be useful,
948
     but WITHOUT ANY WARRANTY; without even the implied warranty of
949
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
950
     GNU General Public License for more details.
951
 
952
     You should have received a copy of the GNU General Public License
953
     along with this program; if not, write to the Free Software
954
     Foundation, Inc., 51 Franklin Street, Fifth Floor,
955
     Boston, MA 02110-1301, USA.
956
 
957
   Also add information on how to contact you by electronic and paper
958
mail.
959
 
960
   If the program is interactive, make it output a short notice like
961
this when it starts in an interactive mode:
962
 
963
     Gnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR
964
     Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
965
     type `show w'.
966
     This is free software, and you are welcome to redistribute it
967
     under certain conditions; type `show c' for details.
968
 
969
   The hypothetical commands `show w' and `show c' should show the
970
appropriate parts of the General Public License.  Of course, the
971
commands you use may be called something other than `show w' and `show
972
c'; they could even be mouse-clicks or menu items--whatever suits your
973
program.
974
 
975
   You should also get your employer (if you work as a programmer) or
976
your school, if any, to sign a "copyright disclaimer" for the program,
977
if necessary.  Here is a sample; alter the names:
978
 
979
     Yoyodyne, Inc., hereby disclaims all copyright interest in the program
980
     `Gnomovision' (which makes passes at compilers) written by James Hacker.
981
 
982
     SIGNATURE OF TY COON, 1 April 1989
983
     Ty Coon, President of Vice
984
 
985
   This General Public License does not permit incorporating your
986
program into proprietary programs.  If your program is a subroutine
987
library, you may consider it more useful to permit linking proprietary
988
applications with the library.  If this is what you want to do, use the
989
GNU Library General Public License instead of this License.
990
 
991

992
File: or1k.info,  Node: GNU Free Documentation License,  Next: Index,  Prev: Copying,  Up: Top
993
 
994
Appendix B GNU Free Documentation License
995
*****************************************
996
 
997
                      Version 1.2, November 2002
998
 
999
     Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
1000
     51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
1001
 
1002
     Everyone is permitted to copy and distribute verbatim copies
1003
     of this license document, but changing it is not allowed.
1004
 
1005
  0. PREAMBLE
1006
 
1007
     The purpose of this License is to make a manual, textbook, or other
1008
     functional and useful document "free" in the sense of freedom: to
1009
     assure everyone the effective freedom to copy and redistribute it,
1010
     with or without modifying it, either commercially or
1011
     noncommercially.  Secondarily, this License preserves for the
1012
     author and publisher a way to get credit for their work, while not
1013
     being considered responsible for modifications made by others.
1014
 
1015
     This License is a kind of "copyleft", which means that derivative
1016
     works of the document must themselves be free in the same sense.
1017
     It complements the GNU General Public License, which is a copyleft
1018
     license designed for free software.
1019
 
1020
     We have designed this License in order to use it for manuals for
1021
     free software, because free software needs free documentation: a
1022
     free program should come with manuals providing the same freedoms
1023
     that the software does.  But this License is not limited to
1024
     software manuals; it can be used for any textual work, regardless
1025
     of subject matter or whether it is published as a printed book.
1026
     We recommend this License principally for works whose purpose is
1027
     instruction or reference.
1028
 
1029
  1. APPLICABILITY AND DEFINITIONS
1030
 
1031
     This License applies to any manual or other work, in any medium,
1032
     that contains a notice placed by the copyright holder saying it
1033
     can be distributed under the terms of this License.  Such a notice
1034
     grants a world-wide, royalty-free license, unlimited in duration,
1035
     to use that work under the conditions stated herein.  The
1036
     "Document", below, refers to any such manual or work.  Any member
1037
     of the public is a licensee, and is addressed as "you".  You
1038
     accept the license if you copy, modify or distribute the work in a
1039
     way requiring permission under copyright law.
1040
 
1041
     A "Modified Version" of the Document means any work containing the
1042
     Document or a portion of it, either copied verbatim, or with
1043
     modifications and/or translated into another language.
1044
 
1045
     A "Secondary Section" is a named appendix or a front-matter section
1046
     of the Document that deals exclusively with the relationship of the
1047
     publishers or authors of the Document to the Document's overall
1048
     subject (or to related matters) and contains nothing that could
1049
     fall directly within that overall subject.  (Thus, if the Document
1050
     is in part a textbook of mathematics, a Secondary Section may not
1051
     explain any mathematics.)  The relationship could be a matter of
1052
     historical connection with the subject or with related matters, or
1053
     of legal, commercial, philosophical, ethical or political position
1054
     regarding them.
1055
 
1056
     The "Invariant Sections" are certain Secondary Sections whose
1057
     titles are designated, as being those of Invariant Sections, in
1058
     the notice that says that the Document is released under this
1059
     License.  If a section does not fit the above definition of
1060
     Secondary then it is not allowed to be designated as Invariant.
1061
     The Document may contain zero Invariant Sections.  If the Document
1062
     does not identify any Invariant Sections then there are none.
1063
 
1064
     The "Cover Texts" are certain short passages of text that are
1065
     listed, as Front-Cover Texts or Back-Cover Texts, in the notice
1066
     that says that the Document is released under this License.  A
1067
     Front-Cover Text may be at most 5 words, and a Back-Cover Text may
1068
     be at most 25 words.
1069
 
1070
     A "Transparent" copy of the Document means a machine-readable copy,
1071
     represented in a format whose specification is available to the
1072
     general public, that is suitable for revising the document
1073
     straightforwardly with generic text editors or (for images
1074
     composed of pixels) generic paint programs or (for drawings) some
1075
     widely available drawing editor, and that is suitable for input to
1076
     text formatters or for automatic translation to a variety of
1077
     formats suitable for input to text formatters.  A copy made in an
1078
     otherwise Transparent file format whose markup, or absence of
1079
     markup, has been arranged to thwart or discourage subsequent
1080
     modification by readers is not Transparent.  An image format is
1081
     not Transparent if used for any substantial amount of text.  A
1082
     copy that is not "Transparent" is called "Opaque".
1083
 
1084
     Examples of suitable formats for Transparent copies include plain
1085
     ASCII without markup, Texinfo input format, LaTeX input format,
1086
     SGML or XML using a publicly available DTD, and
1087
     standard-conforming simple HTML, PostScript or PDF designed for
1088
     human modification.  Examples of transparent image formats include
1089
     PNG, XCF and JPG.  Opaque formats include proprietary formats that
1090
     can be read and edited only by proprietary word processors, SGML or
1091
     XML for which the DTD and/or processing tools are not generally
1092
     available, and the machine-generated HTML, PostScript or PDF
1093
     produced by some word processors for output purposes only.
1094
 
1095
     The "Title Page" means, for a printed book, the title page itself,
1096
     plus such following pages as are needed to hold, legibly, the
1097
     material this License requires to appear in the title page.  For
1098
     works in formats which do not have any title page as such, "Title
1099
     Page" means the text near the most prominent appearance of the
1100
     work's title, preceding the beginning of the body of the text.
1101
 
1102
     A section "Entitled XYZ" means a named subunit of the Document
1103
     whose title either is precisely XYZ or contains XYZ in parentheses
1104
     following text that translates XYZ in another language.  (Here XYZ
1105
     stands for a specific section name mentioned below, such as
1106
     "Acknowledgements", "Dedications", "Endorsements", or "History".)
1107
     To "Preserve the Title" of such a section when you modify the
1108
     Document means that it remains a section "Entitled XYZ" according
1109
     to this definition.
1110
 
1111
     The Document may include Warranty Disclaimers next to the notice
1112
     which states that this License applies to the Document.  These
1113
     Warranty Disclaimers are considered to be included by reference in
1114
     this License, but only as regards disclaiming warranties: any other
1115
     implication that these Warranty Disclaimers may have is void and
1116
     has no effect on the meaning of this License.
1117
 
1118
  2. VERBATIM COPYING
1119
 
1120
     You may copy and distribute the Document in any medium, either
1121
     commercially or noncommercially, provided that this License, the
1122
     copyright notices, and the license notice saying this License
1123
     applies to the Document are reproduced in all copies, and that you
1124
     add no other conditions whatsoever to those of this License.  You
1125
     may not use technical measures to obstruct or control the reading
1126
     or further copying of the copies you make or distribute.  However,
1127
     you may accept compensation in exchange for copies.  If you
1128
     distribute a large enough number of copies you must also follow
1129
     the conditions in section 3.
1130
 
1131
     You may also lend copies, under the same conditions stated above,
1132
     and you may publicly display copies.
1133
 
1134
  3. COPYING IN QUANTITY
1135
 
1136
     If you publish printed copies (or copies in media that commonly
1137
     have printed covers) of the Document, numbering more than 100, and
1138
     the Document's license notice requires Cover Texts, you must
1139
     enclose the copies in covers that carry, clearly and legibly, all
1140
     these Cover Texts: Front-Cover Texts on the front cover, and
1141
     Back-Cover Texts on the back cover.  Both covers must also clearly
1142
     and legibly identify you as the publisher of these copies.  The
1143
     front cover must present the full title with all words of the
1144
     title equally prominent and visible.  You may add other material
1145
     on the covers in addition.  Copying with changes limited to the
1146
     covers, as long as they preserve the title of the Document and
1147
     satisfy these conditions, can be treated as verbatim copying in
1148
     other respects.
1149
 
1150
     If the required texts for either cover are too voluminous to fit
1151
     legibly, you should put the first ones listed (as many as fit
1152
     reasonably) on the actual cover, and continue the rest onto
1153
     adjacent pages.
1154
 
1155
     If you publish or distribute Opaque copies of the Document
1156
     numbering more than 100, you must either include a
1157
     machine-readable Transparent copy along with each Opaque copy, or
1158
     state in or with each Opaque copy a computer-network location from
1159
     which the general network-using public has access to download
1160
     using public-standard network protocols a complete Transparent
1161
     copy of the Document, free of added material.  If you use the
1162
     latter option, you must take reasonably prudent steps, when you
1163
     begin distribution of Opaque copies in quantity, to ensure that
1164
     this Transparent copy will remain thus accessible at the stated
1165
     location until at least one year after the last time you
1166
     distribute an Opaque copy (directly or through your agents or
1167
     retailers) of that edition to the public.
1168
 
1169
     It is requested, but not required, that you contact the authors of
1170
     the Document well before redistributing any large number of
1171
     copies, to give them a chance to provide you with an updated
1172
     version of the Document.
1173
 
1174
  4. MODIFICATIONS
1175
 
1176
     You may copy and distribute a Modified Version of the Document
1177
     under the conditions of sections 2 and 3 above, provided that you
1178
     release the Modified Version under precisely this License, with
1179
     the Modified Version filling the role of the Document, thus
1180
     licensing distribution and modification of the Modified Version to
1181
     whoever possesses a copy of it.  In addition, you must do these
1182
     things in the Modified Version:
1183
 
1184
       A. Use in the Title Page (and on the covers, if any) a title
1185
          distinct from that of the Document, and from those of
1186
          previous versions (which should, if there were any, be listed
1187
          in the History section of the Document).  You may use the
1188
          same title as a previous version if the original publisher of
1189
          that version gives permission.
1190
 
1191
       B. List on the Title Page, as authors, one or more persons or
1192
          entities responsible for authorship of the modifications in
1193
          the Modified Version, together with at least five of the
1194
          principal authors of the Document (all of its principal
1195
          authors, if it has fewer than five), unless they release you
1196
          from this requirement.
1197
 
1198
       C. State on the Title page the name of the publisher of the
1199
          Modified Version, as the publisher.
1200
 
1201
       D. Preserve all the copyright notices of the Document.
1202
 
1203
       E. Add an appropriate copyright notice for your modifications
1204
          adjacent to the other copyright notices.
1205
 
1206
       F. Include, immediately after the copyright notices, a license
1207
          notice giving the public permission to use the Modified
1208
          Version under the terms of this License, in the form shown in
1209
          the Addendum below.
1210
 
1211
       G. Preserve in that license notice the full lists of Invariant
1212
          Sections and required Cover Texts given in the Document's
1213
          license notice.
1214
 
1215
       H. Include an unaltered copy of this License.
1216
 
1217
       I. Preserve the section Entitled "History", Preserve its Title,
1218
          and add to it an item stating at least the title, year, new
1219
          authors, and publisher of the Modified Version as given on
1220
          the Title Page.  If there is no section Entitled "History" in
1221
          the Document, create one stating the title, year, authors,
1222
          and publisher of the Document as given on its Title Page,
1223
          then add an item describing the Modified Version as stated in
1224
          the previous sentence.
1225
 
1226
       J. Preserve the network location, if any, given in the Document
1227
          for public access to a Transparent copy of the Document, and
1228
          likewise the network locations given in the Document for
1229
          previous versions it was based on.  These may be placed in
1230
          the "History" section.  You may omit a network location for a
1231
          work that was published at least four years before the
1232
          Document itself, or if the original publisher of the version
1233
          it refers to gives permission.
1234
 
1235
       K. For any section Entitled "Acknowledgements" or "Dedications",
1236
          Preserve the Title of the section, and preserve in the
1237
          section all the substance and tone of each of the contributor
1238
          acknowledgements and/or dedications given therein.
1239
 
1240
       L. Preserve all the Invariant Sections of the Document,
1241
          unaltered in their text and in their titles.  Section numbers
1242
          or the equivalent are not considered part of the section
1243
          titles.
1244
 
1245
       M. Delete any section Entitled "Endorsements".  Such a section
1246
          may not be included in the Modified Version.
1247
 
1248
       N. Do not retitle any existing section to be Entitled
1249
          "Endorsements" or to conflict in title with any Invariant
1250
          Section.
1251
 
1252
       O. Preserve any Warranty Disclaimers.
1253
 
1254
     If the Modified Version includes new front-matter sections or
1255
     appendices that qualify as Secondary Sections and contain no
1256
     material copied from the Document, you may at your option
1257
     designate some or all of these sections as invariant.  To do this,
1258
     add their titles to the list of Invariant Sections in the Modified
1259
     Version's license notice.  These titles must be distinct from any
1260
     other section titles.
1261
 
1262
     You may add a section Entitled "Endorsements", provided it contains
1263
     nothing but endorsements of your Modified Version by various
1264
     parties--for example, statements of peer review or that the text
1265
     has been approved by an organization as the authoritative
1266
     definition of a standard.
1267
 
1268
     You may add a passage of up to five words as a Front-Cover Text,
1269
     and a passage of up to 25 words as a Back-Cover Text, to the end
1270
     of the list of Cover Texts in the Modified Version.  Only one
1271
     passage of Front-Cover Text and one of Back-Cover Text may be
1272
     added by (or through arrangements made by) any one entity.  If the
1273
     Document already includes a cover text for the same cover,
1274
     previously added by you or by arrangement made by the same entity
1275
     you are acting on behalf of, you may not add another; but you may
1276
     replace the old one, on explicit permission from the previous
1277
     publisher that added the old one.
1278
 
1279
     The author(s) and publisher(s) of the Document do not by this
1280
     License give permission to use their names for publicity for or to
1281
     assert or imply endorsement of any Modified Version.
1282
 
1283
  5. COMBINING DOCUMENTS
1284
 
1285
     You may combine the Document with other documents released under
1286
     this License, under the terms defined in section 4 above for
1287
     modified versions, provided that you include in the combination
1288
     all of the Invariant Sections of all of the original documents,
1289
     unmodified, and list them all as Invariant Sections of your
1290
     combined work in its license notice, and that you preserve all
1291
     their Warranty Disclaimers.
1292
 
1293
     The combined work need only contain one copy of this License, and
1294
     multiple identical Invariant Sections may be replaced with a single
1295
     copy.  If there are multiple Invariant Sections with the same name
1296
     but different contents, make the title of each such section unique
1297
     by adding at the end of it, in parentheses, the name of the
1298
     original author or publisher of that section if known, or else a
1299
     unique number.  Make the same adjustment to the section titles in
1300
     the list of Invariant Sections in the license notice of the
1301
     combined work.
1302
 
1303
     In the combination, you must combine any sections Entitled
1304
     "History" in the various original documents, forming one section
1305
     Entitled "History"; likewise combine any sections Entitled
1306
     "Acknowledgements", and any sections Entitled "Dedications".  You
1307
     must delete all sections Entitled "Endorsements."
1308
 
1309
  6. COLLECTIONS OF DOCUMENTS
1310
 
1311
     You may make a collection consisting of the Document and other
1312
     documents released under this License, and replace the individual
1313
     copies of this License in the various documents with a single copy
1314
     that is included in the collection, provided that you follow the
1315
     rules of this License for verbatim copying of each of the
1316
     documents in all other respects.
1317
 
1318
     You may extract a single document from such a collection, and
1319
     distribute it individually under this License, provided you insert
1320
     a copy of this License into the extracted document, and follow
1321
     this License in all other respects regarding verbatim copying of
1322
     that document.
1323
 
1324
  7. AGGREGATION WITH INDEPENDENT WORKS
1325
 
1326
     A compilation of the Document or its derivatives with other
1327
     separate and independent documents or works, in or on a volume of
1328
     a storage or distribution medium, is called an "aggregate" if the
1329
     copyright resulting from the compilation is not used to limit the
1330
     legal rights of the compilation's users beyond what the individual
1331
     works permit.  When the Document is included in an aggregate, this
1332
     License does not apply to the other works in the aggregate which
1333
     are not themselves derivative works of the Document.
1334
 
1335
     If the Cover Text requirement of section 3 is applicable to these
1336
     copies of the Document, then if the Document is less than one half
1337
     of the entire aggregate, the Document's Cover Texts may be placed
1338
     on covers that bracket the Document within the aggregate, or the
1339
     electronic equivalent of covers if the Document is in electronic
1340
     form.  Otherwise they must appear on printed covers that bracket
1341
     the whole aggregate.
1342
 
1343
  8. TRANSLATION
1344
 
1345
     Translation is considered a kind of modification, so you may
1346
     distribute translations of the Document under the terms of section
1347
     4.  Replacing Invariant Sections with translations requires special
1348
     permission from their copyright holders, but you may include
1349
     translations of some or all Invariant Sections in addition to the
1350
     original versions of these Invariant Sections.  You may include a
1351
     translation of this License, and all the license notices in the
1352
     Document, and any Warranty Disclaimers, provided that you also
1353
     include the original English version of this License and the
1354
     original versions of those notices and disclaimers.  In case of a
1355
     disagreement between the translation and the original version of
1356
     this License or a notice or disclaimer, the original version will
1357
     prevail.
1358
 
1359
     If a section in the Document is Entitled "Acknowledgements",
1360
     "Dedications", or "History", the requirement (section 4) to
1361
     Preserve its Title (section 1) will typically require changing the
1362
     actual title.
1363
 
1364
  9. TERMINATION
1365
 
1366
     You may not copy, modify, sublicense, or distribute the Document
1367
     except as expressly provided for under this License.  Any other
1368
     attempt to copy, modify, sublicense or distribute the Document is
1369
     void, and will automatically terminate your rights under this
1370
     License.  However, parties who have received copies, or rights,
1371
     from you under this License will not have their licenses
1372
     terminated so long as such parties remain in full compliance.
1373
 
1374
 10. FUTURE REVISIONS OF THIS LICENSE
1375
 
1376
     The Free Software Foundation may publish new, revised versions of
1377
     the GNU Free Documentation License from time to time.  Such new
1378
     versions will be similar in spirit to the present version, but may
1379
     differ in detail to address new problems or concerns.  See
1380
     `http://www.gnu.org/copyleft/'.
1381
 
1382
     Each version of the License is given a distinguishing version
1383
     number.  If the Document specifies that a particular numbered
1384
     version of this License "or any later version" applies to it, you
1385
     have the option of following the terms and conditions either of
1386
     that specified version or of any later version that has been
1387
     published (not as a draft) by the Free Software Foundation.  If
1388
     the Document does not specify a version number of this License,
1389
     you may choose any version ever published (not as a draft) by the
1390
     Free Software Foundation.
1391
 
1392
B.1 ADDENDUM: How to use this License for your documents
1393
========================================================
1394
 
1395
To use this License in a document you have written, include a copy of
1396
the License in the document and put the following copyright and license
1397
notices just after the title page:
1398
 
1399
       Copyright (C)  YEAR  YOUR NAME.
1400
       Permission is granted to copy, distribute and/or modify this document
1401
       under the terms of the GNU Free Documentation License, Version 1.2
1402
       or any later version published by the Free Software Foundation;
1403
       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
1404
       Texts.  A copy of the license is included in the section entitled ``GNU
1405
       Free Documentation License''.
1406
 
1407
   If you have Invariant Sections, Front-Cover Texts and Back-Cover
1408
Texts, replace the "with...Texts." line with this:
1409
 
1410
         with the Invariant Sections being LIST THEIR TITLES, with
1411
         the Front-Cover Texts being LIST, and with the Back-Cover Texts
1412
         being LIST.
1413
 
1414
   If you have Invariant Sections without Cover Texts, or some other
1415
combination of the three, merge those two alternatives to suit the
1416
situation.
1417
 
1418
   If your document contains nontrivial examples of program code, we
1419
recommend releasing these examples in parallel under your choice of
1420
free software license, such as the GNU General Public License, to
1421
permit their use in free software.
1422
 
1423

1424
File: or1k.info,  Node: Index,  Prev: GNU Free Documentation License,  Up: Top
1425
 
1426
Index
1427
*****
1428
 
1429
 
1430
* Menu:
1431
1432
* Alessandro Forin:                      Contributors.        (line  16)
1433
* Bennett, Jeremy:                       Contributors.        (line  22)
1434
* BFD:                                   Contributors.        (line  13)
1435
* Binary File Description library:       Contributors.        (line  13)
1436
* Bothner, Per:                          Contributors.        (line  16)
1437
* breakpoint command example:            OpenRISC 1000 Example.
1438
                                                              (line 155)
1439
* bt command example:                    OpenRISC 1000 Example.
1440
                                                              (line 136)
1441
* bugs:                                  OpenRISC 1000 Limitations.
1442
                                                              (line   6)
1443
* bugs, architectural compatibility:     OpenRISC 1000 Limitations.
1444
                                                              (line  23)
1445
* bugs, Or1ksim architectural simulator: OpenRISC 1000 Limitations.
1446
                                                              (line  31)
1447
* bugs, remote JTAG connection robustness: OpenRISC 1000 Limitations.
1448
                                                              (line  17)
1449
* Bugs, reporting:                       OpenRISC 1000 Limitations.
1450
                                                              (line  41)
1451
* bugs, watchpoints:                     OpenRISC 1000 Limitations.
1452
                                                              (line   8)
1453
* Chris Ziomkowski:                      Contributors.        (line  19)
1454
* commands, breakpoint, example:         OpenRISC 1000 Example.
1455
                                                              (line 155)
1456
* commands, bt, example:                 OpenRISC 1000 Example.
1457
                                                              (line 136)
1458
* commands, continue, example:           OpenRISC 1000 Example.
1459
                                                              (line 155)
1460
* commands, info registers for OpenRISC 1000: Summary.        (line  26)
1461
* commands, info spr <1>:                Reading SPRs.        (line   6)
1462
* commands, info spr <2>:                OpenRISC 1000 Specific Commands.
1463
                                                              (line   6)
1464
* commands, info spr:                    Summary.             (line  21)
1465
* commands, info spr, example:           OpenRISC 1000 Example.
1466
                                                              (line 136)
1467
* commands, OpenRISC 1000 specific:      Summary.             (line  21)
1468
* commands, set, example:                OpenRISC 1000 Example.
1469
                                                              (line 211)
1470
* commands, spr:                         Summary.             (line  21)
1471
* commands, spr command <1>:             Writing SPRs.        (line   6)
1472
* commands, spr command:                 OpenRISC 1000 Specific Commands.
1473
                                                              (line   6)
1474
* commands, step, example:               OpenRISC 1000 Example.
1475
                                                              (line 167)
1476
* commands, target extended-remote:      Connecting to the Target.
1477
                                                              (line  11)
1478
* commands, target jtag:                 Connecting to the Target.
1479
                                                              (line   8)
1480
* commands, target jtag, direct:         Direct JTAG Connection.
1481
                                                              (line  10)
1482
* commands, target jtag, direct, testing: Direct JTAG Connection.
1483
                                                              (line  12)
1484
* commands, target jtag, local:          Direct JTAG Connection.
1485
                                                              (line  10)
1486
* commands, target jtag, local, testing: Direct JTAG Connection.
1487
                                                              (line  12)
1488
* commands, target jtag, remote <1>:     Remote JTAG Connection.
1489
                                                              (line  24)
1490
* commands, target jtag, remote:         Remote Serial Protocol Connection.
1491
                                                              (line  21)
1492
* commands, target remote:               Connecting to the Target.
1493
                                                              (line  11)
1494
* commands, target remote, remote, example: OpenRISC 1000 Example.
1495
                                                              (line 116)
1496
* configuration, OpenRISC 1000 Architectural Simulator: OpenRISC 1000 Example.
1497
                                                              (line  74)
1498
* configuration, Or1ksim:                OpenRISC 1000 Example.
1499
                                                              (line  74)
1500
* connecting, OpenRISC 1000 target:      Connecting to the Target.
1501
                                                              (line   6)
1502
* connecting, OpenRISC 1000 target, direct <1>: Direct JTAG Connection.
1503
                                                              (line   6)
1504
* connecting, OpenRISC 1000 target, direct: Connecting to the Target.
1505
                                                              (line   8)
1506
* connecting, OpenRISC 1000 target, local <1>: Direct JTAG Connection.
1507
                                                              (line   6)
1508
* connecting, OpenRISC 1000 target, local: Connecting to the Target.
1509
                                                              (line   8)
1510
* connecting, OpenRISC 1000 target, remote: Remote JTAG Connection.
1511
                                                              (line   6)
1512
* connecting, OpenRISC 1000 target, remote via JTAG: Connecting to the Target.
1513
                                                              (line  16)
1514
* connecting, OpenRISC 1000 target, remote via RSP <1>: Remote Serial Protocol Connection.
1515
                                                              (line   6)
1516
* connecting, OpenRISC 1000 target, remote via RSP: Connecting to the Target.
1517
                                                              (line  11)
1518
* continue command example:              OpenRISC 1000 Example.
1519
                                                              (line 155)
1520
* continuening the remote program:       OpenRISC 1000 Example.
1521
                                                              (line 155)
1522
* contributors, OpenRISC 1000:           Contributors.        (line   9)
1523
* contributors, unknown:                 Contributors.        (line  25)
1524
* custom commands, OpenRISC 1000:        OpenRISC 1000 Specific Commands.
1525
                                                              (line   6)
1526
* ddd:                                   Summary.             (line  32)
1527
* Debug interface types:                 Remote JTAG Connection.
1528
                                                              (line  33)
1529
* direct OpenRISC 1000 target, connecting <1>: Direct JTAG Connection.
1530
                                                              (line   6)
1531
* direct OpenRISC 1000 target, connecting: Connecting to the Target.
1532
                                                              (line   8)
1533
* direct target jtag command:            Direct JTAG Connection.
1534
                                                              (line  10)
1535
* direct target specification:           Direct JTAG Connection.
1536
                                                              (line  10)
1537
* Embecosm:                              Contributors.        (line  22)
1538
* examples:                              OpenRISC 1000 Example.
1539
                                                              (line   6)
1540
* examples, breakpoint command:          OpenRISC 1000 Example.
1541
                                                              (line 155)
1542
* examples, bt command:                  OpenRISC 1000 Example.
1543
                                                              (line 136)
1544
* examples, continue command:            OpenRISC 1000 Example.
1545
                                                              (line 155)
1546
* examples, continuing a program:        OpenRISC 1000 Example.
1547
                                                              (line 155)
1548
* examples, Hello World:                 OpenRISC 1000 Example.
1549
                                                              (line   6)
1550
* examples, info spr command:            OpenRISC 1000 Example.
1551
                                                              (line 136)
1552
* examples, program loading:             OpenRISC 1000 Example.
1553
                                                              (line 124)
1554
* examples, remote target remote command: OpenRISC 1000 Example.
1555
                                                              (line 116)
1556
* examples, remote target specification via RSP: OpenRISC 1000 Example.
1557
                                                              (line 116)
1558
* examples, set command:                 OpenRISC 1000 Example.
1559
                                                              (line 211)
1560
* examples, step command:                OpenRISC 1000 Example.
1561
                                                              (line 167)
1562
* examples, symbol file loading:         OpenRISC 1000 Example.
1563
                                                              (line 103)
1564
* FDL, GNU Free Documentation License:   GNU Free Documentation License.
1565
                                                              (line   6)
1566
* Forin, Alessandro:                     Contributors.        (line  16)
1567
* GDB 5.3, differences in port of GDB version 6.8: OpenRISC 1000 Limitations.
1568
                                                              (line  23)
1569
* GDB interface, OpenRISC 1000:          Contributors.        (line  16)
1570
* gdbtui:                                Summary.             (line  32)
1571
* graphical debugging:                   Summary.             (line  32)
1572
* graphical debugging, ddd:              Summary.             (line  32)
1573
* graphical debugging, gdbtui:           Summary.             (line  32)
1574
* Guzvinex, Ivan:                        Contributors.        (line  13)
1575
* Hello World example:                   OpenRISC 1000 Example.
1576
                                                              (line   6)
1577
* Igor Mohor:                            Remote JTAG Connection.
1578
                                                              (line  33)
1579
* info registers command  for OpenRISC 1000: Summary.         (line  26)
1580
* info spr command <1>:                  Reading SPRs.        (line   6)
1581
* info spr command <2>:                  OpenRISC 1000 Specific Commands.
1582
                                                              (line   6)
1583
* info spr command:                      Summary.             (line  21)
1584
* info spr command example:              OpenRISC 1000 Example.
1585
                                                              (line 136)
1586
* info spr command, argument specification: Reading SPRs.     (line   6)
1587
* info spr command, complete group:      Reading SPRs.        (line  21)
1588
* info spr command, single register:     Reading SPRs.        (line   6)
1589
* Ivan Guzvinex:                         Contributors.        (line  13)
1590
* Jeremy Bennett:                        Contributors.        (line  22)
1591
* Johan Rydverg:                         Contributors.        (line  13)
1592
* JTAG:                                  Summary.             (line  15)
1593
* JTAG, OpenRISC 1000 interface:         Contributors.        (line  19)
1594
* JTAG, remote connection robustness:    OpenRISC 1000 Limitations.
1595
                                                              (line  17)
1596
* JTAG, robustness or remote interface:  Remote JTAG Connection.
1597
                                                              (line  69)
1598
* jtag, target:                          Summary.             (line  15)
1599
* known problems:                        OpenRISC 1000 Limitations.
1600
                                                              (line   6)
1601
* known problems, architectural compatability: OpenRISC 1000 Limitations.
1602
                                                              (line  23)
1603
* known problems, Or1ksim architectural simulator: OpenRISC 1000 Limitations.
1604
                                                              (line  31)
1605
* known problems, remote JTAG connection robustness: OpenRISC 1000 Limitations.
1606
                                                              (line  17)
1607
* known problems, watchpoints:           OpenRISC 1000 Limitations.
1608
                                                              (line   8)
1609
* local OpenRISC 1000 target, connecting <1>: Direct JTAG Connection.
1610
                                                              (line   6)
1611
* local OpenRISC 1000 target, connecting: Connecting to the Target.
1612
                                                              (line   8)
1613
* local target jtag command:             Direct JTAG Connection.
1614
                                                              (line  10)
1615
* local target specification:            Direct JTAG Connection.
1616
                                                              (line  10)
1617
* Mark Mlinar:                           Contributors.        (line  19)
1618
* Mlinar, Mark:                          Contributors.        (line  19)
1619
* Mohor, Igor:                           Remote JTAG Connection.
1620
                                                              (line  33)
1621
* OpenRISC 1000 Architectural Simulator: Connecting to the Target.
1622
                                                              (line  25)
1623
* OpenRISC 1000 Architectural Simulator, configuration: OpenRISC 1000 Example.
1624
                                                              (line  74)
1625
* OpenRISC 1000 Architectural Simulator, patch: Connecting to the Target.
1626
                                                              (line  25)
1627
* OpenRISC 1000 JTAG interface:          Contributors.        (line  19)
1628
* OpenRISC 1000 specific commands:       Summary.             (line  21)
1629
* OpenRISC 1000 target, connecting:      Connecting to the Target.
1630
                                                              (line   6)
1631
* OpenRISC 1000 target, direct connecting <1>: Direct JTAG Connection.
1632
                                                              (line   6)
1633
* OpenRISC 1000 target, direct connecting: Connecting to the Target.
1634
                                                              (line   8)
1635
* OpenRISC 1000 target, local connecting <1>: Direct JTAG Connection.
1636
                                                              (line   6)
1637
* OpenRISC 1000 target, local connecting: Connecting to the Target.
1638
                                                              (line   8)
1639
* OpenRISC 1000 target, remote connecting: Remote JTAG Connection.
1640
                                                              (line   6)
1641
* OpenRISC 1000 target, remote connecting via JTAG: Connecting to the Target.
1642
                                                              (line  16)
1643
* OpenRISC 1000 target, remote connecting via RSP <1>: Remote Serial Protocol Connection.
1644
                                                              (line   6)
1645
* OpenRISC 1000 target, remote connecting via RSP: Connecting to the Target.
1646
                                                              (line  11)
1647
* OpenRISC 1000, custom commands:        OpenRISC 1000 Specific Commands.
1648
                                                              (line   6)
1649
* OpenRISC 1000, known GDB problems:     OpenRISC 1000 Limitations.
1650
                                                              (line   6)
1651
* Or1ksim:                               Connecting to the Target.
1652
                                                              (line  25)
1653
* Or1ksim, bugs fixed:                   OpenRISC 1000 Limitations.
1654
                                                              (line  31)
1655
* Or1ksim, configuration:                OpenRISC 1000 Example.
1656
                                                              (line  74)
1657
* Or1ksim, patch:                        Connecting to the Target.
1658
                                                              (line  25)
1659
* Overview:                              Summary.             (line   6)
1660
* patch, OpenRISC 1000 Architectural Simulator: Connecting to the Target.
1661
                                                              (line  25)
1662
* patch, Or1ksim:                        Connecting to the Target.
1663
                                                              (line  25)
1664
* Per Bothner:                           Contributors.        (line  16)
1665
* program loading:                       OpenRISC 1000 Example.
1666
                                                              (line 124)
1667
* program loading, example:              OpenRISC 1000 Example.
1668
                                                              (line 124)
1669
* program loading, remote:               OpenRISC 1000 Example.
1670
                                                              (line 124)
1671
* remote JTAG, connection robustness:    OpenRISC 1000 Limitations.
1672
                                                              (line  17)
1673
* remote OpenRISC 1000 target, connecting: Remote JTAG Connection.
1674
                                                              (line   6)
1675
* remote OpenRISC 1000 target, connecting via JTAG: Connecting to the Target.
1676
                                                              (line  16)
1677
* remote OpenRISC 1000 target, connecting via RSP <1>: Remote Serial Protocol Connection.
1678
                                                              (line   6)
1679
* remote OpenRISC 1000 target, connecting via RSP: Connecting to the Target.
1680
                                                              (line  11)
1681
* remote program loading, example:       OpenRISC 1000 Example.
1682
                                                              (line 124)
1683
* remote program restart:                OpenRISC 1000 Example.
1684
                                                              (line 211)
1685
* remote program termination:            OpenRISC 1000 Example.
1686
                                                              (line 201)
1687
* Remote Serial Protocol <1>:            Remote JTAG Connection.
1688
                                                              (line  69)
1689
* Remote Serial Protocol:                Summary.             (line   9)
1690
* remote target jtag command <1>:        Remote JTAG Connection.
1691
                                                              (line  24)
1692
* remote target jtag command:            Remote Serial Protocol Connection.
1693
                                                              (line  21)
1694
* remote target remote command, example: OpenRISC 1000 Example.
1695
                                                              (line 116)
1696
* remote target specification:           Remote JTAG Connection.
1697
                                                              (line  24)
1698
* remote target specification for RSP:   Remote Serial Protocol Connection.
1699
                                                              (line  21)
1700
* remote target specification via RSP, example: OpenRISC 1000 Example.
1701
                                                              (line 116)
1702
* remote target specification, same machine: Remote JTAG Connection.
1703
                                                              (line  31)
1704
* remote target specification, same machine for RSP: Remote Serial Protocol Connection.
1705
                                                              (line  27)
1706
* Reporting bugs:                        OpenRISC 1000 Limitations.
1707
                                                              (line  41)
1708
* reset:                                 Remote JTAG Connection.
1709
                                                              (line  61)
1710
* resetting the target:                  Remote JTAG Connection.
1711
                                                              (line  61)
1712
* restart, remote program:               OpenRISC 1000 Example.
1713
                                                              (line 211)
1714
* robustness, OpenRISC remote JTAG interface: Remote JTAG Connection.
1715
                                                              (line  69)
1716
* RSP <1>:                               Remote JTAG Connection.
1717
                                                              (line  69)
1718
* RSP:                                   Summary.             (line   9)
1719
* Rydverg, Johan:                        Contributors.        (line  13)
1720
* set command example:                   OpenRISC 1000 Example.
1721
                                                              (line 211)
1722
* Special Purpose Registers:             Summary.             (line  21)
1723
* SPR:                                   Summary.             (line  21)
1724
* spr command <1>:                       Writing SPRs.        (line   6)
1725
* spr command <2>:                       OpenRISC 1000 Specific Commands.
1726
                                                              (line   6)
1727
* spr command:                           Summary.             (line  21)
1728
* spr command, argument specification:   Writing SPRs.        (line   6)
1729
* step command example:                  OpenRISC 1000 Example.
1730
                                                              (line 167)
1731
* Summary:                               Summary.             (line   6)
1732
* symbol file loading:                   OpenRISC 1000 Example.
1733
                                                              (line 103)
1734
* symbols when remote debugging:         OpenRISC 1000 Example.
1735
                                                              (line 103)
1736
* target extended-remote command:        Connecting to the Target.
1737
                                                              (line  11)
1738
* target jtag:                           Summary.             (line  15)
1739
* target jtag command:                   Connecting to the Target.
1740
                                                              (line   8)
1741
* target jtag command, direct:           Direct JTAG Connection.
1742
                                                              (line  10)
1743
* target jtag command, direct, testing:  Direct JTAG Connection.
1744
                                                              (line  12)
1745
* target jtag command, local:            Direct JTAG Connection.
1746
                                                              (line  10)
1747
* target jtag command, local, testing:   Direct JTAG Connection.
1748
                                                              (line  12)
1749
* target jtag command, remote <1>:       Remote JTAG Connection.
1750
                                                              (line  24)
1751
* target jtag command, remote:           Remote Serial Protocol Connection.
1752
                                                              (line  21)
1753
* target remote command:                 Connecting to the Target.
1754
                                                              (line  11)
1755
* target remote command, remote, example: OpenRISC 1000 Example.
1756
                                                              (line 116)
1757
* target reset:                          Remote JTAG Connection.
1758
                                                              (line  61)
1759
* target specification for RSP:          Remote Serial Protocol Connection.
1760
                                                              (line  21)
1761
* target specification for RSP, same machine: Remote Serial Protocol Connection.
1762
                                                              (line  27)
1763
* target specification, direct:          Direct JTAG Connection.
1764
                                                              (line  10)
1765
* target specification, local:           Direct JTAG Connection.
1766
                                                              (line  10)
1767
* target specification, remote:          Remote JTAG Connection.
1768
                                                              (line  24)
1769
* target specification, remote via RSP, example: OpenRISC 1000 Example.
1770
                                                              (line 116)
1771
* target specification, same machine:    Remote JTAG Connection.
1772
                                                              (line  31)
1773
* target, direct, OpenRISC 1000, connecting <1>: Direct JTAG Connection.
1774
                                                              (line   6)
1775
* target, direct, OpenRISC 1000, connecting: Connecting to the Target.
1776
                                                              (line   8)
1777
* target, local, OpenRISC 1000, connecting <1>: Direct JTAG Connection.
1778
                                                              (line   6)
1779
* target, local, OpenRISC 1000, connecting: Connecting to the Target.
1780
                                                              (line   8)
1781
* target, OpenRISC 1000, connecting:     Connecting to the Target.
1782
                                                              (line   6)
1783
* target, remote, OpenRISC 1000, connecting: Remote JTAG Connection.
1784
                                                              (line   6)
1785
* target, remote, OpenRISC 1000, connecting via JTAG: Connecting to the Target.
1786
                                                              (line  16)
1787
* target, remote, OpenRISC 1000, connecting via RSP <1>: Remote Serial Protocol Connection.
1788
                                                              (line   6)
1789
 
1790
 
1791
* Ziomkowski, Chris:                     Contributors.        (line  19)
1792
1793
1794

1795
Tag Table:
1796
Node: Top839
1797
Node: Summary1747
1798
Node: Contributors3516
1799
Node: Connecting to the Target4611
1800
Node: Direct JTAG Connection6534
1801
Node: Remote Serial Protocol Connection7326
1802
Node: Remote JTAG Connection8537
1803
Node: OpenRISC 1000 Specific Commands11552
1804
Node: Reading SPRs12773
1805
Node: Writing SPRs13795
1806
Node: OpenRISC 1000 Example14422
1807
Node: OpenRISC 1000 Limitations20903
1808
Node: Copying23115
1809
Node: GNU Free Documentation License42340

powered by: WebSVN 2.1.0

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