URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Subversion Repositories or1k
[/] [or1k/] [branches/] [stable_0_2_x/] [or1ksim/] [README] - Rev 54
Go to most recent revision | Compare with Previous | Blame | View Log
What is this stuff?===================This is OpenRISC 1000 and DLX architectural simulator. It was written byDamjan Lampret and it is free software. See the file COPYING for copyingpermission. To contact the author, send mail to <lampret@opencores.org>.I use it to define OR1K system architecture. An implementation simulatorfor OR1K will be also available, probably in Mar/2000 or later.Initially this software was not meant to be released to public because itwas developed just to analyze program flow of GCC generated assembly code.With the time it became bigger and was able to generate statistics aboutsuperscalar issuing of multiple instructions. I've used it as a test simulatorto test OR1K GCC port. Perhaps some day I will (or perhaps someone else wouldlike to do that ??) clean-up the code and reorganize it.This simulator loads an assembly file for one of the both architecturesand it simulates the operation of instructions. Because it was meant to be usedonly to test characteristics of various RISC architectures and various GCCoptimization methods, it has a bit strange memory model. It is abstract andphysical at the same time. I can't really explain, just check the sources ifinterested. Some other things are strange or incomplete too (likeC library emulation, currently supports only printf via simprintf).MMU directory is not functional. Someday it will be filled with code forvirtual memory simulation.Installation============To compile, run the configure script and specify the target architecture.Example:$ ./configure --target=or32After that, just issue "make all" command. By default there should be nowarnings. There is no "make install". Just use it from default locationor copy it to your bin directory (usually something like /usr/local/binor ~/bin).This program hasn't been written with security in mind. It has many staticbuffers and it does not check the size of input strings (user commandsor whatever). So don't setuid it. If it kills your dog, don't blame it on me.To select DLX simulation, change the target to the configure script to 'dlx'and recompile everything (do 'make all' again).Simulator test==============Issue 'sim testbench/dhry.or32' or 'sim testbench/dhry.dlx' totest simulator. See testbench/README for details about Dhrystone 2.1benchmark.For microkernel test (exception test) undefine ONLY_VIRTUAL_MACHINE (you wantexceptions, right !) in cpu/or1k/except.h and recompile simulator. A compiledand linked version should already exist in testbench/uos. Just issue'sim testbench/uos/uos.or32' from the top level sim directory. Currently onlyOR32 is supported by UOS.OpenRISC and open cores=======================About the same idea as with GNU project except we want free and open sourceIP (intellectual property) cores. We design open source, synthesizablecores. OpenRISC is one such core. It is a 32-bit RISC microprocessor thatwill run GNU/Linux.For more information visit us at http://www.opencores.org.--29/Feb/2000, Damjan Lampret email:lampret@opencores.org03/Mar/2000, Johan Rydberg email:johan.rydberg@netinsight.net04/May/2000, Jimmy Chen-Min Chen email:jimmy@ee.nctu.edu.tw
Go to most recent revision | Compare with Previous | Blame | View Log
