Instructions for Running JBits SDK on XESS XSV board

1. xsv.class

   This is the XHWIF interface. If you have installed JBits 2.6 or any higher version this file would have been installed under com/xilinx/XHWIF/Boards by the installer.

   This interface defaults for XCV800 device and HQ240. If your board has a different device or/and package, say for example XCV300 and PQ240, then all you have to do to support that particular device and package is to create a class, say, xsv300 as shown below.

   package com.xilinx.XHWIF.Boards;

   import com.xilinx.JBits.Virtex.Devices;
   import com.xilinx.XHWIF.XHWIF;
   

   /**
   **
   ** This is the interface to support XESS board to support devices
   ** other than the default device (XCV800) on XESS board **
   **
   ** See the comments in XHWIF.java for a description of the
   ** functions in this class.
   **
   */

   public class xsv300 extends xsv {

   /* The parameters below define the system */
   private final static int boardxsv300[] = {Devices.XCV300};
   private final static int boardxsvpkg[] = {Devices.PQ240};
   

   /*
   ** This constructor sets the device type for XESS XCV300 device
   ** Change the device according to your system
   */

   public xsv300() {
       devType = boardxsv300;
       pkgType = boardxsvpkg;
   }

   }; /* end class */

   The above example is given for XCV300 device with a PQ240 package but change it to with whatever your system has. Compile and place this class file under com/xilinx/XHWIF/Boards. This would enable xsv.class file to support your device and package.

2. xsvJNI.dll

   This is the native interface needed for XHWIF interface to talk to the board. Place this under winnt/system32 for Win NT machine. If not placing under winnt/system32 make sure that this is placed under some directory pointed by the system path environment variable.

3. vir.svf

   This is the NEW CPLD interface that would be needed by the XESS board to support JBits. This has to be downloaded to the CPLD using the Load utility provided by XESS.

   Apart from this you have to REMOVE shunt from J36 jumper, when using JBits SDK with the XESS board. J36 jumper provides the clock for the FPGA using the on-board oscillator. But if you are single stepping the clock using BoardScope or XHWIF this SHOULD NOT be used AT ALL. If J36 is present and if you are trying to single step using Boardscope or XWIF then it will cause a contention on the CLOCK line and may damage the device and board.

Check List

1. Remove shunt from J36 jumper
2. Download the New CPLD interface
3. Place the Native Interface(xsvJNI.dll) in the menitoned directory
4. Place the xsv.class file in the mentioned directory.
5. If needed, to support the device on your board, create the class file as shown in the example and place that in the mentioned directory.
6. Download NULL bitstream as a test case using XHWIF's main() routine. The command is shown below.

java com.xilinx.XHWIF.XHWIF -xsv infile.bit

java RunBoardScope -xsv

If you have created an additional class file, say for example, xsv300.class, to support the device and package specific to your board, then the example command to test the interface is shown below:

java com.xilinx.XHWIF.XHWIF -xsv300 infile.bit

java RunBoardScope -xsv300

WARNING: Xilinx Inc is not responsible for damage caused by improper installation of the board.