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

Opening Signal Tap 2 Causes Fatal Error

AWrithingMassOfFlesh
New Contributor I
‎10-16-2020 01:28 PM
1,919 Views
Solved Jump to solution

Why does this happen to me?

I was using signal tap and suddenly this happened and now it happens every time I try to open signal tap and Quartus crashes. 

This is the error log:

Problem Details
Error:
*** Fatal Error: Access Violation at 0X00007FFBBE7F72D0
Module: quartus.exe
Stack Trace:
    0x172cf: SDR_DATA_INSTANCE::get_dom_node + 0xf (sld_sdr)
    0x74b2e: SEDQ_JTAG_WIDGET::get_jtag_hardware + 0x1e (sld_sedq)
     0x5d03: SLDQ_JTAG_WIDGET::on_update_hardware_combo_timer + 0x53 (sld_sldq)
   0x11d700: QMetaObject::activate + 0x520 (QtCore4)
   0x120c59: QObject::event + 0x69 (QtCore4)
    0x22c55: QApplicationPrivate::notify_helper + 0xf5 (QtGui4)
    0x228ef: QApplication::notify + 0x17bf (QtGui4)
   0x10ec4b: QCoreApplication::notifyInternal + 0x7b (QtCore4)
   0x134cdd: QEventDispatcherWin32::registeredTimers + 0x59d (QtCore4)
   0x1340ff: QEventDispatcherWin32::processEvents + 0xb5f (QtCore4)
    0x17445: DispatchMessageW + 0x6a5 (USER32)
    0x16f61: DispatchMessageW + 0x1c1 (USER32)
   0x133982: QEventDispatcherWin32::processEvents + 0x3e2 (QtCore4)
    0x82004: QApplicationPrivate::openPopup + 0x204 (QtGui4)
   0x10bb7b: QEventLoop::exec + 0x22b (QtCore4)
   0x428520: QDialog::exec + 0xf0 (QtGui4)
    0x9edc7: AFCQ_MSG_DISPLAY::internal_error_display + 0x277 (GCL_AFCQ)
    0x1dc81: MSG_REPORT::internal_error + 0xf1 (CCL_MSG)
    0x38817: MSG_ERROR_INFO::finalize + 0x97 (CCL_MSG)
    0x39234: MSG_INTERNAL_ERROR::report + 0xd4 (CCL_MSG)
    0x10389: SDR_DATA_SESSION::parse + 0x1a99 (sld_sdr)
     0x9871: SDR_DATA_SESSION::SDR_DATA_SESSION + 0x241 (sld_sdr)
     0x8071: SDR_DATA_MANAGER::open_session + 0x61 (sld_sdr)
    0x5ed12: SDR_TX_SESSION::open_session + 0x32 (sld_sdr)
    0xcbd14: SEDQ_TX_MANAGER::open_document + 0x104 (sld_sedq)
    0xcc60b: SEDQ_FRAME_WND::open_file + 0x9b (sld_sedq)
    0x1f23e: QUI_FRAME_MGR::open_file + 0x53e (SYS_QUI)
    0x625f6: QUI_TOOLS_MENU::sedq_action + 0x1b6 (SYS_QUI)
   0x11d700: QMetaObject::activate + 0x520 (QtCore4)
     0xa09f: QAction::activate + 0xdf (QtGui4)
   0x3ba703: QMenu::actionGeometry + 0x443 (QtGui4)
   0x3ba595: QMenu::actionGeometry + 0x2d5 (QtGui4)
    0x61b84: QWidget::event + 0xd4 (QtGui4)
   0x3bb444: QMenu::event + 0x284 (QtGui4)
    0x22c55: QApplicationPrivate::notify_helper + 0xf5 (QtGui4)
    0x2184e: QApplication::notify + 0x71e (QtGui4)
   0x10ec4b: QCoreApplication::notifyInternal + 0x7b (QtCore4)
    0x25a9e: QApplicationPrivate::sendMouseEvent + 0x1de (QtGui4)
    0x865b6: QScrollBar::trUtf8 + 0x10b6 (QtGui4)
    0x8a301: QApplication::winMouseButtonUp + 0x2761 (QtGui4)
    0x17445: DispatchMessageW + 0x6a5 (USER32)
    0x16f61: DispatchMessageW + 0x1c1 (USER32)
   0x133982: QEventDispatcherWin32::processEvents + 0x3e2 (QtCore4)
    0x82004: QApplicationPrivate::openPopup + 0x204 (QtGui4)
   0x10bb7b: QEventLoop::exec + 0x22b (QtCore4)
   0x10e18f: QCoreApplication::exec + 0xdf (QtCore4)
     0x198b: qgq_main + 0x8b (quartus)
    0x133a8: msg_main_thread + 0x18 (CCL_MSG)
    0x14bae: msg_thread_wrapper + 0x6e (CCL_MSG)
    0x16af0: mem_thread_wrapper + 0x70 (ccl_mem)
    0x12c41: msg_exe_main + 0xa1 (CCL_MSG)
     0x2777: WinMain + 0x127 (quartus)
     0x1f40: __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: 19.1.0
