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

Subversion Repositories claw

[/] [claw/] [trunk/] [Readme.txt] - Blame information for rev 4

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 2 conte
Firstly, I would like to thank you for considering my processor.
2
This readme file will explain the conventions that I have followed in my file structure and
3
filenames.
4
 
5
1) All the verilog source will be in
6
        ./or1200_cpu
7
 
8
2) Inside the or1200_cpu directory, these are the naming conventions I have
9
   followed
10
        - tb_.v => It is the test bench for a certain project
11
                                 indicated by 
12
                                 (for example: tb_or1200_cpu.v => test bench for
13
                                 or1200_cpu module).
14
        - .sc   => Synthesis script in synopsys
15
        - COMPILE_SCRIPT      => This is used to compile in the cadence verilog
16
                                 compiler.
17
        - .synopsys_dc.setup  => This is the setup file for the synopsys
18
                                 design_analyzer software
19
 
20
 
21
3) All the waveforms for different relevant modules are given in the
22
   ./Wave_Forms_For_The_Whole_Thing/ directory
23
 
24
   Inside this directory there is another directory that gives you the results
25
   when the modules are tested seperately.
26
 
27
   Please note that all the waveforms are of the Postscript module that is read
28
   using the ghostview software that can be downloaded from
29
   http://www.cs.wisc.edu/~ghost/ (I am not sure if there are any others but
30
        this is the one I used)
31
 
32
4) ./Work/ directory is the directory that is used by model sim to store its
33
   binary when I compiled it using it.
34
 
35
5) I have followed the same conventions as OpenRISC to name my files.

powered by: WebSVN 2.1.0

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