saving the examined data of Max V failed --- in the Intel Quartus Prime lite 22.1

Tested with

Intel® Quartus® Prime Programmer and Tools

Version 22.1 -> same Failure

Tested wit

Intel® Quartus® Prime Programmer and Tools

Version 17.1.1 saving possible

but after saving

Max V 5M80ZE64C5N examine / Verify Failure

Still saving File Problems ?

see

https://community.intel.com/t5/Programmable-Devices/Max-V-5M80ZE64C5N-examine-Verify-Failure/m-p/1514585/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExMRFY5N01OTVhZQkhPfDE1MTQ1ODV8U1VCU0NSSVBUSU9OU3xoSw#M92089

Hi,

Thank you for contacting Intel community.

Created a Project by wizzard - selected the correct Chip

Open the Programmer - Add device - select chip

check the box for Examine and start

Progress 100% success

From the steps mention above, you mention that you have check the 'examine' box and start. However in the photo, I did not see the examine box has been checked. Is the photo correct?

Can you provide us the .qar file for your design? So we can tested from our end.

Regards,

Aiman

Hi,

I am checking this with our engineering team. I will get back to you for the findings.

Regards,

Aiman

Hi,

This case is different from the KDB link that you have mentioned. The KDB is regarding examining the data from a CFI flash.

However, this case is examining the data from the internal flash of Max V.

Could you provide the stack trace by clicking the "Preview Report..." button on the Quartus Prime Problem Report dialog box?

Is the issue intermittent?

Our engineering team has tested this and they do not get similar issue.

Regards,

Aiman

Hi,

Any update for this case?

Regards,

Aiman

Hi,

Any update for this case?

Regards,

Aiman

Hallo

At the End the Report of 22.1std.2

Saving Failed

Additional Tests :

----------------------------------------------------

Tested with

Intel® Quartus® Prime Programmer and Tools

Version 22.1 -> same Failure

------------------------------------------------------

Tested with

Intel® Quartus® Prime Programmer and Tools

Version 20.4 saving possible

-------------------------------------------------------

Tested with

Intel® Quartus® Prime Programmer and Tools

Version 17.1.1 saving possible

--------------------------------------------------------

but after saving

Max V 5M80ZE64C5N examine / Verify Failure

Still examine or saving File Problems ?

see

https://community.intel.com/t5/Programmable-Devices/Max-V-5M80ZE64C5N-examine-Verify-Failure/m-p/1514585/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExMRFY5N01OTVhZQkhPfDE1MTQ1ODV8U1VCU0NSSVBUSU9OU3xoSw#M92089

-----------------------------------

Report

Problem Details
Error:
Internal Error: Sub-system: AFCQ, File: /quartus/gcl/afcq/afcq_file_dlg.cpp, Line: 378

QFileDialog layout has changed

