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

Subversion Repositories w11

Compare Revisions

  • This comparison shows the changes necessary to convert path 
    /w11/trunk
    from Rev 23 to Rev 22
    ↔ Reverse comparison
  •

Rev 23 → Rev 22

/tools/bin/xtwv File deleted
tools/bin/xtwv Property changes : Deleted: svn:executable ## -1 +0,0 ## -* \ No newline at end of property Index: tools/bin/vbomconv =================================================================== --- tools/bin/vbomconv (revision 23) +++ tools/bin/vbomconv (revision 22) @@ -1,5 +1,5 @@ #!/usr/bin/perl -w -# $Id: vbomconv 558 2014-06-01 22:20:51Z mueller $ +# $Id: vbomconv 543 2013-11-03 22:43:41Z mueller $ # # Copyright 2007-2013 by Walter F.J. Mueller # @@ -835,6 +835,5 @@ print " --xst_export=s export all xst source files into directory s\n"; print " --ghdl_export=s export all ghdl source files into directory s\n"; print " --isim_export=s export all isim source files into directory s\n"; - print " --get_top return top level entity name\n"; print " --flist list all files touched by vbom for all tags\n"; } Index: tools/oskit/rt11-40_rk/README_rt11-40_rkset.txt =================================================================== --- tools/oskit/rt11-40_rk/README_rt11-40_rkset.txt (revision 23) +++ tools/oskit/rt11-40_rk/README_rt11-40_rkset.txt (revision 22) @@ -1,4 +1,4 @@ -# $Id: README_rt11-40_rkset.txt 558 2014-06-01 22:20:51Z mueller $ +# $Id: README_rt11-40_rkset.txt 519 2013-05-12 20:44:16Z mueller $ Notes on oskit: RT-11 V4.0 system on RK05 volumes @@ -12,16 +12,16 @@ See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt - Also read README_license.txt which is included in the oskit !! + Also read README_license.txt !! 2. Installation ------------------------------------------------------ - A disk set is available from - http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_rkset.tgz + http://www.retro11.de/data/oc_w11/rsx11m-31_rkset.tgz Download, unpack and copy the disk images (*.dsk), e.g. cd $RETROBASE/tools/oskit/rt11-40_rk - wget http://www.retro11.de/data/oc_w11/oskits/rt11-40_rkset.tgz + wget http://www.retro11.de/data/oc_w11/rt11-40_rkset.tgz tar -xzf rt11-40_rkset.tgz 3. Usage -------------------------------------------------------------
/tools/oskit/unix-v5_rk/README_unix_v5_rkset.txt
1,4 → 1,4
# $Id: README_unix_v5_rkset.txt 558 2014-06-01 22:20:51Z mueller $
# $Id: README_unix_v5_rkset.txt 518 2013-05-12 16:45:02Z mueller $
 
Notes on oskit: Unix V5 system on RK05 volumes
 
22,11 → 22,11
2. Installation ------------------------------------------------------
 
- A disk set is available from
http://www.retro11.de/data/oc_w11/oskits/unix_v5_rkset.tgz
http://www.retro11.de/data/oc_w11/unix_v5_rkset.tgz
Download, unpack and copy the disk images (*.dsk), e.g.
 
cd $RETROBASE/tools/oskit/unix-v5_rk
wget http://www.retro11.de/data/oc_w11/oskits/unix_v5_rkset.tgz
wget http://www.retro11.de/data/oc_w11/unix_v5_rkset.tgz
tar -xzf unix_v5_rkset.tgz
 
3. Usage -------------------------------------------------------------
/tools/oskit/211bsd_rk/README_211bsd_rkset.txt
1,4 → 1,4
# $Id: README_211bsd_rkset.txt 558 2014-06-01 22:20:51Z mueller $
# $Id: README_211bsd_rkset.txt 518 2013-05-12 16:45:02Z mueller $
 
Notes on oskit: 2.11BSD system on RK05 volumes
 
22,11 → 22,11
2. Installation ------------------------------------------------------
 
- A disk set is available from
http://www.retro11.de/data/oc_w11/oskits/211bsd_rkset.tgz
http://www.retro11.de/data/oc_w11/211bsd_rkset.tgz
Download, unpack and copy the disk images (*.dsk), e.g.
 
