Xilinx ISE Installation Instructions - Revision history

ITechGeek: Undo revision 3976 by Yrewevaca (talk)

2010-11-24T06:22:36Z

Undo revision 3976 by Yrewevaca (talk)

← Older revision		Revision as of 06:22, 24 November 2010
Line 1:		Line 1:
	~~----~~
	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
	~~----~~
	~~=[http://edojalys.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=~~
	~~----~~
	~~=[http://edojalys.co.cc CLICK HERE]=~~
	~~----~~
	~~</div>~~
	== ISE Installation Instructions ==		== ISE Installation Instructions ==
	# Make sure you have a xilinx.com account		# Make sure you have a xilinx.com account
Line 14:		Line 6:
	# Follow the screens to download the ISE Webpack. You'll be presented with either downloading the 2.5Gb image or the Webinstall client, which will download the files you'll need as it installs. You can choose either, I would recommend grabbing the 2.25Gb tarball. Instructions will be based on installing from the full tarball. Expect your vm drive to start growing.		# Follow the screens to download the ISE Webpack. You'll be presented with either downloading the 2.5Gb image or the Webinstall client, which will download the files you'll need as it installs. You can choose either, I would recommend grabbing the 2.25Gb tarball. Instructions will be based on installing from the full tarball. Expect your vm drive to start growing.
	# By default, your download (webpack_SFD.tar for the full file) will go to your ~/Desktop folder. Open up a terminal and unpack the tarball.		# By default, your download (webpack_SFD.tar for the full file) will go to your ~/Desktop folder. Open up a terminal and unpack the tarball.
	##~~<~~pre> cd ~/Desktop ~~<~~/pre>		##<pre> cd ~/Desktop </pre>
	## ~~<~~pre>tar -xvf webpack_SFD.tar ~~<~~/pre>		## <pre>tar -xvf webpack_SFD.tar </pre>
	##This creates the directory ~/Desktop/webpack containing the installation files for the webpack. These installation files will work for '''Linux''' and '''Windows'''.		##This creates the directory ~/Desktop/webpack containing the installation files for the webpack. These installation files will work for '''Linux''' and '''Windows'''.
	## ~~<~~pre> UESC-Boomer:Public wgibb$ md5 webpack_SFD.tar ...results(webpack_SFD.tar) = 87c3452d36ef990930a8596acd6a4899 ~~<~~/pre>		## <pre> UESC-Boomer:Public wgibb$ md5 webpack_SFD.tar ...results(webpack_SFD.tar) = 87c3452d36ef990930a8596acd6a4899 </pre>
	# Now we're going to run the installer as root		# Now we're going to run the installer as root
	##~~<~~pre> cd webpack ~~<~~/pre>		##<pre> cd webpack </pre>
	##~~<~~pre> su (password is linux on the vm) ~~<~~/pre>		##<pre> su (password is linux on the vm) </pre>
	##~~<~~pre> ./setup ~~<~~/pre>		##<pre> ./setup </pre>
	# During the setup you'll be prompted for a registrationID. This is the registrationID in the email you got back in step 3. Enter it here.		# During the setup you'll be prompted for a registrationID. This is the registrationID in the email you got back in step 3. Enter it here.
	# You'll then be presented with terms of service screens. Agree through them to proceed.		# You'll then be presented with terms of service screens. Agree through them to proceed.
Line 34:		Line 26:
	# The cable drivers will fail to build. A solution for this is forthcoming (just need to test it).		# The cable drivers will fail to build. A solution for this is forthcoming (just need to test it).
	# You can remove the folder from your desktop. You may want to keep the tarball around if you need to reinstall.		# You can remove the folder from your desktop. You may want to keep the tarball around if you need to reinstall.
	## ~~<~~pre> exit ~~<~~/pre> To get out of su		## <pre> exit </pre> To get out of su
	## ~~<~~pre> rm -rf ./webpack ~~<~~/pre>		## <pre> rm -rf ./webpack </pre>

	~~<~~br>		<br>

	==Running the tools==		==Running the tools==
	# Open up a terminal and type the following commands		# Open up a terminal and type the following commands
	## ~~<~~pre> cd /opt/Xilinx/10.1/ISE ~~<~~/pre>		## <pre> cd /opt/Xilinx/10.1/ISE </pre>
	## ~~<~~pre> source settings32.sh ~~<~~/pre>		## <pre> source settings32.sh </pre>
	## ~~<~~pre> ise ~~<~~/pre>		## <pre> ise </pre>
	# You will now have launched Xilinx ISE.		# You will now have launched Xilinx ISE.
	## If this is your first time using Xilinx ISE, you should go through the in-depth tutorial linked to on the [[FPGA_Workshop#Xilinx_Links\|mainpage]].		## If this is your first time using Xilinx ISE, you should go through the in-depth tutorial linked to on the [[FPGA_Workshop#Xilinx_Links\|mainpage]].
Line 81:		Line 73:
	but this setting also works for the USB JTAG interface.		but this setting also works for the USB JTAG interface.

	A fine bit of clue: [http://www.edaboard.com/ftopic345414.html '''Programming Digilent Nexys 2 from Linux'''] ~~<~~br>		A fine bit of clue: [http://www.edaboard.com/ftopic345414.html '''Programming Digilent Nexys 2 from Linux'''] <br>

	That leads to the good stuff in		That leads to the good stuff in

Yrewevaca at 02:39, 24 November 2010

2010-11-24T02:39:09Z

74.52.156.98: /* 64 bit install */

2010-01-06T22:51:54Z

64 bit install

← Older revision		Revision as of 22:51, 6 January 2010
Line 41:		Line 41:
	==64 bit install==		==64 bit install==

	~~If the~~ Xilinx ISE Webpack install file complains about not supporting your 64-bit computer:		The Xilinx ISE Webpack install file complains about not supporting your 64-bit computer when you run the toplevel "setup" script, so run the alternate installer found at webpack/bin/lin/setup. (Clean install tested on Ubuntu Karmic AMD64 by Elliot.)

	~~The installer is just a shell~~ script, ~~edit out~~ the ~~test~~.

	Since ISE is a 32-bit application, you'll need 32-bit libraries on your 64-bit system.		Since ISE is a 32-bit application, you'll need 32-bit libraries on your 64-bit system.
Line 52:		Line 50:
	32-bit i386 binaries just fine.		32-bit i386 binaries just fine.

	~~Run the installer script. Things will work just fine.~~		But note that when it comes time to flash things over the USB cable, you'll need to run the USB loader within a 32-bit shell, and tell it to use the 32-bit USB library:

	But note that when it comes time to flash things over the USB cable~~, you'll need to add a little extra elbow grease. Specifically~~, you'll need to run the USB loader within a 32-bit shell:
	cd /opt/Xilinx/10.1/ISE		cd /opt/Xilinx/10.1/ISE
	linux32 bash		linux32 bash

74.52.156.98: /* 64 bit install */

2010-01-06T22:48:07Z

64 bit install

← Older revision		Revision as of 22:48, 6 January 2010
Line 53:		Line 53:

	Run the installer script. Things will work just fine.		Run the installer script. Things will work just fine.

			But note that when it comes time to flash things over the USB cable, you'll need to add a little extra elbow grease. Specifically, you'll need to run the USB loader within a 32-bit shell:
			cd /opt/Xilinx/10.1/ISE
			linux32 bash
			./settings32.sh
			export LD_PRELOAD=/lib32/libusb-0.1.so
			impact
			(And don't forget to "exit" when you're done to prevent infinitely-deeply nested linux32 bash shells.)

	==Alternative to Digilent Adept Suite==		==Alternative to Digilent Adept Suite==

74.52.156.98: /* Programming the board with the USB cable in Linux */

2010-01-06T22:41:52Z

Programming the board with the USB cable in Linux

← Older revision		Revision as of 22:41, 6 January 2010
Line 100:		Line 100:

	SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0008", MODE="666"		SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0008", MODE="666"
	SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I /opt/Xilinx/10.1/ISE/bin/lin/xusbdfwu.hex -D %N		SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I /opt/Xilinx/10.1/ISE/bin/lin/xusbdfwu.hex -D %N"

	(You may need to restart the udev subsystem: "sudo restart udev")		(You may need to restart the udev subsystem: "sudo restart udev")

Williamgibb at 14:35, 6 January 2010

2010-01-06T14:35:21Z

← Older revision		Revision as of 14:35, 6 January 2010
Line 19:		Line 19:
	# Next is installation options You may as well choose all of them, but you must choose "All FPGA devices except Virtex 4 and Virtex 5" in order to design towards the Spartan 3E boards. You should be ready for your VM's disk to grow by 4 more gigs.		# Next is installation options You may as well choose all of them, but you must choose "All FPGA devices except Virtex 4 and Virtex 5" in order to design towards the Spartan 3E boards. You should be ready for your VM's disk to grow by 4 more gigs.
	# You'll then be presented with a set of environmental variables which are set in a settings file for ise. They can be left at defaults.		# You'll then be presented with a set of environmental variables which are set in a settings file for ise. They can be left at defaults.
	# ~~Select~~ the cable drivers. Click through to confirm the settings and install the tools.		# On '''windows''', select the cable drivers. On '''linux''', unselect the cable drivers and be sure to follow the directions further down this page for information on setting up the cable drivers.
			#Click through to confirm the settings and install the tools.
	## You may uncheck the update feature, if you do not wish to immeadiately update the tools after installation. This will cause a large download to occur after installation, if it is checked.		## You may uncheck the update feature, if you do not wish to immeadiately update the tools after installation. This will cause a large download to occur after installation, if it is checked.
	# Wait for the tools to install. Play cards with a buddy.		# Wait for the tools to install. Play cards with a buddy.

Hexagon5un: /* Programming the board with the USB cable in Linux */

2010-01-06T04:50:02Z

Programming the board with the USB cable in Linux

← Older revision		Revision as of 04:50, 6 January 2010
Line 99:		Line 99:

	SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0008", MODE="666"		SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0008", MODE="666"
			SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I /opt/Xilinx/10.1/ISE/bin/lin/xusbdfwu.hex -D %N
	SUBSYSTEM=="usb", ACTION=="add", \
	ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d", \
	RUN+="/sbin/fxload -v -t fx2 -I /opt/Xilinx/10.1/ISE/bin/lin/xusbdfwu.hex -D %N

	(You may need to restart the udev subsystem: "sudo restart udev")		(You may need to restart the udev subsystem: "sudo restart udev")

Hexagon5un: /* Programming the board with the USB cable in Linux */

2010-01-06T04:38:03Z

Programming the board with the USB cable in Linux

← Older revision		Revision as of 04:38, 6 January 2010
Line 117:		Line 117:

	You should now be able to run ISE (or iMPACT directly) and it'll detect the cable and the board.		You should now be able to run ISE (or iMPACT directly) and it'll detect the cable and the board.

			[[http://www.george-smart.co.uk/wiki/Xilinx_JTAG_Linux This site]] has good information about the USB JTAG programming interface and configuration for the Spartan3E. (Found the page after I wrote this guide. Would have saved us hours.)

	[[Category:FPGAWorkshop]]		[[Category:FPGAWorkshop]]

Hexagon5un: /* Programming the board with the USB cable in Linux */

2010-01-06T03:27:15Z

Programming the board with the USB cable in Linux

← Older revision		Revision as of 03:27, 6 January 2010
Line 109:		Line 109:

	If you can't get the whole udev thing working, you can type by hand:		If you can't get the whole udev thing working, you can type by hand:

	/sbin/fxload -v -t fx2 -I /opt/Xilinx/10.1/ISE/bin/lin/xusbdfwu.hex -D /proc/bus/usb/001/007		/sbin/fxload -v -t fx2 -I /opt/Xilinx/10.1/ISE/bin/lin/xusbdfwu.hex -D /proc/bus/usb/001/007

	where the 001/007 is the bus and id that you'll find from lsusb.		where the 001/007 is the bus and id that you'll find from lsusb.

Hexagon5un: /* Programming the board with the USB cable in Linux */

2010-01-06T03:22:23Z

Programming the board with the USB cable in Linux

← Older revision		Revision as of 03:22, 6 January 2010
Line 116:		Line 116:
	Then to run iMPACT (the program that flashes in your .bit file) with or without ISE, you'll need to tell it to use USB:		Then to run iMPACT (the program that flashes in your .bit file) with or without ISE, you'll need to tell it to use USB:

	export XIL_IMPACT_USE_LIBUSB=0		export XIL_IMPACT_USE_LIBUSB=1

	You should now be able to run ISE (or iMPACT directly) and it'll detect the cable and the board.		You should now be able to run ISE (or iMPACT directly) and it'll detect the cable and the board.

	[[Category:FPGAWorkshop]]		[[Category:FPGAWorkshop]]

← Older revision		Revision as of 02:39, 24 November 2010
Line 1:		Line 1:
			----
			<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
			----
			=[http://edojalys.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
			----
			=[http://edojalys.co.cc CLICK HERE]=
			----
			</div>
	== ISE Installation Instructions ==		== ISE Installation Instructions ==
	# Make sure you have a xilinx.com account		# Make sure you have a xilinx.com account
Line 6:		Line 14:
	# Follow the screens to download the ISE Webpack. You'll be presented with either downloading the 2.5Gb image or the Webinstall client, which will download the files you'll need as it installs. You can choose either, I would recommend grabbing the 2.25Gb tarball. Instructions will be based on installing from the full tarball. Expect your vm drive to start growing.		# Follow the screens to download the ISE Webpack. You'll be presented with either downloading the 2.5Gb image or the Webinstall client, which will download the files you'll need as it installs. You can choose either, I would recommend grabbing the 2.25Gb tarball. Instructions will be based on installing from the full tarball. Expect your vm drive to start growing.
	# By default, your download (webpack_SFD.tar for the full file) will go to your ~/Desktop folder. Open up a terminal and unpack the tarball.		# By default, your download (webpack_SFD.tar for the full file) will go to your ~/Desktop folder. Open up a terminal and unpack the tarball.
	##<pre> cd ~/Desktop </pre>		##<pre> cd ~/Desktop </pre>
	## <pre>tar -xvf webpack_SFD.tar </pre>		## <pre>tar -xvf webpack_SFD.tar </pre>
	##This creates the directory ~/Desktop/webpack containing the installation files for the webpack. These installation files will work for '''Linux''' and '''Windows'''.		##This creates the directory ~/Desktop/webpack containing the installation files for the webpack. These installation files will work for '''Linux''' and '''Windows'''.
	## <pre> UESC-Boomer:Public wgibb$ md5 webpack_SFD.tar ...results(webpack_SFD.tar) = 87c3452d36ef990930a8596acd6a4899 </pre>		## <pre> UESC-Boomer:Public wgibb$ md5 webpack_SFD.tar ...results(webpack_SFD.tar) = 87c3452d36ef990930a8596acd6a4899 </pre>
	# Now we're going to run the installer as root		# Now we're going to run the installer as root
	##<pre> cd webpack </pre>		##<pre> cd webpack </pre>
	##<pre> su (password is linux on the vm) </pre>		##<pre> su (password is linux on the vm) </pre>
	##<pre> ./setup </pre>		##<pre> ./setup </pre>
	# During the setup you'll be prompted for a registrationID. This is the registrationID in the email you got back in step 3. Enter it here.		# During the setup you'll be prompted for a registrationID. This is the registrationID in the email you got back in step 3. Enter it here.
	# You'll then be presented with terms of service screens. Agree through them to proceed.		# You'll then be presented with terms of service screens. Agree through them to proceed.
Line 26:		Line 34:
	# The cable drivers will fail to build. A solution for this is forthcoming (just need to test it).		# The cable drivers will fail to build. A solution for this is forthcoming (just need to test it).
	# You can remove the folder from your desktop. You may want to keep the tarball around if you need to reinstall.		# You can remove the folder from your desktop. You may want to keep the tarball around if you need to reinstall.
	## <pre> exit </pre> To get out of su		## <pre> exit </pre> To get out of su
	## <pre> rm -rf ./webpack </pre>		## <pre> rm -rf ./webpack </pre>

	<br>		<br>

	==Running the tools==		==Running the tools==
	# Open up a terminal and type the following commands		# Open up a terminal and type the following commands
	## <pre> cd /opt/Xilinx/10.1/ISE </pre>		## <pre> cd /opt/Xilinx/10.1/ISE </pre>
	## <pre> source settings32.sh </pre>		## <pre> source settings32.sh </pre>
	## <pre> ise </pre>		## <pre> ise </pre>
	# You will now have launched Xilinx ISE.		# You will now have launched Xilinx ISE.
	## If this is your first time using Xilinx ISE, you should go through the in-depth tutorial linked to on the [[FPGA_Workshop#Xilinx_Links\|mainpage]].		## If this is your first time using Xilinx ISE, you should go through the in-depth tutorial linked to on the [[FPGA_Workshop#Xilinx_Links\|mainpage]].
Line 73:		Line 81:
	but this setting also works for the USB JTAG interface.		but this setting also works for the USB JTAG interface.

	A fine bit of clue: [http://www.edaboard.com/ftopic345414.html '''Programming Digilent Nexys 2 from Linux'''] <br>		A fine bit of clue: [http://www.edaboard.com/ftopic345414.html '''Programming Digilent Nexys 2 from Linux'''] <br>

	That leads to the good stuff in		That leads to the good stuff in