BYU's SLAAC1 JHDL® Site
Introduction
The SLAAC1 board was created as a part of the SLAAC project under
DARPA sponsorship and is currently being used at a number of locations.
See the
SLAAC
HomePage for more information about the SLAAC project and the
board.
A simulation and debug environment have been created at BYU to use
with this board. This environment simplifies the creation of designs
for SLAAC1. See the examples below to understand how you can create
designs for SLAAC1 and simulate and execute them.
Currently these models are not being supported although one can
download the following jars and corresponding JHDL releases which were
the releases the models were last compiled against.
Slaac1 Rev A Download (for use with JHDL 0.2.14):
Slaac1 Rev B Download (for use with JHDL 0.2.27):
Examples
Both these examples were written for the rev A board, but they can be
ported over to the rev B board by simply importing
byucc.jhdl.platforms.slaac1b instead of byucc.jhdl.platforms.slaac1 in
the pertinent java files.
Backend Compilation
To make the backend compilation proceed as smoothly as possible, there
is a tar file which contains everything needed to compile a design.
This version will work when compiling
on HPUX and Linux under wine (you probably will have to change a few
variables depending on where you install the Xilinx tools in your
Linux wine environment).
You can get it using the following link:
slaac1revAsynth.tar
slaac1revBsynth.tar
Untar this file in your project directory (the same place where your
java and class files are that you load into the Slaac1 model).
Note:
This will extract a Makefile and could overwrite a Makefile which you
already have in this directory.
To untar the file use one of the following commands (depending if
you are using a rev A or a rev B board):
gtar -xvf slaac1revAsynth.tar
gtar -xvf slaac1revBsynth.tar
Now, you will need to edit the Makefile. The lines that start
export
CLASSX will need to be edited. You can just replace the "notset"s
with your classnames (without the .class extension). If you are not using a PE, make sure that the
value remains at notset, otherwise the make utility will die at that PE
and may not compile all your designs. Also make sure to use gmake for
proper operation.
Make sure that the Xilinx tools are in your path.
Then you can siimply type gmake to
compile the design. Note: This stage of the compile will only
work on a machine which actually has the Xilinx software installed.
When this completes you will have a placed and routed design file.
To make the binary files (.bit) which are loaded onto the FPGAs type
gmake
bin. This will finish making the files needed to run your
design on the Slaac1 hardware.
Hardware Execution
The above hardware examples have been successfully executed on SLAAC1,
complete with readback using JHDL under Windows NT and linux.
To do this you under Windows NT will need the following (this has
currently only been tested for the rev A board):
- This DLL file which should be put
into either your PATH or in the directory where you are executing
from.
- The SLAAC1 board driver and runtime libraries. See
[email protected]
for the proper copy of the driver and libraries.
- The above synthethis files.
To do this you under linux, you will need the following:
- The SLAAC1 board driver and runtime libraries. See
[email protected] for the proper copy of the driver and
libraries and instruction on how to set them up on your machine.
- The library file libjavasl1.so which
serves as the liason between the JHDL Java environment and the C++
calls of the slaac runtime libraries.
- The above synthethis files.
To install the libjavasl1.so file under linux do the following (you
will need to be root for some of the following). The following is
only tested for the slaac1 rev B models.
- Put libjavasl1.so in some directory on the computer you will be
using (in mine I put it in /usr/local/lib).
- Edit the /etc/ld.so.conf file so that the directory you put the
file in will be put in the library cache.
- Run the following command as root:
/sbin/ldconfig
This will rebuild the libarary cache. You can check that things are
correct by running /sbin/ldconfig -p and it will list all
the libs found in the cache.
[email protected]
Last modified: Tue Feb 20 15:33:07 MST 2001