Difference between revisions of "Documents/NPL Build Project"

From Nutwiki
Jump to: navigation, search
(Created page with "<div id="content"> = NPL Tutorial - Step 3 = Previous Contents  Next == Building The ISE Project == We will now bui...")
(No difference)

Latest revision as of 09:42, 13 July 2017

NPL Tutorial - Step 3

Previous Contents  Next

Building The ISE Project

We will now build the binary file to be uploaded to the CPLD.

[[File:../../img/ise-build-proj01.png|ISE Build Project 01]] Select the Verilog Source npltut01.v in the Sources in Project Window and Implement Design in the Processes for Source "npltut01" Window. From the Process Menu select Rerun All.

[[File:../../img/ise-build-proj02.png|ISE Build Project 02]] The process will take some seconds and finally present a Fitter Report in the Edit Window. You may have noticed several warnings, which are caused by unused input pins. The reason is, that the User Constraint File specifies all pin signals of the Ethernut CPLD, but our simple Verilog Source will only use a few of them. Thus, you can safely ignore the warnings.

Now scroll down the Processes Tree and select Generate SVF/XSVF/STAPL File. Open the Process Menu again and select Run.

[[File:../../img/ise-build-proj03.png|ISE Build Project 03]] This will invoke the iMPACT Utility. This is the programming software for Xilinx Programmable Logic Chips, similar to the JTAG-O-MAT for the ARM7 or avrdude for the AVR. However, we will not directly program the CPLD with this tool, but create a programming file instead. This file will be later implanted in a Nut/OS application called XSVF Executor, which in turn will be uploaded to the Ethernut Board. When the XSVF Executor is started, it will program the CPLD using the programming file.

Select Boundary-Scan-File on the first dialog page, because this is what the Executor expects.

[[File:../../img/ise-build-proj04.png|ISE Build Project 04]] Three different boundary scan file formats are offered on the next page. Select XSVF File.

[[File:../../img/ise-build-proj05.png|ISE Build Project 05]] A file creation dialog will appear. Enter enut30d.xsvf. iMPACT will store all programming instructions in this file.

[[File:../../img/ise-build-proj06.png|ISE Build Project 06]] Press OK.

[[File:../../img/ise-build-proj07.png|ISE Build Project 07]] Finally iMPACT queries us for the name of the device file. Luckily ISE created one for us during the Design Implementation Phase. It got the same name as our project and the extension .jed (for Jedec). Select this file and press the Open button.

[[File:../../img/ise-build-proj08.png|ISE Build Project 08]] After returning to the iMPACT main window, we notice that an image of a Xilinx chip appeared. Click on this image and select Program... from the Operations Menu.

[[File:../../img/ise-build-proj09.png|ISE Build Project 09]] In the Program Options Dialog make sure that Erase Before Programming and Verify are both selected and that all other options are deselected.

Press OK to start programming. As stated above, the programming commands are now stored in the xsfv file.

[[File:../../img/ise-build-proj10.png|ISE Build Project 10]] After a few seconds Programming Succeeded should appear in the main window. We can quit the iMPACT utility. As a result we end up with the XSVF file.

Previous Contents  Next