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

Subversion Repositories w11

[/] [w11/] [tags/] [w11a_V0.74/] [doc/] [INSTALL.txt] - Diff between revs 20 and 21

Go to most recent revision | Only display areas with differences | Details | Blame | View Log

Rev 20 Rev 21
# $Id: INSTALL.txt 511 2013-04-27 13:51:46Z mueller $
# $Id: INSTALL.txt 512 2013-04-28 07:44:02Z mueller $
 
 
Guide to install and build w11a systems, test benches and support software
Guide to install and build w11a systems, test benches and support software
  Table of content:
  Table of content:
  1.  Download
  1.  Download
  2.  System requirements
  2.  System requirements
  3.  Setup system environment
  3.  Setup system environment
       a. Setup environment variables
       a. Setup environment variables
       b. Setup USB access
       b. Setup USB access
  4.  Compile UNISIM/SIMPRIM libraries for ghdl
  4.  Compile UNISIM/SIMPRIM libraries for ghdl
  5.  Compile and install the support software
  5.  Compile and install the support software
       a. Compile sharable libraries
       a. Compile sharable libraries
       b. Setup Tcl packages
       b. Setup Tcl packages
       c. Rebuild Cypress FX2 firmware
       c. Rebuild Cypress FX2 firmware
  6.  The build system
  6.  The build system
  7.  Building test benches
  7.  Building test benches
       a. General instructions
       a. General instructions
       b. Available test benches
       b. Available test benches
  8.  Building systems
  8.  Building systems
       a. General instructions
       a. General instructions
       b. Configuring FPGAs
       b. Configuring FPGAs
       c. Available systems
       c. Available systems
  9.  Generate Doxygen based source code view
  9.  Generate Doxygen based source code view
1. Download ---------------------------------------------------------------
1. Download ---------------------------------------------------------------
  All instructions below assume that the project files reside in a
  All instructions below assume that the project files reside in a
  working directory with the name represented as 
  working directory with the name represented as 
  To download latest tagged version (V0.5) of w11a
  To download latest tagged version (V0.5) of w11a
    cd 
    cd 
    svn co http://opencores.org/ocsvn/w11/w11/tags/w11a_V0.5
    svn co http://opencores.org/ocsvn/w11/w11/tags/w11a_V0.5
  To download latest snapshot of trunk
  To download latest snapshot of trunk
    cd 
    cd 
    svn co http://opencores.org/ocsvn/w11/w11/trunk
    svn co http://opencores.org/ocsvn/w11/w11/trunk
