LVDS SERDES RECEIVER

[jerry_anto]

Hello,

I'm trying to use LVDS SERDES intel ip for receiving LVDS signals and I have instantiated my ip from my top-module and i'm getting the below mentioned critical warnings.

I'm using a internal pll for LVDS RX  which is not shown in PLL usage summary after i run fitter.

Kindly help us with a solution.

Critical Warning: The auto-constraining script was not able to detect any instance for lib < LVDS_RX_altera_lvds_core20_191_nwfh5si > core < altera_lvds_core20 >

Critical Warning: Make sure the core < altera_lvds_core20 > is instantiated within another component (wrapper)

Critical Warning: and it's not the top-level for your project

[AqidAyman_Intel]

Hi,

Is there error number for the critical warnings you observed? If yes, can you share it?

[jerry_anto]

Hi, 

There is no error related to this critical warning.

[AqidAyman_Intel]

Hi,

I found a Knowledge Base that may describe issue same as you. You can try out the workaround if applicable. Refer to below link:

https://www.intel.com/content/www/us/en/support/programmable/articles/000083063.html?wapkw=Critical%20Warning%3A%20%22The%22%20auto-constraining%20script%20was%20not%20able%20to%20detect%20any%20instance%20for%20lib

[jerry_anto]

Hi,

In this article ( ID: 000083063 ) it says the following,

The problematic line in the pin_map.tcl file is in the get_p2c_c2p_clock_uncertainty procedure:

set pll_atoms [get_atom_nodes -matching *${instname}|*:arch|*:arch_inst|*:pll_inst|* -type IOPLL]

Resolution

Open the pin_map.tcl file, replace *${instname} with *, and re-compile. The design should compile without the critical warnings.

This issue will be fixed in a future version of the Quartus® II software.

In my project files there no files named pin_map.tcl, is sdc_util.tcl the same as as pin_map.tcl ?

I have another tcl file named *my_prj_name*.pdp_assignments.tcl  which is generated from the interface planner since I have placed all my pins using that legally.

Kindly clarify which is the tcl script that i need to edit the above mentioned workaround to remove my critical warning and place the pll.

[jerry_anto]

Hi, 

Is there any update on this chain ?

Please update.

[AqidAyman_Intel]

Hi,

Apologies for the late reply.

Can you check between both the .tcl file you mentioned, which one has the following line:

set pll_atoms [get_atom_nodes -matching *${instname}|*:arch|*:arch_inst|*:pll_inst|* -type IOPLL]

Then, you can try to change the *${instname} with *, and re-compile to see if it does resolve the critical warnings.