Package Details: quartus-free 23.1.0.991-1

Git Clone URL: https://aur.archlinux.org/quartus-free.git (read-only, click to copy)
Package Base: quartus-free
Description: Meta-package containing all Quartus Prime Lite tools and device libraries
Upstream URL: http://fpgasoftware.intel.com/?edition=lite
Keywords: altera fpga intel quartus
Licenses: custom
Submitter: mabl
Maintainer: gbs
Last Packager: gbs
Votes: 21
Popularity: 0.000000
First Submitted: 2012-12-20 19:49 (UTC)
Last Updated: 2024-02-02 23:17 (UTC)

Required by (0)

Sources (16)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 11 Next › Last »

gwatcha commented on 2020-07-04 19:44 (UTC) (edited on 2020-07-04 19:44 (UTC) by gwatcha)

How can I install it with the HLS compiler? Is there an option to pass to the QuartusLite setup? Altera says HLS comes with Quartus Lite, but I noticed there's no quartus/hls directory.

gbs commented on 2020-06-28 22:18 (UTC)

I have updated to the 20.1 release, and following wall07's request, I've split the package into the existing components. quartus-free is now a meta-package that will pull all components by default.

Please tell if there is any missing functionality due to this change.

<deleted-account> commented on 2020-05-04 09:13 (UTC)

For me default 51-usbblaster.rules didn't work. I had to use

# USB Blaster
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6001", MODE="0666", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", RUN+="/bin/chmod 0666 %c"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6002", MODE="0666", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", RUN+="/bin/chmod 0666 %c"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6003", MODE="0666", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", RUN+="/bin/chmod 0666 %c"
# USB Blaster II
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6010", MODE="0666", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", RUN+="/bin/chmod 0666 %c"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6810", MODE="0666", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", RUN+="/bin/chmod 0666 %c"

pagdot commented on 2020-01-02 20:04 (UTC) (edited on 2020-01-02 20:16 (UTC) by pagdot)

Quartus 19.1 has issues with its perl distribution on Linux. When compiling a QSYS project, I get the following error:

Can't locate Getopt/Long.pm in @INC (you may need to install the Getopt::Long module) (
   @INC contains:
      /opt/altera/19.1/quartus/sopc_builder/bin/europa 
      /opt/altera/19.1/quartus/sopc_builder/bin 
      /opt/altera/19.1/quartus/../ip/altera/sopc_builder_ip/common 
      /opt/altera/19.1/quartus/../ip/altera/sopc_builder_ip/altera_avalon_pio 
      /tools/perl/5.28.1/linux64/lib/site_perl/5.28.1/x86_64-linux 
      /tools/perl/5.28.1/linux64/lib/site_perl/5.28.1 
      /tools/perl/5.28.1/linux64/lib/5.28.1/x86_64-linux 
      /tools/perl/5.28.1/linux64/lib/5.28.1
   ) at /opt/altera/19.1/quartus/../ip/altera/sopc_builder_ip/altera_avalon_pio/generate_rtl.pl line 18.

It seems like the perl distribution points to the wrong directory because the library is located at /opt/altera/19.1/quartus/linux64/perl/lib/5.28.1/Getopt/Long.pm

I've found a bunch references in the perl distribution pointing to the wrong directory ( https://pastebin.com/wfUKcSjq )

A "fix" seems to be to link to the system perl executeable: http://www.armadeus.org/wiki/index.php?title=Quartus_installation_on_Linux#Perl_Getopt::Long

Edit:

I created a post in the Intel forum: https://forums.intel.com/s/question/0D50P00004YMMd4SAH/cant-locate-getoptlongpm-when-generating-a-qsys-project

wall007 commented on 2019-12-20 21:41 (UTC)

I have created a patch that splits the package into several packages using the PACKAGE SPLITTING FUNCTION. https://jlk.fjfi.cvut.cz/arch/manpages/man/PKGBUILD.5#PACKAGE_SPLITTING

Thus it is possible to install only the components that are required for the specific use case to save up some disk space. It should not impact the build time or the space needed for building. The "quartus-free" package is now a meta package, that installs all components. So there should be no difference for the one who are already using this package.

The patch is avaible at: https://pastebin.com/fK2uZ7ix If you wish, you can take it upstream.

pagdot commented on 2019-11-11 23:25 (UTC)

Please add /opt/altera/18.1/quartus/sopc_builder/bin/ to the path in quartus.sh

dsonck92 commented on 2019-10-30 16:23 (UTC)

Would it be appropriate to let this pkgbuild also include the eclipse system that is not present anymore starting from 19.1?

If not, for anyone wondering how to still get it, these are the instructions: https://www.intel.com/content/altera-www/global/en_us/index/support/support-resources/knowledge-base/tools/2019/why-does-the-nios--ii-not-installed-after-full-installation-of-t.html

pagdot commented on 2019-08-06 15:31 (UTC)

I've had problems with "NiosII Software Build Tools for Eclipse" not rendering correctly. I've fixed it by starting it manually with:

SWT_GTK3=0 /opt/altera/18.1/nios2eds/bin/eclipse-nios2

ckoller commented on 2019-07-08 12:29 (UTC) (edited on 2019-07-08 12:36 (UTC) by ckoller)

Warning: quartus-free 18.1.0.625-1 depends on the packaged bzip2 version 1.0.6 and below. Latest working: bzip2-1.0.6-8-x86_64.pkg.tar.xz

Otherwise, you might get errors like this: Warning (12251): FIR.fir_compiler_ii_0: Generation Error: /opt/altera/18.1/quartus/dspba/backend/linux64/fir_ip_api_interface.bin: error while loading shared libraries: libbz2.so.1: cannot open shared object file: No such file or directory

Workaround: Create the missing symbolic link:

cd /usr/lib/lib64

ln -s libbz2.so.1.0.7 libbz2.so.1

ckoller commented on 2019-02-06 00:50 (UTC) (edited on 2019-02-06 00:53 (UTC) by ckoller)

Warning: Building the newer version (currently v18.1.0.625) requires now around 43GBytes of free space during package building!

If you keep the build directory in /tmp (tmpfs), you might need >43GBytes of RAM and/or swapspace. Increasing the size of tmpfs while the system is running can be achieved with:

mount -o remount,size=50G,noatime /tmp

Increasing the amount of swapspace for tmpfs is mandatory, too. You can temporarily add some more or additional swapspace with:

mkswap /dev/sdxX

followed by:

swapon /dev/sdxX