Altera_Forum
Honored Contributor
14 years agoPin uses pseudo-differential output node - can't fit design in device
I have the Stratix IV GX dev board and I'm working trying to build a fairly simple design, but I'm having trouble getting the pin constraints set properly.
I started with the golden_top.qsf that's installed with the dev kit installer and modified the applicable signals for my design. The problem I'm running into is with DDR3 constraints that come straight from the golden_top.qsf file. Here's the first error followed by the constraints:Error: Can't place node "ddr3top_ck_pn" -- node is a differential I/O node set_location_assignment PIN_D24 -to ddr3top_ck_p
set_location_assignment PIN_C24 -to ddr3top_ck_pn
…
set_instance_assignment -name IO_STANDARD "SSTL-15 CLASS I" -to ddr3top_ck_p
set_instance_assignment -name IO_STANDARD "SSTL-15 CLASS I" -to ddr3top_ck_pn
…
set_instance_assignment -name OUTPUT_TERMINATION "SERIES 50 OHM WITH CALIBRATION" -to ddr3top_ck_p
set_instance_assignment -name OUTPUT_TERMINATION "SERIES 50 OHM WITH CALIBRATION" -to ddr3top_ck_pn I tried commenting out the *_pn constraints and let the tool auto-assign them. That cleared up that error, but flagged the same error on the DQS constraints. I tried commenting out the *_pn constraints again, but now I get the following error: Error: Pin ddr3top_dqs_p uses pseudo-differential output node vip_system:U_VIP_System|ddr3_mc_top:the_ddr3_mc_top|ddr3_mc_top_controller_phy:controller_phy_inst|ddr3_mc_top_memphy_top:memphy_top_inst|ddr3_mc_top_memphy:umemphy|ddr3_mc_top_new_io_pads:uio_pads|ddr3_mc_top_altdqdqs:dq_ddio.ubidir_dq_dqs|pseudo_diffa_0. However, these pins also have an I/O standard LVDS that cannot be supported by the pseudo-differential output node. Okay... so while trying to figure that one out, I came across this in the Quartus Help under altiobuf_out Megafunction: Do not use pseudo-differential I/O standards such as differential SSTL or differential HSTL on an output or bidirectional pin with output enable or on-chip termination (OCT) control. The output-enable/OCT logic does not automatically duplicate to the n-pin and your design will not fit. So what's the correct way to constrain these pins? I would have thought the "golden" constraints file supplied with the dev kit would work!