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

Quartus crash

Altera_Forum
Honored Contributor II
1,788 Views

Hello! 

 

My Quartus Prime Version 15.1.2 Lite Edition crashes every time at Fitter 80% ("Fitter placement operations beginning"). Can someone help me to solve this? 

Build machine: Intel i7-4790K, 32GB RAM, MB ASUS Z97-P. 

Please find problem details few lines below. Thx! 

 

 

--- Quote Start ---  

 

Problem Details 

Error: 

Internal Error: Sub-system: STA, File: /quartus/tsm/sta/sta_tdc_common_req.cpp, Line: 972 

m_dst_clk == clk_dst_from_mask 

Stack Trace: 

0x37e38: STA_TDC_CLOCK_INTERFACE::~STA_TDC_CLOCK_INTERFACE + 0x3fc8 (tsm_sta) 

0x364d2: STA_TDC_CLOCK_INTERFACE::~STA_TDC_CLOCK_INTERFACE + 0x2662 (tsm_sta) 

0x1f57a: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x51ca (tsm_sta) 

0x1e3d2: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x4022 (tsm_sta) 

0x1d999: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x35e9 (tsm_sta) 

0x1cb4a: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x279a (tsm_sta) 

0x4394: PUT_SPMD_JOB_VOID_PTR::create_job + 0x7a4 (ccl_put) 

0x1bc2c: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x187c (tsm_sta) 

0x1bd7c: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x19cc (tsm_sta) 

0x1be21: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x1a71 (tsm_sta) 

0x1c9ac: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x25fc (tsm_sta) 

0x1c6c0: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x2310 (tsm_sta) 

0x1c609: STA_SLACK_CALCULATOR_HELPER::~STA_SLACK_CALCULATOR_HELPER + 0x2259 (tsm_sta) 

0x5dc8c: sta_tdb_node_has_max_skew + 0x8570 (tsm_sta) 

0x5e275: sta_compute_slack_for_tdc + 0x1c5 (tsm_sta) 

0x17faa: TDC_STA_CLOCK_UTIL::TDC_STA_CLOCK_UTIL + 0x2e0a (tsm_tdc) 

0x196f9: TDC_STA_CLOCK_UTIL::TDC_STA_CLOCK_UTIL + 0x4559 (tsm_tdc) 

0x193ac: TDC_STA_CLOCK_UTIL::TDC_STA_CLOCK_UTIL + 0x420c (tsm_tdc) 

0x9aa7: TDC_ATOM_NETLIST_TAINT_MANAGER::indicate_tdc_reflects_atom_netlist_exactly + 0x3eb3 (tsm_tdc) 

0x5538fd: VPR_QI_FACADE::vpr_post_place_bsyn_flow + 0x5e2bd (fitter_vpr20kmain) 

0x41c1ad: BSYN_LABMGR_INTERFACE erator= + 0x40ff1d (fitter_vpr20kmain) 

0x2f89d8: BSYN_LABMGR_INTERFACE erator= + 0x2ec748 (fitter_vpr20kmain) 

0x2f75c7: BSYN_LABMGR_INTERFACE erator= + 0x2eb337 (fitter_vpr20kmain) 

0x2d9bf4: BSYN_LABMGR_INTERFACE erator= + 0x2cd964 (fitter_vpr20kmain) 

0x19b91: BSYN_LABMGR_INTERFACE erator= + 0xd901 (fitter_vpr20kmain) 

0x17043: BSYN_LABMGR_INTERFACE erator= + 0xadb3 (fitter_vpr20kmain) 

0x2d00d7: BSYN_LABMGR_INTERFACE erator= + 0x2c3e47 (fitter_vpr20kmain) 

0x242e42: BSYN_LABMGR_INTERFACE erator= + 0x236bb2 (fitter_vpr20kmain) 

0x2445de: BSYN_LABMGR_INTERFACE erator= + 0x23834e (fitter_vpr20kmain) 

0x24405f: BSYN_LABMGR_INTERFACE erator= + 0x237dcf (fitter_vpr20kmain) 

0x240262: BSYN_LABMGR_INTERFACE erator= + 0x233fd2 (fitter_vpr20kmain) 

0x4f478c: VPR_QI_FACADE::vpr_qi_main + 0x3c (fitter_vpr20kmain) 

0x32d80: fitapi_run_vpr + 0x70 (fitter_fitapi) 

0x1b33f: fsv_execute + 0x327f (fitter_fsv) 

0x1adfd: fsv_execute + 0x2d3d (fitter_fsv) 

0x1a266: fsv_execute + 0x21a6 (fitter_fsv) 

0x180e2: fsv_execute + 0x22 (fitter_fsv) 

0xed0f: fmain_start + 0x89f (FITTER_FMAIN) 

 

 

 

 

 

 

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_apply_ini_vars + 0x2724 (comp_qexe) 

0x16725: qexe_run_tcl_option + 0x585 (comp_qexe) 

0x32068: qcu_run_tcl_option + 0xd78 (comp_qcu) 

0x1607a: qexe_process_cmdline_arguments + 0x242a (comp_qexe) 

0x16de1: qexe_standard_main + 0xc1 (comp_qexe) 

 

 

0x12938: msg_initialize_out_of_memory_handler + 0x348 (CCL_MSG) 

0x13f5e: msg_set_stack_size + 0x7e (CCL_MSG) 

0x4092: mem_cfg_is_on + 0x11a (ccl_mem) 

0x12021: msg_exe_main + 0xa1 (CCL_MSG) 

 

 

0x8363: BaseThreadInitThunk + 0x13 (KERNEL32) 

0x670d0: RtlUserThreadStart + 0x20 (ntdll) 

 

 

End-trace 

 

 

 

 

Executable: quartus_fit 

Comment: 

None 

 

 

System Information 

Platform: windows64 

OS name: Windows 8 

OS version: 6.2 

 

 

Quartus Prime Information 

Address bits: 64 

Version: 15.1.2 

Build: 193 

Edition: Lite Edition 

 

--- Quote End ---  

0 Kudos
5 Replies
Altera_Forum
Honored Contributor II
493 Views

You'll have to raise a ticket with altera mysupport.

0 Kudos
Altera_Forum
Honored Contributor II
493 Views

for which device are you compiling? 

I remember seeing something similar when I compiled for a device where Quartus needed more RAM than was available on the machine. I have no idea if you see the same, but you could take a look at the datasheet/system requirements
0 Kudos
Altera_Forum
Honored Contributor II
493 Views

 

--- Quote Start ---  

for which device are you compiling? 

I remember seeing something similar when I compiled for a device where Quartus needed more RAM than was available on the machine. I have no idea if you see the same, but you could take a look at the datasheet/system requirements 

--- Quote End ---  

 

 

His machine, with 32GB ram, should cover pretty much everything. 

Crashes can only be answered by Altera. But to the OP: have you tried Q16?
0 Kudos
Altera_Forum
Honored Contributor II
493 Views

 

--- Quote Start ---  

have you tried Q16? 

--- Quote End ---  

 

 

No, did not try with Q16
0 Kudos
Altera_Forum
Honored Contributor II
493 Views

 

--- Quote Start ---  

for which device are you compiling? 

--- Quote End ---  

 

 

Cyclone V (5CEFA5U19C8)
0 Kudos
Reply