Forum Discussion

bitstreamer's avatar
bitstreamer
Icon for Occasional Contributor rankOccasional Contributor
4 years ago

PreSICE Avalon calibration

In the user guide ug_arria10_xcvr_phy, section 7.5 there is a recalibration example. Does this work for PLLs that are not connected to transceivers, or is being connected to a transceiver a requirement for PreSICE?

The PLL does not assert lock on an eval board, but does lock when connected to a transceiver. When not connected to a transceiver, the pll_powerdown pin is controlled via a register.

When I complete step 3, writing a one to enable calibration - the register clears on write. Is this supposed to happen?

5 Replies

  • Deshi_Intel's avatar
    Deshi_Intel
    Icon for Regular Contributor rankRegular Contributor

    Hi,


    Pls see my comment below.


    1. Does this work for PLLs that are not connected to transceivers, or is being connected to a transceiver a requirement for PreSICE?
    • It still works on PLL that doesn't connect to transceiver which I presume you are referring to fPLL here.
    1. The PLL does not assert lock on an eval board, but does lock when connected to a transceiver. When not connected to a transceiver, the pll_powerdown pin is controlled via a register.
    • I am not sure about your design on your board but byright PLL lock has no dependency on the connected transceiver channel.
      • The factor that I can think of that may affect PLL lock are PLL refclk and PLL reset
    1. When I complete step 3, writing a one to enable calibration - the register clears on write. Is this supposed to happen?


    Thanks.


    Regards,

    dlim


    • bitstreamer's avatar
      bitstreamer
      Icon for Occasional Contributor rankOccasional Contributor

      1. Not fPLL - ATX.

      2. Good to know - but it's definitely not working with those two dependencies. Eval board from Intel.

      It just doesn't lock. Any suggestions?

  • Deshi_Intel's avatar
    Deshi_Intel
    Icon for Regular Contributor rankRegular Contributor

    HI,


    Now this is interesting,


    My understanding is ATX PLL is meant to connect to transceiver channel only, not for other usage purpose.

    • ATX PLL should be connected to transceiver PHY IP like NativePHY IP and also transceiver PHY reset controller
    • Sometime we may use ATX PLL to clock protocol IP like Ethernet IP as example but fundamentally it's used to clock the transceiver channel in the protocol IP.
    • The ATX PLL loose lock could be due to your design clocking connection is not correct or IP setting is mismatch with your board hardware setup
      • For instance on ATX PLL -> pll_powerdown
        • Resets the PLL when asserted high. Needs to be connected to a dynamically controlled signal (the Transceiver PHY Reset Controller pll_powerdown output if using this Intel FPGA IP).
        • This is the exact design connection as per user guide doc that user need to follow for it to work properly


    If your intention is to clock something else like custom design logic in FPGA core then I suggest to use either fPLL or IOPLL


    You can refer to below link for general debug guideline on PLL loose lock issue


    Thanks.


    Regards,

    dlim


    • bitstreamer's avatar
      bitstreamer
      Icon for Occasional Contributor rankOccasional Contributor

      Just debugging the ATX for a transceiver application.

      Yes, working within powerdown to reconfigure - trying to achieve lock - I am assuming lock will assert while in powerdown - but I don't see a spec for it. I also don't see timing requirements for the minimum amount of time needed from the lock assertion to when the transceivers resets should be de-asserted. I was thinking 10 microseconds to be safe.

      Thank you for the link. Look forward to your thoughts.