Quartus 18.1 fitter crash

Hi Eugene,

I can see you are using EOL Window 7 which might be hard to support. Is it possible to migrate to Win 10 and see if this resolve?

May I know if previous reply is feasible?

Sorry for the late answer. I tried to check it on computer with Win 10 a also upgrade Quartus to 21.1. But the problem remains the same. Nothing changes.

Problem Details
Error:
Internal Error: Sub-system: VPR20KMAIN, File: /quartus/fitter/vpr20k/vpr_common/cluster_legality_pincount.c, Line: 1332

Internal Error

Stack Trace:

   0x5d30d0: vpr_qi_jump_to_exit + 0x80 (fitter_vpr20kmain)

   0x106cda: vpr_exit_at_line + 0x8a (fitter_vpr20kmain)

   0x106d20: handle_assertion_failure_stripped + 0x30 (fitter_vpr20kmain)

    0x9fa65: cl_legality_pincount_block_list_legal_for_inputs_and_outputs + 0x255 (fitter_vpr20kmain)

    0x73ed0: l_block_list_feasible_with_specified_inputs + 0x150 (fitter_vpr20kmain)

    0x7473a: l_block_list_feasible_with_default_inputs_vpr_engine + 0xca (fitter_vpr20kmain)

    0x7152e: cl_block_list_and_first_ale_position_feasible_with_default_inputs + 0x1ce (fitter_vpr20kmain)

    0x51da8: l_anneal_try_ale_swap + 0x208 (fitter_vpr20kmain)

    0x51ab1: l_anneal_try_pair_swaps + 0x211 (fitter_vpr20kmain)

    0x4fd6f: l_anneal_prl_try_pair_swaps + 0x9f (fitter_vpr20kmain)

   0x1bf7e5: simd_job_wait + 0x95 (fitter_vpr20kmain)

    0x50347: l_anneal_prl_perform_temperature + 0x597 (fitter_vpr20kmain)

    0x4c447: anneal_clustering + 0x657 (fitter_vpr20kmain)

    0x4585f: cl_build_cluster_of_block_from_scratch + 0x75f (fitter_vpr20kmain)

    0x39996: do_clustering + 0x4e6 (fitter_vpr20kmain)

    0x7e126: cl_flow_pack_to_cbes_2 + 0x816 (fitter_vpr20kmain)

    0x7d816: cl_flow_pack_to_cbes + 0x96 (fitter_vpr20kmain)

   0x297abc: l_do_clustering_phase + 0x18c (fitter_vpr20kmain)

   0x296e14: aa_flow_place + 0x64 (fitter_vpr20kmain)

   0x296aec: aa_flow_fit + 0x11c (fitter_vpr20kmain)

   0x5d27e9: VPR_QI_FACADE::vpr_qi_main + 0x69 (fitter_vpr20kmain)

    0x3ce20: fitapi_run_vpr + 0x90 (fitter_fitapi)

    0x207ff: FSV_EXPERT_BASE::run_vpr + 0x13f (fitter_fsv)

    0x20229: FSV_EXPERT_BASE::place_and_route + 0x139 (fitter_fsv)

    0x1f677: FSV_EXPERT_BASE::invoke_fitter + 0x617 (fitter_fsv)

    0x1d282: fsv_execute + 0x22 (fitter_fsv)

     0xf01c: fmain_start + 0x8ac (FITTER_FMAIN)

     0x36ab: qfit_execute_fit + 0x1c7 (comp_qfit_legacy_flow)

     0x48d8: QFIT_FRAMEWORK::execute + 0x2b4 (comp_qfit_legacy_flow)

     0x1afb: qfit_legacy_flow_run_legacy_fitter_flow + 0x1c3 (comp_qfit_legacy_flow)

    0x14640: TclInvokeStringCommand + 0xf0 (tcl86)

    0x16442: TclNRRunCallbacks + 0x62 (tcl86)

    0x17c4d: TclEvalEx + 0x9ed (tcl86)

    0xa6a8b: Tcl_FSEvalFileEx + 0x22b (tcl86)

    0xa5136: Tcl_EvalFile + 0x36 (tcl86)

    0x127c0: qexe_evaluate_tcl_script + 0x340 (comp_qexe)

    0x11a6d: qexe_do_tcl + 0x2fd (comp_qexe)

    0x16c9e: qexe_run_tcl_option + 0x5ee (comp_qexe)

    0x369f1: qcu_run_tcl_option + 0xdd1 (comp_qcu)

    0x16599: qexe_run + 0x309 (comp_qexe)

    0x17641: qexe_standard_main + 0xc1 (comp_qexe)

     0x2092: qfit2_main + 0x82 (quartus_fit)

    0x13638: msg_main_thread + 0x18 (CCL_MSG)

    0x1494e: msg_thread_wrapper + 0x6e (CCL_MSG)

    0x18520: mem_thread_wrapper + 0x70 (ccl_mem)

    0x12df1: msg_exe_main + 0xa1 (CCL_MSG)

     0x2c88: __scrt_common_main_seh + 0x11c (quartus_fit)

    0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)

    0x526a0: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: quartus
Comment:
None

System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0

Quartus Prime Information
Address bits: 64
Version: 21.1.1
Build: 850
Edition: Standard Edition

Is it possible to attach the design in qar for me to reproduce?

This seem to me a legit bug. we need a design to further investigate and possibly provide a workaround.

Unfortunately I can not send a design because of our company policy.

I try to change a design and compiler settings to find exact cause of error, but I still don't succeed with that.

Can you help me to find possible error causes, according to file and functions where it happens, from the report?

If the design cannot be shared, is small test design possible to be created at your end? replicating the issue.

Or you can send your compilation database without sending the source design files? may follow below link on how to do that.

https://www.intel.com/content/www/us/en/support/programmable/articles/000076181.html

Quartus database at least will give some hint to move this forward.

Hello,

Thanks for the database. I am checking this with engineering team. Will get back to you once there is any update

I am still pending reply regarding the issue. Might take sometimes due to holiday seasons.

Hello Eugene,

I am pending from developer and it has been assigned to right person.

Will let you know if there is any update.