facing 12002 error while upgrading qsys design from 13.0 to 22.1 quartus

[SERMASWATHIKA]

Hi Team,

   i have upgrading the qsys design from 13.0 to 22.1 . during upgradation, added ddr3 ip and generated the qsys.

  while synthesizing the design , facing 12002 error. whether do i miss any steps in qsys?

  i am new to qsys design and please help me to resolve this issue? Attached the screenshot of error.

[sstrell]

For such a huge jump in versions, you probably still have old components in the system no longer supported in the newer version and that can't be updated automatically.  If so, you need to delete and then re-add and parameterize the new versions of the components.

[ShengN_Intel]

Hi,

Yes, from 13.0 to 22.1 there'll be much old components which are EOL and need replacement.

Thanks,

Best Regards,

Sheng

[ShengN_Intel]

Hi,

Do you have any further concern or consideration from your side?

Thanks,

Best Regards,

Sheng

[SERMASWATHIKA]

i have removed submodules directory 13.0 version still i am facing this error.

[ShengN_Intel]

Hi,

You may need to remove from Project Navigator in GUI as well. Then replace with a new IP.

Thanks,

Sheng

[SERMASWATHIKA]

when i tried to update  top bdf file i am getting the following error. and quartus tool closed abruptly.

Problem Details
Error:
 

*** Fatal Error: Uncaught C++ Exception

Module: quartus.exe

Stack Trace:

    0x2cf18: RaiseException + 0x68 (KERNELBASE)

     0x4461: _CxxThrowException + 0xc1 (VCRUNTIME140)

     0x6bf5: boost::filesystem::detail::recur_dir_itr_imp::increment + 0xd5 (boost_filesystem-mt-x64)

    0x1306b: boost::filesystem::recursive_directory_iterator::increment + 0x5b (CCL_FIO)

    0x101d5: FIO_FIND::add_subdirs + 0x4d5 (CCL_FIO)

    0x134cf: FIO_FIND::init + 0x3ef (CCL_FIO)

    0xc6ee6: GEDQ_VIEW::symbol_file_exists + 0x1a6 (edt_gedq)

    0xb0d19: GEDQ_UPDATE_SYMBOL_COMMAND::update_symbol_or_block + 0x199 (edt_gedq)

    0xae1d5: GEDQ_UPDATE_SYMBOL_COMMAND::create_update_command + 0x2d5 (edt_gedq)

    0xae434: GEDQ_UPDATE_SYMBOL_COMMAND::execute + 0x24 (edt_gedq)

    0x54ad4: GEDQ_FRAME_WND::execute_command + 0x44 (edt_gedq)

    0xc417a: GEDQ_VIEW::on_update_symbol_action + 0x8a (edt_gedq)

   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)

    0xb4da2: GEDQ_VIEW::contextMenuEvent + 0x2d2 (edt_gedq)

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

    0x1737c: QApplicationPrivate::notify_helper + 0x13c (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)

    0x17343: 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: Standard Edition
 

[ShengN_Intel]

Hi,

Possible to provide that .bdf for testing out?

Thanks,

Sheng

[SERMASWATHIKA]

i tried to add the  bdf file in attachment, bdf format is not supported in attachment. i am migrating the design from cyclone III device to cyclone v gx and ddr2 to ddr3.

So i have removed the ddr2 ip and added the ddr3 ip in qsys system and generated the qsys file without errors.

but in bdf file i could not update the port signal names which are for ddr2.. while updating for that( click the update and symbol block option) i am facing the above quartsu error and project window closed abruptly.

[ShengN_Intel]

Hi,

Since ddr2 ip had been replaced with ddr3 ip, you should see .bsf file being generated when generating ddr3 ip. In bdf, probably need to manually remove the ddr2 and insert the ddr3 block symbol.

Btw you can provide the .bdf file in zip format.

Thanks,

Best Regards,

Sheng

[SERMASWATHIKA]

ok i will try that. i have attached bdf file in this message

[ShengN_Intel]

Hi,

I had done checking the bdf file. In bdf, that's the qsys system .bsf.

When generating qsys system, tick the Create block symbol file (.bsf), should see qsys system bsf being generated.

Thanks,

Best Regards,

Sheng

[SERMASWATHIKA]

i have opted for bsf file option while generating the qsys. But the thing is updated bsf file is not reflecting in bdf file . if we tried update also tool is closing.

Now i have deleted the symbol and added new symbol in bdf file. analysis is going through.

[ShengN_Intel]

Hi,

Yes, have to replace the block symbol (.bsf) in bdf file with a new one since you have changed the ddr2 ip to ddr3 ip.

Simply update the .bsf file wouldn't work.

Thanks,

Sheng

[ShengN_Intel]

Hi,

Do you have any further concern or consideration?

Thanks,

Best Regards,

Sheng