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

Quartus Fitter Crashing

audrey1
Beginner
221 Views

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!

report.pngI noticed that similar cases appeared in the forum, but they were not solved. I have no problem compiling with a native Windows computer.

0 Kudos
4 Replies
AR_A_Intel
Employee
185 Views

Hello

 

Welcome to Intel forum. Apologies for the delay, could you share more detail of the problem. Provide error message screenshot or any warning notice. 


audrey1
Beginner
178 Views
Problem Details
Error:
Internal Error: Sub-system: DYGR, File: /quartus/ddb/dygr/dygr_place_info.cpp, Line: 3270
 
Stack Trace:
    0x48b5e: DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID::operator unsigned __int64 + 0x2c08e (DDB_DYGR)
    0x1e210: 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)
    0x1f91e: 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)
    0x1d5bb: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0xff (DDB_DYGR)
    0x18586: DYGR_PLACE_INFO_BODY::set_transient_data_members + 0x66 (DDB_DYGR)
    0x3407b: DYGR_PLACE_INFO_BODY::load_data_from_pdb + 0x83 (DDB_DYGR)
    0x15188: 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)
    0xeb93b: uaw_wcsrchr + 0xe5e7b (KERNEL32)
    0x71ef7: uaw_wcsrchr + 0x6c437 (KERNEL32)
   0x1bc7ef: NtWaitLowEventPair + 0x1ae25f (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.0
Build: 711
Edition: Lite Edition
AR_A_Intel
Employee
171 Views

Thanks for update. Based on my understanding, regrettably Quartus compilation don’t support Parallel Boot/VM.

Please accept my apologies for not being able to assist you fully as this is out of my expertise. Thank you for patience and understanding on this matter.


AR_A_Intel
Employee
160 Views

We have not heard from you and I hope that my last note clears up this matter. If you don’t have any further question, I will now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.


Reply