1 |
2 |
cvs |
|
2 |
|
|
What is this stuff?
|
3 |
|
|
===================
|
4 |
|
|
|
5 |
|
|
This is OpenRISC 1000 and DLX architectural simulator. It was written by
|
6 |
|
|
Damjan Lampret and it is free software. See the file COPYING for copying
|
7 |
|
|
permission. To contact the author, send mail to .
|
8 |
|
|
|
9 |
|
|
I use it to define OR1K system architecture. An implementation simulator
|
10 |
|
|
for OR1K will be also available, probably in Nov/1999.
|
11 |
|
|
|
12 |
|
|
Initially this software was not meant to be released to public because it
|
13 |
|
|
was developed just to analyze program flow of GCC generated assembly code.
|
14 |
|
|
With the time it became bigger and was able to generate statistics about
|
15 |
|
|
superscalar issuing of multiple instructions. I've used it as a test simulator
|
16 |
|
|
to test OR1K GCC port. Perhaps some day I will (or perhaps someone else would
|
17 |
|
|
like to do that ??) clean-up the code and reorganize it.
|
18 |
|
|
|
19 |
|
|
This simulator loads an assembly file for one of the both architectures
|
20 |
|
|
and it simulates the operation of instructions. Because it was meant to be used
|
21 |
|
|
only to test characteristics of various RISC architectures and various GCC
|
22 |
|
|
optimization methods, it has a bit strange memory model. It is abstract and
|
23 |
|
|
physical at the same time. I can't really explain, just check the sources if
|
24 |
|
|
interested. Some other things are strange or incomplete too (like
|
25 |
|
|
C library emulation, currently supports only printf).
|
26 |
|
|
|
27 |
|
|
cache and mmu directories are still empty. Someday (Nov/1999 probably) they
|
28 |
|
|
will be filled with code for cache simulation and with code for virtual
|
29 |
|
|
memory simulation.
|
30 |
|
|
|
31 |
|
|
|
32 |
|
|
Installation
|
33 |
|
|
============
|
34 |
|
|
|
35 |
|
|
To compile just issue "make all" command. By default there should be no
|
36 |
|
|
warnings. There is no "make install". Just use it from default location
|
37 |
|
|
or copy it to your bin directory (usually something like /usr/local/bin
|
38 |
|
|
or ~/bin).
|
39 |
|
|
This program hasn't been written with security in mind. It has many static
|
40 |
|
|
buffers and it does not check the size of input strings (user commands
|
41 |
|
|
or whatever). So don't setuid it. If it kills your dog, don't blame it on me.
|
42 |
|
|
|
43 |
|
|
To select DLX simulation, change CPU_ARCH in top level Makefile to 'dlx'
|
44 |
|
|
and recompile everything (do 'make all' again).
|
45 |
|
|
|
46 |
|
|
Simulator test
|
47 |
|
|
==============
|
48 |
|
|
|
49 |
|
|
Issue 'or1ksim testbench/dhry.or1k' or 'dlxsim testbench/dhry.dlx' to
|
50 |
|
|
test simulator. Use 'help' to get list of simulator commands.
|
51 |
|
|
Run simulation with 'run 1000000 hush'. It will take
|
52 |
|
|
a couple of seconds and you should get an error about label _exit.
|
53 |
|
|
Now quit simulator with 'q' and open file stdout.txt. You should see
|
54 |
|
|
output from simulated dhrystone benchmark.
|
55 |
|
|
See testbench/README for details about Dhrystone 2.1 benchmark.
|
56 |
|
|
|
57 |
|
|
OpenRISC and open cores
|
58 |
|
|
=======================
|
59 |
|
|
|
60 |
|
|
About the same idea as with GNU project except we want free hardware
|
61 |
|
|
IP (intellectual property). We design open source, synthesizeable
|
62 |
|
|
cores. OpenRISC is one such core. It is a 32-bit RISC microprocessor that
|
63 |
|
|
will run GNU/Linux.
|
64 |
|
|
For more information visit us at http://www.opencores.org.
|
65 |
|
|
|
66 |
|
|
--
|
67 |
|
|
|
68 |
4 |
lampret |
24/Oct/1999, Damjan Lampret email:lampret@opencores.org
|
69 |
2 |
cvs |
|