2. System requirements ----------------------------------------------------
2. System requirements ----------------------------------------------------
  This project contains not only VHDL code but also support software. Therefore
  This project contains not only VHDL code but also support software. Therefore
  quite a few software packages are expected to be installed. The following
  quite a few software packages are expected to be installed. The following
  list gives the Ubuntu/Debian package names, but mapping this to other
  list gives the Ubuntu/Debian package names, but mapping this to other
  distributions should be straight forward.
  distributions should be straight forward.
  - building the bit files for the FPGAs requires a Xilinx WebPACK installation
  - building the bit files for the FPGAs requires a Xilinx WebPACK installation
  - building and using the RLink backend software requires:
  - building and using the RLink backend software requires:
    - full C/C++ development chain (gcc,g++,cpp,make)
    - full C/C++ development chain (gcc,g++,cpp,make)
      -> package: build-essential
      -> package: build-essential
    - Boost C++ library (>= 1.40), with date-time, thread, and regex
    - Boost C++ library (>= 1.40), with date-time, thread, and regex
      -> package: libboost-dev libboost-date-time-dev libboost-thread-dev
      -> package: libboost-dev libboost-date-time-dev libboost-thread-dev
                  libboost-regex-dev
                  libboost-regex-dev
    - libusb 1.0 (>= 1.0.6)
    - libusb 1.0 (>= 1.0.6)
      -> package: libusb-1.0-0-dev
      -> package: libusb-1.0-0-dev
    - Perl (>= 5.10)  (usually included in base installations)
    - Perl (>= 5.10)  (usually included in base installations)
    - Tcl  (>= 8.4), with tclreadline support
    - Tcl  (>= 8.4), with tclreadline support
      -> package: tcl tcl-dev tcllib tclreadline
      -> package: tcl tcl-dev tcllib tclreadline
  - the download contains pre-build firmware images for the Cypress FX2
  - the download contains pre-build firmware images for the Cypress FX2
    USB Interface. Re-building them requires
    USB Interface. Re-building them requires
    - Small Device C Compiler
    - Small Device C Compiler
      -> package: sdcc sdcc-ucsim
      -> package: sdcc sdcc-ucsim
  - for FX2 firmware download and jtag programming over USB one needs
  - for FX2 firmware download and jtag programming over USB one needs
    - fxload
    - fxload
      -> package: fxload
      -> package: fxload
    - urjtag
    - urjtag
      -> package: urjtag   for Ubuntu 12.04
      -> package: urjtag   for Ubuntu 12.04
      -> see INSTALL_urjtag.txt for other distributions !!
      -> see INSTALL_urjtag.txt for other distributions !!
  - for VHDL simulations one needs
  - for VHDL simulations one needs
    - ghdl
    - ghdl
      -> see INSTALL_ghdl.txt for the unfortunately gory details
      -> see INSTALL_ghdl.txt for the unfortunately gory details
  - for doxygen documentation an up-to-date installation of doxygen is
  - for doxygen documentation an up-to-date installation of doxygen is
    required, version 1.8.3.1 or later
    required, version 1.8.3.1 or later
  - optional but very useful is:
  - optional but very useful is:
    - gtkwave
    - gtkwave
      -> package: gtkwave
      -> package: gtkwave
3. Setup system environment -----------------------------------------------
3. Setup system environment -----------------------------------------------
3a. Setup environment variables --------------------------------------
3a. Setup environment variables --------------------------------------
  The make flow for building test benches (ghdl and ISim based) and systems
  The make flow for building test benches (ghdl and ISim based) and systems
  (Xilinx xst based) as well as the support software (mainly the rlink backend
  (Xilinx xst based) as well as the support software (mainly the rlink backend
  server) requires
  server) requires
    - the definition of the environment variables:
    - the definition of the environment variables:
      - RETROBASE: must refer to the installation root directory
      - RETROBASE: must refer to the installation root directory
      - TCLINC:    pathname for includes of Tcl runtime library
      - TCLINC:    pathname for includes of Tcl runtime library
      - RETRO_FX2_VID and RETRO_FX2_PID: default USB VID/PID, see below
      - RETRO_FX2_VID and RETRO_FX2_PID: default USB VID/PID, see below
    - that the tools binary directory is in the path
    - that the tools binary directory is in the path
    - that the tools library directory is in the library path
    - that the tools library directory is in the library path
    - optional environment variables:
    - optional environment variables:
      - BOOSTINC:  pathname for includes of boost library
      - BOOSTINC:  pathname for includes of boost library
      - BOOSTLIB:  pathname for libraries of boost library
      - BOOSTLIB:  pathname for libraries of boost library
        {Note: Either both must be undefined, or both must be defined}
        {Note: Either both must be undefined, or both must be defined}
  For bash and alike use
  For bash and alike use
    export RETROBASE=
    export RETROBASE=
    export PATH=$PATH:$RETROBASE/tools/bin
    export PATH=$PATH:$RETROBASE/tools/bin
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$RETROBASE/tools/lib
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$RETROBASE/tools/lib
  In most cases the boost library version coming with the distribution will
  In most cases the boost library version coming with the distribution will
  work, similar for Tcl, in those cases simply use
  work, similar for Tcl, in those cases simply use
    export TCLINC=/usr/include/tcl8.5
    export TCLINC=/usr/include/tcl8.5
  and don't setup BOOSTINC and BOOSTLIB.
  and don't setup BOOSTINC and BOOSTLIB.
  After that building functional model based test benches will work. If you
  After that building functional model based test benches will work. If you
  want to also build post-xst or post-par test benches read next section.
  want to also build post-xst or post-par test benches read next section.
  If the Cypress USB controller available on Digilent Nexys2, Nexys3 and
  If the Cypress USB controller available on Digilent Nexys2, Nexys3 and
  Atlys boards is used the default USB VID and PID is defined by two
  Atlys boards is used the default USB VID and PID is defined by two
  environment variables. For internal lab use one can use
  environment variables. For internal lab use one can use
    export RETRO_FX2_VID=16c0
    export RETRO_FX2_VID=16c0
    export RETRO_FX2_PID=03ef
    export RETRO_FX2_PID=03ef
  !! Carefully read the disclaimer about usage of USB VID/PID numbers  !!
  !! Carefully read the disclaimer about usage of USB VID/PID numbers  !!
  !! in the file README_USB-VID-PID.txt. You'll be responsible for any !!
  !! in the file README_USB-VID-PID.txt. You'll be responsible for any !!
  !! misuse of the defaults provided with the project sources.         !!
  !! misuse of the defaults provided with the project sources.         !!
  !! Usage of this VID/PID in any commercial product is forbidden.     !!
  !! Usage of this VID/PID in any commercial product is forbidden.     !!