cd $RETROBASE/tools/oskit/211bsd_rk/
wget http://www.retro11.de/data/oc_w11/oskits/211bsd_rkset.tgz
wget http://www.retro11.de/data/oc_w11/211bsd_rkset.tgz
tar -xzf 211bsd_rkset.tgz
 
3. Usage -------------------------------------------------------------
/tools/oskit/rsx11m-40_rk/README_rsx11m-40_rkset.txt
1,4 → 1,4
# $Id: README_rsx11m-40_rkset.txt 558 2014-06-01 22:20:51Z mueller $
# $Id: README_rsx11m-40_rkset.txt 518 2013-05-12 16:45:02Z mueller $
 
Notes on oskit: RSX-11M V4.0 system on RK05 volumes
 
12,16 → 12,16
 
See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt
 
Also read README_license.txt which is included in the oskit !!
Also read README_license.txt !!
 
2. Installation ------------------------------------------------------
 
- A disk set is available from
http://www.retro11.de/data/oc_w11/oskits/rsx11m-40_rkset.tgz
http://www.retro11.de/data/oc_w11/rsx11m-40_rkset.tgz
Download, unpack and copy the disk images (*.dsk), e.g.
 
cd $RETROBASE/tools/oskit/rsx11m-40_rk
wget http://www.retro11.de/data/oc_w11/oskits/rsx11m-40_rkset.tgz
wget http://www.retro11.de/data/oc_w11/rsx11m-40_rkset.tgz
tar -xzf rsx11m-40_rkset.tgz
 
3. Usage -------------------------------------------------------------
/tools/oskit/rsx11m-31_rk/README_rsx11m-31_rkset.txt
1,4 → 1,4
# $Id: README_rsx11m-31_rkset.txt 558 2014-06-01 22:20:51Z mueller $
# $Id: README_rsx11m-31_rkset.txt 518 2013-05-12 16:45:02Z mueller $
 
Notes on oskit: RSX-11M V3.1 system on RK05 volumes
 
12,16 → 12,16
 
See notes, especially on legal terms, in $RETROBASE/doc/w11a_os_guide.txt
 
Also read README_license.txt which is included in the oskit !!
Also read README_license.txt !!
 
2. Installation ------------------------------------------------------
 
- A disk set is available from
http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_rkset.tgz
http://www.retro11.de/data/oc_w11/rsx11m-31_rkset.tgz
Download, unpack and copy the disk images (*.dsk), e.g.
 
cd $RETROBASE/tools/oskit/rsx11m-31_rk
wget http://www.retro11.de/data/oc_w11/oskits/rsx11m-31_rkset.tgz
wget http://www.retro11.de/data/oc_w11/rsx11m-31_rkset.tgz
tar -xzf rsx11m-31_rkset.tgz
 
3. Usage -------------------------------------------------------------
/tools/simh/setup_w11a_min.scmd
1,8 → 1,8
; $Id: setup_w11a_min.scmd 559 2014-06-06 21:26:47Z mueller $
; $Id: setup_w11a_min.scmd 518 2013-05-12 16:45:02Z mueller $
;
; Setup file for 'minimal' w11a configuration under simh 3.8 and above
;
; This setup reflects the minimal w11a system on a S3BOARD
; This setup reflects the current w11a system on a S3BOARD
; --> 1MByte, 2 DL11, LP+PC, RK05
;
; 11/70 CPU no FPP, 1 MByte memory
/tools/simh/setup_w11a_max.scmd
1,11 → 1,11
; $Id: setup_w11a_max.scmd 559 2014-06-06 21:26:47Z mueller $
; $Id: setup_w11a_max.scmd 518 2013-05-12 16:45:02Z mueller $
;
; Setup file for 'maximal' w11a configuration under simh 3.8 and above
;
; This setup reflects the full w11a system on a Nexys[234] board
; This setup reflects the planned w11a system on a Nexys[234] board
; --> 4 MByte, 2 DL11, DZ+LP+PC, RK05+RL02+RP06+TM11, DEUNA
;
; 11/70 CPU no FPP, 4 MByte memory
; 11/70 CPU no FPP, 1 MByte memory
; 2 DL11
; 1 DZ11
; 1 LP11
/doc/README.txt
1,4 → 1,4
$Id: README.txt 559 2014-06-06 21:26:47Z mueller $
# $Id: README.txt 556 2014-05-29 19:01:39Z mueller $
 
