Forum Discussion

Alessio01's avatar
Alessio01
Icon for New Contributor rankNew Contributor
1 year ago

Problem with simulation quartus II web edition

Hello, I installed Quartus II Web Edition (version 13.0sp1, as required by the professor) for a university project. The software was installed on a MacBook using Parallels Desktop on a virtual machine with Windows 11. I haven’t encountered any issues until I tried to run a simulation of a schematic. After creating and saving the .VWF file, when I click “Run Simulation,” a window opens but closes after a few seconds (without generating error messages), and the simulation doesn’t run correctly. I also followed all the steps as instructed by the professor, including modifying the path to ModelSim-Altera in the “EDA Tool Options.” Can someone help me? Thank you.

3 Replies

  • Hi there, many old version are not supported by Win11. You may try Win10 which can support more version of Quartus.


    • Alessio01's avatar
      Alessio01
      Icon for New Contributor rankNew Contributor

      However, many of my classmates use Windows 11 without any issues (on a PC with native Windows 11, not through a virtual machine). Besides the problem mentioned earlier, I noticed that when I click on 'EDA Netlist Writer', the following error appears:

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

      Stack Trace:

      0x43282: DYGR_ROUTE_TIMING_INFO::get_timing_node + 0xd6c2

      0x131b0: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0xaf0

      0x12e3c: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0x77c

      0x127ed: DYGR_BLK_PHYSICAL_IMPLEMENTATION::populate_port_info_transient_data + 0x12d

      0x15b3a: DYGR_PLACE_INFO_BODY::set_transient_data_members + 0x5a

      0x1afd1: DYGR_PLACE_INFO_BODY::load_data_from_pdb + 0x191

      0x2829: DYGR_PLACE_INFO_BODY::load_data + 0x29

      0x289e: DYGR_PLACE_INFO::load_data + 0x3e

      0x2a31: DYGR_DIE_INFO_BODY::load_data + 0x131

      0x1951d: MPP_ROOT::start + 0x5bd

      0x6bba: Legacy_fitter_Init + 0x5b4a

      0x1e0f: Legacy_fitter_Init + 0xd9f

      0x2e68: Legacy_fitter_Init + 0x1df8

      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

      0xbd5f: qexe_ipc_progress_bar_name + 0xf3f

      0x11498: qexe_get_command_line + 0x1068

      0x147a5: qexe_run_tcl_option + 0x585

      0x1dacd: qcu_run_tcl_option + 0xb8d

      0x14dbd: qexe_process_cmdline_arguments + 0x54d

      0x14f21: qexe_standard_main + 0xa1

      0x4c78: msg_exe_fini + 0x58

      0x53bc: msg_exe_fini + 0x79c

      0x1584: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194

      0x5f9f: msg_exe_main + 0x8f

      0xf09fb: uaw_wcsrchr + 0xeaf3b

      0x87baf: uaw_wcsrchr + 0x820ef

      0x1bc4c7: ZwWaitLowEventPair + 0x1add47

      End-trace

      Quartus II 64-Bit Version 13.0.1 Build 232 06/12/2013 SJ Web Edition

      Service Pack Installed: 1

      At this point, I would be inclined to say that it is a problem caused by running the program on a virtual machine, even though one of my classmates is doing exactly the same thing and has no issues.

  • Thanks for providing the information. Accessing Quartus through virtual machines or remote desktop methods can indeed lead to certain issues.

    If any progress or issue, please let us know. Thanks again.