dni - dni Is dni not supposed to work in quartus pro 22.4? Replies: Re: dni Alex, I’m glad that your problem has been solved, I now transition this thread to community support. If you have a new question, Feel free to open a new thread or login to ‘ https://supporttickets.intel.com ’, view details of the desire request, and post a feed/response within 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 on your follow-up questions. If any answer from the community or Intel Support are helpful, feel free to rank your support experience by rating 4/5 survey. Please let me know of any inconvenience so that I may improve your future service experience. Have a great day! Best regards, Nurina W. Replies: Re: dni Hi Nurina, the RTL analyzer is indeed working in Quartus 23.1 pro, see the attached picture. I will create two other topics for the 2 other points. Replies: Re: dni Alex, It seems like your dni problem has been solved. Can you post a new thread for the new problem you are seeing? Thanks, Nurina Replies: Re: dni Quartus 23.1 pro reports a .qsf error with this line: set_global_assignment -name ANALYZE_LATCHES_AS_SYNCHRONOUS_ELEMENTS ON That line seems ok in Quartus 22.4 pro (Default value is on according the doc). How are the latch being analyzed in Quartus 23.1 pro then (still with the falling edge enable analysis or as combi)? Looks like it cannot analyse anymore as sync, I saw that warning: Warning(335091): The Timing Analyzer found 77 latches that cannot be analyzed as synchronous elements. For more details, run the Check Timing command in the Timing Analyzer to see the list of unsupported latches. Note : We extensively use latch for clock gating (as for the chip) and they are functional, so they cannot be removed. https://www.intel.com/content/www/us/en/docs/programmable/683084/current/analyze-latches-as-synchronous-elements.html Replies: Re: dni A colleague found that the crash was due to a unsupported soft link in the wrapper, I can start the tool now. Replies: Re: dni After deleting the quartus settings (I had to do that many years ago as well): rm -rf ~/.altera.quartus/* Then the Quartus opens the windows to select the license, I enter it but then it crashes. So that does not seems to be license related. Replies: Re: dni It's alright. Just send an update here when you get a response from IT. Regards, Nurina Replies: Re: dni Our IT is still busy with that, I don't know why it takes so long ... Replies: Re: dni Try regenerating and reinstalling the license. This seems to work a lot for similar cases/threads. Regards, Nurina Replies: Re: dni Not yet not yet... Hopefully this week. Replies: Re: dni Alex, Do you have any updates? Is the license issue fixed? Regards, Nurina Replies: Re: dni No, this is a problem with the license installation on one environment. Replies: Re: dni Bad installer maybe? Try reinstalling the Quartus software. In the meantime I'm trying to investigate this problem. Regards, Nurina Replies: Re: dni I still try to see with our IT if they can make it work under one of our environment. FYI, 23.1 runs fine on the other environment on red hat 7. So I don't think red had 7 is the problem. Replies: Re: dni Hello, Do you have any updates? Regards, Nurina Replies: Re: dni Hi Alex, Probably because Red Hat 7 is very old: https://www.redhat.com/en/blog/end-maintenance-red-hat-enterprise-linux-7-almost-here I suggest to use Quartus 21.4 as it is the latest software that supports RHEL 7.7 (is this the same as yours?) If you are using an unsupported OS, you will come across unforeseen problems and you also cannot receive full support from Intel as we cannot reproduce your problems/errors. Regards, Nurina Replies: Re: dni Hi Alex, Check this https://www.macnica.co.jp/business/semiconductor/support/faqs/intel/136797/ probably the root cause for the internal error. Thanks, Best Regards, Sheng Replies: Re: dni Ouch! I asked the IT if they have plan to move to red hat 8 but I'm pretty sure that won't happen any time soon. Why was red hat 7 support dropped? Alex. Replies: Re: dni Hi Alex, I can see that you are using RedHat 7, this is not supported for Quartus 23.1 Pro. It's probably why you are seeing this Internal Error. Please use the supported OS for 23.1 Pro: https://www.intel.com/content/www/us/en/support/programmable/support-resources/design-software/os-support.html Regards, Nurina Replies: Re: dni Hi Nurina, I've got Quartus 23.1.0 pro installed today by our IT, but it crashes at start (GUI does not even open), I asked the IT if they have installed all family devices and especially the Stratix 10 I use, if you have any remark that can help out, let me know: Problem Details Error: Internal Error: Sub-system: DEV, File: /quartus/ddb/dev/dev_family_info_mgr_body.cpp, Line: 3198 Required PDB file(s) not installed. Last choice was /home/xxx/devices/ddb_cumulative_info.ddb Stack Trace: Quartus 0xc5928: DEV_FAMILY_INFO_MGR_BODY::load_data_from_pdb(DEV_FAMILY_ENUM, DEV_FAMILY_INFO_MGR_BODY::DEV_FAMILY_DATA_TYPE, FIO_PATH const*) [clone .cold] + 0xa54 (ddb_dev) Quartus 0x1630d9: DEV_FAMILY_INFO_MGR_BODY::load_family_data(DEV_FAMILY_ENUM) + 0x49 (ddb_dev) Quartus 0x13eed3: DEV_FAMILY_INFO_MGR_BODY::get_desc_of(DEV_FAMILY_ENUM) + 0x33 (ddb_dev) Quartus 0x137449: DEV_FAMILY_MANAGER::test_trait_of(DEV_FAMILY_ENUM, DEV_FAMILY_TRAIT_ENUM) const + 0x39 (ddb_dev) Quartus 0x14c755: DEV_FAMILY_MANAGER::filter_family_list(std::vector<DEV_FAMILY_ENUM, std::allocator<DEV_FAMILY_ENUM> >*, DEV_FAMILY_ENUM, std::vector<DEV_FAMILY_TRAIT_ENUM, std::allocator<DEV_FAMILY_TRAIT_ENUM> >*, bool, bool) const + 0x75 (ddb_dev) Quartus 0x1e451: IPCATALOG_QUARTUS_PROXY::retrieve_quartus_installed_families() + 0xe3 (mega_ipcatalog) Quartus 0x1e4f5: IPCATALOG_QUARTUS_PROXY::get_all_quartus_installed_families() + 0x9 (mega_ipcatalog) Quartus 0x2431f: IPCATVIEWQ_VIEW::setup_device_family_combobox() + 0xb1 (mega_ipcatviewq) Quartus 0x25523: IPCATVIEWQ_VIEW::IPCATVIEWQ_VIEW(QWidget*, IPCATALOG_QUARTUS_PROXY*) + 0xf5d (mega_ipcatviewq) Quartus 0x25962: IPCATVIEWQ_IP_CATALOG_VIEW::IPCATVIEWQ_IP_CATALOG_VIEW(QWidget*, unsigned int) + 0x14 (mega_ipcatviewq) Quartus 0x25b01: IPCATVIEWQ_DOCK_WIDGET::IPCATVIEWQ_DOCK_WIDGET(QWidget*, unsigned int) + 0xc3 (mega_ipcatviewq) Quartus 0x25b94: mega_ipcatviewq_create_dock_widget + 0x26 (mega_ipcatviewq) Quartus 0xf143e: AFCQ_DOCK_MGR::create_dock_widget(AFCQ_DOCK_ENUM, AFCQ_MAIN_WINDOW*) const + 0x468 (gcl_afcq) Quartus 0xb3ff3: QUI_FRAME_WND::create_dock_widget(int, char const*, Qt::DockWidgetArea, bool) + 0xc5 (sys_qui) Quartus 0xba2b0: QUI_FRAME_WND::ip_catalog_action() + 0x12c (sys_qui) Quartus 0x18f46: QGQ_MAIN_WINDOW::QGQ_MAIN_WINDOW(QUI_FRAME_INFO*, QUI_FW_STATE_ENUM, QWidget*, QFlags<Qt::WindowType>, bool) + 0x1a6c (sys_qgq) Quartus 0x1ad63: sys_qgq_create_frame_wnd + 0x36 (sys_qgq) Quartus 0xa4e28: QUI_FRAME_MGR::create_frame_wnd(QUI_FW_STATE_ENUM, QUI_FRAME_INFO*, bool) + 0x4b0 (sys_qui) Quartus 0xa50ed: QUI_FRAME_MGR::create_main(_GUID const&) + 0x2f (sys_qui) Quartus 0x7680a: QUI_APP::init_instance(int, char const**, QUI_CMDLINE*) + 0x512 (sys_qui) Quartus 0x11a05: QGQ_APP::init_instance(int, char const**, QUI_CMDLINE*) + 0x117 (sys_qgq) Quartus 0x113a8: QGQ_APP::init_instance(int, char const**) + 0x12 (sys_qgq) Quartus 0x4042b7: qgq_main(int, char const**) + 0x65 (quartus) Quartus 0x4e5c0: msg_main_thread(void*) + 0x10 (ccl_msg) Quartus 0x50b07: msg_thread_wrapper(void* (*)(void*), void*) + 0x8c (ccl_msg) Quartus 0x1f568: mem_thread_wrapper(void* (*)(void*), void*) + 0x98 (ccl_mem) Quartus 0x10f58: err_thread_wrapper(void* (*)(void*), void*) + 0x1e (ccl_err) Quartus 0xba55: thr_thread_wrapper + 0x15 (ccl_thr) Quartus 0x4f6f4: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xd3 (ccl_msg) Quartus 0x4043a8: main + 0x26 (quartus) System 0x22555: __libc_start_main + 0xf5 (c) Quartus 0x4041a9: _start + 0x29 (quartus) End-trace Executable: quartus Comment: None System Information Platform: linux64 OS name: Red Hat OS version: 7 Quartus Prime Information Address bits: 64 Version: 23.1.0 Build: 115 Edition: Pro Edition Replies: Re: dni Alex, do you have any updates? Regards, Nurina Replies: Re: dni Sure Alex, I'll wait for your update. Regards, Nurina Replies: Re: dni Hello Nurina, I did not use any tcl command, I just opened the RTL viewer and double clicked on my top level on the left side (as the schematic view was empty), then these messages popped-up. We have a Quartus pro license for 2023 , I have asked the IT to install the latest version 23.1, will see if this message is gone. Alex. Replies: Re: dni Alex, May I know how you entered dni mode and which tcl commands you have used? Please provide step by step flow on what you have done. Regards, Nurina Replies: Re: dni Hi Alex, It should work on 22.4 as well. I think you might need the developer license as stated in the error message, let me check with my team and get to you on this shortly. Regards, Nurina Replies: Re: dni Only starting from 23.1 pro?