Release notes for w11a
 
22,7 → 22,6
2. Files ---------------------------------------------------------------------
 
doc Documentation
doc/man man pages for retro11 commands
rtl VHDL sources
rtl/bplib - board and component support libs
rtl/bplib/atlys - for Digilent Atlys board
83,40 → 82,10
 
3. Change Log ----------------------------------------------------------------
 
- w11a_V0.50 -> w11a_V0.60 cummulative summary of key changes
- revised ibus protocol V2 (in w11a_V0.51)
- revised rbus protocol V3 (in w11a_V0.52)
- backend server rewritten in C++ and Tcl (in w11a_V0.53 and w11a_V0.562)
- add Nexys3 port of w11a (in w11a_V0.54)
- add Cypress FX2 support (in w11a_V0.56 and w11a_V0.57)
- added LP11,PC11 support (in w11a_V0.58)
- reference system now ISE 14.7 and Ubuntu 12.04 64 bit, ghdl 0.31
- many code cleanups; use numeric_std
- many documentation improvements
- development status upgraded to beta (from alpha)
 
- trunk (2014-06-06: svn rev 23(oc) 559+(wfjm); tagged w11a_V0.60) +++++++++
 
- Summary
- many documentation updates; no functional changes
 
- New features
- Tarballs with ready to use bit files and and all logfiles from the tool
chain can be downloaded from
http://www.retro11.de/data/oc_w11/bitkits/
This area is organized in folders for different releases. The tarball
file names contain information about release, Xlinix tool, and design.
 
- Changes
- documentation updates
- URL of oskits changed, they are now unter
http://www.retro11.de/data/oc_w11/oskits
 
- trunk (2014-05-29: svn rev 22(oc) 556(wfjm); untagged w11a_V0.581) ++++++++
 
- Summary
- summary
- new reference system
- switched from ISE 13.3 to 14.7.
- Switched from ISE 13.3 to 14.7.
- map/par behaviour changed, unfortunately unfavorably for w11a.
On Nexys3 no timing closure anymore for 80 MHz, only 72 MHz can
be achieved now.
/doc/man/man5/vbom.5
1,156 → 1,74
.\" -*- nroff -*-
.\" $Id: vbom.5 558 2014-06-01 22:20:51Z mueller $
.\" $Id: vbom.5 522 2013-05-24 17:50:29Z mueller $
.\"
.\" Copyright 2010-2013 by Walter F.J. Mueller <W.F.J.Mueller@gsi.de>
.\" Copyright 2010- by Walter F.J. Mueller <W.F.J.Mueller@gsi.de>
.\"
.\" ------------------------------------------------------------------
.
.TH VBOM 2013-10-20 "Retro Project" "Retro Project Manual"
.TH VBOM 2010-07-25 "Retro Project" "Retro Project Manual"
.\" ------------------------------------------------------------------
.SH NAME
vbom \- vhdl manifest file format - 'vhdl bill of material'
vbom \- 'vhdl bill of material' file format
.
.\" ------------------------------------------------------------------
.SH DESCRIPTION
\fBvbom\fP files describe the sources needed to build a \fIvhdl\fP
entity. The source files are either given directly in case of libraries
or via other \fBvbom\fP's in case of instantiated components.
These files describe the sources needed to build a \fIvhdl\fP
module. The source files are either given directly in case of libraries
or via other \fIvbom\fP's in case of instantiated components.
They are used by \fBvbomconv\fP(1) to build project descriptions
for synthesis and simulation tools.
 
\fBvbomconv\fP expects that the entries in the \fBvbom\fP's
are ordered, libraries first, than the components in the order they are
instantiated, finally the name of the associated source file.
 
The format has five types of lines:
The format has four types of lines:
.
.\" ----------------------------------------------
.IP \fBComments\fP 4
Each line starting with '\fB#\fP' is treated as comment and ignored.
.IP \fBcomments\fP
each line starting with \fB#\fP is treated as comment and ignored.
.
.\" ----------------------------------------------
.IP "\fBFile names\fP"
Either source files or nested \fBvbom\fP's. The file names must be given
as relative path name from the directory the \fBvbom\fP file is located in.
Absolute path names are not allowed, nor is expansion of environment variables.
 
