Dane Martel CMPE

1
ECE 290 Final Presentation
Verilog Program Interface

• Dane Martel CMPE
• Noor Yahia CMPE
• Mark Ragaza EE

Advisor Professor John Chandy
2
Problem

• Large scale integrated circuits are created in
  design programs such as Cadence, Xilinx,
  ModelSim.
• The cost of going from software to hardware
  prototypes costs the company thousands millions
  of dollars in production costs.
• If a serious mistake is made the design must be
  corrected in software and a prototype reproduced.
• Hardware taking in multiple signals can be hard
  to interpret.
• The interpretation process can be misread
  depending on the number of signals that must be
  compared.

3
Example

• A company needs to develop a VGA Controller for a
  LCD screen they plan to use in a product.
• In order for them to test their design they need
  to implement it in hardware.
• This is time consuming
• Costs money
• They need a way to test their design in software,
  so they can minimize the amount of prototypes
  they build in hardware.

4
Solution

• We need a program that interfaces with the
  software to allow testing
• The program will help cut costs involved in
  developing hardware
• Allows for better training of new employees
• Allow devices that have multiple data input be
  represented in software.
• Design a simulator that allows designers to
  simulate codes without the construction of
  expensive prototypes

5
Solution
6
Simulation Programs

• Modelsim
• Xilinx
• Cadence
• Icarus
• Verilator
• Hardware Description Languages
• System C
• VHDL
• Verilog
• System Verilog

7
Simulation Program

• Modelsim
• Used in Windows/Linux
• Supports VHDL, Verilog, and System C,
• Limited to student edition
• Support for program interfaces through multiple
  programming languages.

8
Verilog

• Simpler Language
• Compatible with ModelSim Simulator
• Uses VPI/PLI interfaces

9
VPI/PLI

• The Verilog Procedural Interface (VPI) is a
  C-programming interface for the Verilog
• VPI provides consistent, object-oriented access
  to the complete Verilog language
• VPI consists of routines that allow you to
  utilize standard C programming language
  functions.
• These routines interact with simulation objects
  contained in Verilog designs.
• Any simulation program that supports PLI/VPI can
  run our program

10
Verilog Interface Goals

• Easy to use graphical user interface (GUI)
• Low amount of time needed to training
• Include inputs and outputs that allow user to
  test their design
• Ability to change inputs during the simulation to
  test outputs
• Allow the program to interface with multiple CAD
  programs on multiple platforms

11
Platform Independent GUI

• Can operate on multiple operating systems.
• Saves developers time and money in optimizing for
  newer builds.
• Less of a hassle in debugging platform specific
  errors.
• Examples
• Fox
• QT
• Amulet
• MiniGUI

12
Program User Interface

• The program will provide user a choice of using
  hardware inputs such as
• Keyboard (PS/2 Interface)
• Switches
• The inputs drive software simulated outputs in
  our program
• Monitor (Standard VGA Interface)
• LED
• The user will choose the inputs and outputs and
  our program will build an interface for them.

13
Input

• Switch
• Changes to logic input in simulation
• Shows the current state of input

14
Output

• LED
• On for logical 1
• Off for logical 0

15
Input

• Keyboard (PS/2 Interface)
• Pin 1 DATA
• Pin 2 Not connected
• Pin 3 GND
• Pin 4 5 V DC at 100 mA
• Pin 5 CLK
• Pin 6 Not connected

16
Output

• Monitor (VGA Interface)
• 640x480 in 16 colors
• Pin Layout
• Pin 1 Red Video
• Pin 2 Green Video
• Pin 3 Blue Video
• Pin 4 Horizontal Sync
• Pin 5 Vertical Sync
• Pin 6-9 Ground

17
GUI
18
Project Phases
19
Budget

• Employee Costs 0
• Materials Costs 0
• Transportation Costs 0
• Software Costs 0
• Visual Studio
• Free for Students
• Simulation Programs
• Provided by school or student licenses
• Total Costs 0

20
Conclusion

• Will lower overall costs in hardware design
• Allow students/developers to train better
• Speed up the time on debugging design
• Test complicated designs without having to build
• Questions??