Build: 670
Edition: Lite Edition

 

 

 

 

Also when I try to recompile I get this

Problem Details
Error:
Internal Error: Sub-system: SDR, File: /quartus/sld/sdr/sdr_data_session.cpp, Line: 2105
Unexpected FIO_FILE_SYSTEM::status() return
Stack Trace:
    0x10389: SDR_DATA_SESSION::parse + 0x1a99 (sld_sdr)
     0x9871: SDR_DATA_SESSION::SDR_DATA_SESSION + 0x241 (sld_sdr)
     0x8071: SDR_DATA_MANAGER::open_session + 0x61 (sld_sdr)
    0x1f896: ICE_CONTROL_GUI::setup_assignment + 0x356 (sld_ice)
    0x2a54a: QUI_FRAME_WND::flow_starting_setup + 0xca (SYS_QUI)
    0x128f1: QUI_APP::start_flow + 0x51 (SYS_QUI)
    0x4e622: QUI_PROCESSING_MENU::start_compile_action + 0x62 (SYS_QUI)
   0x11d700: QMetaObject::activate + 0x520 (QtCore4)
     0xa09f: QAction::activate + 0xdf (QtGui4)
   0x3485b5: QAbstractButton::click + 0x135 (QtGui4)
   0x349499: QAbstractButton::mouseReleaseEvent + 0x59 (QtGui4)
   0x3f4e7e: QToolButton::mouseReleaseEvent + 0xe (QtGui4)
    0x61b84: QWidget::event + 0xd4 (QtGui4)
    0x22c55: QApplicationPrivate::notify_helper + 0xf5 (QtGui4)
    0x2184e: QApplication::notify + 0x71e (QtGui4)
   0x10ec4b: QCoreApplication::notifyInternal + 0x7b (QtCore4)
    0x25a9e: QApplicationPrivate::sendMouseEvent + 0x1de (QtGui4)
    0x86940: QScrollBar::trUtf8 + 0x1440 (QtGui4)
    0x8a301: QApplication::winMouseButtonUp + 0x2761 (QtGui4)
    0x17445: DispatchMessageW + 0x6a5 (USER32)
    0x16f61: DispatchMessageW + 0x1c1 (USER32)
   0x133982: QEventDispatcherWin32::processEvents + 0x3e2 (QtCore4)
    0x82004: QApplicationPrivate::openPopup + 0x204 (QtGui4)
   0x10bb7b: QEventLoop::exec + 0x22b (QtCore4)
   0x10e18f: QCoreApplication::exec + 0xdf (QtCore4)
     0x198b: qgq_main + 0x8b (quartus)
    0x133a8: msg_main_thread + 0x18 (CCL_MSG)
    0x14bae: msg_thread_wrapper + 0x6e (CCL_MSG)
    0x16af0: mem_thread_wrapper + 0x70 (ccl_mem)
    0x12c41: msg_exe_main + 0xa1 (CCL_MSG)
     0x2777: WinMain + 0x127 (quartus)
     0x1f40: __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: 19.1.0
Build: 670
Edition: Lite Edition

 

Not sure what to do since this makes Quartus unusable

0 Kudos
1 Solution
AWrithingMassOfFlesh
New Contributor I
‎11-02-2020 07:36 AM
1,867 Views
Solved Jump to solution

I deleted all the .stp files in the project and that fixed it 

View solution in original post

Copy link

Link Copied

6 Replies
sstrell
Honored Contributor III
‎10-18-2020 07:15 PM
1,907 Views
Solved Jump to solution

Trash the db and incremental_db folders and try to compile again.  Something probably got corrupted in the compilation database.

0 Kudos
Copy link
Kenny_Tan
Moderator
‎10-18-2020 09:35 PM
1,903 Views
Solved Jump to solution

Besides this, try to reduce some signal to be monitor.


0 Kudos
Copy link
Kenny_Tan
Moderator
‎10-25-2020 07:20 PM
1,889 Views
Solved Jump to solution

any update?


0 Kudos
Copy link
Kenny_Tan
Moderator
‎11-01-2020 05:48 PM
1,872 Views
Solved Jump to solution

We do not receive any response from you to the previous question that we have provided. Please post a response in 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 with your follow-up questions. 


0 Kudos
Copy link
AWrithingMassOfFlesh
New Contributor I
‎11-02-2020 07:36 AM
1,868 Views
Solved Jump to solution

I deleted all the .stp files in the project and that fixed it 

Copy link
Kris
Novice
‎09-24-2021 07:45 AM
1,693 Views
Solved Jump to solution
In response to AWrithingMassOfFlesh

thank you, this problem was causing me grief with removing and readding platform designer files and attempting to recompile

In response to AWrithingMassOfFlesh
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.