Help-Site Computer Manuals
Software
Hardware
Programming
Networking
  Algorithms & Data Structures   Programming Languages   Revision Control
  Protocols
  Cameras   Computers   Displays   Keyboards & Mice   Motherboards   Networking   Printers & Scanners   Storage
  Windows   Linux & Unix   Mac

B<Verilog::Codegen::Gui>
Verilog code generator GUI

B<Verilog::Codegen::Gui> - Verilog code generator GUI


NAME

Verilog::Codegen::Gui - Verilog code generator GUI


SYNOPSIS


  $ ./gui.pl [design name]

The GUI and its utility scrips are in the scripts folder of the distribution.

The design name is optional. If no design name is provided, the GUI will check the .vcgrc file for one. If this file does not exists, the design library module defaults to DeviceLibs/Verilog.pm and the objects will reside directly under DeviceLibs/Objects. Otherwise, the design library module will be DeviceLibs/YourDesign.pm and the objects will reside under DeviceLibs/YourDesign/Objects. You can also set the design name via the GUI.


USAGE

The GUI is very simple to use. A short manual:

To create, test and run Verilog code using the Verilog::CodeGen GUI:

0. Choose your design.

In the Design text entry field, type the full name of the design. Click Set.

If the design does not exist, it will be created, that is, an empty structure with skeleton files will be created. Otherwise, the design will be set to the entered value.

1. Create or edit the Device Object.

This is the Perl script that will generate the Verilog code.

  • If this is a new file:

    In the Device Object Code area text entry field, type the full name of the script, including the .pl extension. Click Edit (hitting return does not work). The GUI will create a skeleton from a template, and open it in XEmacs.

  • If the file already exists:

    -If this was the last file to be modified previously, just click Edit. The GUI will open the file in XEmacs.

    -If not, type the beginning of the file in the Device Object Code text entry field, then click Edit. The GUI will open the first file matching the pattern in XEmacs.

2. Test the object code

In the Device Object Code area, click Parse. This executes the script and displays the output in the Output log window. Ticking the Show result tick box will cause the output to be displayed in an XEmacs window. To close this window, click Done. This is a modal window, in other words it will freeze the main display as long as it stays open.

3. Add the Device Object to the Device Library

When the object code is bug finished, click Update in the Device Library Module area. This will add the device object to the device library (which is a Perl module). Ticking the Show module tick box will cause the complete library module to be displayed in an XEmacs window. To close this window, click Done. This is a modal window, in other words it will freeze the main display as long as it stays open.

4. Create or edit the test bench code

This is the Perl script that will generate the Verilog testbench code.

  • If this is a new file:

    In the Testbench Code area text entry field, type the full name of the script, including the .pl extension, click Edit. The GUI will create a skeleton from a template, and open it in XEmacs.

  • If the file already exists:

    -If this was the last file to be modified previously, just click Edit. The GUI will open the file in XEmacs.

    -If not, type the beginning of the file in the Device Object Code text entry field. The testbench must have the name test_[device obect file name]. Then click Edit. The GUI will open the first file matching the pattern in XEmacs.

    -If the Overwrite tick box is ticked, the existing script will be overwritten with the skeleton. This is usefull in case of major changes to the device object code.

5. Test the testbench code

In the Testbench Code area, click Parse. This executes the script and displays the output in the Output log window.

-Ticking the Show result tick box will cause the output to be displayed in an XEmacs window. To close this window, click Done. This is a modal window, in other words it will freeze the main display as long as it stays open.

-Ticking the Inspect code tick box will open a browser window with pages generated by the v2html Verilog to HTML convertor.

-Ticking the Run tick box will execute the generated testbench.

-Ticking the Plot tick box will plot the simulation results (if any exist).


REQUIREMENTS

To use a different Verilog compiler/simulator and/or VCD viewer:

In CodeGen.pm, change the following lines:


   #Modify this to use different compiler/simulator/viewer

   my $compiler="/usr/bin/iverilog";

   my $simulator="/usr/bin/vvp";

   my $vcdviewer="/usr/local/bin/gtkwave";


TODO

  • Convert the utility scripts to functions to be called from Verilog::CodeGen.

  • Put the GUI scripts in a module Gui.pm.


AUTHOR

W. Vanderbauwhede wim@motherearth.org.

http://www.comms.eee.strath.ac.uk/~wim


COPYRIGHT

Copyright (c) 2002,2003 Wim Vanderbauwhede. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

Programminig
Wy
Wy
yW
Wy
Programming
Wy
Wy
Wy
Wy