quartus_eda crashes (core dump) very often. I have to clean my project before compile to prevent crash

BLee15 · ‎09-21-2019

Core dump:

Problem Details
Error:
Internal Error: Sub-system: WSC, File: /quartus/neto/wsc/wsc_port.cpp, Line: 409
m_port_info.num_of_dimensions() == 1
Stack Trace:
     0x54a7: WSC_PORT::left_bit + 0x37 (NETO_WSC)
    0x2488f: VLGO_SV_WRITER::write_port_declare + 0x14f (NETO_VLGO)
    0x171db: VLGO_WRITER::write_port_declarations + 0xbb (NETO_VLGO)
    0x15983: VLGO_WRITER::write_module_declare + 0x133 (NETO_VLGO)
    0x1536e: VLGO_WRITER::write_module + 0xde (NETO_VLGO)
    0x1241d: VLGO_WRITER::write_file + 0x7ed (NETO_VLGO)
    0x1e386: QNETO_START::generate_simulation_files + 0xf86 (quartus_eda)
    0x1f61e: QNETO_START::generate_simulation_files + 0x57e (quartus_eda)
    0x1726f: QNETO_START::generate_eda_files + 0x2f (quartus_eda)
    0x2762c: generate_all_eda_files + 0x4c (quartus_eda)
    0x28240: qneto_execute + 0x1a0 (quartus_eda)
     0x9b98: QNETO_FRAMEWORK::execute + 0x288 (quartus_eda)
    0x112bc: qexe_do_normal + 0x1ec (comp_qexe)
    0x16142: qexe_run + 0x432 (comp_qexe)
    0x16e51: qexe_standard_main + 0xc1 (comp_qexe)
     0xfabd: qneto_main + 0x9d (quartus_eda)
    0x12f28: msg_main_thread + 0x18 (CCL_MSG)
    0x1470e: msg_thread_wrapper + 0x6e (CCL_MSG)
    0x16660: mem_thread_wrapper + 0x70 (ccl_mem)
    0x127f1: msg_exe_main + 0xa1 (CCL_MSG)
    0x29be2: __tmainCRTStartup + 0x10e (quartus_eda)
    0x17bd3: BaseThreadInitThunk + 0x13 (KERNEL32)
    0x6cee0: RtlUserThreadStart + 0x20 (ntdll)
 
End-trace
 
 
Executable: quartus_eda
Comment:
None
 
System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0
 
Quartus Prime Information
Address bits: 64
Version: 18.1.1
Build: 646
Edition: Lite Edition

I attached my project as archive file

Kenny_Tan · ‎09-23-2019

Can you provide the exact steps that you have used? I try duplicate it on my side but failed.

BLee15 · ‎09-24-2019

Restore archived project
Start compilation. This usually success.
Modify top.sv; adding some whitespace would be enough
Start compilation. quartus_eda crashes about 2 out of 3 times.

Kenny_Tan · ‎09-23-2019

Seems like this is known issue. you can refer to https://www.intel.com/content/www/us/en/programmable/support/support-resources/knowledge-base/solutions/rd09302013_869.html

BLee15 · ‎09-24-2019

Changing output format to other languages significantly modifies top module interface.

It is hard to accept this workaround, as it brings heavy testbench rework.

Verilog HDL: 2D array is unrolled to individual single-wire ports

