Forum Discussion

mikeyl's avatar
mikeyl
Icon for New Contributor rankNew Contributor
4 years ago

Quartus Fitter Crashing

Hi, I'm looking to get some help to get my Quartus to work for my digital logic/comp org class. Its been giving me quite a headache. Currently I have the M1 Pro Macbook and I need to run Quartus using a Parallel Boot/VM. I'm able to install Quaratus and compile it however I run into an error while fitting. Is there anything I can do to fix this error. Thank you! 

Problem Details
Error:
Internal Error: Sub-system: DYGR, File: /quartus/ddb/dygr/dygr_place_info.cpp, Line: 3270
 
Stack Trace:
    0x48b8c: DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID::operator unsigned __int64 + 0x2bb4c (DDB_DYGR)
    0x1e780: std::_Hash<std::_Umap_traits<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID,DYGR_BLK_PORT_INFO const * __ptr64,std::_Uhash_compare<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID,STL_HASH_FUNCTOR<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID>,std::equal_to<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID> >,std::allocator<std::pair<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID const ,DYGR_BLK_PORT_INFO const * __ptr64> >,0> >::_Hashval + 0x10 (DDB_DYGR)
    0x1fc3e: std::unordered_map<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID,DYGR_BLK_PORT_INFO const * __ptr64,STL_HASH_FUNCTOR<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID>,std::equal_to<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID>,std::allocator<std::pair<DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID const ,DYGR_BLK_PORT_INFO const * __ptr64> > >::operator[] + 0x1e (DDB_DYGR)
    0x1db2b: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0xff (DDB_DYGR)
    0x189d6: DYGR_PLACE_INFO_BODY::set_transient_data_members + 0x66 (DDB_DYGR)
    0x3433b: DYGR_PLACE_INFO_BODY::load_data_from_pdb + 0x83 (DDB_DYGR)
    0x15360: DYGR_DIE_INFO_BODY::load_data + 0x2a4 (DDB_DYGR)
    0x1d1f7: MPP_ROOT::start + 0x587 (COMP_MPP)
     0x5e5a: qfit_execute_mpp + 0x42 (comp_qfit_legacy_flow)
     0x555b: QFIT_FRAMEWORK::execute + 0x22f (comp_qfit_legacy_flow)
     0x2768: qfit_legacy_flow_run_legacy_fitter_flow + 0x1d4 (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)
    0x12877: qexe_evaluate_tcl_script + 0x367 (comp_qexe)
    0x11ac3: qexe_do_tcl + 0x343 (comp_qexe)
    0x16c34: qexe_run_tcl_option + 0x584 (comp_qexe)
    0x39285: qcu_run_tcl_option + 0xf95 (comp_qcu)
    0x1658d: qexe_run + 0x39d (comp_qexe)
    0x17371: qexe_standard_main + 0xc1 (comp_qexe)
     0x2262: qfit2_main + 0x82 (quartus_fit)
    0x13258: msg_main_thread + 0x18 (CCL_MSG)
    0x14a5e: msg_thread_wrapper + 0x6e (CCL_MSG)
    0x16af0: mem_thread_wrapper + 0x70 (ccl_mem)
    0x12af1: msg_exe_main + 0xa1 (CCL_MSG)
     0x2a02: __tmainCRTStartup + 0x10e (quartus_fit)
    0xeae0b: uaw_wcsrchr + 0xe534b (KERNEL32)
    0x84a5f: uaw_wcsrchr + 0x7ef9f (KERNEL32)
   0x1bac4f: ZwWaitLowEventPair + 0x1ac5cf (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: 20.1.1
Build: 720
Edition: Lite Edition

35 Replies

Show More
  • q1's avatar
    q1
    Icon for New Contributor rankNew Contributor
    4 years ago

    @mikeyl , did you find a solution? I'm in the exact same position as you. Just bought a M1 mac and am trying to run Quartus Lite on Parallels

  • pingu00's avatar
    pingu00
    Icon for New Contributor rankNew Contributor
    4 years ago

    So,,,

    Who can solve this problem...

    iI have same situation.

    help

  • Tom_Gambill's avatar
    Tom_Gambill
    Icon for New Contributor rankNew Contributor
    4 years ago

    Same exact problem on MacBook Pro M1 in Parallels. It would be great to be able to use this machine for work... there are SO many posts about these issues online with Windows on ARM.

  • Jjseg's avatar
    Jjseg
    Icon for New Contributor rankNew Contributor
    4 years ago

    Same exact problem on a MacBook Pro M1 Max running Parallels 18:

    Internal Error: Sub-system: DYGR, File: /quartus/ddb/dygr/dygr_place_info.cpp, Line: 3776

    It is always the same exact problem with all designs

    Is this issue finally solved?

  • SkyWT's avatar
    SkyWT
    Icon for New Contributor rankNew Contributor
    4 years ago

    Same issue on MacBook Air M1 running Parallels 17, Windows11 arm

    "Internal Error: Sub-system: DYGR, File: /quartus/ddb/dygr/dygr_place_info.cpp, Line: 3776"
    It would be great if anyone could provide a solution...
  • Ryan_S_Intel's avatar
    Ryan_S_Intel
    Icon for New Contributor rankNew Contributor
    4 years ago

    This is not a response to the specific IE, but the ways you are seeing them move around.

    Note that Quartus is deterministic, e.g. if you start with the same project on the same machine(and let's delete the /db), it will do the exact same steps and give the same results. (If you change anything though, even as little as the name of a signal in your design, or maybe add a comment, then all bets are off).

    So internal errors should not jump around. When I've seen them, the user can repeat it and get the same one time-after-time. One thing I have seen when they jump around is corrupted memory on a machine. I hate suggesting that but throwing it out there.

    One other thing I've heard might have an effect is the Number of Processors used. Maybe try setting this to 1 (I think it defaults to max available) and see if it becomes consistent.

  • salwa's avatar
    salwa
    Icon for New Contributor rankNew Contributor
    3 years ago

    hi, anyone knows the solution?

  • SkyWT's avatar
    SkyWT
    Icon for New Contributor rankNew Contributor
    3 years ago

    I use Quartus 9.0 Free instead, which works in my VM.