Creating the eVA Plugin

The hardware-specific eVA Plugin for Visual applets is created out of the following files:

  • Mandatory:
    • Hardware description file (*.xml), including operator definitions (see Defining Hardware-Specific Operators)
    • Top-level netlist, including wrapped IP core black box (*.ngc / *.edn) (see box below)
    • Constraints file (*.ucf format if you use Xilinx ISE®, *.xdc format if you use Xilinx Vivado®) (see box below)
  • Optional:
    • Icon file for the hardware device (*.png) for graphical representation of hardware in VisualApplets GUI
    • Icon files for the individual hardware-specific operators (*.png) for graphical representation of operators in VisualApplets GUI
    • Help files for the platform specific operators (*.html)

All these files you have already entered to eVA Designer while working through the steps described in sections Defining the IP Core Properties and Entering Build Flow Details .

VA IP Core Netlist Generation

 

You can also create a plugin installer without top-level netlist and constraints file. After installation, you will be able to see how the integration looks like in VisualApplets (available hardware-specific operators etc.).

However, with a plugin that doesn’t contain the top-level netlist and constraints file, you cannot build applets that can run on your hardware platform.

   

To build the actual eVA Plugin for VisualApplets, you have two options. You can either

  • Build and immediately install the eVA Plugin into the VisualApplets 3 installation on your machine.
  • Build an executable eVA Plugin installer which you can provide to colleagues and/or customers.
(missing or bad snippet)