Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
16597 Discussions

Internal Error: Sub-system: QIS File ....

Altera_Forum
Honored Contributor II
1,673 Views

I was attempting to synthesize a mixed VHDL Verilog design. This design compiles in older quartus versions (12 and 15.1), modelsim, and all xilinx tools, but it will not compile in Quartus Prime Pro 17.1. Thank you in advance for any help.  

 

I have attached the tarball with the source code and the QPF. This can be replicated by opening the QPF in Pro 17.1 and attempting to synthesize. 

 

I see no warnings, but synthesis errors with the following report: 

 

Problem Details 

Error: 

Internal Error: Sub-system: QIS, File: /quartus/synth/qis/qis_ip.cpp, Line: 1146 

We auto discovered something not supported, look at debug messages above 

Stack Trace: 

0xb36fa: QIS_IP_PROCESSOR_IMPL::search_and_analyze(std::string const&, std::string const&, bool, bool, HDB_NAMESPACE*) + 0x23e (synth_qis) 

0x6afb8: QIS_RTL_STAGE::IMPL::get_entity(HDB_INSTANCE_NAME*, CDB_SGATE_COMPONENT*) + 0x7ac (synth_qis) 

0x8e86d: QIS_RTL_STAGE::IMPL::elaborate(QHD_PARTITION&) + 0x1a1 (synth_qis) 

0x90734: QIS_RTL_STAGE::elaborate(QHD_PARTITION&) + 0xc (synth_qis) 

0x90833: QIS_RTL_RECURSIVE_ELABORATION::after_elaboration(QHD_PARTITION&) + 0xf9 (synth_qis) 

0x8fcb2: QIS_RTL_STAGE::IMPL::elaborate(QHD_PARTITION&) + 0x15e6 (synth_qis) 

0x90734: QIS_RTL_STAGE::elaborate(QHD_PARTITION&) + 0xc (synth_qis) 

0x90833: QIS_RTL_RECURSIVE_ELABORATION::after_elaboration(QHD_PARTITION&) + 0xf9 (synth_qis) 

0x8fcb2: QIS_RTL_STAGE::IMPL::elaborate(QHD_PARTITION&) + 0x15e6 (synth_qis) 

0x90734: QIS_RTL_STAGE::elaborate(QHD_PARTITION&) + 0xc (synth_qis) 

0x90833: QIS_RTL_RECURSIVE_ELABORATION::after_elaboration(QHD_PARTITION&) + 0xf9 (synth_qis) 

0x8fcb2: QIS_RTL_STAGE::IMPL::elaborate(QHD_PARTITION&) + 0x15e6 (synth_qis) 

0x90734: QIS_RTL_STAGE::elaborate(QHD_PARTITION&) + 0xc (synth_qis) 

0x56fce: qis_elaborate + 0x191 (synth_qis) 

0x4c977: TclNRRunCallbacks + 0x47 (tcl8.6) 

0x4e1ca: TclEvalEx + 0x96a (tcl8.6) 

0xf68c6: Tcl_FSEvalFileEx + 0x266 (tcl8.6) 

0xf69ce: Tcl_EvalFile + 0x2e (tcl8.6) 

0x11d8b: qexe_evaluate_tcl_script(std::string const&) + 0x390 (comp_qexe) 

0x1611d: qexe_do_tcl(QEXE_FRAMEWORK*, std::string const&, std::string const&, std::list<std::string, std::allocator<std::string> > const&, bool, bool) + 0x6c0 (comp_qexe) 

0x1720e: qexe_run_tcl_option(QEXE_FRAMEWORK*, char const*, std::list<std::string, std::allocator<std::string> >*, bool) + 0x5df (comp_qexe) 

0x39069: qcu_run_tcl_option(QCU_FRAMEWORK*, char const*, std::list<std::string, std::allocator<std::string> >*, bool) + 0xf20 (comp_qcu) 

0x40739a: qsyn2_tcl_process_default_flow_option(ACF_VARIABLE_TYPE_ENUM, char const*) + 0xb4 (quartus_syn) 

0x1ab65: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0x486 (comp_qexe) 

0x40608e: qsyn2_main(int, char const**) + 0x141 (quartus_syn) 

0x3f160: msg_main_thread(void*) + 0x10 (ccl_msg) 

0x5b4c: thr_final_wrapper + 0xc (ccl_thr) 

0x3f21f: msg_thread_wrapper(void* (*)(void*), void*) + 0x62 (ccl_msg) 

0xac5c: mem_thread_wrapper(void* (*)(void*), void*) + 0x5c (ccl_mem) 

0x8b49: err_thread_wrapper(void* (*)(void*), void*) + 0x27 (ccl_err) 

0x5b8f: thr_thread_wrapper + 0x15 (ccl_thr) 

0x41b11: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xb2 (ccl_msg) 

0x4062af: main + 0x26 (quartus_syn) 

0x21c05: __libc_start_main + 0xf5 (c) 

 

 

 

 

End-trace 

 

 

Executable: quartus_syn 

Comment: 

None 

 

System Information 

Platform: linux64 

OS name: CentOS Linux 

OS version:  

 

Quartus Prime Information 

Address bits: 64 

Version: 17.1.0 

Build: 240 

Edition: Pro Edition
0 Kudos
2 Replies
Altera_Forum
Honored Contributor II
757 Views

Any luck, I've also encountered the exact same error but on Ubuntu 16.04.

0 Kudos
Altera_Forum
Honored Contributor II
757 Views

I submitted a service request, and they said they are searching their internal database.

0 Kudos
Reply