Forum Discussion
Linux Quartus Pro Edition quits unexpectecly because of jspice model library
Hello, I am getting an error when compiling a design for Intel Cyclone 10 GX using Quartus Pro Edition on Linux. It crashes on Fitter > Place stage at 99 %.
I tried looking for a jspice model library, but found nothing that looked useful. Any idea what the problem could be?
I've installed the software using individual files, I have the base Quartus installed + Intel Cyclone GX and Intel Arria 10 device support. I've also installed questa, high level synthesis and Intel FPGA SDK for OpenCL in the hopes of resolving the error. I was thinking that there may be a jspice library in one of these.
Problem Details Error: Internal Error: Sub-system: SIN, File: /quartus/tsm/sin/sin_nightfury_buffer_netlist_builder.cpp, Line: 212 Could not load jspice model library Stack Trace: Quartus 0x10959b: SIN_NIGHTFURY_BUFFER_NETLIST_BUILDER::load_simulation_models() + 0x81b (tsm_sin) Quartus 0x13398b: SIN_NIGHTFURY_SIMULATION_INTERFACE::allocate_buffer_builder() + 0x1b (tsm_sin) Quartus 0x935a7: SIN_DB_MANAGER_BODY::initialize_managers(SIN_PROCESS_MODEL*) + 0x57 (tsm_sin) Quartus 0x94bc9: SIN_DB_MANAGER_BODY::run_simulations(CDB_ATOM_NETLIST const*, SIN_PROCESS_MODEL*) + 0x69 (tsm_sin) Quartus 0x1ccdea: PTI_AIOT_CALCULATOR::run_aiot_simulations() + 0xca (tsm_pti) Quartus 0x1b969d: PTI_CELL_ANNOTATOR::run_aiot_simulations() + 0x2d (tsm_pti) Quartus 0x16bee0: PTI_DELAY_ANNOTATOR::full_annotate_routing_and_cell(std::vector<CDB_ATOM_NODE*, std::allocator<CDB_ATOM_NODE*> > const&, PTI_ROUTING_ANNOTATOR&, PTI_CELL_ANNOTATOR&, bool) + 0x6c0 (tsm_pti) Quartus 0x173b78: PTI_DELAY_ANNOTATOR::build_multicorner(PTI_DELAY_ANNOTATOR::INVOKE_MODE, bool, std::vector<TDB_TIMING_MODEL, std::allocator<TDB_TIMING_MODEL> > const&, bool) + 0x8f8 (tsm_pti) Quartus 0x11f6f2: FITCC_TDC_UTILITY::initialize_dat(TDC_ACCESSORIES::INVOKE_MODE, std::vector<TDB_TIMING_MODEL, std::allocator<TDB_TIMING_MODEL> > const&, bool, bool, bool, QGL::FOREST<int, int>*, bool, bool) + 0x842 (fitter_fitcc) Quartus 0x1223ca: FITCC_TDC_UTILITY::setup_tdc_utility(TDC_ACCESSORIES::INVOKE_MODE, std::vector<TDB_TIMING_MODEL, std::allocator<TDB_TIMING_MODEL> >, bool, bool, bool, bool, bool, bool, bool, QGL::FOREST<int, int>*, bool, bool, bool) + 0x91a (fitter_fitcc) Quartus 0x122e87: FITCC_TDC_UTILITY::FITCC_TDC_UTILITY(FITCC_ENV const*, TDC_ACCESSORIES::INVOKE_MODE, std::vector<TDB_TIMING_MODEL, std::allocator<TDB_TIMING_MODEL> >, bool, bool, bool, bool, bool, bool, bool, QGL::FOREST<int, int>*, bool, bool, bool) + 0x257 (fitter_fitcc) Quartus 0xcefd7: FITCC_ENV::get_tdc_utility_or_create_if_necessary(FITCC_ENV::FITCC_TDC_UTILITY_REQUEST_TYPE, TDC_ACCESSORIES::INVOKE_MODE, std::vector<TDB_TIMING_MODEL, std::allocator<TDB_TIMING_MODEL> >, bool, bool, bool, bool, QGL::FOREST<int, int>*, bool, bool) + 0x817 (fitter_fitcc) Quartus 0x5dd7e2: vpr_qi_change_default_dat_to_all_corners() + 0x1e2 (fitter_vpr20kmain) Quartus 0x6c81db: aa_flow_place(FIT::STATE&, PLACER_MODE) + 0x74b (fitter_vpr20kmain) Quartus 0x5d0c8d: (anonymous namespace)::place_internal(FIT::STATE&, PLACER_MODE) + 0x5d (fitter_vpr20kmain) Quartus 0xa3df1: VPR_QI_FACADE::place(FIT::STATE&) [clone .cold] + 0xe3 (fitter_vpr20kmain) Quartus 0x11934b: FDRGN_EXPERT::run_place_flow(QTL::OPAQUE_PTR<PCA::DEVICE_DATA, void (*)(PCA::DEVICE_DATA*)>) + 0x158b (fitter_fdrgn) Quartus 0x119cad: FDRGN_EXPERT::run_place(QTL::OPAQUE_PTR<PCA::DEVICE_DATA, void (*)(PCA::DEVICE_DATA*)>) + 0x20d (fitter_fdrgn) Quartus 0x11a37a: FDRGN_EXPERT::place() + 0x5fa (fitter_fdrgn) Quartus 0x3b589: fit2_fit_place_auto + 0xda (comp_fit2) Quartus 0x50fb7: TclNRRunCallbacks + 0x47 (tcl8.6) Quartus 0x2985b: fit2_fit_place + 0x2bf (comp_fit2) Quartus 0x50fb7: TclNRRunCallbacks + 0x47 (tcl8.6) Quartus 0x527df: TclEvalEx + 0x94f (tcl8.6) Quartus 0xfa3a6: Tcl_FSEvalFileEx + 0x266 (tcl8.6) Quartus 0xfa4be: Tcl_EvalFile + 0x2e (tcl8.6) Quartus 0x2a93e: qexe_evaluate_tcl_script(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x3de (comp_qexe) Quartus 0x2dda6: qexe_do_tcl(QEXE_FRAMEWORK*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, bool, bool) + 0x4c2 (comp_qexe) Quartus 0x2eeae: qexe_run_tcl_option(QEXE_FRAMEWORK*, char const*, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*, bool) + 0x66e (comp_qexe) Quartus 0x6ea03: QCU::DETAIL::intialise_qhd_and_run_qexe(QCU_FRAMEWORK&, FIO_PATH const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const*, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*, bool) + 0x9c (comp_qcu) Quartus 0x6ee4a: qcu_run_tcl_option(QCU_FRAMEWORK*, char const*, std::__cxx11::list<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*, bool) + 0x33e (comp_qcu) Quartus 0x34275: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0xbc7 (comp_qexe) Quartus 0x40adac: qfit2_main(int, char const**) + 0x8c (quartus_fit) Quartus 0x4e5c0: msg_main_thread(void*) + 0x10 (ccl_msg) Quartus 0x50b07: msg_thread_wrapper(void* (*)(void*), void*) + 0x8c (ccl_msg) Quartus 0x1f568: mem_thread_wrapper(void* (*)(void*), void*) + 0x98 (ccl_mem) Quartus 0x10f58: err_thread_wrapper(void* (*)(void*), void*) + 0x1e (ccl_err) Quartus 0xba55: thr_thread_wrapper + 0x15 (ccl_thr) Quartus 0x4f6f4: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xd3 (ccl_msg) System 0x23850: (c) System 0x2390a: __libc_start_main + 0x8a (c) Quartus 0x4062e9: _start + 0x29 (quartus_fit) End-trace Executable: quartus Comment: Compiling any project for Intel Cyclone 10 GX using Pro edition ends up in this error, when Fitter > Place stage is at 99 %. System Information Platform: linux64 OS name: Arch Linux OS version: Quartus Prime Information Address bits: 64 Version: 23.1.0 Build: 115 Edition: Pro Edition
8 Replies
- SyafieqS
Super Contributor
Internal error most of the time might be due to tool issue.
I need to check the issue, thus is it possible for you to attach the design in qar?
- Rutherther
New Contributor
That's not a problem at all. The compilation crashes for every project in Quartus Prime Pro (without license, only Cyclone 10 GX support). So I am including a simple project that contains just an AND gate connected to two inputs and one output.
- SyafieqS
Super Contributor
Thanks. I am looking into this to replicate at my end.
- SyafieqS
Super Contributor
Hi Ruth,
I am not able to see the issue using the design.
Just for sanity check, can you reinstall Quartus?
Just to make sure everything is setup properly.
- SyafieqS
Super Contributor
Let me know if there is any update
- Rutherther
New Contributor
Hi,
yes, I have an update from today. It took me a few days to download all of the components as I don't posses that fast internet connection and the files are large.
I have downloaded installation from tab called Multiple Files instead of Individual Files like last time, just to change something if there was a problem. After installation, it is working correctly.
So this has been solved. I am not sure whether the problem was in the individual files or just something went wrong in the installation process.
PS: When I install only Quartus with Cyclone 10 GX support, when compiling, I get an error and I have to install Aria 10 support to resolve it. This happened to me on two separate computers, once Windows and once Linux.
- SyafieqS
Super Contributor
Glad that had been resolved. Let me know if there is any other concern at your end.
- SyafieqS
Super Contributor
I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, Please login to https://supporttickets.intel.com/, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.
p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution, give Kudos and rate 5/5 survey