Installing QuartusII9.1 steps in ubuntu14.04

Home computer installed WIN10, out of enough and installation files small, want to install QuartusII9.1, according to m$ style, drive is definitely not on. It's a dual-system ubuntu14.04 64-bit. The installation process is not going well and is recorded as a backup of the brain that is already out of mind.

According to the normal steps to install, and play a good patch SP1 and SP2, basically smooth, here is to note that some of the installation script is declared in the shell is Cshell, run-time command can not be found, the declaration in the CSH changed to TCSH and then installed.

Next is the persistent JTAG USB blaster that does not recognize the problem. Since Ubuntu is not in an officially supported system (at least Quartus9.1), UBUNTU14 is in its very long version, that is, the kernel of Linux has changed. The following processing is required.

USB Blaster Configuration

settings for USB permissions

(copied from http://blog.csdn.net/xforce_zuoxiang/article/details/18092023 and thanked)

Because the USB default only root access, so as long as the permissions to modify, USB Blaster link on the computer

$ lsusbbus007Device001: ID 1d6b:0001Linux Foundation1.1Root Hubbus002Device001: ID 1d6b:0002Linux Foundation2.0Root Hubbus006Device001: ID 1d6b:0001Linux Foundation1.1Root Hubbus005Device001: ID 1d6b:0001Linux Foundation1.1Root Hubbus001Device003: ID 09FB:6001Altera Blasterbus001Device001: ID 1d6b:0002Linux Foundation2.0Root Hubbus004Device001: ID 1d6b:0001Linux Foundation1.1Root Hubbus003Device002: ID 093a:2510Pixart Imaging, Inc. Optical Mousebus003Device001: ID 1d6b:0001Linux Foundation1.1Root Hub

Description/dev/bus/usb/001/003 This file is now our Altera Blaster device.

 $ cd/dev/bus/usb/001  $  ls -0  CRW -rw-r--1  root root 189 , 0  May 30  20 : 55  001  CRW -rw-rw-"1  root root 189 , 30  21 : 14  003  

It is clear that only users of the root group have permission to use USB

sudo chmod 666 ./003

Add write permissions to users outside of the user group

However, because the 003 path this is the system allocation, and sometimes it is not the path, so if you do not go in, lsusb to see if there is no change to another path, and then re-chmod a bit on it.
However, each time it is necessary to change or trouble, the PC should be human services rather than artificial PC services, so we use udev set rules so that every time a USB Blaster device mode changed to 666 (rw-rw-rw-) on the line
It's very simple to write our files by creating a new file with the rule suffix in the default/ETC/UDEV/RULES.D directory.
And the name can be arbitrary but the first two numbers are better to ensure than the previous existence of the larger, this is the decision to prioritize the order,
I have built a name for 80-usbblaster.rules here:
sudo nano/etc/udev/rules.d/80-usbblaster.rules
Then add this sentence inside:
attrs{idvendor}== "09FB", attrs{idproduct}== "6001", mode= "666"
Save on OK, this means that Idendor is 09FB and idproduct is 6001, mode to set to 666, then this usbblaster used up is quite convenient.

at this point, the USB permissions problem is set to complete, because the original author uses ubuntu14+quartus12, it seems to be able to use directly, but for us, the problem is far from over

Changes to kernel changes

ubuntu9.1 and later versions of the kernel, USB FS is not in use, so there is no longer /proc/bus/usb this directory, and unfortunately, QuartusII9.1 is using this directory to drive the USB Blaster.

Use the following two to fix these changes:

Mount --bind/dev/bus/proc/busLn -s/sys/kernel/debug/usb/devices/proc/bus/usb/devices

The complete steps are as follows:

$sudo Killalljtagd$sudo chmod 755/sys/kernel/debug/usb/devices$sudo chmod 755/sys/kernel/debug/usb$sudo chmod 755/sys/kernel/debug$sudo Mount--bind/dev/bus/proc/bus$sudo LN-s/sys/kernel/debug/usb/devices/proc/bus/usb/devices$sudo<quartus_directory>/bin/jtagd$sudo<quartus_directory>/bin/jtagconfig

You can see that before the fix, modify the permissions, or JTAGD still have no way to use ordinary user rights to access devices

When you can start JTAGD by using debug mode

$./jtagd--foreground--debug--user-start--config/etc/jtagd/file /etc/jtagd/jtagd.pgm_ Partsno remote JTAG because stops when idle

Then check if the Jtagconfig can detect the USB BLASTER

$./jtagconfig11-1.4]  020b20dd   ep2c8

At this point, the Development Board has been inserted, if the board is not connected to the display

1) usb-blaster [USB 1-1.4]
Unable to read device chain (JTAG chain broken)

OK, as long as you can find Usb-blaster.

Some put JTAGD as a system service, look at personal needs, in Quartus burning, will automatically start it, time-out does not use, will automatically quit, there seems to be no great need.

Reference:

http://ubuntuforums.org/showthread.php?t=1441742

http://www.fpga-dev.com/altera-usb-blaster-with-ubuntu/

http://www.fpga-dev.com/altera-usb-blaster-with-ubuntu/

Settings for Environment variables
In a 64-bit environment, if you do not set an environment variable, you should add the--64bit parameter when you start Quartus, otherwise you will be prompted not to find the shared library, although the shared library already exists, but it is actually caused by a 32-bit initiated program.

Someone set up their own environment variable to solve this problem, and now they are directly in the boot add parameter.

Other questions

It seems that some people in the installation of Modsim and DSP Builder is also a bit of trouble, there is no installation, then if there is a problem to record the supplement.

Installing QuartusII9.1 steps in ubuntu14.04