3b. Setup USB access -------------------------------------------------
3b. Setup USB access -------------------------------------------------
  For using the Cypress FX2 USB interface on Digilent Nexys2, Nexys3 and
  For using the Cypress FX2 USB interface on Digilent Nexys2, Nexys3 and
  Atlys boards 'udev' rules must be setup to allow user level access to
  Atlys boards 'udev' rules must be setup to allow user level access to
  these devices. A set of rules is provided under
  these devices. A set of rules is provided under
    $RETROBASE/tools/fx2/sys
    $RETROBASE/tools/fx2/sys
  Follow the 'README.txt' file in this directory.
  Follow the 'README.txt' file in this directory.
  Notes:
  Notes:
  - the provided udev rules use the VID/PID for 'internal lab use' as
  - the provided udev rules use the VID/PID for 'internal lab use' as
    described above. If other VID/PID used the file must be modified.
    described above. If other VID/PID used the file must be modified.
  - your user account must be in group 'plugdev' (should be the default).
  - your user account must be in group 'plugdev' (should be the default).
4. Compile UNISIM/SIMPRIM libraries for ghdl ------------------------------
4. Compile UNISIM/SIMPRIM libraries for ghdl ------------------------------
  The build system for test benches also supports test benches run against
  The build system for test benches also supports test benches run against
  the gate level models derived after the xst, map or par step. In this
  the gate level models derived after the xst, map or par step. In this
  case ghdl has to link against a compiled UNISIM or SIMPRIM library.
  case ghdl has to link against a compiled UNISIM or SIMPRIM library.
  To make handling of the parallel installion of several WebPack versions
  To make handling of the parallel installion of several WebPack versions
  easy the compiled libraries are stored in sub-directories under $XILINX:
  easy the compiled libraries are stored in sub-directories under $XILINX:
     $XILINX/ghdl/unisim
     $XILINX/ghdl/unisim
     $XILINX/ghdl/simprim
     $XILINX/ghdl/simprim
  Two helper scripts will create these libraries:
  Two helper scripts will create these libraries:
    
    
    cd $RETROBASE
    cd $RETROBASE
    xilinx_ghdl_unisim
    xilinx_ghdl_unisim
    xilinx_ghdl_simprim
    xilinx_ghdl_simprim
  If you have several WebPack versions installed, repeat for each version.
  If you have several WebPack versions installed, repeat for each version.
