How to make a VHDL design in Ubuntu/Debian - Revision history

FabienM at 10:44, 30 June 2022

2022-06-30T10:44:55Z

← Older revision		Revision as of 12:44, 30 June 2022
Line 138:		Line 138:
	export PATH		export PATH

	Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.php Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus ~~sourceforge~~ project: [~~http~~://~~sourceforge~~.~~net~~/p/armadeus/~~code/ci~~/~~dcfda086d2b013b82e57f44bca156e5087a66581~~/~~tree~~/firmware/wishbone_example/wishbone_example9328_27/Makefile]. To use it modify the head and write the names of your files :		Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.php Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus gitlab project: [https://gitlab.com/armadeus/armadeus-bsp/-/blob/master/firmware/wishbone_example/wishbone_example9328_27/Makefile]. To use it modify the head and write the names of your files :

	*General options		*General options

Jorasse at 14:16, 16 December 2012

2012-12-16T14:16:15Z

← Older revision		Revision as of 16:16, 16 December 2012
Line 138:		Line 138:
	export PATH		export PATH

	Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.php Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://~~armadeus.git.~~sourceforge.net/~~git~~/~~gitweb.cgi?p=~~armadeus/~~armadeus;a=blob;f=firmware~~/~~wishbone_example~~/~~Makefile;h=95a5aaf33600e576bb5650ee2115309c847f73d0;hb=HEAD armadeus~~/firmware/wishbone_example/Makefile]. To use it modify the head and write the names of your files :		Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.php Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://sourceforge.net/p/armadeus/code/ci/dcfda086d2b013b82e57f44bca156e5087a66581/tree/firmware/wishbone_example/wishbone_example9328_27/Makefile]. To use it modify the head and write the names of your files :

	*General options		*General options

RobOtter: fixed: link to makefile on Xess website; FabM's MakeFile link

2009-12-03T16:43:45Z

fixed: link to makefile on Xess website; FabM's MakeFile link

← Older revision		Revision as of 18:43, 3 December 2009
Line 138:		Line 138:
	export PATH		export PATH

	Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.~~html~~ Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://armadeus.~~svn~~.sourceforge.net/~~viewvc~~/~~checkout~~/armadeus~~/trunk/~~firmware/~~bus_led~~/Makefile armadeus/firmware/~~bus_led~~/Makefile]. To use it modify the head and write the names of your files :		Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.php Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://armadeus.git.sourceforge.net/git/gitweb.cgi?p=armadeus/armadeus;a=blob;f=firmware/wishbone_example/Makefile;h=95a5aaf33600e576bb5650ee2115309c847f73d0;hb=HEAD armadeus/firmware/wishbone_example/Makefile]. To use it modify the head and write the names of your files :

	*General options		*General options

WikiSysop: installation already has a page

2009-03-03T15:07:02Z

installation already has a page

← Older revision		Revision as of 17:07, 3 March 2009
Line 99:		Line 99:

	=== GUI installation ===		=== GUI installation ===
	To synthesize the design it is mandatory to use Xilinx tools (It's not exactly true, others tools can be used for synthesize like Mentor tools, but at the end to make the bitstream Xilinx tools are ~~necessary~~), fortunately Xilinx provides his webpack for Linux [~~http://www.xilinx.com/support/download/i92linwp.htm~~ here~~] (~~you ~~have to register). You "just" have to download~~ it ~~(1.7Go)~~.		To synthesize the design it is mandatory to use Xilinx tools (It's not exactly true, others tools can be used for synthesize like Mentor tools, but at the end, to make the bitstream, Xilinx tools are mandatory), fortunately Xilinx provides his webpack for Linux. [[ISE_WebPack_installation_on_Linux\| Click here if you didn't install it yet.]]

	~~Before launching the installer, some packages are needed:~~		To launch the floorplanner, DISPLAY has to be change:
	~~sudo apt-get install libmotif3 libxp6 libcurl3 portmap~~		<pre class="host">

	~~Then launch the installer~~
	~~./Webpack_full.sh~~

	To launch the floorplanner, DISPLAY has to be change :
	export DISPLAY=:0		export DISPLAY=:0
			</pre>

	After this installation, ISE can be found in the directory ''$(Xilinx_root_dir)/bin/lin''.		After this installation, ISE can be found in the directory ''$(Xilinx_root_dir)/bin/lin''.
	To avoid retyping export, a little script ''launch_ise.sh'' can be made in ''bin/lin/'' directory:		To avoid retyping export, a little script ''launch_ise.sh'' can be made in ''bin/lin/'' directory:
	#!/bin/bash		<source lang="bash">
	export DISPLAY=:0		#!/bin/bash
	~/Xilinx92i/bin/lin/ise		export DISPLAY=:0
			~/Xilinx92i/bin/lin/ise
			</source>

	Then make launch click :		Then make launch click :

JulienB: previous correction done in the wrong place

2008-10-30T08:11:42Z

previous correction done in the wrong place

← Older revision		Revision as of 10:11, 30 October 2008
Line 72:		Line 72:
	VIEW_CMD = /usr/bin/gtkwave		VIEW_CMD = /usr/bin/gtkwave

	ghdl-~~compil~~ :		ghdl-compile :
	mkdir -p simu		mkdir -p simu
	$(GHDL_CMD) -i $(GHDL_FLAGS) --workdir=simu --work=work $(SIMFILES) $(FILES)		$(GHDL_CMD) -i $(GHDL_FLAGS) --workdir=simu --work=work $(SIMFILES) $(FILES)
Line 89:		Line 89:

	to use it, just write :		to use it, just write :
	$ make ghdl-~~compil~~		$ make ghdl-compile
	to compile, then:		to compile, then:
	$ make ghdl-run		$ make ghdl-run

NicolasL: /* Simulation */

2008-10-29T22:09:15Z

Simulation

← Older revision		Revision as of 00:09, 30 October 2008
Line 89:		Line 89:

	to use it, just write :		to use it, just write :
	$ make ghdl-~~compile~~		$ make ghdl-compil
	to compile, then:		to compile, then:
	$ make ghdl-run		$ make ghdl-run

FabienM at 13:58, 8 April 2008

2008-04-08T13:58:41Z

← Older revision		Revision as of 15:58, 8 April 2008
Line 1:		Line 1:
			[[Category: FPGA]]

	This tutorial describes how to install all the necessary tools to develop simple designs under Ubuntu for the Armadeus Project.<br>		This tutorial describes how to install all the necessary tools to develop simple designs under Ubuntu for the Armadeus Project.<br>
	As Ubuntu is a Debian based distribution, all the informations on this page should work with Debian too.		As Ubuntu is a Debian based distribution, all the informations on this page should work with Debian too.

FabienM: /* Making a simple project */

2008-03-14T21:54:03Z

Making a simple project

← Older revision		Revision as of 23:54, 14 March 2008
Line 10:		Line 10:
	== Making a simple project ==		== Making a simple project ==

	It's a good idea to make a ~~?proper?~~ project tree for your design, because different software are		It's a good idea to make a clean project tree for your design, because different software are
	used and each generates a large amount of files.		used and each generates a large amount of files.

FabienM: /* Using Xilinx command line tools */

2008-03-14T21:41:11Z

Using Xilinx command line tools

← Older revision		Revision as of 23:41, 14 March 2008
Line 119:		Line 119:
	There is a good tutorial on [http://harded.free.fr/site/?p=31 harded.free.fr].		There is a good tutorial on [http://harded.free.fr/site/?p=31 harded.free.fr].

	=== Using Xilinx command line tools===		=== Using Xilinx command line tools for shell syntesis ===

	See [http://panteltje.com/panteltje/fpga/index.html Using Xilinx Webpack-8.1i on grml Linux in scripted mode, without GUI] for an introduction.		See [http://panteltje.com/panteltje/fpga/index.html Using Xilinx Webpack-8.1i on grml Linux in scripted mode, without GUI] for an introduction.

JulienB: /* Using Xilinx tools in command line */

2008-03-05T22:06:03Z

Using Xilinx tools in command line

← Older revision		Revision as of 00:06, 6 March 2008
Line 119:		Line 119:
	There is a good tutorial on [http://harded.free.fr/site/?p=31 harded.free.fr].		There is a good tutorial on [http://harded.free.fr/site/?p=31 harded.free.fr].

	=== Using Xilinx ~~tools in~~ command line ===		=== Using Xilinx command line tools===

	See [http://panteltje.com/panteltje/fpga/index.html Using Xilinx Webpack-8.1i on grml Linux in scripted mode, without GUI] for an introduction.		See [http://panteltje.com/panteltje/fpga/index.html Using Xilinx Webpack-8.1i on grml Linux in scripted mode, without GUI] for an introduction.
Line 130:		Line 130:
	ldconfig		ldconfig

	Then modify your .bashrc ~~adding~~ at the end:		Then modify your .bashrc (add at the end):
	PLATFORM=lin		PLATFORM=lin
	XILINX=Xilinx_directory		XILINX=Xilinx_directory
Line 137:		Line 137:
	export PATH		export PATH

	Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.html Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://armadeus.svn.sourceforge.net/viewvc/checkout/armadeus/trunk/firmware/bus_led/Makefile armadeus/firmware/bus_led/Makefile]. To use it modify the head and write the names of ~~yours~~ files :		Then ISE can be used in command line (xst, ngdbuild, map, bit,...). To avoid typing very long commands it can be a good idea to use a Makefile, xess.com provide a full [http://www.xess.com/appnotes/makefile.html Makefile] to do this and a basic Makefile for simulation and synthesis can be found in the armadeus sourceforge project: [http://armadeus.svn.sourceforge.net/viewvc/checkout/armadeus/trunk/firmware/bus_led/Makefile armadeus/firmware/bus_led/Makefile]. To use it modify the head and write the names of your files :

	*~~Generals~~ options		*General options

	# project name		# project name
Line 159:		Line 159:
	SIMFILES = ../apf_pkg/apf_test_pkg.vhd testbench/led_top_tb.vhd		SIMFILES = ../apf_pkg/apf_test_pkg.vhd testbench/led_top_tb.vhd

	*Simulation can stop after a ~~certain~~ time or after an assert error (end of test for example)		*Simulation can stop after a given time or after an assert error (end of test for example)

	# Simu break condition		# Simu break condition
	GHDL_SIM_OPT = --assert-level=error		GHDL_SIM_OPT = --assert-level=error
	#GHDL_SIM_OPT = --stop-time=500ns		#GHDL_SIM_OPT = --stop-time=500ns