remov_b4_flight
New ContributorJoined 4 months ago
User Profile
New Contributor
User Widgets
Contributions
'*.vho not found' in Modelsim ALTERA
Dear sirs, At QuartusII 13.1 / Stratix3 project, "DDR3 SDRAM Controller with UniPHY" IP on our design. I finished synthesys and run modelsim 10.1d for RTL simulation, After launched modelsim and do jobs in transcript window until 1st prompt. I got error: # vcom -93 -work work {*PATH*/*TO*/*PROJ/*IP_name*.vho} # Model Technology ModelSim ALTERA vcom 10.1d Compiler 2012.11 Nov 2 2012 # ** Error: (vcom-7) Failed to open design unit file "*PATH*/*TO*/*PROJ*/*IP_name*.vho" in read mode. Certainly do not have *.vho (IPFS FILES ?) file. How to generate it and run simulation?1.8KViews0likes6CommentsRe: Fitter failed with "Unknown DQ mode"
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.1.3KViews0likes0CommentsRe: Fitter failed with "Unknown DQ mode"
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 Version1.5KViews0likes0CommentsFitter failed with "Unknown DQ mode"
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 Version1.6KViews0likes6CommentsDDR IP on stratix3
Hi, my project uses stratx3 insides ddr3 controller w/UniPHY, on Fitter lots of 174068 and 174058 errors are appared. Error (174052): I/O "mem_dq[0]" has dynamic termination control connected, but does not use parallel termination that repeats for mem_dq[0] ~ mem_dq[31] mem_dqs[0] ~ mem_dqs[3] mem_dqs_n[0] ~ mem_dqs[3] Error (174068): Output buffer atom "ddr3_ip:U_ddr3_ip|ddr3_ip_0002:ddr3_ip_inst|ddr3_ip_p0:p0|ddr3_ip_p0_memphy:umemphy|ddr3_ip_p0_new_io_pads:uio_pads|ddr3_ip_p0_altdqdqs:dq_ddio[2].ubidir_dq_dqs|altdq_dqs2_ddio_3reg_stratixiii:altdq_dqs2_inst|obuf_os_0" has port "SERIESTERMINATIONCONTROL[0]" connected, but does not use calibrated on-chip termination this repeats for dq_ddio[0] ~ dq_ddio[3] approx. 1100 errors in Fitter process. Is there any way to solve this?Solved697Views0likes2Comments