Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
120 Views

Quartus II 13.0 SP1 fails installing

Jump to solution

System: Linux 5.5.13-1-MANJARO x86_64

installer version: 8.5.2

 

I have attempted to install Quartus II 13.0 SP1 multiple times using intel's software download site and several different AUR packages (web and subscription edition).

If the method manages to download the actual installers, they all fail and dump an XML file with some kind of dump and the linux distro info at the bottom.

 

To add insult to injury, all that the install script says is that an error occurred, no specifics.

0 Kudos

Accepted Solutions
Highlighted
Moderator
33 Views

Hi Mikhail,

 

Seem there could be two reasons:

 

  1. Your OS desktop if Manjaro is using Xfce or Openbox. Change to KDE or GNOME as they are the prerequisite to installl Quartus. Refer to link for more details.[1]

 

Assuming you are using KDE or GNOME, there could be a firewall, or window defender that blocked certain packages to be download result in fail installing. Try to disable it for a moment.

 

https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/manual/quartus_install.pdf (p6)

 

Thanks,

Regards

View solution in original post

3 Replies
Highlighted
Moderator
34 Views

Hi Mikhail,

 

Seem there could be two reasons:

 

  1. Your OS desktop if Manjaro is using Xfce or Openbox. Change to KDE or GNOME as they are the prerequisite to installl Quartus. Refer to link for more details.[1]

 

Assuming you are using KDE or GNOME, there could be a firewall, or window defender that blocked certain packages to be download result in fail installing. Try to disable it for a moment.

 

https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/manual/quartus_install.pdf (p6)

 

Thanks,

Regards

View solution in original post

Highlighted
Beginner
33 Views

Installed plasma DE and the installer worked. Rather interesting failure mode, erroring out due to window managers.

 

Thank you!

0 Kudos
Highlighted
Beginner
33 Views

Quartus II 13.1 fails terribly where Xilinx produces perfect RTL schematics from the same VHDL code! And I already upgraded Quartus to get rid of the wrong terrible bugs that showed in its RTL results. And the Intel site gives none help, no support to ask a question by sending a simple email nothing!

 

See next code that after days of wasted checking keeps failing in Quartus but works great as it is in Xilinx ISE 14.6!

 

HELP !!! QUARTUS II Web free version 13.1 (32-bit) for Windows 7 fails many times to compile a perfectly good VHDL example code!

 

Those examples tried never work in Quartus but the same files 

WORK PERFECTLY in Xilinx ISE version 14.6 !!! (on a Windows XP laptop).

 

See following VHDL code below of an UpCounter that never works in Quartus II for some reason but works great in Xilinx ISE producing a decent and correct RTL schematic!

 

----------------

 

-- Engineer: Albert van Bemmelen

-- Create Date:  15:46:31 05/09/2020 

-- Module Name:  UpCounter - Behavioral 

-- Upcounter Vahid book

library ieee;

use ieee.std_logic_1164.all;

entity UpCounter is

port ( clk: in std_logic;

cnt: in std_logic;

C: out std_logic_vector(3 downto 0);

tc: out std_logic);

end UpCounter;

 

architecture structure of UpCounter is

component Reg4

port ( I: in std_logic_vector(3 downto 0);

Q: out std_logic_vector(3 downto 0);

clk, ld: in std_logic);

end component;

 

component Inc4

port ( a: in std_logic_vector(3 downto 0);

s: out std_logic_vector(3 downto 0));

end component;

 

component And_4

port ( w,x,y,z: in std_logic;

F: out std_logic);

end component;

 

signal tempC: std_logic_vector (3 downto 0);

signal incC: std_logic_vector(3 downto 0);

begin

Reg4_1: Reg4 port map(incC, tempC, clk, cnt);

Inc4_1: Inc4 port map(tempC, incC);

And_4_1: And_4 port map(tempC(3),tempC(2),tempC(1),tempC(0), tc);

outputC: process(tempC)

begin

C <= tempC;

end process;

end structure;

 

 

I am trying to understand why Quartus makes a problem of good VHDL code where it shouldn't be!!

Any help is greatly appreciated!

 

Albert van Bemmelen

Weert The Netherlands.

0 Kudos