5. Compile and install the support software -------------------------------
5. Compile and install the support software -------------------------------
5a. Compile sharable libraries ---------------------------------------
5a. Compile sharable libraries ---------------------------------------
  Required tools and libraries:
  Required tools and libraries:
    g++    >= 4.3    (decltype support assumed in usage of boost::bind)
    g++    >= 4.3    (decltype support assumed in usage of boost::bind)
    boost  >= 1.35   (boost::thread api changed, new one is used)
    boost  >= 1.35   (boost::thread api changed, new one is used)
    linusb >= 1.0.5  (timerfd support)
    linusb >= 1.0.5  (timerfd support)
  Build was tested under:
  Build was tested under:
    ubuntu lucid (12.04 LTS):  gcc 4.6.3  boost 1.46.1  libusb 1.0.9
    ubuntu lucid (12.04 LTS):  gcc 4.6.3  boost 1.46.1  libusb 1.0.9
    debian squezze (6.0.6):    gcc 4.4.5  boost 1.46.1  libusb 1.0.8
    debian squezze (6.0.6):    gcc 4.4.5  boost 1.46.1  libusb 1.0.8
  To build all sharable libraries
  To build all sharable libraries
    cd $RETROBASE/tools/src
    cd $RETROBASE/tools/src
    make -j 4
    make -j 4
  To cleanup, e.g. before a re-build
  To cleanup, e.g. before a re-build
    cd $RETROBASE/tools/src
    cd $RETROBASE/tools/src
    rm_dep
    rm_dep
    make realclean
    make realclean
5b. Setup Tcl environment --------------------------------------------
5b. Setup Tcl environment --------------------------------------------
  The Tcl files are organized in several packages. To create the Tcl
  The Tcl files are organized in several packages. To create the Tcl
  package files (pkgIndex.tcl)
  package files (pkgIndex.tcl)
    cd $RETROBASE/tools/tcl
    cd $RETROBASE/tools/tcl
    setup_packages
    setup_packages
  To use these packages it is convenient to make them available via the
  To use these packages it is convenient to make them available via the
  'auto_path' mechanism. To do that add in your .tclshrc or .wishrc
  'auto_path' mechanism. To do that add in your .tclshrc or .wishrc
    lappend auto_path [file join $env(RETROBASE) tools tcl]
    lappend auto_path [file join $env(RETROBASE) tools tcl]
    lappend auto_path [file join $env(RETROBASE) tools lib]
    lappend auto_path [file join $env(RETROBASE) tools lib]
  The w11 distribution contains two ready to use .tclshrc or .wishrc
  The w11 distribution contains two ready to use .tclshrc or .wishrc
  files which
  files which
    - include the auto_path statements above
    - include the auto_path statements above
    - activate tclreadline (and thus in tclshrc an event loop)
    - activate tclreadline (and thus in tclshrc an event loop)
  To use them simply copy them into your home directory (or soft link them)
  To use them simply copy them into your home directory (or soft link them)
    cd $HOME
    cd $HOME
    ln -s $RETROBASE/tools/tcl/.tclshrc .
    ln -s $RETROBASE/tools/tcl/.tclshrc .
    ln -s $RETROBASE/tools/tcl/.wishrc  .
    ln -s $RETROBASE/tools/tcl/.wishrc  .
5c. Rebuild Cypress FX2 firmware -------------------------------------
5c. Rebuild Cypress FX2 firmware -------------------------------------
  The download includes pre-build firmware images for the Cypress FX2
  The download includes pre-build firmware images for the Cypress FX2
  USB interface used on the Digilent Nexys2, Nexys3 and Atlys Boards.
  USB interface used on the Digilent Nexys2, Nexys3 and Atlys Boards.
  These firmware images are under
  These firmware images are under
    $RETROBASE/tools/fx2/bin
    $RETROBASE/tools/fx2/bin
  To re-build them, e.g. because a different USB VID/PID is to be used
  To re-build them, e.g. because a different USB VID/PID is to be used
    cd $RETROBASE/tools/fx2/src
    cd $RETROBASE/tools/fx2/src
    make clean
    make clean
    make
    make
    make install
    make install
  Please read README_USB_VID-PID.txt carefully to understand the usage
  Please read README_USB_VID-PID.txt carefully to understand the usage
  of USB VID and PID.
  of USB VID and PID.
