| Line 1... |
Line 1... |
This is ../../or1ksim/doc/or1ksim.info, produced by makeinfo version
|
This is ../../doc/or1ksim.info, produced by makeinfo version 4.13 from
|
4.13 from ../../or1ksim/doc/or1ksim.texi.
|
../../doc/or1ksim.texi.
|
|
|
INFO-DIR-SECTION Embedded development
|
INFO-DIR-SECTION Embedded development
|
START-INFO-DIR-ENTRY
|
START-INFO-DIR-ENTRY
|
* Or1ksim: (or32-uclinux-or1ksim). The OpenRISC 1000 Architectural
|
* Or1ksim: (or32-uclinux-or1ksim). The OpenRISC 1000 Architectural
|
Simulator
|
Simulator
|
| Line 62... |
Line 62... |
===============
|
===============
|
|
|
Unpack the software and create a _separate_ directory in which to build
|
Unpack the software and create a _separate_ directory in which to build
|
it:
|
it:
|
|
|
tar jxf or1ksim-2010-11-26.tar.bz2
|
tar jxf or1ksim-2010-12-08.tar.bz2
|
mkdir builddir_or1ksim
|
mkdir builddir_or1ksim
|
cd builddir_or1ksim
|
cd builddir_or1ksim
|
|
|
|
|
File: or1ksim.info, Node: Configuring the Build, Next: Build and Install, Prev: Preparation, Up: Installation
|
File: or1ksim.info, Node: Configuring the Build, Next: Build and Install, Prev: Preparation, Up: Installation
|
| Line 79... |
Line 79... |
|
|
The most significant argument is `--target', which should specify the
|
The most significant argument is `--target', which should specify the
|
OpenRISC 1000 32-bit architecture. If this argument is omitted, it will
|
OpenRISC 1000 32-bit architecture. If this argument is omitted, it will
|
default to OpenRISC 1000 32-bit with a warning
|
default to OpenRISC 1000 32-bit with a warning
|
|
|
../or1ksim-2010-11-26/configure --target=or32-uclinux ...
|
../or1ksim-2010-12-08/configure --target=or32-uclinux ...
|
|
|
There are several other options available, many of which are standard
|
There are several other options available, many of which are standard
|
to GNU `configure' scripts. Use `configure --help' to see all the
|
to GNU `configure' scripts. Use `configure --help' to see all the
|
options. The most useful is `--prefix' to specify a directory for
|
options. The most useful is `--prefix' to specify a directory for
|
installation of the tools.
|
installation of the tools.
|
| Line 284... |
Line 284... |
|
|
* Standalone Simulator::
|
* Standalone Simulator::
|
* Profiling Utility::
|
* Profiling Utility::
|
* Memory Profiling Utility::
|
* Memory Profiling Utility::
|
* Simulator Library::
|
* Simulator Library::
|
|
* Ethernet TUN/TAP Interface::
|
|
|
|
|
File: or1ksim.info, Node: Standalone Simulator, Next: Profiling Utility, Up: Usage
|
File: or1ksim.info, Node: Standalone Simulator, Next: Profiling Utility, Up: Usage
|
|
|
2.1 Standalone Simulator
|
2.1 Standalone Simulator
|
| Line 507... |
Line 508... |
FROM and TO are respectively the start and end address of the
|
FROM and TO are respectively the start and end address of the
|
region of memory to be analysed.
|
region of memory to be analysed.
|
|
|
|
|
|
|
File: or1ksim.info, Node: Simulator Library, Prev: Memory Profiling Utility, Up: Usage
|
File: or1ksim.info, Node: Simulator Library, Next: Ethernet TUN/TAP Interface, Prev: Memory Profiling Utility, Up: Usage
|
|
|
2.4 Simulator Library
|
2.4 Simulator Library
|
=====================
|
=====================
|
|
|
Or1ksim may be used as a static of dynamic library, `libsim.a' or
|
Or1ksim may be used as a static of dynamic library, `libsim.a' or
|
| Line 755... |
Line 756... |
|
|
* Add the library directory to `/etc/ld.so.conf'
|
* Add the library directory to `/etc/ld.so.conf'
|
|
|
|
|
|
|
|
File: or1ksim.info, Node: Ethernet TUN/TAP Interface, Prev: Simulator Library, Up: Usage
|
|
|
|
2.5 Ethernet TUN/TAP Interface
|
|
==============================
|
|
|
|
When an Ethernet peripheral is configured (*note Ethernet
|
|
Configuration: Ethernet Configuration.), one option is to tunnel
|
|
traffic through a TUN/TAP interface. The low level TAP interface is
|
|
used to tunnel raw Ethernet datagrams.
|
|
|
|
The TAP interface can then be connected to a physical Ethernet through a
|
|
bridge, allowing the Or1ksim model to connect to a physical network.
|
|
This is particularly when Or1ksim is running the OpenRISC Linux kernel
|
|
image.
|
|
|
|
This section explains how to set up a bridge for use by Or1ksim. It does
|
|
require superuser access to the host machine (or at least the relevant
|
|
network capabilities). A system administrator can modify these
|
|
guidelines so they are executed on reboot if appropriate.
|
|
|
|
* Menu:
|
|
|
|
* Setting Up a Persistent TAP device::
|
|
* Establishing a Bridge::
|
|
* Opening the Firewall::
|
|
* Disabling Ethernet Filtering::
|
|
* Networking from OpenRISC Linux and BusyBox::
|
|
* Tearing Down a Bridge::
|
|
|
|
|
|
File: or1ksim.info, Node: Setting Up a Persistent TAP device, Next: Establishing a Bridge, Up: Ethernet TUN/TAP Interface
|
|
|
|
2.5.1 Setting Up a Persistent TAP device
|
|
----------------------------------------
|
|
|
|
TUN/TAP devices can be created dynamically, but this requires superuser
|
|
privileges (or at least `CAP_NET_ADMIN' capability). The solution is
|
|
to create a persistent TAP device. This can be done using either
|
|
`openvpn' or `tunctl'. In either case the package must be installed on
|
|
the host system. Using `openvpn', the following would set up a TAP
|
|
interface for a specified user and group.
|
|
|
|
openvpn --mktun --dev tap_n_ --user _username_ --group _groupname_
|
|
|
|
|
|
File: or1ksim.info, Node: Establishing a Bridge, Next: Opening the Firewall, Prev: Setting Up a Persistent TAP device, Up: Ethernet TUN/TAP Interface
|
|
|
|
2.5.2 Establishing a Bridge
|
|
---------------------------
|
|
|
|
A bridge is a "virtual" local area network interfaces, subsuming two or
|
|
more existing network interfaces. In this case we will bridge the
|
|
physical Ethernet interface of the host with the TAP interface that
|
|
will be used by Or1ksim.
|
|
|
|
The Ethernet and TAP must lose their own individual IP addresses (by
|
|
setting them to 0.0.0.0) and are replaced by the IP address of the
|
|
bridge interface. To do this we use the `bridge-utils' package, which
|
|
must be installed on the host system. These commands are require
|
|
superuser privileges or `CAP_NET_ADMIN' capability. To create a new
|
|
interface `br_n_' the following commands are appropriate.
|
|
|
|
brctl addbr br_n_
|
|
brctl addif br_n_ eth_x_
|
|
brctl addif br_n_ tap_y_
|
|
|
|
ifconfig eth_x_ 0.0.0.0 promisc up
|
|
ifconfig tap_y_ 0.0.0.0 promisc up
|
|
|
|
dhclient br_n_
|
|
|
|
The last command instructs the bridge to obtain its IP address, netmask,
|
|
broadcast address, gateway and nameserver information using DHCP. In a
|
|
network without DHCP it should be replaced by `ifconfig' to set a
|
|
static IP address, netmask and broadcast address.
|
|
|
|
Note: This will leave a spare dhclient process running in the
|
|
background, which should be killed for tidiness. There is a
|
|
technique to avoid this using `omshell', but that is beyond the
|
|
scope of this guide.
|
|
|
|
Note: It is not clear to the author why the existing interfaces
|
|
need to be brought up in promiscuous mode, but it seems to cure
|
|
various problems.
|
|
|
|
|
|
File: or1ksim.info, Node: Opening the Firewall, Next: Disabling Ethernet Filtering, Prev: Establishing a Bridge, Up: Ethernet TUN/TAP Interface
|
|
|
|
2.5.3 Opening the Firewall
|
|
--------------------------
|
|
|
|
Firewall rules should be added to ensure traffic flows freely through
|
|
the TAP and bridge interfaces. As superuser the following commands are
|
|
appropriate.
|
|
|
|
iptables -A INPUT -i tap_y_ -j ACCEPT
|
|
iptables -A INPUT -i br_n_ -j ACCEPT
|
|
iptables -A FORWARD -i br_n_ -j ACCEPT
|
|
|
|
|
|
File: or1ksim.info, Node: Disabling Ethernet Filtering, Next: Networking from OpenRISC Linux and BusyBox, Prev: Opening the Firewall, Up: Ethernet TUN/TAP Interface
|
|
|
|
2.5.4 Disabling Ethernet Filtering
|
|
----------------------------------
|
|
|
|
Some systems may have ethernet filtering enabled (`ebtables',
|
|
`bridge-nf', `arptables') which will stop traffic flowing through the
|
|
bridge.
|
|
|
|
The easiest way to disable this is by writing zero to all `bridge-nf-*'
|
|
entries in `/proc/sys/net/bridge'. As superuser the following commands
|
|
will achieve this.
|
|
|
|
cd /proc/sys/net/bridge
|
|
for f in bridge-nf-*; do echo 0 > $f; done
|
|
|
|
|
|
File: or1ksim.info, Node: Networking from OpenRISC Linux and BusyBox, Next: Tearing Down a Bridge, Prev: Disabling Ethernet Filtering, Up: Ethernet TUN/TAP Interface
|
|
|
|
2.5.5 Networking from OpenRISC Linux and BusyBox
|
|
------------------------------------------------
|
|
|
|
The main use of this style of Ethernet interface to Or1ksim is when
|
|
running the OpenRISC Linux kernel with BusyBox. The following commands
|
|
in the BusyBox console window will configure the Ethernet interface
|
|
(assumed to be `eth0') and bring it up with a DHCP assigned address.
|
|
|
|
ifconfig eth0
|
|
ifup eth0
|
|
|
|
At this stage interface to IP addresses will work correctly.
|
|
|
|
For DNS to work the BusyBox system needs to know where to find a
|
|
nameserver. Under BusyBox, `udhcp' does not configure
|
|
`/etc/resolv.conf' automatically.
|
|
|
|
The solution is to duplicate the nameserver entry from the
|
|
`/etc/resolv.conf' file of the host on the BusyBox system. A typical
|
|
file might be as follows:
|
|
|
|
`nameserver 192.168.0.1'
|
|
|
|
It is convenient to make this permanent within the Linux initramfs. Add
|
|
the file as `arch/openrisc/support/initramfs/etc/resolv.conf' within
|
|
the Linux source tree and rebuild `vmlinux'. It will then be present
|
|
automatically.
|
|
|
|
One of the most useful functions that is possible is to mount the host
|
|
file system through NFS. For example, from the BusyBox console:
|
|
|
|
mount -t nfs -o nolock 192.168.0.60:/home /mnt
|
|
|
|
Another useful technique is to telnet into the BusyBox system from the
|
|
host. This is particularly valuable when a console process locks up,
|
|
since the `xterm' console will not recognize ctrl-C. Instead the rogue
|
|
process can be killed from a telnet connection.
|
|
|
|
|
|
File: or1ksim.info, Node: Tearing Down a Bridge, Prev: Networking from OpenRISC Linux and BusyBox, Up: Ethernet TUN/TAP Interface
|
|
|
|
2.5.6 Tearing Down a Bridge
|
|
---------------------------
|
|
|
|
There is little reason why a bridge should ever need to be torn down,
|
|
but if desired, the following commands will achieve the effect.
|
|
|
|
ifconfig br_n_ down
|
|
brctl delbr br_n_
|
|
|
|
dhclient eth_x_
|
|
|
|
As before this will leave a spare `dhclient' process in the background
|
|
which should be killed.
|
|
|
|
If desired the TAP interface can be deleted using
|
|
|
|
openvpn --rmtun -dev tap_y_
|
|
|
|
Caution: The TAP interface should not be in use when running this
|
|
command. For example any OpenRISC Linux/BusyBox sessions should be
|
|
closed first.
|
|
|
|
|
File: or1ksim.info, Node: Configuration, Next: Interactive Command Line, Prev: Usage, Up: Top
|
File: or1ksim.info, Node: Configuration, Next: Interactive Command Line, Prev: Usage, Up: Top
|
|
|
3 Configuration
|
3 Configuration
|
***************
|
***************
|
|
|
| Line 1946... |
Line 2130... |
File: or1ksim.info, Node: Ethernet Configuration, Next: GPIO Configuration, Prev: DMA Configuration, Up: Peripheral Configuration
|
File: or1ksim.info, Node: Ethernet Configuration, Next: GPIO Configuration, Prev: DMA Configuration, Up: Peripheral Configuration
|
|
|
3.4.4 Ethernet Configuration
|
3.4.4 Ethernet Configuration
|
----------------------------
|
----------------------------
|
|
|
The Ethernet MAC used in Or1ksim is the component implemented at
|
|
OpenCores, and found in the top level SVN directory, `ethmac'. It also
|
|
forms part of the OpenRISC SoC, ORPSoC. It is described in the
|
|
document `Ethernet IP Core Specification' by Igor Mohor, which can be
|
|
found in the `doc' subdirectory. It is a memory mapped component,
|
|
which resides on the main OpenRISC Wishbone data bus.
|
|
|
|
Ethernet configuration is described in `section ethernet'. This
|
Ethernet configuration is described in `section ethernet'. This
|
section may appear multiple times, specifying multiple Ethernet
|
section may appear multiple times, specifying multiple Ethernet
|
interfaces. The following parameters may be specified.
|
interfaces. The following parameters may be specified.
|
|
|
|
The Ethernet MAC used in Or1ksim corresponds to the Verilog
|
|
implementation in project "ethmac". It's source code can be found in
|
|
the top level SVN directory, `ethmac'. It also forms part of the
|
|
OpenRISC reference SoC, ORPSoC. It is described in the document
|
|
`Ethernet IP Core Specification' by Igor Mohor, which can be found in
|
|
the `doc' subdirectory. It is a memory mapped component, which resides
|
|
on the main OpenRISC Wishbone data bus.
|
|
|
`enabled = 0|1'
|
`enabled = 0|1'
|
If 1 (true, the default), this Ethernet MAC is enabled. If 0, it
|
If 1 (true, the default), this Ethernet MAC is enabled. If 0, it
|
is disabled.
|
is disabled.
|
|
|
`baseaddr = VALUE'
|
`baseaddr = VALUE'
|
| Line 1985... |
Line 2170... |
Configuration: DMA Configuration.).
|
Configuration: DMA Configuration.).
|
|
|
`irq = VALUE'
|
`irq = VALUE'
|
Use VALUE as the IRQ number of this Ethernet MAC. Default value 0.
|
Use VALUE as the IRQ number of this Ethernet MAC. Default value 0.
|
|
|
`rtx_type = 0|1'
|
`rtx_type = "file"|"tap"'
|
If 1 (true) use a socket interface to the Ethernet (see parameter
|
Specifies whether to use a TUN/TAP interface or file interface
|
`sockif' below). If 0 (the default), use a file interface,
|
(the default) to model the external connection of the Ethernet.
|
reading and writing from and to the files specified in the
|
|
`rxfile' and `txfile' parameters (see below).
|
If a TUN/TAP interface is requested, Ethernet packets will be sent
|
|
and received through the pesistent TAP interface specified in
|
Note: By default the socket interface is not provided in
|
parameter `tap_dev' (see below).
|
Or1ksim. If it is required, this must be requested when
|
|
configuring, by use of the `--enable-ethphy' option to
|
More details on configuring the TUN/TAP interface are given in the
|
`configure'.
|
Usage section (*note Ethernet TUN/TAP Interface: Ethernet TUN/TAP
|
|
Interface.).
|
configure --target=or32-uclinux --enable-ethphy ...
|
|
|
If a file interface (the default), is requested, the Ethernet will
|
|
be modelled by reading and writing from and to the files specified
|
|
in the `rxfile' and `txfile' parameters (see below).
|
|
|
|
Caution: If a file interface is specified, Or1ksim will
|
|
terminate once the receive file specified by `rxfile' is
|
|
exhausted.
|
|
|
`rx_channel = RXVALUE'
|
`rx_channel = RXVALUE'
|
`tx_channel = TXVALUE'
|
`tx_channel = TXVALUE'
|
RXVALUE specifies the DMA channel to use for receive and TXVALUE
|
RXVALUE specifies the DMA channel to use for receive and TXVALUE
|
the DMA channel to use for transmit. Both default to 0.
|
the DMA channel to use for transmit. Both default to 0.
|
| Line 2022... |
Line 2214... |
|
|
The input file must exist and be readable. The output file must be
|
The input file must exist and be readable. The output file must be
|
writable and will be created if necessary. If either of these
|
writable and will be created if necessary. If either of these
|
conditions is not met, a warning will be given.
|
conditions is not met, a warning will be given.
|
|
|
`sockif = "SERVICE"'
|
Caution: Or1ksim will terminate once the RXFILE is exhausted.
|
When `rtx_type' is 1 (see above), SERVICE specifies the service to
|
|
use for communication. This may be TCP/IP or UDP/IP. The default
|
`tap_dev = "TAP"'
|
value of this parameter is `"or1ksim_eth"'.
|
When `rtx_type' is `"tap"' (see above), TAP_DEV specifies the TAP
|
|
device to use for communication. This should be a persistent TAP
|
|
device configured for the system (*note Ethernet TUN/TAP
|
|
Interface: Ethernet TUN/TAP Interface.)
|
|
|
`vapi_id = VALUE'
|
`vapi_id = VALUE'
|
VALUE specifies the value of the Verification API (VAPI) base
|
VALUE specifies the value of the Verification API (VAPI) base
|
address to be used with the Ethernet PHY. *Note Verification API:
|
address to be used with the Ethernet PHY. *Note Verification API:
|
Verification API, for more details, which details the use of the
|
Verification API, for more details, which details the use of the
|
VAPI with the DMA controller.
|
VAPI with the DMA controller.
|
|
|
`phy_addr = VALUE'
|
`phy_addr = VALUE'
|
VALUE specifies address for emulated ethernet PHY. Defaults to 0
|
VALUE specifies the address for emulated ethernet PHY (default 0).
|
otherwise.
|
If there are multiple Ethernet peripherals, they should each have a
|
|
different PHY value.
|
|
|
|
|
|
|
File: or1ksim.info, Node: GPIO Configuration, Next: Display Interface Configuration, Prev: Ethernet Configuration, Up: Peripheral Configuration
|
File: or1ksim.info, Node: GPIO Configuration, Next: Display Interface Configuration, Prev: Ethernet Configuration, Up: Peripheral Configuration
|
|
|
| Line 3678... |
Line 3874... |
(line 32)
|
(line 32)
|
* baseaddr (ATA/ATAPI configuration): Disc Interface Configuration.
|
* baseaddr (ATA/ATAPI configuration): Disc Interface Configuration.
|
(line 26)
|
(line 26)
|
* baseaddr (DMA configuration): DMA Configuration. (line 24)
|
* baseaddr (DMA configuration): DMA Configuration. (line 24)
|
* baseaddr (Ethernet configuration): Ethernet Configuration.
|
* baseaddr (Ethernet configuration): Ethernet Configuration.
|
(line 22)
|
(line 23)
|
* baseaddr (frame buffer configuration): Frame Buffer Configuration.
|
* baseaddr (frame buffer configuration): Frame Buffer Configuration.
|
(line 20)
|
(line 20)
|
* baseaddr (generic peripheral configuration): Generic Peripheral Configuration.
|
* baseaddr (generic peripheral configuration): Generic Peripheral Configuration.
|
(line 22)
|
(line 22)
|
* baseaddr (GPIO configuration): GPIO Configuration. (line 21)
|
* baseaddr (GPIO configuration): GPIO Configuration. (line 21)
|
| Line 3706... |
Line 3902... |
(line 60)
|
(line 60)
|
* breakpoint set/clear (Interactive CLI): Interactive Command Line.
|
* breakpoint set/clear (Interactive CLI): Interactive Command Line.
|
(line 57)
|
(line 57)
|
* breaks (Interactive CLI): Interactive Command Line.
|
* breaks (Interactive CLI): Interactive Command Line.
|
(line 60)
|
(line 60)
|
|
* bridge setup: Establishing a Bridge.
|
|
(line 6)
|
* btic (branch prediction configuration): Branch Prediction Configuration.
|
* btic (branch prediction configuration): Branch Prediction Configuration.
|
(line 19)
|
(line 19)
|
|
* BusyBox and Ethernet: Networking from OpenRISC Linux and BusyBox.
|
|
(line 6)
|
* byte_enabled (generic peripheral configuration): Generic Peripheral Configuration.
|
* byte_enabled (generic peripheral configuration): Generic Peripheral Configuration.
|
(line 48)
|
(line 48)
|
* cache configuration: Cache Configuration. (line 6)
|
* cache configuration: Cache Configuration. (line 6)
|
* calling_convention (CUC configuration): CUC Configuration. (line 37)
|
* calling_convention (CUC configuration): CUC Configuration. (line 37)
|
* ce (memory configuration): Memory Configuration.
|
* ce (memory configuration): Memory Configuration.
|
| Line 3779... |
Line 3979... |
(line 6)
|
(line 6)
|
* configuring the debug unit and interface to external debuggers: Debug Interface Configuration.
|
* configuring the debug unit and interface to external debuggers: Debug Interface Configuration.
|
(line 6)
|
(line 6)
|
* configuring the Ethernet interface: Ethernet Configuration.
|
* configuring the Ethernet interface: Ethernet Configuration.
|
(line 6)
|
(line 6)
|
|
* configuring the Ethernet TUN/TAP interface: Ethernet TUN/TAP Interface.
|
|
(line 6)
|
* configuring the frame buffer: Frame Buffer Configuration.
|
* configuring the frame buffer: Frame Buffer Configuration.
|
(line 6)
|
(line 6)
|
* configuring the GPIO: GPIO Configuration. (line 6)
|
* configuring the GPIO: GPIO Configuration. (line 6)
|
* configuring the interrupt controller: Interrupt Configuration.
|
* configuring the interrupt controller: Interrupt Configuration.
|
(line 6)
|
(line 6)
|
| Line 3848... |
Line 4050... |
* displaying registers (Interactive CLI): Interactive Command Line.
|
* displaying registers (Interactive CLI): Interactive Command Line.
|
(line 14)
|
(line 14)
|
* dm (Interactive CLI): Interactive Command Line.
|
* dm (Interactive CLI): Interactive Command Line.
|
(line 31)
|
(line 31)
|
* dma (Ethernet configuration): Ethernet Configuration.
|
* dma (Ethernet configuration): Ethernet Configuration.
|
(line 33)
|
(line 34)
|
* DMA configuration: DMA Configuration. (line 6)
|
* DMA configuration: DMA Configuration. (line 6)
|
* DMA verification (VAPI): Verification API. (line 73)
|
* DMA verification (VAPI): Verification API. (line 73)
|
* dma_mode0_td (ATA/ATAPI configuration): Disc Interface Configuration.
|
* dma_mode0_td (ATA/ATAPI configuration): Disc Interface Configuration.
|
(line 74)
|
(line 74)
|
* dma_mode0_teoc (ATA/ATAPI configuration): Disc Interface Configuration.
|
* dma_mode0_teoc (ATA/ATAPI configuration): Disc Interface Configuration.
|
| Line 3883... |
Line 4085... |
* enabled (cache configuration): Cache Configuration. (line 11)
|
* enabled (cache configuration): Cache Configuration. (line 11)
|
* enabled (debug interface configuration): Debug Interface Configuration.
|
* enabled (debug interface configuration): Debug Interface Configuration.
|
(line 11)
|
(line 11)
|
* enabled (DMA configuration): DMA Configuration. (line 20)
|
* enabled (DMA configuration): DMA Configuration. (line 20)
|
* enabled (Ethernet configuration): Ethernet Configuration.
|
* enabled (Ethernet configuration): Ethernet Configuration.
|
(line 18)
|
(line 19)
|
* enabled (frame buffer configuration): Frame Buffer Configuration.
|
* enabled (frame buffer configuration): Frame Buffer Configuration.
|
(line 16)
|
(line 16)
|
* enabled (generic peripheral configuration): Generic Peripheral Configuration.
|
* enabled (generic peripheral configuration): Generic Peripheral Configuration.
|
(line 18)
|
(line 18)
|
* enabled (GPIO configuration): GPIO Configuration. (line 17)
|
* enabled (GPIO configuration): GPIO Configuration. (line 17)
|
| Line 3910... |
Line 4112... |
(line 59)
|
(line 59)
|
* entrysize (MMU configuration): Memory Management Configuration.
|
* entrysize (MMU configuration): Memory Management Configuration.
|
(line 32)
|
(line 32)
|
* ETH_VAPI_CTRL (Ethernet verification): Verification API. (line 86)
|
* ETH_VAPI_CTRL (Ethernet verification): Verification API. (line 86)
|
* ETH_VAPI_DATA (Ethernet verification): Verification API. (line 84)
|
* ETH_VAPI_DATA (Ethernet verification): Verification API. (line 84)
|
|
* Ethernet bridge setup: Establishing a Bridge.
|
|
(line 6)
|
* Ethernet configuration: Ethernet Configuration.
|
* Ethernet configuration: Ethernet Configuration.
|
(line 6)
|
(line 6)
|
* Ethernet verification (VAPI): Verification API. (line 78)
|
* Ethernet verification (VAPI): Verification API. (line 78)
|
* Ethernet via socket, enabling: Configuring the Build.
|
* Ethernet via socket, enabling: Configuring the Build.
|
(line 59)
|
(line 59)
|
| Line 3951... |
Line 4155... |
(line 51)
|
(line 51)
|
* filename (frame buffer configuration - deprecated): Frame Buffer Configuration.
|
* filename (frame buffer configuration - deprecated): Frame Buffer Configuration.
|
(line 36)
|
(line 36)
|
* filename (VGA configuration - deprecated): Display Interface Configuration.
|
* filename (VGA configuration - deprecated): Display Interface Configuration.
|
(line 47)
|
(line 47)
|
|
* firewall with Ethernet bridge and TAP/TUN: Opening the Firewall.
|
|
(line 6)
|
* firmware (ATA/ATAPI device configuration): Disc Interface Configuration.
|
* firmware (ATA/ATAPI device configuration): Disc Interface Configuration.
|
(line 121)
|
(line 121)
|
* flag setting by instructions: Configuring the Build.
|
* flag setting by instructions: Configuring the Build.
|
(line 118)
|
(line 118)
|
* frame buffer configuration: Frame Buffer Configuration.
|
* frame buffer configuration: Frame Buffer Configuration.
|
| Line 4024... |
Line 4230... |
* keyboard configuration: Keyboard Configuration.
|
* keyboard configuration: Keyboard Configuration.
|
(line 6)
|
(line 6)
|
* library version of Or1ksim: Simulator Library. (line 6)
|
* library version of Or1ksim: Simulator Library. (line 6)
|
* license for Or1ksim: GNU Free Documentation License.
|
* license for Or1ksim: GNU Free Documentation License.
|
(line 6)
|
(line 6)
|
|
* Linux (OpenRISC) and Ethernet: Networking from OpenRISC Linux and BusyBox.
|
|
(line 6)
|
* list breakpoints (Interactive CLI): Interactive Command Line.
|
* list breakpoints (Interactive CLI): Interactive Command Line.
|
(line 60)
|
(line 60)
|
* load_hitdelay (data cache configuration): Cache Configuration.
|
* load_hitdelay (data cache configuration): Cache Configuration.
|
(line 46)
|
(line 46)
|
* load_missdelay (data cache configuration): Cache Configuration.
|
* load_missdelay (data cache configuration): Cache Configuration.
|
| Line 4129... |
Line 4337... |
(line 51)
|
(line 51)
|
* pattern (memory configuration): Memory Configuration.
|
* pattern (memory configuration): Memory Configuration.
|
(line 82)
|
(line 82)
|
* pc (Interactive CLI): Interactive Command Line.
|
* pc (Interactive CLI): Interactive Command Line.
|
(line 51)
|
(line 51)
|
|
* persistent TAP device creation: Setting Up a Persistent TAP device.
|
|
(line 6)
|
* phy_addr: Ethernet Configuration.
|
* phy_addr: Ethernet Configuration.
|
(line 94)
|
(line 105)
|
* PIC configuration: Interrupt Configuration.
|
* PIC configuration: Interrupt Configuration.
|
(line 6)
|
(line 6)
|
* pio (ATA/ATAPI device configuration): Disc Interface Configuration.
|
* pio (ATA/ATAPI device configuration): Disc Interface Configuration.
|
(line 136)
|
(line 136)
|
* pio_mode0_t1 (ATA/ATAPI configuration): Disc Interface Configuration.
|
* pio_mode0_t1 (ATA/ATAPI configuration): Disc Interface Configuration.
|
| Line 4235... |
Line 4445... |
* rsp_enabled (debug interface configuration): Debug Interface Configuration.
|
* rsp_enabled (debug interface configuration): Debug Interface Configuration.
|
(line 20)
|
(line 20)
|
* rsp_port (debug interface configuration): Debug Interface Configuration.
|
* rsp_port (debug interface configuration): Debug Interface Configuration.
|
(line 32)
|
(line 32)
|
* rtx_type (Ethernet configuration): Ethernet Configuration.
|
* rtx_type (Ethernet configuration): Ethernet Configuration.
|
(line 46)
|
(line 47)
|
* run (Interactive CLI): Interactive Command Line.
|
* run (Interactive CLI): Interactive Command Line.
|
(line 23)
|
(line 23)
|
* running code (Interactive CLI): Interactive Command Line.
|
* running code (Interactive CLI): Interactive Command Line.
|
(line 23)
|
(line 23)
|
* running Or1ksim: Usage. (line 6)
|
* running Or1ksim: Usage. (line 6)
|
| Line 4253... |
Line 4463... |
* runtime.cuc: Global Data Structures.
|
* runtime.cuc: Global Data Structures.
|
(line 62)
|
(line 62)
|
* runtime.vapi: Global Data Structures.
|
* runtime.vapi: Global Data Structures.
|
(line 62)
|
(line 62)
|
* rx_channel (Ethernet configuration): Ethernet Configuration.
|
* rx_channel (Ethernet configuration): Ethernet Configuration.
|
(line 59)
|
(line 67)
|
* rxfile (Ethernet configuration): Ethernet Configuration.
|
* rxfile (Ethernet configuration): Ethernet Configuration.
|
(line 68)
|
(line 76)
|
* sbp_bf_fwd (branch prediction configuration): Branch Prediction Configuration.
|
* sbp_bf_fwd (branch prediction configuration): Branch Prediction Configuration.
|
(line 23)
|
(line 23)
|
* sbp_bnf_fwd (branch prediction configuration): Branch Prediction Configuration.
|
* sbp_bnf_fwd (branch prediction configuration): Branch Prediction Configuration.
|
(line 28)
|
(line 28)
|
* sbuf_len (CPU configuration): CPU Configuration. (line 101)
|
* sbuf_len (CPU configuration): CPU Configuration. (line 101)
|
| Line 4334... |
Line 4544... |
(line 16)
|
(line 16)
|
* slow down factor (power management register): Power Management Configuration.
|
* slow down factor (power management register): Power Management Configuration.
|
(line 12)
|
(line 12)
|
* SME (power management register): Power Management Configuration.
|
* SME (power management register): Power Management Configuration.
|
(line 16)
|
(line 16)
|
* sockif (Ethernet configuration): Ethernet Configuration.
|
|
(line 83)
|
|
* sr (CPU configuration): CPU Configuration. (line 53)
|
* sr (CPU configuration): CPU Configuration. (line 53)
|
* stall (Interactive CLI): Interactive Command Line.
|
* stall (Interactive CLI): Interactive Command Line.
|
(line 72)
|
(line 72)
|
* stall the processor (Interactive CLI): Interactive Command Line.
|
* stall the processor (Interactive CLI): Interactive Command Line.
|
(line 72)
|
(line 72)
|
| Line 4360... |
Line 4568... |
* superscalar (CPU configuration): CPU Configuration. (line 63)
|
* superscalar (CPU configuration): CPU Configuration. (line 63)
|
* suspend mode (power management register): Power Management Configuration.
|
* suspend mode (power management register): Power Management Configuration.
|
(line 24)
|
(line 24)
|
* t (Interactive CLI): Interactive Command Line.
|
* t (Interactive CLI): Interactive Command Line.
|
(line 19)
|
(line 19)
|
|
* TAP device creation: Setting Up a Persistent TAP device.
|
|
(line 6)
|
|
* tap_dev (Ethernet configuration): Ethernet Configuration.
|
|
(line 93)
|
* target test code: Regression Testing. (line 63)
|
* target test code: Regression Testing. (line 63)
|
* TCP/IP port range: Verification API Configuration.
|
* TCP/IP port range: Verification API Configuration.
|
(line 23)
|
(line 23)
|
* TCP/IP port range for or1ksim-rsp service: Debug Interface Configuration.
|
* TCP/IP port range for or1ksim-rsp service: Debug Interface Configuration.
|
(line 37)
|
(line 37)
|
| Line 4382... |
Line 4594... |
* toggle debug channels (Interactive CLI): Interactive Command Line.
|
* toggle debug channels (Interactive CLI): Interactive Command Line.
|
(line 141)
|
(line 141)
|
* toggle debug mode (Interactive CLI): Interactive Command Line.
|
* toggle debug mode (Interactive CLI): Interactive Command Line.
|
(line 151)
|
(line 151)
|
* tx_channel (Ethernet configuration): Ethernet Configuration.
|
* tx_channel (Ethernet configuration): Ethernet Configuration.
|
(line 60)
|
(line 68)
|
* txfile (Ethernet configuration): Ethernet Configuration.
|
* txfile (Ethernet configuration): Ethernet Configuration.
|
(line 69)
|
(line 77)
|
* txfile (frame buffer configuration): Frame Buffer Configuration.
|
* txfile (frame buffer configuration): Frame Buffer Configuration.
|
(line 36)
|
(line 36)
|
* txfile (VGA configuration): Display Interface Configuration.
|
* txfile (VGA configuration): Display Interface Configuration.
|
(line 47)
|
(line 47)
|
* type (ATA/ATAPI device configuration): Disc Interface Configuration.
|
* type (ATA/ATAPI device configuration): Disc Interface Configuration.
|
| Line 4431... |
Line 4643... |
* VAPI for GPIO: Verification API. (line 88)
|
* VAPI for GPIO: Verification API. (line 88)
|
* VAPI for UART: Verification API. (line 41)
|
* VAPI for UART: Verification API. (line 41)
|
* vapi_id (debug interface configuration): Debug Interface Configuration.
|
* vapi_id (debug interface configuration): Debug Interface Configuration.
|
(line 43)
|
(line 43)
|
* vapi_id (DMA configuration) <1>: Ethernet Configuration.
|
* vapi_id (DMA configuration) <1>: Ethernet Configuration.
|
(line 88)
|
(line 99)
|
* vapi_id (DMA configuration): DMA Configuration. (line 38)
|
* vapi_id (DMA configuration): DMA Configuration. (line 38)
|
* vapi_id (GPIO configuration): GPIO Configuration. (line 32)
|
* vapi_id (GPIO configuration): GPIO Configuration. (line 32)
|
* vapi_id (UART configuration): UART Configuration. (line 85)
|
* vapi_id (UART configuration): UART Configuration. (line 85)
|
* vapi_log_file (verification API configuration): Verification API Configuration.
|
* vapi_log_file (verification API configuration): Verification API Configuration.
|
(line 41)
|
(line 41)
|
| Line 4453... |
Line 4665... |
(line 50)
|
(line 50)
|
|
|
|
|
|
|
Tag Table:
|
Tag Table:
|
Node: Top830
|
Node: Top814
|
Node: Installation1240
|
Node: Installation1224
|
Node: Preparation1487
|
Node: Preparation1471
|
Node: Configuring the Build1782
|
Node: Configuring the Build1766
|
Node: Build and Install7926
|
Node: Build and Install7910
|
Node: Known Issues8704
|
Node: Known Issues8688
|
Node: Usage9759
|
Node: Usage9743
|
Node: Standalone Simulator9973
|
Node: Standalone Simulator9988
|
Node: Profiling Utility14537
|
Node: Profiling Utility14552
|
Node: Memory Profiling Utility15447
|
Node: Memory Profiling Utility15462
|
Node: Simulator Library16812
|
Node: Simulator Library16827
|
Node: Configuration27217
|
Node: Ethernet TUN/TAP Interface27267
|
Node: Configuration File Format27829
|
Node: Setting Up a Persistent TAP device28350
|
Node: Configuration File Preprocessing28214
|
Node: Establishing a Bridge29025
|
Node: Configuration File Syntax28511
|
Node: Opening the Firewall30708
|
Node: Simulator Configuration31296
|
Node: Disabling Ethernet Filtering31199
|
Node: Simulator Behavior31587
|
Node: Networking from OpenRISC Linux and BusyBox31824
|
Node: Verification API Configuration36168
|
Node: Tearing Down a Bridge33486
|
Node: CUC Configuration38108
|
Node: Configuration34229
|
Node: Core OpenRISC Configuration40100
|
Node: Configuration File Format34841
|
Node: CPU Configuration40602
|
Node: Configuration File Preprocessing35226
|
Node: Memory Configuration44721
|
Node: Configuration File Syntax35523
|
Node: Memory Management Configuration51443
|
Node: Simulator Configuration38308
|
Node: Cache Configuration53820
|
Node: Simulator Behavior38599
|
Node: Interrupt Configuration56206
|
Node: Verification API Configuration43180
|
Node: Power Management Configuration58039
|
Node: CUC Configuration45120
|
Node: Branch Prediction Configuration59316
|
Node: Core OpenRISC Configuration47112
|
Node: Debug Interface Configuration60676
|
Node: CPU Configuration47614
|
Node: Peripheral Configuration63019
|
Node: Memory Configuration51733
|
Node: Memory Controller Configuration63645
|
Node: Memory Management Configuration58455
|
Node: UART Configuration67425
|
Node: Cache Configuration60832
|
Node: DMA Configuration70944
|
Node: Interrupt Configuration63218
|
Node: Ethernet Configuration72811
|
Node: Power Management Configuration65051
|
Node: GPIO Configuration76893
|
Node: Branch Prediction Configuration66328
|
Node: Display Interface Configuration78526
|
Node: Debug Interface Configuration67688
|
Node: Frame Buffer Configuration80835
|
Node: Peripheral Configuration70031
|
Node: Keyboard Configuration82699
|
Node: Memory Controller Configuration70657
|
Node: Disc Interface Configuration84937
|
Node: UART Configuration74437
|
Node: Generic Peripheral Configuration90041
|
Node: DMA Configuration77956
|
Node: Interactive Command Line92336
|
Node: Ethernet Configuration79823
|
Node: Verification API99310
|
Node: GPIO Configuration84468
|
Node: Code Internals103740
|
Node: Display Interface Configuration86101
|
Node: Coding Conventions104323
|
Node: Frame Buffer Configuration88410
|
Node: Global Data Structures108750
|
Node: Keyboard Configuration90274
|
Node: Concepts111407
|
Node: Disc Interface Configuration92512
|
Ref: Output Redirection111552
|
Node: Generic Peripheral Configuration97616
|
Ref: Interrupts Internal112090
|
Node: Interactive Command Line99911
|
Node: Internal Debugging113243
|
Node: Verification API106885
|
Node: Regression Testing113767
|
Node: Code Internals111315
|
Node: GNU Free Documentation License117556
|
Node: Coding Conventions111898
|
Node: Index139963
|
Node: Global Data Structures116325
|
|
Node: Concepts118982
|
|
Ref: Output Redirection119127
|
|
Ref: Interrupts Internal119665
|
|
Node: Internal Debugging120818
|
|
Node: Regression Testing121342
|
|
Node: GNU Free Documentation License125131
|
|
Node: Index147538
|
|
|
End Tag Table
|
End Tag Table
|
