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

Quartus Prime Problem Report

SThom66
Beginner
744 Views

I am working on a project in Quartus Prime Standard version 2018.1 build 646 and it crashes during compilation. Below is the problem report. Any idea what could be causing this?

 

Problem Details
Error:
Internal Error: Sub-system: TDB, File: /quartus/tsm/tdb/tdb_node.cpp, Line: 2080
fanin_edge->get_dst_node() == this
Stack Trace:
     0x4cc3: TDB_NODE::clean_up_dangling_fanin_edges + 0x2d3 (TSM_TDB)
     0x4fbf: TDB_NODE::clean_up_dangling_edges + 0x1b (TSM_TDB)
     0x8ceb: sta_rebuild_and_preprocess_tdb + 0x207 (tsm_sta)
     0xb13c: TDC_STA_ACCESSORIES::incrementally_rebuild_tdb_netlist_for_atoms + 0x138 (tsm_tdc)
     0xb35e: TDC_STA_ACCESSORIES::incrementally_rebuild_tdb_netlist_for_atoms + 0x4e (tsm_tdc)
    0xd0f0f: FITCC_TDC_UTILITY::setup_tdc_utility + 0x48f (FITTER_FITCC)
    0xc9cd1: FITCC_TDC_UTILITY::FITCC_TDC_UTILITY + 0x2f1 (FITTER_FITCC)
    0x4c4dd: FITCC_ENV::get_tdc_utility_or_create_if_necessary + 0x68d (FITTER_FITCC)
    0x4c872: FITCC_ENV::get_tdc_utility_or_create_if_necessary + 0x152 (FITTER_FITCC)
   0x5c6d57: vpr_qi_timing_analysis_direct_api_prepare_to_talk_to_tdc + 0x1b7 (fitter_vpr20kmain)
   0x5ca33e: vpr_qi_timing_direct_api_create_tdc_filter + 0x5e (fitter_vpr20kmain)
    0x72bc6: cl_flow_pack_to_cbes_2 + 0x836 (fitter_vpr20kmain)
    0x72296: cl_flow_pack_to_cbes + 0x96 (fitter_vpr20kmain)
   0x26c16c: l_do_clustering_phase + 0x18c (fitter_vpr20kmain)
   0x26b4b4: aa_flow_place + 0x64 (fitter_vpr20kmain)
   0x26b15d: aa_flow_fit + 0x11d (fitter_vpr20kmain)
   0x573ffe: VPR_QI_FACADE::vpr_qi_main + 0x6e (fitter_vpr20kmain)
    0x3384e: fitapi_run_vpr + 0x7e (fitter_fitapi)
    0x1fc7f: FSV_EXPERT_BASE::run_vpr + 0x13f (fitter_fsv)
    0x1f73d: FSV_EXPERT_BASE::place_and_route + 0x12d (fitter_fsv)
    0x1eba6: FSV_EXPERT_BASE::invoke_fitter + 0x636 (fitter_fsv)
    0x1ca42: fsv_execute + 0x22 (fitter_fsv)
     0xea50: fmain_start + 0x900 (FITTER_FMAIN)
     0x41b1: qfit_execute_fit + 0x1bd (comp_qfit_legacy_flow)
     0x5384: QFIT_FRAMEWORK::execute + 0x2a0 (comp_qfit_legacy_flow)
     0x267f: qfit_legacy_flow_run_legacy_fitter_flow + 0x1c7 (comp_qfit_legacy_flow)
    0x14410: TclInvokeStringCommand + 0xf0 (tcl86)
    0x161e2: TclNRRunCallbacks + 0x62 (tcl86)
    0x17a65: TclEvalEx + 0xa65 (tcl86)
    0xa6f8b: Tcl_FSEvalFileEx + 0x22b (tcl86)
    0xa5646: Tcl_EvalFile + 0x36 (tcl86)
    0x12606: qexe_evaluate_tcl_script + 0x376 (comp_qexe)
    0x11864: qexe_do_tcl + 0x334 (comp_qexe)
    0x16755: qexe_run_tcl_option + 0x585 (comp_qexe)
    0x38083: qcu_run_tcl_option + 0x1003 (comp_qcu)
    0x160aa: qexe_run + 0x39a (comp_qexe)
    0x16e51: qexe_standard_main + 0xc1 (comp_qexe)
     0x2233: qfit2_main + 0x73 (quartus_fit)
    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)
     0x287e: __tmainCRTStartup + 0x10e (quartus_fit)
    0x17c23: BaseThreadInitThunk + 0x13 (KERNEL32)
    0x6cea0: RtlUserThreadStart + 0x20 (ntdll)
 
End-trace


Executable: quartus_fit
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: Standard Edition

  

0 Kudos
3 Replies
Kenny_Tan
Moderator
726 Views

Can you try to use the latest release of Quartus Prime 20.1std?


If still cannot solve, you may have to attached your design.qar files for us to have a look. Let's us know if you want to send the design privately so that we can arrange for you.


0 Kudos
Kenny_Tan
Moderator
695 Views

Any update?


0 Kudos
Kenny_Tan
Moderator
673 Views

We do not receive any response from you to the previous question that we have provided. Please post a response in 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 with your follow-up questions. 


0 Kudos
Reply