Forum Discussion

Balaji_G_Intel's avatar
Balaji_G_Intel
Icon for New Contributor rankNew Contributor
6 years ago

Using Quartus Pro SW 18.0 tool crashes during placement stage. I am looking for a workaround to avoid this crash.

Info (170191): Fitter placement operations beginning

Internal Error: Sub-system: VPR20KMAIN, File: /quartus/fitter/vpr20k/dap/dap_initial.cpp, Line: 7130

Internal Error

Stack Trace:

0xb7992: vpr_qi_jump_to_exit + 0x6f (fitter_vpr20kmain)

0x169fb9: vpr_exit_at_line + 0x83 (fitter_vpr20kmain)

0x72eb50: l_dap_initial_placed_at_hint_location() + 0x2cb0 (fitter_vpr20kmain)

0x5829bd: dap_initial_placement + 0x78d (fitter_vpr20kmain)

0x72b211: dap_do_initial_placement_phase + 0x81 (fitter_vpr20kmain)

0x723d15: dap_try_place + 0x95 (fitter_vpr20kmain)

0x63ed0a: aa_flow_do_placement_attempt + 0x2a (fitter_vpr20kmain)

0x6074b7: aa_flow_place + 0x167 (fitter_vpr20kmain)

0x5a69ff: (anonymous namespace)::place_internal(e_fitter_flow_stage, unsigned long long*) [clone .constprop.4613] + 0xf (fitter_vpr20kmain)

0xda1f4: VPR_QI_FACADE::post_bsyn_placement_flow() + 0x48 (fitter_vpr20kmain)

0x73ce7: VPR_QI_FACADE::vpr_bsyn_flow(bool, bool) + 0x53 (fitter_vpr20kmain)

0x6fef4: FDRGN_EXPERT::run_vpr(bool, bool, bool, bool, BSYN_FLOW_TYPE) + 0x194 (fitter_fdrgn)

0x29869: fit2_fit_place_auto + 0x143 (comp_fit2)

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

0x13eb3: fit2_fit_place + 0x2d7 (comp_fit2)

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

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

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

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

0x1268c: qexe_evaluate_tcl_script(std::string const&) + 0x397 (comp_qexe)

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

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

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

0x1b497: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0x483 (comp_qexe)

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

0x671c: thr_final_wrapper + 0xc (ccl_thr)

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

0x10f69: mem_thread_wrapper(void* (*)(void*), void*) + 0x99 (ccl_mem)

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

0x675f: thr_thread_wrapper + 0x15 (ccl_thr)

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

0x1ec36: __libc_start_main + 0xe6 (c)

End-trace

2 Replies

  • KennyT_altera's avatar
    KennyT_altera
    Icon for Super Contributor rankSuper Contributor

    Hi,

    1) can you use the latest release of quartus Prime pro 19.2?

    2) can you attached your design.qar files for us to investigate?

    Thanks,

  • sstrell's avatar
    sstrell
    Icon for Super Contributor rankSuper Contributor

    Try quitting Quartus and throwing out the qdb folder in your project directory. Start Quartus again and try to recompile.

    #iwork4intel