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

ERROR IN LAUNCHING PIN PLANNER IN QUARTUS

Tim25
Beginner
529 Views

Im currently using Quartus 18.1 lite on a M2 MacBook running on parallels Windows 11 Arm and is implementing it on a DE10-Lite board. After clicking on the pin planner in Quartus, it prompts me this error message displayed below and quits the program immediately. May I know if there is any solution to this issue?

Error message :

Version:1.0 StartHTML:0000000105 EndHTML:0000017063 StartFragment:0000000541 EndFragment:0000017025
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<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)
0x1f5fe: 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)
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)
0xfdb6: DPF_DEVICE::create_pads + 0xc6 (db_dpf)
0x5aef: DPF_DEVICE::DPF_DEVICE + 0xdf (db_dpf)
0xc6442: PPLQ_DEVICE::load_device_info + 0x132 (prj_pplq)
0x64983: PPLQ_DEVICE::create_device + 0x13 (prj_pplq)
0x6495c: PPLQ_DESIGN::create_device + 0x8c (prj_pplq)
0xc62e4: PPLQ_DESIGN::load_device_info + 0x124 (prj_pplq)
0x1c3c9: PPLQ_DESIGN::PPLQ_DESIGN + 0x1e9 (prj_pplq)
0xc6193: PPLQ_FRAME_WND::load_design + 0x83 (prj_pplq)
0x23538: PPLQ_FRAME_WND::PPLQ_FRAME_WND + 0x228 (prj_pplq)
0x129420: prj_pplq_create_frame_wnd + 0x70 (prj_pplq)
0x1c130: QUI_FRAME_MGR::create_frame_wnd + 0x190 (SYS_QUI)
0x1bd19: QUI_FRAME_MGR::create_frame_wnd + 0x2a9 (SYS_QUI)
0x1c6da: QUI_FRAME_MGR::create_new + 0x11a (SYS_QUI)
0x1c5a1: QUI_FRAME_MGR::create_new + 0xa1 (SYS_QUI)
0x1f632: qui_create_new + 0x42 (SYS_QUI)
0x11c420: QMetaObject::activate + 0x520 (QtCore4)
0xa23f: QAction::activate + 0xdf (QtGui4)
0x3b5c03: QMenu::actionGeometry + 0x443 (QtGui4)
0x3b5a95: QMenu::actionGeometry + 0x2d5 (QtGui4)
0x60794: QWidget::event + 0xd4 (QtGui4)
0x3b6934: QMenu::event + 0x284 (QtGui4)
0x22e95: QApplicationPrivate::notify_helper + 0xf5 (QtGui4)
0x21a8e: QApplication::notify + 0x71e (QtGui4)
0x10d92b: QCoreApplication::notifyInternal + 0x7b (QtCore4)
0x25cfe: QApplicationPrivate::sendMouseEvent + 0x1de (QtGui4)
0x85366: QScrollBar::trUtf8 + 0x10b6 (QtGui4)
0x890b1: QApplication::winMouseButtonUp + 0x2761 (QtGui4)
0x11615b: SetThreadCursorCreationScaling + 0x111edb (USER32)
0xa2b83: SetThreadCursorCreationScaling + 0x9e903 (USER32)
0x9f02b: SetThreadCursorCreationScaling + 0x9adab (USER32)
0x115b4b: SetThreadCursorCreationScaling + 0x1118cb (USER32)
0x132802: QEventDispatcherWin32::processEvents + 0x3e2 (QtCore4)
0x80eb4: QApplicationPrivate::openPopup + 0x204 (QtGui4)
0x10a88b: QEventLoop::exec + 0x22b (QtCore4)
0x10ce6f: QCoreApplication::exec + 0xdf (QtCore4)
0x197b: qgq_main + 0x7b (quartus)
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)
0x24e7: WinMain + 0x127 (quartus)
0x1e58: __tmainCRTStartup + 0x148 (quartus)
0xef62b: uaw_wcsrchr + 0xe9b6b (KERNEL32)
0x8660f: uaw_wcsrchr + 0x80b4f (KERNEL32)
0x1ba2d7: ZwWaitLowEventPair + 0x1abb97 (ntdll)

End-trace


Executable: quartus
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

Labels (1)
0 Kudos
2 Replies
sstrell
Honored Contributor III
511 Views

As much as I love the Mac, you're trying to run Windows software in an unsupported OS (Windows 11) for that version of Quartus (18.1; 6 year old software at this point) in a virtual machine!  I'm surprised it worked at all.  Try a more recent version of Quartus Lite or Standard.

0 Kudos
ShengN_Intel
Employee
501 Views

Hi,


You may check the Operating System (OS) Support list here https://www.intel.com/content/www/us/en/support/programmable/support-resources/design-software/os-support.html

Based on internal previous message, MacBook is not officially supported OS yet.


Thanks,

Best Regards,

Sheng


0 Kudos
Reply