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

Quartus 2 internel error on virtual machine

Giray
Beginner
738 Views

Hi, I don't know if this is asked a lot but I've been receiving internal error when I am trying to compile schematics on Quartus II (13.1.0). I'm using the program on a virtual machine downloaded to M1 MacBook.  The complete error is belove,

 

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

 

Stack Trace:

0x43782: DYGR_ROUTE_TIMING_INFO::get_timing_node + 0xcc12

0x14d80: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0xaf0

0x14a0c: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0x77c

0x143bd: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0x12d

0x1a043: DYGR_PLACE_INFO_BODY::set_transient_data_members + 0x53

0x4701: DYGR_PLACE_INFO_BODY::load_data_from_pdb + 0x191

0x23f69: DYGR_PLACE_INFO_BODY::load_data + 0x29

0x23f12: DYGR_PLACE_INFO::load_data + 0x52

0x2484: DYGR_DIE_INFO_BODY::load_data + 0x104

0x19686: MPP_ROOT::start + 0x5a6

0x73da: Legacy_fitter_Init + 0x636a

0x257f: Legacy_fitter_Init + 0x150f

0x2168: Legacy_fitter_Init + 0x10f8

0xf8a6: TclInvokeStringCommand + 0xc6

0x112a8: TclEvalObjvInternal + 0x328

0x121b5: TclEvalEx + 0x8d5

0x12d48: TclEvalObjEx + 0x2d8

0x1abbd: Tcl_EvalObjCmd + 0xfd

0x112a8: TclEvalObjvInternal + 0x328

0x56917: TclExecuteByteCode + 0xe47

0xa2376: TclObjInterpProcCore + 0x76

0x112a8: TclEvalObjvInternal + 0x328

0x56917: TclExecuteByteCode + 0xe47

0xa2376: TclObjInterpProcCore + 0x76

0x112a8: TclEvalObjvInternal + 0x328

0x121b5: TclEvalEx + 0x8d5

0x7c117: Tcl_FSEvalFileEx + 0x1d7

0x7a626: Tcl_EvalFile + 0x36

0xc1ff: qexe_ipc_progress_bar_name + 0x12bf

0x11dd6: qexe_get_command_line + 0x1556

0x150d5: qexe_run_tcl_option + 0x585

0x1e03d: qcu_run_tcl_option + 0xb8d

0x156ed: qexe_process_cmdline_arguments + 0x54d

0x15851: qexe_standard_main + 0xa1

 

0xa7f8: msg_exe_fini + 0x58

0xaf3c: msg_exe_fini + 0x79c

0x1f14: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194

0xb8bf: msg_exe_main + 0x8f

 

0xee2bb: uaw_wcsrchr + 0xe87fb

0x8520f: uaw_wcsrchr + 0x7f74f

0x1b6b27: NtWaitLowEventPair + 0x1a83e7

 

End-trace

 

Quartus II 64-Bit Version 13.1.0 Build 162 10/23/2013 SJ Web Edition

Thanks!

 

0 Kudos
2 Replies
ShengN_Intel
Employee
696 Views

Hi,


Could you provide a sample design to duplicate the internal error?

Can provide the design privately to my email qi.sheng.ng@intel.com as well.


Thanks,

Best Regards,

Sheng


0 Kudos
ShengN_Intel
Employee
663 Views

Hi,

 

The internal error is not exist in Microsoft Windows machine. Seems like that internal error only appears on virtual machine in M1 MacBook. Previously there's a similar internal error on virtual machine in M1 Mac check image:

Screenshot 2023-03-21 082101.png

However, based on previous internal message that we do not officially support the use model of Windows running within VM in MacBook check image:

Screenshot 2023-03-21 082432.png

 

Thanks,

Best Regards,

Sheng

 

0 Kudos
Reply