How to setup the Quartus 13,1 in Ubuntu 12.4.1?

To get any program to execute from the command line, add the directory it is in to your path environment variable. I'm not familiar with Ubuntu, but you'd probably find info by goggling "Ubuntu PATH environment variable"

By the way, Quartus isn't officially supported in Ubuntu. It is only supported in Red Hat Enterprise Linux (RHEL). I've been usiing CentOS which is a free distribution that is very close to RHEL.

If you just want to run quartus and modelsim you can add this to your .bash_profile (or I think that would be .bashrc on Ubuntu since they seem to do everything from the .bashrc file):

qhome=/path/where/you/installed/quartus
PATH=$qhome/quartus/bin:$PATH
PATH=$qhome/modelsim_ase/bin:$PATH
export PATH
QUARTUS_64BIT=1
export QUARTUS_64BIT

Assuming you have installed and want to use the 64-bit version as well. You must source the .bash_profile/.bashrc file or start a new shell for it to take effect.

--- Quote Start ---

If you just want to run quartus and modelsim you can add this to your .bash_profile (or I think that would be .bashrc on Ubuntu since they seem to do everything from the .bashrc file):

qhome=/path/where/you/installed/quartus
PATH=$qhome/quartus/bin:$PATH
PATH=$qhome/modelsim_ase/bin:$PATH
export PATH
QUARTUS_64BIT=1
export QUARTUS_64BIT

Assuming you have installed and want to use the 64-bit version as well. You must source the .bash_profile/.bashrc file or start a new shell for it to take effect.

--- Quote End ---

Thanks very much for reply. It works.

So for:

QUARTUS_64BIT=1

export QUARTUS_64BIT

It sets I want to use 64 bit instead of 32 bit. How do you know this variable (QUARTUS_64BIT) ? Where should I check it?

Thanks in advance.

--- Quote Start ---

Thanks very much for reply. It works.

So for:

QUARTUS_64BIT=1

export QUARTUS_64BIT

It sets I want to use 64 bit instead of 32 bit. How do you know this variable (QUARTUS_64BIT) ? Where should I check it?

Thanks in advance.

--- Quote End ---

I'm not quite sure I understand your question. If you set the QUARTUS_64BIT environment variable as shown above Quartus will start in 64-bit mode. You don't have to check it. If you don't want to run the 64-bit version of Quartus simply don't set it.

--- Quote Start ---

I'm not quite sure I understand your question. If you set the QUARTUS_64BIT environment variable as shown above Quartus will start in 64-bit mode. You don't have to check it. If you don't want to run the 64-bit version of Quartus simply don't set it.

--- Quote End ---

Hi petter,

Sorry that I didn't clarify my question clearly. So as you mentioned QUARTUS_64BIT is an environment variable. But after I installed Quartus, how can I know I should set this environment variable "QUARTUS_64BIT" to configure the Quartus working in 64 bit mode? What document did you check? I think it should be some documents from Altera.

Hope I clarify my question clearly this time. Thanks.

You set it in your environment if you want to run the 64-bit version. By setting it in your .bashrc (or .bash_profile on most other Linux systems) it will be set each time you start a new login shell, e.g. when you log in. You can also set it on the command line by typing "quartus --64bit"

It's documented here (and probably other places as well):

http://quartushelp.altera.com/13.1/mergedprojects/global/install/install_pro_64bit.htm

--- Quote Start ---

You set it in your environment if you want to run the 64-bit version. By setting it in your .bashrc (or .bash_profile on most other Linux systems) it will be set each time you start a new login shell, e.g. when you log in. You can also set it on the command line by typing "quartus --64bit"

It's documented here (and probably other places as well):

http://quartushelp.altera.com/13.1/mergedprojects/global/install/install_pro_64bit.htm

--- Quote End ---

Yes, I already set it up. It works well. Thanks very much pointing me the link!

I've been solving the same problem in the last few days, I'm nearly there.

A few issues that Altera need to solve.

When Altera build all there Linux binaries they should add the following to the 'ld' command line:

-Wl,--enable-new-dtags -Wl,-rpath,'$ORIGIN'

This will add 'RUNPATH' and 'RPATH' entries to the elf headers that contain '$ORIGIN' (run objdump -p to see them).

Then the programs are run the dynamic linker will then look for shared libraries in the directory the program was run from.

Better would be to move all the .so into a separate directory and use (say) '$ORIGIN/../lib' for the path.

Installing the 32bit compatibility libraries in completely non-trivial (try in on Ubuntu 14.1). Since almost all systems that anyone would consider running the Altera software on are very likely to be running on are 63bit this is a complete PITA.

Altera need to release 64bit versions of ALL the toolset.

(Our company has the same problem.)

The qsys window was placed at (0,0), this meant it was almost impossible to move or to select the 'file' buttom (hidden behind parts of the screen the window manager uses).

The USB jtag interface doesn't work by default, and the tools just say 'failed'. It 'fixed' it by making the jtagd binany suid root - not an ideal solution.

All I need to do now is get past the 'download elf failed' error.

Maybe 14.1 is better, but I'm using a cyclone III board which isn't supported by releases after 13.1

Hi all,

I've got 13.1 working great under Windows 10; of course, now I want it to work great under Ubuntu; referring to the Getting Started with SoC Guide, section 4.2 "Installing the USB-Blaster II Driver", I'm a bit lost.

Does anyone have hints either Linux command line or GUI love?

Many thanks!