Quartus Prime 18.1 Fitter Crash

[Minahil]

Quartus crashes during the fitter of this simple verilog code. I am using quartus prime lite 18.1 as per my university course requirements and am running it through arm windows 11 on MacBook Pro (M2 Max) . The VM I’m using is UTM.


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

Stack Trace:
0x482c4: DYGR_BLK_PHYSICAL_IMPLEMENTATION::PORT_ID::operator unsigned __int64 + 0x2ba80 (DDB_DYGR)
0x1df80: std::_Hash<:_UMAP_TRAITS><:PORT_ID>,std::equal_to<:PORT_ID> &gt;,std::allocator<:PAIR><:PORT_ID const=""> &gt;,0&gt; &gt;::_Hashval + 0x10 (DDB_DYGR)
0x1f5fe: std::unordered_map<:PORT_ID>,std::equal_to<:PORT_ID>,std::allocator<:PAIR><:PORT_ID const=""> &gt; &gt;::operator[] + 0x1e (DDB_DYGR)
0x1d32b: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0xff (DDB_DYGR)
0x183f6: DYGR_PLACE_INFO_BODY::set_transient_data_members + 0x66 (DDB_DYGR)
0x33bcb: DYGR_PLACE_INFO_BODY::load_data_from_pdb + 0x83 (DDB_DYGR)
0x15088: DYGR_DIE_INFO_BODY::load_data + 0x2a4 (DDB_DYGR)
0x1cbd3: MPP_ROOT::start + 0x573 (COMP_MPP)
0x5bea: qfit_execute_mpp + 0x42 (comp_qfit_legacy_flow)
0x52ff: QFIT_FRAMEWORK::execute + 0x21b (comp_qfit_legacy_flow)
0x267f: qfit_legacy_flow_run_legacy_fitter_flow + 0x1c7 (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)
0x12606: qexe_evaluate_tcl_script + 0x376 (comp_qexe)
0x11864: qexe_do_tcl + 0x334 (comp_qexe)
0x16755: qexe_run_tcl_option + 0x585 (comp_qexe)
0x380c3: qcu_run_tcl_option + 0x1003 (comp_qcu)
0x160aa: qexe_run + 0x39a (comp_qexe)
0x16e51: qexe_standard_main + 0xc1 (comp_qexe)
0x2233: qfit2_main + 0x73 (quartus_fit)
0x12e98: msg_main_thread + 0x18 (CCL_MSG)
0x1467e: msg_thread_wrapper + 0x6e (CCL_MSG)
0x16660: mem_thread_wrapper + 0x70 (ccl_mem)
0x12761: msg_exe_main + 0xa1 (CCL_MSG)
0x287e: __tmainCRTStartup + 0x10e (quartus_fit)
0xeb93b: uaw_wcsrchr + 0xe5e7b (KERNEL32)
0x71ef7: uaw_wcsrchr + 0x6c437 (KERNEL32)
0x1bb19f: NtWaitLowEventPair + 0x1acc1f (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: 18.1.0
Build: 625
Edition: Lite Edition



verilog code:
module light (x1,x2,f);
input x1, x2;
output f;

assign f = (~x1 &amp; x2) | (x1 &amp; ~x2);

endmodule</:PORT_ID></:PAIR></:PORT_ID></:PORT_ID></:PORT_ID></:PAIR></:PORT_ID></:PORT_ID></:_UMAP_TRAITS>

[sstrell]

You're trying to run 7 year old software in a virtualized operating system on what is essentially an ARM processor.  You're lucky you can even start Quartus let alone attempt a compilation.  The error says you are using Windows 10 as well, not Windows 11, so which is it?  If you are indeed running Windows 11, Quartus 18.1 is not compatible with that.  You would definitely need to use a newer version.

There are too many non-supported factors in play here.  At the very least, use a newer version of Quartus (23.1 is the latest I believe for the Lite edition).

[RichardTanSY_Intel]

Please run your design on the latest Quartus version 23.1 and see if the internal error occurred. As a lot of bug has been fixed since then.

Regards.

Richard Tan

[RichardTanSY_Intel]

Any update on this?

Regards,

Richard Tan

[Minahil · Accepted solution]

I was able to resolve the issue by using the Parallels VM; Quartus Prime 18.1 works fine, even in Windows 11. When I want to upload to my de1-soc board, I switch to my 2017 Intel Mac since USB Blaster 2 is not supported by ARM. 

[RichardTanSY_Intel]

I'm pleased to know that your question has been addressed. 

Now, I will transitioning this thread to community support. If you have any further questions or concerns, please don't hesitate to reach out. Please login to https://supporttickets.intel.com/s/?language=en_US , view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support.

The community users will be able to help you on your follow-up questions.

Thank you and have a great day!

Best Regards,

Richard Tan