Introduction
The Wilcard from Annapolis Micro Systems is a PCMCIA board that contains a single Xilinx Virtex processing element, the XCV300.
A simulation and debug environment have been created at BYU to use
with this board. This environment simplifies the creation of designs
for Wildcard. See the examples below to understand how you can create
designs for Wildcard and simulate and execute them.
To run JHDL™ simulation examples for Wildcard,
you will need the a JHDL™ release and the following jar file:
This jar was compiled against JHDL Development Release 0.3
(available for download from
this link
). You should put both the JHDL jar and wildcard jar in your
CLASSPATH.
Documentation
Examples
The following examples are documented to show you how to write a Wildcard circuit.
You should be able to compile and simulate these files.
Hardware Execution
The above hardware examples have been successfully executed on the Wildcard
using JHDL™ under Windows 98 and Linux. Windows NT is not supported by
Annapolis Micro Systems.
To do this you under Windows 98 will need the following:
- The Wildcard board driver and runtime libraries. These should have come with
your Wildcard from Annapolis.
- This DLL file, javaWClib.dll, which should be put
into either your PATH or in the directory where you are executing
from.
To do this you under Linux will need the following:
- The Wildcard board driver and runtime libraries. These should have come with
your Wildcard from Annapolis.
- The library file libjavaWC.so which
serves as the liason between the JHDL Java environment and the C++
calls of the Wildcad runtime libraries.
To install the libjavaWC.so file under Linux do the following (you
will need to be root for some of the following).
- Put libjavaWC.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.
koechemr@ee.byu.edu
Last modified: Tue Feb 20 15:33:07 MST 2001