module top (
	raw_clock,
	raw_reset,
	number,
	instruction,
	in_5_1,
	in_6_1,
	in_4_1,
	in_7_1,
	in_2_1,
	in_1_1,
	in_0_1,
	in_3_1,
	in_5_0,
	in_6_0,
	in_4_0,
	in_7_0,
	in_2_0,
	in_1_0,
	in_0_0,
	in_3_0,
	in_5_2,
	in_6_2,
	in_4_2,
	in_7_2,
	in_2_2,
	in_1_2,
	in_0_2,
	in_3_2,
	in_5_3,
	in_6_3,
	in_4_3,
	in_7_3,
	in_2_3,
	in_1_3,
	in_0_3,
	in_3_3,
	in_5_4,
	in_6_4,
	in_4_4,
	in_7_4,
	in_2_4,
	in_1_4,
	in_0_4,
	in_3_4,
	in_5_5,
	in_6_5,
	in_4_5,
	in_7_5,
	in_2_5,
	in_1_5,
	in_0_5,
	in_3_5,
	in_5_6,
	in_6_6,
	in_4_6,
	in_7_6,
	in_2_6,
	in_1_6,
	in_0_6,
	in_3_6,
	in_5_7,
	in_6_7,
	in_4_7,
	in_7_7,
	in_2_7,
	in_1_7,
	in_0_7,
	in_3_7,
	out_7_0,
	out_7_1,
	out_7_2,
	out_7_3,
	out_7_4,
	out_7_5,
	out_7_6,
	out_7_7,
	out_6_0,
	out_6_1,
	out_6_2,
	out_6_3,
	out_6_4,
	out_6_5,
	out_6_6,
	out_6_7,
	out_5_0,
	out_5_1,
	out_5_2,
	out_5_3,
	out_5_4,
	out_5_5,
	out_5_6,
	out_5_7,
	out_4_0,
	out_4_1,
	out_4_2,
	out_4_3,
	out_4_4,
	out_4_5,
	out_4_6,
	out_4_7,
	out_3_0,
	out_3_1,
	out_3_2,
	out_3_3,
	out_3_4,
	out_3_5,
	out_3_6,
	out_3_7,
	out_2_0,
	out_2_1,
	out_2_2,
	out_2_3,
	out_2_4,
	out_2_5,
	out_2_6,
	out_2_7,
	out_1_0,
	out_1_1,
	out_1_2,
	out_1_3,
	out_1_4,
	out_1_5,
	out_1_6,
	out_1_7,
	out_0_0,
	out_0_1,
	out_0_2,
	out_0_3,
	out_0_4,
	out_0_5,
	out_0_6,
	out_0_7);

VHDL: Introduces user-defined type, and kind of output port is changed to BUFFER.

PACKAGE top_data_type IS
 
TYPE \in\_7_0_type IS ARRAY (7 DOWNTO 0) OF std_logic;
TYPE \in\_7_0_0_7_type IS ARRAY (0 TO 7) OF \in\_7_0_type;
SUBTYPE \in\_type IS \in\_7_0_0_7_type;
 
TYPE \out\_7_0_type IS ARRAY (7 DOWNTO 0) OF std_logic;
TYPE \out\_7_0_0_7_type IS ARRAY (0 TO 7) OF \out\_7_0_type;
SUBTYPE \out\_type IS \out\_7_0_0_7_type;
 
END top_data_type;
 
ENTITY 	top IS
    PORT (
	raw_clock : IN std_logic;
	raw_reset : IN std_logic;
	number : BUFFER std_logic_vector(7 DOWNTO 0);
	instruction : IN std_logic_vector(15 DOWNTO 0);
	\in\ : IN \in\_type;
	\out\ : BUFFER \out\_type
	);
END top;

Kenny_Tan · ‎09-25-2019

Any concern if you use the clean project? Currently, Quartus std are in the lower priority on the fixes.

BLee15 · ‎09-25-2019

I have to do "modify - compile - core dump - clean project - compile - simulation" cycle instead of "modify - compile - simulation".

Is there any option to clean project automatically before compile?

Kenny_Tan · ‎09-25-2019

You can write a tcl scripts for it if you want to have the compiles goes with clean project.

Kenny_Tan · ‎09-30-2019

let me know if you have trouble to write the tcl scripts?

Kenny_Tan · ‎10-07-2019

any update?

BLee15 · ‎10-07-2019

I'm learning TCL scripts / commands.

One question: can I add my custom TCL scripts to menu bar and/or toolbar, so that I can click the menu/icon to execute my script?

Kenny_Tan · ‎10-08-2019

One question: can I add my custom TCL scripts to menu bar and/or toolbar, so that I can click the menu/icon to execute my script?

usually, for this type of script is no. But you can run it in the command prompt and it only take one click.

However, you can always explore yourself. If you successfully created this scripts, all you need to do is goto tools -> tcl script

we created a scripts for you, please note that you may have to create it next time. You can run it with:

cd to quartus install directory where the quartus_sh exist:

quartus_sh -t compile.tcl