hi, I am using ALTLVDS megacore for serialization and deserialization. the serializer has tx_out : OUT STD_LOGIC_VECTOR (0 DOWNTO 0) and the deserializer has rx_in : IN STD_LOGIC_VECTOR (0 DOWNTO 0) when i assign the io standar for these pins as LVDS, the pin planner creates tx_out(0)n & rx_in(0)n. when i assign these pins to diffential pain then during fitter i get the below error Error: Found two LVDS low registers instead of one! is am i connecting pins correctly or do i have to add an alt_inbuff_diff & alt_outbuff_diff?

Can you post your current pin assignments either from your QSF or by exporting a TCL from the pin planner? Jake

It's sufficient to assign LVDS IO standard to the logical pin. The location must be the positive pin of a differential pair. The negative pin is also displayed in the Pin Planner tool, but you don't need to assign it anyway. You can even delete the negative pin entry from the Pin Planner list. The handling of negative differential pins isn't actually consistent throughout the different Quartus tools, it seems confusing in part.

pls. find the archived project attached, i tried the methods sugessted...but did not work

quartus 9.1sp1 fitter error Error: Found two LVDS low registers instead of one! Error: Found two LVDS high registers instead of one! for this piece of code generated by megawizad // synopsys translate_off initial dataout_h_reg = 0; // synopsys translate_on always @ ( posedge clock) dataout_h_reg <= ddio_h_reg; // synopsys translate_off initial dataout_l_latch = 0; // synopsys translate_on always @ ( negedge clock) dataout_l_latch <= ddio_l_reg; // synopsys translate_off initial dataout_l_reg = 0; // synopsys translate_on always @ ( posedge clock) dataout_l_reg <= dataout_l_latch; // synopsys translate_off initial ddio_h_reg = 0; // synopsys translate_on always @ ( posedge clock) ddio_h_reg <= datain; // synopsys translate_off initial ddio_l_reg = 0; // synopsys translate_on always @ ( negedge clock) ddio_l_reg <= datain; assign dataout_h = dataout_l_reg, dataout_l = dataout_h_reg; endmodule //RxLVDS_lvds_ddio_in

The problem is, that Quartus doesn't accept this port definitions (1-bit arrays): RxData : in std_logic_vector(0 downto 0); -- IP data transmit TxData : out std_logic_vector(0 downto 0); -- IP data transmit Define the ports as std_logic, use additional wire signals and assign them to the Rx/Tx IP: signal RxData0 : std_logic_vector(0 downto 0); signal TxData0 : std_logic_vector(0 downto 0); ... TxData <= TxData0(0); RxData0(0) <= RxData; Then your code compiles without problems.

Forum Discussion

Altera_Forum

Honored Contributor

16 years ago

ALTLVDS pins io standard

hi,

I am using ALTLVDS megacore for serialization and deserialization.

the serializer has tx_out : OUT STD_LOGIC_VECTOR (0 DOWNTO 0)

and the deserializer has rx_in : IN STD_LOGIC_VECTOR (0 DOWNTO 0)

when i assign the io standar for these pins as LVDS, the pin planner creates tx_out(0)n & rx_in(0)n. when i assign these pins to diffential pain then during fitter i get the below error

Error: Found two LVDS low registers instead of one!

is am i connecting pins correctly or do i have to add an alt_inbuff_diff & alt_outbuff_diff?

11 Replies

Altera_Forum
Honored Contributor
16 years ago
I found the reason, why Quartus doesn't accept your design.

You connected four RxLVDS instances to the same pin. This doesn't work, because Quartus needs to implement the double data rate registers as IO registers. So there can be only one RxLVDS MegaFunction for each pin.

P.S.: You can disable the requirement to use IO-registers by removing the Altera synthesis attributes LVDS_RX_REGISTER=LOW and LVDS_RX_REGISTER=HIGH from RxLVDS_lvds_rx.v, which resides as a copy in the db directory. Then Quartus can use regular LE registers, but the timing will become worse, of course.

Forum Discussion

ALTLVDS pins io standard

11 Replies

Recent Discussions

Can an Application Ignore PCIe flow Control Credits?

LTPI IP - any plan to support OCP LTPI Revision 1.2? (MAX 10)

How to handle tx_st_ready for Cyclone V PCIe

Stratix 10 fPLL is cascade source mode doesn't lock

F-tile 10GE Ethernet Reference Design ISSP Error