6. The build system -------------------------------------------------------
6. The build system -------------------------------------------------------
  Simulation and synthesis tools usually need a list of the VHDL source
  Simulation and synthesis tools usually need a list of the VHDL source
  files, often in proper compilation order (libraries before components).
  files, often in proper compilation order (libraries before components).
  The different tools have different formats of these 'project files'.
  The different tools have different formats of these 'project files'.
  The build system employed in this project is based on
  The build system employed in this project is based on
     "VHDL bill of material" or 'vbom' files
     "VHDL bill of material" or 'vbom' files
  which list for each vhdl source file the libraries and sources for
  which list for each vhdl source file the libraries and sources for
  the instantiated components, the later via their vbom, and last but
  the instantiated components, the later via their vbom, and last but
  not least the name of the vhdl source file. All file name are relative
  not least the name of the vhdl source file. All file name are relative
  to the current directory. A recursive traversal through all vbom's gives
  to the current directory. A recursive traversal through all vbom's gives
  for each vhld module all sources needed to compile it. The vbomconv script
  for each vhld module all sources needed to compile it. The vbomconv script
  in tools/bin does this, and generates depending on options
  in tools/bin does this, and generates depending on options
   - make dependency files
   - make dependency files
   - ISE xst project files
   - ISE xst project files
   - ISE ISim project files
   - ISE ISim project files
   - ghdl commands for analysis, inspection and make step
   - ghdl commands for analysis, inspection and make step
  The master make files contain pattern rules like
  The master make files contain pattern rules like
    %.ngc  : %.vbom           -- synthesize with xst
    %.ngc  : %.vbom           -- synthesize with xst
    %      : %.vbom           -- build functional model test bench
    %      : %.vbom           -- build functional model test bench
  which encapsulate all the vbomconf magic
  which encapsulate all the vbomconf magic
  A full w11a is build from more than 80 source files, test benches from
  A full w11a is build from more than 80 source files, test benches from
  even more. Using the vbom's a large number of designs can be easily
  even more. Using the vbom's a large number of designs can be easily
  maintained.
  maintained.
7. Building test benches --------------------------------------------------
7. Building test benches --------------------------------------------------
7a. General instructions ---------------------------------------------
7a. General instructions ---------------------------------------------
  To compile a test bench named  all is needed is
  To compile a test bench named  all is needed is
    make 
    make 
  The make file will use .vbom, create all make dependency files,
  The make file will use .vbom, create all make dependency files,
  and generate the needed ghdl commands.
  and generate the needed ghdl commands.
  In many cases the test benches can also be compiled against the gate
  In many cases the test benches can also be compiled against the gate
  level models derived after the xst, map or par step. To compile them
  level models derived after the xst, map or par step. To compile them
    make ghdl_tmp_clean
    make ghdl_tmp_clean
    make _ssim                  # for post-xst
    make _ssim                  # for post-xst
    make _fsim                  # for post-map
    make _fsim                  # for post-map
    make _tsim                  # for post-par
    make _tsim                  # for post-par
  The 'make ghdl_tmp_clean' is needed to flush the ghdl work area from
  The 'make ghdl_tmp_clean' is needed to flush the ghdl work area from
  the compilation remains of earlier functional model compiles.
  the compilation remains of earlier functional model compiles.
7b. Available test benches -------------------------------------------
7b. Available test benches -------------------------------------------
  See file w11a_tb_guide.txt
  See file w11a_tb_guide.txt
