VHDL: Xilinx ISE - Revision history

Krueger at 14:18, 18 July 2007

2007-07-18T14:18:20Z

Krueger at 20:13, 9 July 2007

2007-07-09T20:13:39Z

Krueger at 20:08, 9 July 2007

2007-07-09T20:08:20Z

Krueger at 20:04, 9 July 2007

2007-07-09T20:04:09Z

Krueger at 19:56, 9 July 2007

2007-07-09T19:56:04Z

Krueger at 19:53, 9 July 2007

2007-07-09T19:53:31Z

Krueger at 19:51, 9 July 2007

2007-07-09T19:51:18Z

Krueger at 19:37, 9 July 2007

2007-07-09T19:37:03Z

Krueger at 19:29, 9 July 2007

2007-07-09T19:29:11Z

Krueger at 19:28, 9 July 2007

2007-07-09T19:28:08Z

← Older revision		Revision as of 14:18, 18 July 2007
Line 12:		Line 12:

	Now that we've discussed VHDL itself, it's time to learn the development environment. If you don't already have it installed, you will want to install the [http://www.xilinx.com/ise/logic_design_prod/webpack.htm Xilinx ISE WebPACK]. The ISE Foundation is a professional tool that will cost you an arm and a leg. The ISE WebPACK is a free version of the software that does most of what you need (unless you have large, complex designs or are working with the newest and best Xilinx FPGAs). If you know ahead of time which series of FPGAs you plan to use, you can save time and disk space by only installing the files for that FPGA series. Once you've got that installed, fire it up.		Now that we've discussed VHDL itself, it's time to learn the development environment. If you don't already have it installed, you will want to install the [http://www.xilinx.com/ise/logic_design_prod/webpack.htm Xilinx ISE WebPACK]. The ISE Foundation is a professional tool that will cost you an arm and a leg. The ISE WebPACK is a free version of the software that does most of what you need (unless you have large, complex designs or are working with the newest and best Xilinx FPGAs). If you know ahead of time which series of FPGAs you plan to use, you can save time and disk space by only installing the files for that FPGA series. Once you've got that installed, fire it up.
		+
		+	If you find this tutorial a bit lacking, then you'll want to look over the [http://toolbox.xilinx.com/docsan/xilinx9/books/manuals.pdf ISE manuals].

	== Creating a new project ==		== Creating a new project ==

@@ Line 48: / Line 48: @@
 [[Image:ISE - RTL.PNG|thumb|left|125px|The Register Transfer Level Schematic.]]
-Once you've synthesized your design, double click on "View RTL Schematic".  RTL stands for Register Transfer Level.  This gives you what is effectively a block diagram of your circuit, with all the gates and parts in place and wired together.  As discussed in previous sections, a thick wire is a bus.  By extension, a part drawn with thick lines has bus I/O but performs the same function for all lines of the bus.  Inputs are shown on the left as arrows pointing to the right with lines and buses coming off the points of the arrows.  Outputs are shown on the right as arrows pointing to the right with lines and buses entering the flat ends of the arrows.  Branches of the wires are shown as dots at the intersection points; intersections without dots are separate wires that happen to cross without connecting to each other.  You can also double click "View Technology Schematic."  This is similar to the RTL schematic, however there is no blocking of components together functionally, nor will multiple lines be combined into buses.  It can be a rather large, intimidating, and confusing view so it is not often used, as RTL gives the same information in a much more comprehensible fashion.
+Once you've synthesized your design, double click on "View RTL Schematic".  RTL stands for Register Transfer Level.  This gives you what is effectively a block diagram of your circuit, with all the gates and parts in place and wired together.  As discussed in previous sections, a thick wire is a bus.  By extension, a part drawn with thick lines has bus I/O but performs the same function for all lines of the bus.  Inputs are shown on the left as arrows pointing to the right with lines and buses coming off the points of the arrows.  Outputs are shown on the right as arrows pointing to the right with lines and buses entering the flat ends of the arrows.  Branches of the wires are shown as dots at the intersection points; intersections without dots are separate wires that happen to cross without connecting to each other.  To enter a block, simply double click on it.  To exit a block and go back to the next higher schematic, you can right click and select "Pop to the Calling Schematic."
 == Simulation ==
