Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

lvds with max10 eval board

Altera_Forum
Honored Contributor II
1,343 Views

I am trying to interface ADC (LTC2264) to max10 via LVDS interface. The ADC provides clock, frame and serial data, all as LVDS signals. I need just to interface LVDS to max10, then sample the data; no PLL necessary 

When I define a single pair as LVDS (e.g. DIFFIO_R14P_CLK2P/N) in the assignment editor, the compilation stops with message "Sorry The QuartusII software quit unexpectedly"; the last message 

"Warning (171167): Found invalid Fitter assignments. See the Ignored Assignments panel in the Fitter Compilation Report for more information". Because of the compilation crash there is no Ignored Assignments panel in the report. Details of the crash are shown below. 

 

Before the LVDS definition of the pair the project compiles and works correctly. 

 

Any help is greatly appreciated. 

 

Thank you, 

Vitaly 

 

problem details 

Error: 

Internal Error: Sub-system: FIOMGR, File: /quartus/fitter/fiomgr/fiomgr_io_bank.cpp, Line: 4427  

new_type != DEV_CURRENT_STRENGTH_DEFAULT  

Stack Trace:  

0x38733: FIOMGR_IO_MANAGER::is_lvds_pad_spacing_lab_row_based + 0x21053 (FITTER_FIOMGR)  

0x36335: FIOMGR_IO_MANAGER::is_lvds_pad_spacing_lab_row_based + 0x1ec55 (FITTER_FIOMGR)  

0x150b99: FIOMGR_STRATIXIII_DYNAMICTERMINATIONCONTROL_LEGALITY::operator= + 0x94949 (FITTER_FIOMGR)  

0xa325a: FIOMGR_IO_MANAGER::warnings_check + 0x35a (FITTER_FIOMGR)  

0xc17d: fcuda_execute + 0x2a9d (fitter_fcuda)  

0x512c7: FITCC_EXPERT::fitter_post_cleanup + 0x57 (FITTER_FITCC)  

0x52d26: FITCC_EXPERT::invoke_fitter + 0xc86 (FITTER_FITCC)  

0x98d7: fcuda_execute + 0x1f7 (fitter_fcuda)  

0xe142: fmain_start + 0x8e2 (FITTER_FMAIN)  

 

0x14410: TclInvokeStringCommand + 0xf0 (tcl86)  

0x161e2: TclNRRunCallbacks + 0x62 (tcl86)  

0x17a65: TclEvalEx + 0xa65 (tcl86)  

0xa6f8b: Tcl_FSEvalFileEx + 0x22b (tcl86)  

0xa5646: Tcl_EvalFile + 0x36 (tcl86)  

0x13962: qexe_evaluate_tcl_command + 0x582 (comp_qexe)  

0x12adc: qexe_apply_ini_vars + 0x29ec (comp_qexe)  

0x17c05: qexe_run_tcl_option + 0x575 (comp_qexe)  

0x34b13: qcu_run_tcl_option + 0xb63 (comp_qcu)  

0x1755a: qexe_process_cmdline_arguments + 0x246a (comp_qexe)  

0x18381: qexe_standard_main + 0xc1 (comp_qexe)  

 

0xcad8: msg_initialize_out_of_memory_handler + 0x378 (CCL_MSG)  

0xe20c: msg_set_stack_size + 0x7c (CCL_MSG)  

0x5aa0: mem_gen_get_project_output_directory + 0x64 (ccl_mem)  

0xc721: msg_exe_main + 0xa1 (CCL_MSG)  

 

0x159cc: BaseThreadInitThunk + 0xc (kernel32)  

0x2b980: RtlUserThreadStart + 0x20 (ntdll)  

 

End-trace  

 

Executable: quartus_fit 

Comment: 

None 

system information 

Platform: windows64 

OS name: Windows 7 

OS version: 6.1 

 

quartus ii information 

Address bits: 64 

Version: 14.1.0 

Build: 186 

Edition: Web Edition
0 Kudos
3 Replies
Altera_Forum
Honored Contributor II
435 Views

This is the Quartus II internal error. I think you should file a service request to Altera to report this and ask if there is any workaround. Alternatively, you could also try with the latest Quartus II 15.0 to see if similar error still occur.

0 Kudos
Altera_Forum
Honored Contributor II
435 Views

I tried ver 15.0 and it compiled.  

Thank you!
0 Kudos
Altera_Forum
Honored Contributor II
435 Views

You are welcome. Glad that the 15.0 works for you.

0 Kudos
Reply