Currently three file types are accepted:
.RS
.IP "\fB.vbom\fP" 6
refers to a nested \fBvbom\fP. Usually used for instantiated components.
.IP "\fBfile names\fP"
either source files with a '\fI.vhd\fP' file type or nested \fIvbom\fP's
with a '\fI.vbom\fP' file type. The must be given as relative path name
from the directory the \fIvbom\fP file is located in.
Absolute path names are not allowed, nor is expansion of environment variables.
.
.IP "\fB.vhd\fP"
refers to a source file. Usually used for libraries refered to in 'use'
clauses, and as last file, the source file of the entity which is
described by this \fBvbom\fP file.
.
.IP "\fB.c\fP"
refers to the C source which implements a \fIvhdl\fP function or procedure
via the \fIvhpi\fP mechanism. Supported only in conjunction with \fBghdl\fP.
.
.RE
.
.
.\" ----------------------------------------------
.IP "\fBConditional file names\fP"
File names can be preceeded by a condition prefix of the form
 
.EX
[\fItag\fP]filename
[\fItag\fP,\fItag\fP,...]filename
.EE
 
The main purpose of this mechanism is to handle libraries and components
which are only refered in
.EX
-- synthesis translate_off
-- synthesis translate_on
.EE
sections and are used only for simulation.
 
Currently supported \fItag\fP names are
.RS
.RS 3
.PD 0
.IP "\fBxst\fP" 6
included in conjunction with xst synthesis
.IP "\fBghdl\fP"
included in conjunction with ghdl simulation
.IP "\fBisim\fP"
included in conjunction with isim simulation
.IP "\fBsim\fP"
included in conjunction with simulation (ghdl or isim)
.PD
.RE
.RE
.
.\" ----------------------------------------------
.IP "\fBLogical names\fP"
.IP "\fBlogical names\fP"
A logical name can be defined with
.EX
<lname> = <filename>
.EE
The first definition of a logical name encountered in the traversal of the
\fBvbom\fP's by \fBvbomconv\fP(1) is taken, all later definitions are ignored.
\fIvbom\fP's by \fBvbomconv\fP(1) is taken, all later definitions are ignored.
 
A logical name can be used with
.EX
<lname> : <filename>
.EE
The filename in the usage clause is the default used in case the
logical name wasn't defined before it is used.
If it wasn't ???
 
 
Again, the filenames, either of type \fI.vhd\fP or \fI.vbom\fP ,
must be given as relative path name from the directory the \fBvbom\fP
must be given as relative path name from the directory the \fIvbom\fP
file is located in.
 
The definition clause just sets up the logical name for later usage.
The usage clause
 
.\" ----------------------------------------------
.IP \fBDirectives\fP
Directives start with a '\fB@\fP', currently implemented are:
.RS
.IP "\fB@top\fP:\fIname\fP" 4
Specifies the top level design name. Mainly used when it is different
from the stem of the \fBvbom\fP file name.
.IP \fBdirectives\fP
The format is simple, essentially a list of file names, either
source files with a '\fI.vhd\fP' file type or nested \fIvbom\fP's
with a '\fI.vbom\fP' file type.
Lines starting with \fB#\fP are treated as comments.
 
 
.
.IP "\fB@lib\fP:\fIname\fP"
Specifies an additional system library. Allowed values for \fIname\fP are
\fIunisim\fP and \fIsimprim\fP. Currently used to generate the appropriate
-L options for \fBghdl\fP commands, e.g. generated by the
\fBvbomconv\fP action \fB\-\-ghdl_m\fP.
.
.IP "\fB@ucf_cpp\fP:\fIfile\fP"
Specifies that a \fIfile\fP.ucf file is to be generated by \fBcpp\fP(1)
from a \fIfile\fP.ucf_cpp source file. This allows to modularize ISE ucf files.
.RE
.
.\" ------------------------------------------------------------------
.SH EXAMPLES
.SS Simple entity
A simple vhdl entity named \fIbp_2l4l\fP which is defined in the source
file \fIbp_2l4l.vhd\fP, which uses the library \fIslvtypes\fP and
instantiates \fIbp_2line\fP and \fIbp_4line\fP, might have a
\fIbp_2l4l.vbom\fP like
.PP
.EX
# libs
../../vlib/slvtypes.vhd
# components
bp_2line.vbom
bp_4line.vbom
# design
bp_2l4l.vhd
.EE
.PP
Note that the vhdl source file \fIbp_2l4l.vhd\fP is always given in the
\fBvbom\fP file which describes this source file.
The comments are put in by convention to help the human reader and
are not interpreted by \fBvbomconv\fP.
.
.\" ------------------------------------------------------------------
.SH "SEE ALSO"
.BR vbomconv (1),
.BR ghdl (1),
.BR cpp (1)
.BR vbomconv (1)
.
.\" ------------------------------------------------------------------
.SH AUTHOR
/doc/man/man1/vbomconv.1 File deleted
/doc/man/man1/ti_w11.1 File deleted
/doc/man/man1/ti_rri.1 File deleted
/doc/man/man1/xtwi.1 File deleted
/doc/man/man1/xtwv.1 File deleted
/doc/INSTALL.txt
1,4 → 1,4
# $Id: INSTALL.txt 559 2014-06-06 21:26:47Z mueller $
# $Id: INSTALL.txt 512 2013-04-28 07:44:02Z mueller $
 
