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

Quartus Prime Standard 23.1 crashes during timing analyzer report

KfirTito
Employee
1,175 Views

Hi ,

 

FPGA model :

Cyclone 10LP ,

10CL120YF780I7G

Quartus Prime Version 23.1std.1 Build 993 05/14/2024 SC Standard Edition (the only version that support my FPGA model).

 

Synthesis flow done without errors,

In timing analyzer , i choose one of the clocks from my design then click on report timing.

the tool crashed and the below message shown: 

 

 

Problem Details
Error:
Internal Error: Sub-system: STA, File: /quartus/tsm/sta/sta_path_entry.cpp, Line: 4000
Reported slack does not match the slack calculated by the requirement: 2167 reported, 1935 expected
Stack Trace:
0x33e412: STA_TIMING_REPORT_ENTRY::expand_and_check_paths(STA_RT_CLOCK_DETAIL_LEVEL, bool, bool) + 0x2852 (tsm_sta)
0x4191ed: STA_REPORT_TIMING::create_rdb_object() + 0x1fd (tsm_sta)
0x3c1b02: STA_REPORT_MGR_IMPL::create_rdb_object(std::string const&, STA_REPORT_FACTORY*, RDB_FOLDER_OBJECT*, bool, bool) + 0x42 (tsm_sta)
0x416d74: STA_REPORT_TIMING::report_to_panel(STA_REPORT_MGR*) + 0xd4 (tsm_sta)
0x3bd581: STA_REPORT_WRITER::generate_report(STA_REPORT_FACTORY*, STA_REPORT_MGR*) + 0x1c1 (tsm_sta)
0x357d66: sta_report_timing + 0x11c6 (tsm_sta)
0x4bb47: TclNRRunCallbacks + 0x67 (tcl8.6)
0x4cf29: TclEvalEx + 0x599 (tcl8.6)
0xf40fe: Tcl_FSEvalFileEx + 0x21e (tcl8.6)
0xf4246: Tcl_EvalFile + 0x26 (tcl8.6)
0x1879f: qexe_evaluate_tcl_script(std::string const&) + 0x388 (comp_qexe)
0x19ecb: qexe_do_tcl(QEXE_FRAMEWORK*, std::string const&, std::string const&, std::list<std::string, std::allocator<std::string> > const&, bool, bool) + 0x7ff (comp_qexe)
0x1da75: qexe_standard_main(QEXE_FRAMEWORK*, QEXE_OPTION_DEFINITION const**, int, char const**) + 0x51d (comp_qexe)
0x1a989: qsta_main(int, char const**) + 0xa9 (quartus_sta)
0x3e5c0: msg_main_thread(void*) + 0x10 (ccl_msg)
0x5cac: thr_final_wrapper + 0xc (ccl_thr)
0x3e68a: msg_thread_wrapper(void* (*)(void*), void*) + 0x6e (ccl_msg)
0xc096: mem_thread_wrapper(void* (*)(void*), void*) + 0x96 (ccl_mem)
0x91a8: err_thread_wrapper(void* (*)(void*), void*) + 0x27 (ccl_err)
0x5cef: thr_thread_wrapper + 0x15 (ccl_thr)
0x4058a: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xa8 (ccl_msg)
0x23ac5: __libc_start_main + 0xf5 (c.so.6)
0xbad9: _start + 0x29 (quartus_sta)

End-trace


Executable: quartus
Comment:
None

System Information
Platform: linux64
OS name: SUSE LINUX
OS version:

Quartus Prime Information
Address bits: 64
Version: 23.1std.1
Build: 993
Edition: Standard Edition

Labels (1)
0 Kudos
3 Replies
RichardTanSY_Altera
916 Views

I could not find this internal error in our database. Could you help to share your design .qar file (Project> Achieve Project) that could duplicate this error?

 

We will need to duplicate the error as without the error duplication from our side, it would be hard to find a workaround/solution.

 

This will requires the engineering team to investigate on this and please keep in mind that any work involving our engineering team may take some time, ranging from a few days to a few weeks, depending on the complexity of the issue.

 

Regards,

Richard Tan


0 Kudos
KfirTito
Employee
880 Views

Unfortunately , 

I cant upload my design to this portal due to intel legal rules. 

I'm asking if i can communicate with intel employee that will help me with my case and he will guide me where 

can i share my design. 

0 Kudos
RichardTanSY_Altera
764 Views

We noticed that we haven't received a response from you regarding the latest previous question/reply/answer, and will now transitioning your inquiry to our community support. We apologize for any inconvenience this may cause and we appreciate your understanding.


If you have any further questions or concerns, please don't hesitate to reach out. Please 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.


Thank you for reaching out to us!


Best Regards,

Richard Tan



0 Kudos
Reply