Has anybody seen this error? And if so, what is being done to correct this?

MSchu8 · ‎07-02-2019

Currently, it occurs when I click on the "Devices and Pins" tab and try to reset a Dual Function pin. This error is occurring with an Arria10 using version 18.1 Pro on Windows 10.

In the past, I would get this error when scanning a JTAG chain that contained a 64Mbit device. This error occurs on all versions above 16.0 on both Windows 7 and Windows 10 machines.

AnandRaj_S_Intel · ‎07-03-2019

Hi,

Sorry for the inconveniences caused.

Can you please attache the log/report. (Click on preview report)

Also please do check with Quartus 19.1 pro.

Regards

Anand

MSchu8 · ‎07-03-2019

Hi Anand, Here is the report for the V18.1 Pro crash (while viewing Devices and Pins). Problem Details Error: *** Fatal Error: Access Violation at 00007FFA461FB2D0 Module: qpro.exe Stack Trace: 0x6b2cf: Ui_mdb_ip_upgrade_dlg::setupUi + 0x33f (sys_mdb) 0x1efe76: QTranslator::translate + 0x2616 (Qt5Core) 0x1f72a5: QVariant::QVariant + 0xb5 (Qt5Core) 0x29ee69: QStandardItem::setData + 0x289 (Qt5Gui) 0x6c152: DSET_DUAL_PURPOSE_PAGE::fill_list_control + 0x3e2 (saui_dset) 0x6e65f: DSET_DUAL_PURPOSE_PAGE::showEvent + 0x21f (saui_dset) 0x3acc2: QWidget::event + 0x732 (Qt5Widgets) 0xdb006: QFrame::event + 0x36 (Qt5Widgets) 0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets) 0x17c16: QApplication::notify + 0x1b56 (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x4cf88: QWidgetPrivate::show_helper + 0x178 (Qt5Widgets) 0x4b697: QWidget::setVisible + 0x287 (Qt5Widgets) 0x329de: QStackedLayout::setCurrentIndex + 0x16e (Qt5Widgets) 0xb4a0e: AFCQ_TREE_SHEET::tree_clicked + 0xbe (GCL_AFCQ) 0x1de156: QMetaObject::activate + 0x576 (Qt5Core) 0x197b1c: QItemSelectionModel::setCurrentIndex + 0x11c (Qt5Core) 0x235c27: QAbstractItemView::mousePressEvent + 0x2b7 (Qt5Widgets) 0x297998: QTreeView::mousePressEvent + 0x88 (Qt5Widgets) 0x3a655: QWidget::event + 0xc5 (Qt5Widgets) 0xdb006: QFrame::event + 0x36 (Qt5Widgets) 0x23bfe8: QAbstractItemView::viewportEvent + 0x318 (Qt5Widgets) 0x1c0e8c: QCoreApplicationPrivate::sendThroughObjectEventFilters + 0xdc (Qt5Core) 0x18d7b: QApplicationPrivate::notify_helper + 0x12b (Qt5Widgets) 0x1699c: QApplication::notify + 0x8dc (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x1a0d5: QApplicationPrivate::sendMouseEvent + 0x325 (Qt5Widgets) 0x62898: QSizePolicy::QSizePolicy + 0x2d18 (Qt5Widgets) 0x6060d: QSizePolicy::QSizePolicy + 0xa8d (Qt5Widgets) 0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets) 0x17c16: QApplication::notify + 0x1b56 (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x4cc00: QGuiApplicationPrivate::processMouseEvent + 0x870 (Qt5Gui) 0x345fa: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui) 0x2084e4: QEventDispatcherWin32::processEvents + 0xd64 (Qt5Core) 0xca65: DispatchMessageW + 0x6a5 (USER32) 0xc581: DispatchMessageW + 0x1c1 (USER32) 0x207cb5: QEventDispatcherWin32::processEvents + 0x535 (Qt5Core) 0x4ff88: qt_plugin_query_metadata + 0x1d18 (qwindows) 0x1ba982: QEventLoop::exec + 0x1b2 (Qt5Core) 0x1d22f6: QDialog::exec + 0x166 (Qt5Widgets) 0x7f9b3: dset_dyn_option_dlg + 0x123 (saui_dset) 0x31de7: DSET_DEVICE::show_option_dlg + 0x217 (saui_dset) 0x1de156: QMetaObject::activate + 0x576 (Qt5Core) 0xe13fb: QAbstractButton::clicked + 0xab (Qt5Widgets) 0xe131c: QAbstractButton::click + 0x19c (Qt5Widgets) 0xe213b: QAbstractButton::mouseReleaseEvent + 0x8b (Qt5Widgets) 0x3a66b: QWidget::event + 0xdb (Qt5Widgets) 0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets) 0x1699c: QApplication::notify + 0x8dc (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x1a0d5: QApplicationPrivate::sendMouseEvent + 0x325 (Qt5Widgets) 0x62898: QSizePolicy::QSizePolicy + 0x2d18 (Qt5Widgets) 0x6060d: QSizePolicy::QSizePolicy + 0xa8d (Qt5Widgets) 0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets) 0x17c16: QApplication::notify + 0x1b56 (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x4cc00: QGuiApplicationPrivate::processMouseEvent + 0x870 (Qt5Gui) 0x345fa: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui) 0x2084e4: QEventDispatcherWin32::processEvents + 0xd64 (Qt5Core) 0xca65: DispatchMessageW + 0x6a5 (USER32) 0xc581: DispatchMessageW + 0x1c1 (USER32) 0x207cb5: QEventDispatcherWin32::processEvents + 0x535 (Qt5Core) 0x4ff88: qt_plugin_query_metadata + 0x1d18 (qwindows) 0x1ba982: QEventLoop::exec + 0x1b2 (Qt5Core) 0x1d22f6: QDialog::exec + 0x166 (Qt5Widgets) 0x3d8e7: dset_dyn_device_dlg + 0x47 (saui_dset) 0x14d2a: QUI_ASSIGNMENT_MENU::device_action + 0x8a (SYS_QUI) 0x1de156: QMetaObject::activate + 0x576 (Qt5Core) 0x8281: QAction::activate + 0x131 (Qt5Widgets) 0x15f9f7: QMenu::actionGeometry + 0x457 (Qt5Widgets) 0x15f865: QMenu::actionGeometry + 0x2c5 (Qt5Widgets) 0x164c78: QMenu::mouseReleaseEvent + 0xb8 (Qt5Widgets) 0x3a66b: QWidget::event + 0xdb (Qt5Widgets) 0x1610fb: QMenu::event + 0x17b (Qt5Widgets) 0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets) 0x1699c: QApplication::notify + 0x8dc (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x1a0d5: QApplicationPrivate::sendMouseEvent + 0x325 (Qt5Widgets) 0x621ef: QSizePolicy::QSizePolicy + 0x266f (Qt5Widgets) 0x6060d: QSizePolicy::QSizePolicy + 0xa8d (Qt5Widgets) 0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets) 0x17c16: QApplication::notify + 0x1b56 (Qt5Widgets) 0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core) 0x4cc00: QGuiApplicationPrivate::processMouseEvent + 0x870 (Qt5Gui) 0x345fa: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui) 0x2084e4: QEventDispatcherWin32::processEvents + 0xd64 (Qt5Core) 0xca65: DispatchMessageW + 0x6a5 (USER32) 0xc581: DispatchMessageW + 0x1c1 (USER32) 0x207cb5: QEventDispatcherWin32::processEvents + 0x535 (Qt5Core) 0x4ff88: qt_plugin_query_metadata + 0x1d18 (qwindows) 0x1ba982: QEventLoop::exec + 0x1b2 (Qt5Core) 0x1bd713: QCoreApplication::exec + 0x143 (Qt5Core) 0x10bb: qgq_main + 0x8b (qpro) 0x13e58: msg_main_thread + 0x18 (CCL_MSG) 0x1516e: msg_thread_wrapper + 0x6e (CCL_MSG) 0x1f900: mem_thread_wrapper + 0x70 (ccl_mem) 0x1348e: msg_exe_main + 0xae (CCL_MSG) 0x20c3: WinMain + 0x153 (qpro) 0x16d2: __scrt_common_main_seh + 0x116 (qpro) End-trace Executable: qpro Comment: None System Information Platform: windows64 OS name: Windows 10 OS version: 10.0 Quartus Prime Information Address bits: 64 Version: 18.1.2 Build: 277 Edition: Pro Edition And here is the report for the same problem caused by scanning a JTAG chain that contains a 64Mbit device: Problem Details Error: *** Fatal Error: Access Violation at 0X00007FFA990A6D39 Module: quartus.exe Stack Trace: 0x86d38: PGME_SFL_ALGORITHM::push_enhanced_sfl_read_siid + 0xc18 (pgm_pgme) 0x8c75d: PGME_SFL_ALGORITHM::read_enhanced_sfl_siid + 0x13d (pgm_pgme) 0x92e85: PGME_SFL_ALGORITHM::read_silicon_id + 0x2b5 (pgm_pgme) 0x8f0f1: PGME_SFL_ALGORITHM::read_jic_silicon_id + 0x141 (pgm_pgme) 0x4fd55: PGME_PROGRAMMER::get_jic_device_name_from_id + 0x95 (pgm_pgme) 0x2f93c: PGMWQ_FRAME_WND::add_child_devices + 0x12c (pgm_pgmwq) 0x318d5: PGMWQ_FRAME_WND::add_device_list + 0x1655 (pgm_pgmwq) 0x8448e: PGMWQ_FRAME_WND::standalone_auto_detect + 0xce (pgm_pgmwq) 0x621e8: PGMWQ_FRAME_WND::on_auto_detect_action + 0xe98 (pgm_pgmwq) 0x15d5f: PGMWQ_FRAME_WND::qt_static_metacall + 0x16f (pgm_pgmwq) 0x11c420: QMetaObject::activate + 0x520 (QtCore4) 0x58c682: QAbstractButton::clicked + 0x32 (QtGui4) 0x343d9e: QAbstractButton::click + 0x51e (QtGui4) 0x343a17: QAbstractButton::click + 0x197 (QtGui4) 0x344899: QAbstractButton::mouseReleaseEvent + 0x59 (QtGui4) 0x60794: QWidget::event + 0xd4 (QtGui4) 0x22e95: QApplicationPrivate::notify_helper + 0xf5 (QtGui4) 0x21a8e: QApplication::notify + 0x71e (QtGui4) 0x10d92b: QCoreApplication::notifyInternal + 0x7b (QtCore4) 0x25cfe: QApplicationPrivate::sendMouseEvent + 0x1de (QtGui4) 0x856f0: QScrollBar::trUtf8 + 0x1440 (QtGui4) 0x890b1: QApplication::winMouseButtonUp + 0x2761 (QtGui4) 0xca65: DispatchMessageW + 0x6a5 (USER32) 0xc581: DispatchMessageW + 0x1c1 (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) 0x17973: BaseThreadInitThunk + 0x13 (KERNEL32) 0x6a270: RtlUserThreadStart + 0x20 (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.0.0 Build: 614 Edition: Standard Edition I have not yet tried version 19.1 It takes a long while to download and install so I will try it next. Regards. Mark

AnandRaj_S_Intel · ‎07-04-2019

Hi Mark,

Thanks for sharing report,

Please share the project If possible, Which will help in replicate the issue.

Regards

Anand

MSchu8 · ‎07-08-2019

Hi Anand, I cannot share my projects. They are proprietary. As for the failure, you can cause it by scanning a JTAG chain that contains a 64Mbit device. You do not have to be running a specific project for this to occur. I had also attached the crash reports. Are they of any help? Regards. Mark

AnandRaj_S_Intel · ‎07-09-2019

Hi Mark,

Please give me some time, i will check with quartus 19.2 pro and update you.

Regards

Anand

AnandRaj_S_Intel · ‎07-10-2019

Hi Mark,

Just created a simple project with Quartus 19.1 pro for Arria 10 soc Development kit having EPCQL1024 flash device.

I was able to scan the jtag chain and program both sof/jic file successfully, Also change or view the Devices and Pins option.

Please try with Quartus 19.1pro.

Regards

Anand

MSchu8 · ‎07-10-2019

Hi Anand, The programmer problem occurs with a 64Mbit device. I am seeing the issue when using EPCS64, EPCQ64 and EPCQ64A. Regards. Mark

AnandRaj_S_Intel · ‎07-11-2019

Hi Mark,

Apologies for the inconvenience caused, Presently we don't have any kit with 64Mbit flash.

Can you make a video of the issue and attach with latest Quartus version.

So that i can transfer case to next level.

Regards

Anand

MSchu8 · ‎07-16-2019

Hi Anand, Video attached. It may possibly be the worst video ever, but I think you can see it well enough. In the video, I have reproduced the failure in both 18.1 Pro and 17.1 Standard. I can recreate this failure in other versions as well. It is very simple to repeat – JTAG scan a chain that contains an EPCS64, EPCQ64 or EPCQ64A and you will see the problem. Regards. Mark

AnandRaj_S_Intel · ‎07-17-2019

Thanks, Mark but I can't find the attachment

Please try with Quartus 19.2Pro.

If you see the problem I can raise a ticket on behalf of you.

Best Regards

Anand

MSchu8 · ‎07-17-2019

Hi Anand, I will try, but this will not solve my problem. I have many computers on the production floor that use the stand alone programmer. We certainly cannot justify licensing a pro version for a 10 - 20 production workstations. I will let you know how 19.2 works. Regards. Mark

AnandRaj_S_Intel · ‎07-18-2019

Sorry for the inconvenience mark,

we don't have any kit with 64Mbit flash to replicate issue, I can raise a ticket on behalf of you only after replicating the issue.

So i want some video that shown the issue with latest Quartus 19.2 pro

Regards

Anand