8. Building systems -------------------------------------------------------
8. Building systems -------------------------------------------------------
8a. General instructions ---------------------------------------------
8a. General instructions ---------------------------------------------
  To generate a bit file for a system named  all is needed is
  To generate a bit file for a system named  all is needed is
    make .bit
    make .bit
  The make file will use .vbom, create all make dependency files, build
  The make file will use .vbom, create all make dependency files, build
  the ucf file with cpp, and run the synthesis flow (xst, ngdbuild, par, trce).
  the ucf file with cpp, and run the synthesis flow (xst, ngdbuild, par, trce).
  The log files will be named
  The log files will be named
      _xst.log        # xst log file
      _xst.log        # xst log file
      _tra.log        # translate (ngdbuild) log file (renamed %.bld)
      _tra.log        # translate (ngdbuild) log file (renamed %.bld)
      _map.log        # map log file                  (renamed %_map.mrp)
      _map.log        # map log file                  (renamed %_map.mrp)
      _par.log        # par log file                  (renamed %.par)
      _par.log        # par log file                  (renamed %.par)
      _pad.log        # pad file                      (renamed %_pad.txt)
      _pad.log        # pad file                      (renamed %_pad.txt)
      _twr.log        # trce log file                 (renamed %.twr)
      _twr.log        # trce log file                 (renamed %.twr)
  To load the bitfile with WebPack impact into the target board use
  To load the bitfile with WebPack impact into the target board use
    make .iconfig
    make .iconfig
  For boards with a Cypress FX2 USB controller load the bitfile directly with
  For boards with a Cypress FX2 USB controller load the bitfile directly with
    make .jconfig
    make .jconfig
  If only the xst or par output is wanted just use
  If only the xst or par output is wanted just use
    make .ngc
    make .ngc
    make .ncd
    make .ncd
  A simple 'message filter' system is also integrated into the make build flow.
  A simple 'message filter' system is also integrated into the make build flow.
  For many (though not all) systems a .mfset file has been provided which
  For many (though not all) systems a .mfset file has been provided which
  defines the xst,par and bitgen messages which are considered ok. To see
  defines the xst,par and bitgen messages which are considered ok. To see
  only the remaining message extracted from the vaious .log files simply
  only the remaining message extracted from the vaious .log files simply
  use the make target
  use the make target
    make .mfsum
    make .mfsum
  after a re-build.
  after a re-build.
8b. Configuring FPGAs ------------------------------------------------
8b. Configuring FPGAs ------------------------------------------------
  The make flow supports also loading the bitstream into FPGAs, either
  The make flow supports also loading the bitstream into FPGAs, either
  via Xilinx Impact, or via the Cypress FX2 USB controller is available.
  via Xilinx Impact, or via the Cypress FX2 USB controller is available.
  For Xilinx Impact a Xilinx USB Cable II has to be properly setup, than
  For Xilinx Impact a Xilinx USB Cable II has to be properly setup, than
  simply use
  simply use
    make .iconfig
    make .iconfig
  For using the Cypress FX2 USB controller on Digilent Nexys2, Nexys3 and
  For using the Cypress FX2 USB controller on Digilent Nexys2, Nexys3 and
  Atlys boards just connect the USB cable and
  Atlys boards just connect the USB cable and
    make .jconfig
    make .jconfig
  This will automatically check and optionaly re-load the FX2 firmware
  This will automatically check and optionaly re-load the FX2 firmware
  to a version matching the FPGA design, generate a .svf file from the
  to a version matching the FPGA design, generate a .svf file from the
  .bit file, and configure the FPGA. In case the bit file is out-of-date
  .bit file, and configure the FPGA. In case the bit file is out-of-date
  the whole design will be re-implemented before.
  the whole design will be re-implemented before.
