Fitter failed with "Unknown DQ mode"

[remov_b4_flight]

QuartusII 13.1 Windows 64 bit

In the middle of Compile design, Fitter aborted with these signals, 100%

Internal Error: Sub-system: FSAC, File: /quartus/fitter/fsac/fsac_titan_dqs_legality.cpp, Line: 822

Unknown DQ Mode

Stack Trace:

     0xae38: FSAC_COMPOSITE_IO_MGR::get_block_hierarchy_info + 0x9c28

   0x3653b5: FSAC_TITAN_DQS_MGR::initialize + 0x1e5

     0x3f9f: ftitan_execute + 0x191f

     0x9462: ftitan_execute + 0x6de2

    0x4851d: FITCC_EXPERT::fitter_preparation + 0x20d

    0x4acf7: FITCC_EXPERT::invoke_fitter + 0x417

     0x28ef: ftitan_execute + 0x26f

     0xbab9: fmain_start + 0x7f9

     0x1525: Legacy_fitter_Init + 0x4b5

     0x2618: Legacy_fitter_Init + 0x15a8

     0x2168: Legacy_fitter_Init + 0x10f8

     0xf8a6: TclInvokeStringCommand + 0xc6

    0x112a8: TclEvalObjvInternal + 0x328

    0x121b5: TclEvalEx + 0x8d5

    0x12d48: TclEvalObjEx + 0x2d8

    0x1abbd: Tcl_EvalObjCmd + 0xfd

    0x112a8: TclEvalObjvInternal + 0x328

    0x56917: TclExecuteByteCode + 0xe47

    0xa2376: TclObjInterpProcCore + 0x76

    0x112a8: TclEvalObjvInternal + 0x328

    0x56917: TclExecuteByteCode + 0xe47

    0xa2376: TclObjInterpProcCore + 0x76

    0x112a8: TclEvalObjvInternal + 0x328

    0x121b5: TclEvalEx + 0x8d5

    0x7c117: Tcl_FSEvalFileEx + 0x1d7

    0x7a626: Tcl_EvalFile + 0x36

     0xc1ff: qexe_ipc_progress_bar_name + 0x12bf

    0x11dd6: qexe_get_command_line + 0x1556

    0x150d5: qexe_run_tcl_option + 0x585

    0x1e03d: qcu_run_tcl_option + 0xb8d

    0x156ed: qexe_process_cmdline_arguments + 0x54d

    0x15851: qexe_standard_main + 0xa1

     0xa7f8: msg_exe_fini + 0x58

     0xaf3c: msg_exe_fini + 0x79c

     0x1f14: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194

     0xb8bf: msg_exe_main + 0x8f

    0x1259c: BaseThreadInitThunk + 0x1c

    0x5af77: RtlUserThreadStart + 0x27

End-trace

Quartus II 64-Bit Version 13.1.0 Build 162 10/23/2013 SJ Full Version

[remov_b4_flight]

After mem_dq[*] signals change group from "Memory Interface Data pin" to "DQ Group" ,

Fitter progressed little but another Fitter signaled and failed.

Internal Error: Sub-system: FSAC, File: /quartus/fitter/fsac/fsac_titan_dqs_config_op.cpp, Line: 989

dqs_config_cell != 0

Stack Trace:

   0x375b50: FSAC_TITAN_DQS_MGR::get_dq_pad_list_from_dqs_pad + 0x10480

   0x376002: FSAC_TITAN_DQS_MGR::get_dq_pad_list_from_dqs_pad + 0x10932

     0xa3ef: ftitan_execute + 0x7d6f

    0x4851d: FITCC_EXPERT::fitter_preparation + 0x20d

    0x4acf7: FITCC_EXPERT::invoke_fitter + 0x417

     0x28ef: ftitan_execute + 0x26f

     0xbab9: fmain_start + 0x7f9

     0x1525: Legacy_fitter_Init + 0x4b5

     0x2618: Legacy_fitter_Init + 0x15a8

     0x2168: Legacy_fitter_Init + 0x10f8

     0xf8a6: TclInvokeStringCommand + 0xc6

    0x112a8: TclEvalObjvInternal + 0x328

    0x121b5: TclEvalEx + 0x8d5

    0x12d48: TclEvalObjEx + 0x2d8

    0x1abbd: Tcl_EvalObjCmd + 0xfd

    0x112a8: TclEvalObjvInternal + 0x328

    0x56917: TclExecuteByteCode + 0xe47

    0xa2376: TclObjInterpProcCore + 0x76

    0x112a8: TclEvalObjvInternal + 0x328

    0x56917: TclExecuteByteCode + 0xe47

    0xa2376: TclObjInterpProcCore + 0x76

    0x112a8: TclEvalObjvInternal + 0x328

    0x121b5: TclEvalEx + 0x8d5

    0x7c117: Tcl_FSEvalFileEx + 0x1d7

    0x7a626: Tcl_EvalFile + 0x36

     0xc1ff: qexe_ipc_progress_bar_name + 0x12bf

    0x11dd6: qexe_get_command_line + 0x1556

    0x150d5: qexe_run_tcl_option + 0x585

    0x1e03d: qcu_run_tcl_option + 0xb8d

    0x156ed: qexe_process_cmdline_arguments + 0x54d

    0x15851: qexe_standard_main + 0xa1

     0xa7f8: msg_exe_fini + 0x58

     0xaf3c: msg_exe_fini + 0x79c

     0x1f14: MEM_SEGMENT_INTERNAL::~MEM_SEGMENT_INTERNAL + 0x194

     0xb8bf: msg_exe_main + 0x8f

    0x1259c: BaseThreadInitThunk + 0x1c

    0x5af77: RtlUserThreadStart + 0x27

End-trace

Quartus II 64-Bit Version 13.1.0 Build 162 10/23/2013 SJ Full Version

[RichardTanSY_Altera]

I am not able to find a similar internal error in the database.

May I know which device you are using? Is it possible to upgrade the design to the latest Quartus version that supports your device? There is a chance that the internal error might have been fixed in a later Quartus release.

Quartus® Software Latest Version for Device Support:

https://www.intel.com/content/www/us/en/support/programmable/support-resources/design-software/devices-support.html

If upgrading the design is not possible, please kindly share your design by archiving the project (Project > Archive Project) so that I can attempt to reproduce the error on our side.

FYI: For all cases involving Fatal Errors or Internal Errors, we need a design test case to reproduce the issue. Without being able to duplicate the error on our end, it becomes difficult to identify a workaround or solution.

Regards,

Richard Tan

[remov_b4_flight]

Hi all.

Project uses Stratix III device,13.1 is last version of Stratix III support.

I compared settings in Assignment editor with example project that generated by MegaCore wizard,

I found wrong settings with DQ_GROUP (mem_dqs[*] -> mem_dq).

Thank you.

[RichardTanSY_Altera]

Does replacing the incorrect settings with DQ_GROUP resolve the fatal error?

Regards,

Richard Tan

[RichardTanSY_Altera]

Hi @remov_b4_flight ,

Do I understand correctly that changing the incorrect settings with the DQ_GROUP (mem_dqs[*] -> mem_dq) resolves the fatal error?

Regards,

Richard Tan