Stack Trace:

    0x25da6: AFCQ_FILE_DLG::create_checkbox + 0x66 (GCL_AFCQ)

    0x8cfd8: PGMWQ_DEVICE_TREE::save_file + 0x188 (pgm_pgmwq)

    0x8dbc5: PGMWQ_DEVICE_TREE::save_file + 0x145 (pgm_pgmwq)

    0x7a476: PGMWQ_FRAME_WND::on_save_file_action + 0x36 (pgm_pgmwq)

   0x1fb37f: QMimeData::urls + 0x13bf (Qt5Core)

     0x6c96: QAction::activate + 0x136 (Qt5Widgets)

   0x161d17: QMenu::actionGeometry + 0x457 (Qt5Widgets)

   0x161b85: QMenu::actionGeometry + 0x2c5 (Qt5Widgets)

   0x167298: QMenu::mouseReleaseEvent + 0xb8 (Qt5Widgets)

    0x397d5: QWidget::event + 0x145 (Qt5Widgets)

   0x16348b: QMenu::event + 0x17b (Qt5Widgets)

    0x1737c: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x15080: QApplication::notify + 0x7d0 (Qt5Widgets)

   0x1dae38: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)

    0x186e1: QApplicationPrivate::sendMouseEvent + 0x331 (Qt5Widgets)

    0x618cd: QSizePolicy::QSizePolicy + 0x278d (Qt5Widgets)

    0x5fb26: QSizePolicy::QSizePolicy + 0x9e6 (Qt5Widgets)

    0x1737c: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x1531e: QApplication::notify + 0xa6e (Qt5Widgets)

   0x1dae38: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)

    0x5bf63: QGuiApplicationPrivate::processMouseEvent + 0x723 (Qt5Gui)

    0x4726a: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui)

   0x22835d: QEventDispatcherWin32::processEvents + 0xbd (Qt5Core)

    0x5a4e8: qt_plugin_query_metadata + 0x1dc8 (qwindows)

   0x1d6c60: QEventLoop::exec + 0x1a0 (Qt5Core)

   0x1639c7: QMenu::exec + 0x1c7 (Qt5Widgets)

   0x1637ba: QMenu::exec + 0x1a (Qt5Widgets)

    0x39dc4: QWidget::event + 0x734 (Qt5Widgets)

    0xdcb66: QFrame::event + 0x36 (Qt5Widgets)

   0x243ce8: QAbstractItemView::viewportEvent + 0x318 (Qt5Widgets)

    0xba7b8: AFCQ_TREE_VIEW::viewportEvent + 0x2a8 (GCL_AFCQ)

   0x1dd703: QCoreApplicationPrivate::sendThroughObjectEventFilters + 0xe3 (Qt5Core)

    0x17368: QApplicationPrivate::notify_helper + 0x128 (Qt5Widgets)

    0x158b6: QApplication::notify + 0x1006 (Qt5Widgets)

   0x1dae38: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)

    0x62137: QSizePolicy::QSizePolicy + 0x2ff7 (Qt5Widgets)

    0x5fb26: QSizePolicy::QSizePolicy + 0x9e6 (Qt5Widgets)

    0x1737c: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x1531e: QApplication::notify + 0xa6e (Qt5Widgets)

   0x1dae38: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)

    0x5bf63: QGuiApplicationPrivate::processMouseEvent + 0x723 (Qt5Gui)

    0x4726a: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui)

   0x22835d: QEventDispatcherWin32::processEvents + 0xbd (Qt5Core)

    0x5a4e8: qt_plugin_query_metadata + 0x1dc8 (qwindows)

   0x1d6c60: QEventLoop::exec + 0x1a0 (Qt5Core)

   0x1d9b2a: QCoreApplication::exec + 0x14a (Qt5Core)

     0x10bb: qgq_main + 0x8b (quartus)

    0x13538: msg_main_thread + 0x18 (CCL_MSG)

    0x1484e: msg_thread_wrapper + 0x6e (CCL_MSG)

    0x18210: mem_thread_wrapper + 0x70 (ccl_mem)

    0x12cf1: msg_exe_main + 0xa1 (CCL_MSG)

     0x20c6: WinMain + 0x156 (quartus)

     0x16d2: __scrt_common_main_seh + 0x116 (quartus)

    0x17613: BaseThreadInitThunk + 0x13 (KERNEL32)

    0x526b0: 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: 22.1std.2
Build: 922
Edition: Lite Edition

Hi,

While checking, we found that this problem has been fixed starting from Quartus 23.1 standard version.

Hence if you are using Quartus earlier than 23.1, you can used to save the added ips file into the chain, so that it can restore how you added before. In this way, you can still use the previous added ips.

• When programming a device with ISP CLAMP enabled, the Intel® Quartus® Prime Programmer first looks for the .ips. The software only looks for the pin state information in the .pof if the .ips is not found. https://www.intel.com/content/www/us/en/docs/programmable/683786/current/saving-the-ips-file-information-to-the.html

Regards,

Aiman

Hi.,

As you can see from the picture above, MAX V is not supported in Quartus Pro version. You will need to use Quartus standard version for this.

Regards,

Aiman