@@ Line 71: / Line 73: @@
 Once you have defined your input waveforms (don't bother trying to set your output waveforms; those get defined by the simulator), you are now ready to simulate.  Go to the Processes box and double click "Simulate Behavioral Model" (under "Xilinx ISE Simulator").  ISE will think for a bit then open a new window like the one shown to the right.  This shows the input and output signal waveforms.  You can see the internal bus ''count'' (highlighted) expanded to show both the bus notation mentioned above (values in hex) and the individual line waveforms.  You'll have to study these waveforms closely to debug many of your designs.  Timing hazards may appear here (a signal fires a clock cycle too early or too late and ruins the synchronization of the entire device, etc.).  If you look over this design and decide you are happy with the output, then you have successfully designed and done basic testing in VHDL.

← Older revision		Revision as of 20:08, 9 July 2007
Line 68:		Line 68:
	To set the values, simply click on the waveforms wherever you want the value to be toggled. If you wish to use one of the 7 non-binary logic levels ([[VHDL_tutorial#VHDL_Resolution_Table\|shown here]]) or to set a pattern for ISE to fill in for you, right click on the waveform where you wish to start the pattern or non-binary logic level and select "Set Value." Beware of having too many transitions, as it is possible to crash the program that way.		To set the values, simply click on the waveforms wherever you want the value to be toggled. If you wish to use one of the 7 non-binary logic levels ([[VHDL_tutorial#VHDL_Resolution_Table\|shown here]]) or to set a pattern for ISE to fill in for you, right click on the waveform where you wish to start the pattern or non-binary logic level and select "Set Value." Beware of having too many transitions, as it is possible to crash the program that way.

−	Once you have defined your input waveforms (don't bother trying to set your output waveforms; those get defined by the simulator), you are now ready to simulate. Go to the Processes box and double click "Simulate Behavioral Model" (under "Xilinx ISE Simulator"). ISE will think for a bit then open a new window like the one shown to the right.	+	[[Image:ISE - Simulation.PNG\|thumb\|right\|125px\|Simulation results view.]]
		+
		+	Once you have defined your input waveforms (don't bother trying to set your output waveforms; those get defined by the simulator), you are now ready to simulate. Go to the Processes box and double click "Simulate Behavioral Model" (under "Xilinx ISE Simulator"). ISE will think for a bit then open a new window like the one shown to the right. This shows the input and output signal waveforms. You can see the internal bus ''count'' (highlighted) expanded to show both the bus notation mentioned above (values in hex) and the individual line waveforms. You'll have to study these waveforms closely to debug many of your designs. Timing hazards may appear here (a signal fires a clock cycle too early or too late and ruins the synchronization of the entire device, etc.). If you look over this design and decide you are happy with the output, then you have successfully designed and done basic testing in VHDL.

@@ Line 56: / Line 56: @@
 [[Image:ISE - Make New TBW.PNG|thumb|right|125px|Dialog box for creating a new test bench waveform.]]
-Go to '''Project > New Source''' and select "Test Bench Waveform."  Give the file a name and choose a parent directory, then click next.  The next dialog box will ask you which source file to associate with the text bench waveform file.  Select the file you wish to text and click next.  Verify the details you just selected and click finish.  This will bring up the dialog box shown to the right.  Chances are you won't need to change (or even worry about) most of that window.  However in the bottom right corner you can see "Initial Length of Test Bench".  The default value for that tends to be too small for a design of any size; I generally set it to 10,000.  You can try to be clever and change it from 10,000 ns to 10<math>\mu</math>s, but it won't work; changing the time unit adjusts other values across the dialog box.  So just type in "10000".
+Go to '''Project > New Source''' and select "Test Bench Waveform."  Give the file a name and choose a parent directory, then click next.  The next dialog box will ask you which source file to associate with the text bench waveform file.  Select the file you wish to text and click next.  Verify the details you just selected and click finish.  This will bring up the dialog box shown to the right.  Chances are you won't need to change (or even worry about) most of that window.  However in the bottom right corner you can see "Initial Length of Test Bench".  The default value for that tends to be too small for a design of any size; I generally set it to 10,000.  You can try to be clever and change it from 10,000 ns to 10<math>\mu</math>s, but it won't work; changing the time unit adjusts other values across the dialog box.  So just type in "10000" (or whatever other number you feel is best).
 If you have an existing .tbw file that you want to use, go to the Sources box, change the pull-down menu to "Behavioral Simulation", and double click on the file you want.
@@ Line 62: / Line 62: @@
 [[Image:ISE - TBW.PNG|thumb|left|125px|Test bench waveform editor.]]
-So now you have your test bench waveform open.  Your screen will look something along the lines of the one shown to the left.  In the main section of the screen you see the waveforms
+So now you have your test bench waveform open.  Your screen will look something along the lines of the one shown to the left.  In the main section of the screen you see the waveforms for the inputs and outputs.  You can change which waveforms are shown.  To delete a waveform, click on the name and press the delete key.  To add a waveform (including internal signals if you want to monitor those), go to the Processes box in the bottom left and double click on the name of the signal you wish to add to the waveform.

← Older revision		Revision as of 19:56, 9 July 2007
Line 60:		Line 60:
	If you have an existing .tbw file that you want to use, go to the Sources box, change the pull-down menu to "Behavioral Simulation", and double click on the file you want.		If you have an existing .tbw file that you want to use, go to the Sources box, change the pull-down menu to "Behavioral Simulation", and double click on the file you want.

−	So now you have your test bench waveform open. Your screen will look something along the lines of the one shown to the left.	+	[[Image:ISE - TBW.PNG\|thumb\|left\|125px\|Test bench waveform editor.]]
		+
		+	So now you have your test bench waveform open. Your screen will look something along the lines of the one shown to the left. In the main section of the screen you see the waveforms

← Older revision		Revision as of 19:53, 9 July 2007
Line 57:		Line 57:

	Go to '''Project > New Source''' and select "Test Bench Waveform." Give the file a name and choose a parent directory, then click next. The next dialog box will ask you which source file to associate with the text bench waveform file. Select the file you wish to text and click next. Verify the details you just selected and click finish. This will bring up the dialog box shown to the right. Chances are you won't need to change (or even worry about) most of that window. However in the bottom right corner you can see "Initial Length of Test Bench". The default value for that tends to be too small for a design of any size; I generally set it to 10,000. You can try to be clever and change it from 10,000 ns to 10<math>\mu</math>s, but it won't work; changing the time unit adjusts other values across the dialog box. So just type in "10000".		Go to '''Project > New Source''' and select "Test Bench Waveform." Give the file a name and choose a parent directory, then click next. The next dialog box will ask you which source file to associate with the text bench waveform file. Select the file you wish to text and click next. Verify the details you just selected and click finish. This will bring up the dialog box shown to the right. Chances are you won't need to change (or even worry about) most of that window. However in the bottom right corner you can see "Initial Length of Test Bench". The default value for that tends to be too small for a design of any size; I generally set it to 10,000. You can try to be clever and change it from 10,000 ns to 10<math>\mu</math>s, but it won't work; changing the time unit adjusts other values across the dialog box. So just type in "10000".
		+
		+	If you have an existing .tbw file that you want to use, go to the Sources box, change the pull-down menu to "Behavioral Simulation", and double click on the file you want.
		+
		+	So now you have your test bench waveform open. Your screen will look something along the lines of the one shown to the left.

← Older revision		Revision as of 19:51, 9 July 2007
Line 53:		Line 53:

	Now that you've written your code and seen the RTL schematic (then fixed your code and seen the new RTL schematic and repeated that whole process a few times) it's time to see if it actually works. To do that you need to run a simulation. Unfortunately, it's not that easy; you first need to define a '''test bench waveform''' (.tbw) file.		Now that you've written your code and seen the RTL schematic (then fixed your code and seen the new RTL schematic and repeated that whole process a few times) it's time to see if it actually works. To do that you need to run a simulation. Unfortunately, it's not that easy; you first need to define a '''test bench waveform''' (.tbw) file.
		+
		+	[[Image:ISE - Make New TBW.PNG\|thumb\|right\|125px\|Dialog box for creating a new test bench waveform.]]
		+
		+	Go to '''Project > New Source''' and select "Test Bench Waveform." Give the file a name and choose a parent directory, then click next. The next dialog box will ask you which source file to associate with the text bench waveform file. Select the file you wish to text and click next. Verify the details you just selected and click finish. This will bring up the dialog box shown to the right. Chances are you won't need to change (or even worry about) most of that window. However in the bottom right corner you can see "Initial Length of Test Bench". The default value for that tends to be too small for a design of any size; I generally set it to 10,000. You can try to be clever and change it from 10,000 ns to 10<math>\mu</math>s, but it won't work; changing the time unit adjusts other values across the dialog box. So just type in "10000".

@@ Line 44: / Line 44: @@
 Those of you familiar with computer programming may think of this step as "compiling", but since you're not generating an executable file it's not really the same thing.  Synthesis is the step that takes your VHDL code and generates from it a schematic for your circuit.
-Once you've written your code and are ready to see how the schematic looks, go up to the Sources box and set it as the top module.  And make sure that the file you wish to synthesize is selected.  Then go down to the '''Processes''' box and double click on "Synthesize - XST".  If you do not see that option, then you forgot to set your file as the top module.  The User Constraints section allows you to tie certain I/O lines to specific pins on the package.  You can see that in the image Synthesis - XST has a little yellow triangle with an exclamation point next to it.  That means that the design has synthesized with no errors but has warnings.  Double click on "View Synthesis Report" to see any errors and warnings.  Some warnings can safely be ignored, others must be take care of.  An error will generate a red icon.  If ISE is uncertain if the latest version of the file has been synthesized or not, it will place an orange icon with a question mark.  Double clicking Synthesize - XST runs the synthesis, and you can right click and select rerun if you want to be sure the file is up-to-date.
+Once you've written your code and are ready to see how the schematic looks, go up to the Sources box and set it as the top module.  And make sure that the file you wish to synthesize is selected.  Then go down to the '''Processes''' box and double click on "Synthesize - XST".  If you do not see that option, then you forgot to set your file as the top module.  The User Constraints section allows you to tie certain I/O lines to specific pins on the package.  You can see that in the image Synthesis - XST has a little yellow triangle with an exclamation point next to it.  That means that the design has synthesized with no errors but has warnings.  Double click on "View Synthesis Report" to see any errors and warnings.  Some warnings can safely be ignored, others must be take care of.  An error will generate a red icon.  If ISE is uncertain if the latest version of the file has been synthesized or not, it will place an orange icon with a question mark.  And of course a green icon with a check mark means that the synthesis completed with no errors and no warnings.  Double clicking Synthesize - XST runs the synthesis, and you can right click and select rerun if you want to be sure the file is up-to-date.
 [[Image:ISE - RTL.PNG|thumb|left|125px|The Register Transfer Level Schematic.]]

← Older revision		Revision as of 19:28, 9 July 2007
Line 49:		Line 49:

	Once you've synthesized your design, double click on "View RTL Schematic". RTL stands for Register Transfer Level. This gives you what is effectively a block diagram of your circuit, with all the gates and parts in place and wired together. As discussed in previous sections, a thick wire is a bus. By extension, a part drawn with thick lines has bus I/O but performs the same function for all lines of the bus. Inputs are shown on the left as arrows pointing to the right with lines and buses coming off the points of the arrows. Outputs are shown on the right as arrows pointing to the right with lines and buses entering the flat ends of the arrows. Branches of the wires are shown as dots at the intersection points; intersections without dots are separate wires that happen to cross without connecting to each other.		Once you've synthesized your design, double click on "View RTL Schematic". RTL stands for Register Transfer Level. This gives you what is effectively a block diagram of your circuit, with all the gates and parts in place and wired together. As discussed in previous sections, a thick wire is a bus. By extension, a part drawn with thick lines has bus I/O but performs the same function for all lines of the bus. Inputs are shown on the left as arrows pointing to the right with lines and buses coming off the points of the arrows. Outputs are shown on the right as arrows pointing to the right with lines and buses entering the flat ends of the arrows. Branches of the wires are shown as dots at the intersection points; intersections without dots are separate wires that happen to cross without connecting to each other.
		+
		+	== Simulation ==