8c. Available systems ------------------------------------------------
8c. Available systems ------------------------------------------------
  Note: Currently ready to build versions exist for
  Note: Currently ready to build versions exist for
          Digilent S3BOARD (-1000 FPGA version)
          Digilent S3BOARD (-1000 FPGA version)
          Digilent Nexys2 board (-1200 FPGA version)
          Digilent Nexys2 board (-1200 FPGA version)
          Digilent Nexys3 board
          Digilent Nexys3 board
  1. rlink tester
  1. rlink tester
     a. for Digilent Nexys2 board
     a. for Digilent Nexys2 board
        cd $RETROBASE/rtl/sys_gen/tst_rlink/nexys2
        cd $RETROBASE/rtl/sys_gen/tst_rlink/nexys2
        make sys_tst_rlink_n2.bit
        make sys_tst_rlink_n2.bit
     b. for Digilent Nexys3 board
     b. for Digilent Nexys3 board
        cd $RETROBASE/rtl/sys_gen/tst_rlink/nexys3
        cd $RETROBASE/rtl/sys_gen/tst_rlink/nexys3
        make sys_tst_rlink_n3.bit
        make sys_tst_rlink_n3.bit
  2. rlink over USB tester
  2. rlink over USB tester
     a. for Digilent Nexys2 board
     a. for Digilent Nexys2 board
        cd $RETROBASE/rtl/sys_gen/tst_rlink_cuff/nexys2/ic
        cd $RETROBASE/rtl/sys_gen/tst_rlink_cuff/nexys2/ic
        make sys_tst_rlink_cuff_ic_n2.bit
        make sys_tst_rlink_cuff_ic_n2.bit
 
 
 
     b. for Digilent Nexys3 board
 
 
 
        cd $RETROBASE/rtl/sys_gen/tst_rlink_cuff/nexys3/ic
 
        make sys_tst_rlink_cuff_ic_n3.bit
 
 
  3. w11a systems
  3. w11a systems
     a. for Digilent S3BOARD
     a. for Digilent S3BOARD
        cd $RETROBASE/rtl/sys_gen/w11a/s3board
        cd $RETROBASE/rtl/sys_gen/w11a/s3board
        make sys_w11a_s3.bit
        make sys_w11a_s3.bit
     b. for Digilent Nexys2 board
     b. for Digilent Nexys2 board
        cd $RETROBASE/rtl/sys_gen/w11a/nexys2
        cd $RETROBASE/rtl/sys_gen/w11a/nexys2
        make sys_w11a_n2.bit
        make sys_w11a_n2.bit
     c. for Digilent Nexys3 board
     c. for Digilent Nexys3 board
        cd $RETROBASE/rtl/sys_gen/w11a/nexys3
        cd $RETROBASE/rtl/sys_gen/w11a/nexys3
        make sys_w11a_n3.bit
        make sys_w11a_n3.bit
9. Generate Doxygen based source code view --------------------------------
9. Generate Doxygen based source code view --------------------------------
   Currently there is not much real documentation included in the source
   Currently there is not much real documentation included in the source
   files. The doxygen generated html output is nevertheless very useful
   files. The doxygen generated html output is nevertheless very useful
   to browse the code. C++, Tcl and Vhdl source are covered by setup files
   to browse the code. C++, Tcl and Vhdl source are covered by setup files
   contained in the project files.
   contained in the project files.
   To generate the html files
   To generate the html files
     cd $RETROBASE/tools/dox
     cd $RETROBASE/tools/dox
     export RETRODOXY 
     export RETRODOXY 
     ./make_doxy
     ./make_doxy
   If RETRODOXY is not defined '/tmp' is used. To view the docs use
   If RETRODOXY is not defined '/tmp' is used. To view the docs use
     firefox $RETRODOXY/w11/cpp/html/index.html &
     firefox $RETRODOXY/w11/cpp/html/index.html &
     firefox $RETRODOXY/w11/tcl/html/index.html &
     firefox $RETRODOXY/w11/tcl/html/index.html &
     firefox $RETRODOXY/w11/vhd/html/index.html &
     firefox $RETRODOXY/w11/vhd/html/index.html &
 
 

powered by: WebSVN 2.1.0

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