Guide to install and build w11a systems, test benches and support software
 
29,31 → 29,16
All instructions below assume that the project files reside in a
working directory with the name represented as <wdir>
 
- to download latest snapshot of trunk
To download latest tagged version (V0.5) of w11a
 
cd <wdir>
svn co http://opencores.org/ocsvn/w11/w11/trunk
cd <wdir>
svn co http://opencores.org/ocsvn/w11/w11/tags/w11a_V0.5
 
- to download tagged verions (from major releases)
list available svn tags
svn ls http://opencores.org/ocsvn/w11/w11/tags
To download latest snapshot of trunk
 
and download one of them
cd <wdir>
svn co http://opencores.org/ocsvn/w11/w11/trunk
 
cd <wdir>
svn co http://opencores.org/ocsvn/w11/w11/tags/<tag>
 
- to download specific svn revision (from minor releases)
determine desired svn revsion from list given on
http://opencores.org/project,w11,overview
 
and download
 
cd <wdir>
svn co -r <rev> http://opencores.org/ocsvn/w11/w11/trunk
 
 
2. System requirements ----------------------------------------------------
This project contains not only VHDL code but also support software. Therefore
123,10 → 108,6
export PATH=$PATH:$RETROBASE/tools/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$RETROBASE/tools/lib
 
To access the man pages update also the MANPATH
 
export MANPATH=$MANPATH:$RETROBASE/doc/man
 
In most cases the boost library version coming with the distribution will
work, similar for Tcl, in those cases simply use
 
371,32 → 352,18
 
8c. Available systems ------------------------------------------------
 
Currently ready to build versions exist for
- Digilent S3BOARD (-1000 FPGA version)
- Digilent Nexys2 board (-1200 FPGA version)
- Digilent Nexys3 board
Note: Currently ready to build versions exist for
Digilent S3BOARD (-1000 FPGA version)
Digilent Nexys2 board (-1200 FPGA version)
Digilent Nexys3 board
 
Tarballs with ready to use bit file and and all logfiles from the tool
chain can be downloaded from
http://www.retro11.de/data/oc_w11/bitkits/
This area is organized in folders for different releases. The tarball
file names contain information about release, Xlinix tool, and design:
<release>_<tool>_<design>.tgz
 
To build the designs locally use
 
1. rlink tester
a. for Digilent S3BOARD
a. for Digilent Nexys2 board
 
cd $RETROBASE/rtl/sys_gen/tst_rlink/s3board
make sys_tst_rlink_s3.bit
 
b. for Digilent Nexys2 board
 
cd $RETROBASE/rtl/sys_gen/tst_rlink/nexys2
make sys_tst_rlink_n2.bit
 
c. for Digilent Nexys3 board
b. for Digilent Nexys3 board
 
cd $RETROBASE/rtl/sys_gen/tst_rlink/nexys3
make sys_tst_rlink_n3.bit

powered by: WebSVN 2.1.0

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