Final postfit netlist check failed ; Internal Error: Sub-system: FDRGN

Could you upgrade your project to the latest Quartus Pro version 22.3 and see if the internal error(IE) resolves?

If the IE still occur, please help to share us the project .qar files as we will need to duplicate the error.

Without the error duplication from our side, it would be hard to find a workaround/solution.

Best Regards,

Richard Tan

p/s: If any answer from the community or Intel Support are helpful, please feel free to give best answer or rate 9/10 survey.

Do you able to upgrade your project per my last reply?

Thanks for your reply,

Unfortunately, I can't update my Quartus version because of project traceability.

I'm looking for a solution, and an other error raise :

--- Quote ---

Problem Details
Error:

*** Fatal Error: Access Violation at 0000025664B18940
Module: quartus_fit.exe
Stack Trace:
0x25664b1893f:
0x236d: PLACE_DB::~PLACE_DB + 0x5d (db_place_db)
0xc029: `dynamic atexit destructor for 'PLACE_DB::s_place_db'' + 0x19 (db_place_db)
0x142d5: _execute_onexit_table + 0x155 (ucrtbase)
0x141fa: _execute_onexit_table + 0x7a (ucrtbase)
0x141b3: _execute_onexit_table + 0x33 (ucrtbase)
0xa819: dllmain_crt_process_detach + 0x4d (db_place_db)
0xa90f: dllmain_dispatch + 0xbf (db_place_db)
0x19a1c: RtlActivateActivationContextUnsafeFast + 0x11c (ntdll)
0x5dceb: LdrShutdownProcess + 0x24b (ntdll)
0x5da7c: RtlExitUserProcess + 0xac (ntdll)
0x1e0aa: FatalExit + 0xa (KERNEL32)
0x205bb: exit + 0x1db (ucrtbase)
0x2045e: exit + 0x7e (ucrtbase)
0x508c: err_ie_abort_or_exit + 0x3c (CCL_ERR)
0x45e08: MSG_ERROR_INFO::finalize + 0x248 (CCL_MSG)
0x46879: MSG_INTERNAL_ERROR::report_impl + 0x109 (CCL_MSG)
0x466ed: MSG_INTERNAL_ERROR::report + 0xd (CCL_MSG)
0x47394: `anonymous namespace'::fdrgn_final_check + 0x184 (fitter_fdrgn)
0x40a23: FDRGN_EXPERT::check_and_report + 0x2f3 (fitter_fdrgn)
0x13109: fit2_write_fitter_report + 0x169 (comp_fit2)
0x16442: TclNRRunCallbacks + 0x62 (tcl86)
0x17c4d: TclEvalEx + 0x9ed (tcl86)
0xa6a8b: Tcl_FSEvalFileEx + 0x22b (tcl86)
0xa5136: Tcl_EvalFile + 0x36 (tcl86)
0x1531c: qexe_evaluate_tcl_script + 0x3bc (comp_qexe)
0x14342: qexe_do_tcl + 0x4b2 (comp_qexe)
0x1a84e: qexe_run_tcl_option + 0x5ee (comp_qexe)
0x18ae1: QCU::DETAIL::intialise_qhd_and_run_qexe + 0xa1 (comp_qcu)
0x2a74c: qcu_run_tcl_option + 0x2ec (comp_qcu)
0x1a156: qexe_run + 0x446 (comp_qexe)
0x1b28a: qexe_standard_main + 0x26a (comp_qexe)
0x2052: qfit2_main + 0x82 (quartus_fit)
0x149b8: msg_main_thread + 0x18 (CCL_MSG)
0x16061: msg_thread_wrapper + 0x71 (CCL_MSG)
0x20d90: mem_thread_wrapper + 0x70 (ccl_mem)
0x13f3d: msg_exe_main + 0x20d (CCL_MSG)
0x2918: __scrt_common_main_seh + 0x11c (quartus_fit)
0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)
0x526a0: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: quartus_fit
Comment:
None

System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0

Quartus Prime Information
Address bits: 64
Version: 19.4.0
Build: 64
Edition: Pro Edition

--- End quote ---

Maybe this give an other clue to fix this issue.

Thanks in advace for your help,

I don't see similar error in the database. Could you share your project to duplicate the error?

As it would be hard for us to find a workaround/solution with only error message.

If you are not convenience to share the project in the public, do let me know so I can email the detail on how to share the file through FTP platform.

Best Regards,

Richard Tan

Hi,

Please do understanding that we need the project .qar files to duplicate the Internal Error. We are not able to help you work around this Internal Error without the project files. You may try to simplify the design by remove any confidential code and shares us the design, as long as the design is able to duplicate the IE in the first place.

Best Regards,

Richard Tan

Sorry, I don't get it. What do you mean by "This issue can be solve from your side with this modification"?

If you are not able to share the project, then we can not do anything to help you debug the IE as each design is unique.

Best Regards,

Richard Tan

Ok I understand. Good to know that the error is not a roadblock for you anymore else we might stuck here.

With that, I now transition this thread to community support. If you have a new question, 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.

Best Regards,

Richard Tan

p/s: If any answer from the community or Intel Support are helpful, please feel free to give best answer or rate 9/10 survey.