AR# 43537


MIG Spartan-6 MCB - Debugging Calibration Failures


The PHY logic contains state logic for initializing the SDRAM memory after power-up and performs timing training of the read and write data paths to account for system static and dynamic delays. Successful completion of this calibration process is denoted by the assertion of phy_init_done. When phy_init_done does not assert, there are various design aspects that must be analyzed. This section of the MIG Design Assistant focuses on the proper debug process for root causing calibration failures (phy_init_done does not assert).

This Answer Record is contained in a series of MIG hardware debug Answer Records and assumes you are running the MIG Example Design with the Debug Port Enabled. It is best to start at the beginning of this recommended hardware debug flow; see (Xilinx Answer 43520).

NOTE: This Answer Record is part of the Xilinx MIG Solution Center (Xilinx Answer 34243). The Xilinx MIG Solution Center is available to address all questions related to MIG. Whether you are starting a new design with MIG or troubleshooting a problem, use the MIG Solution Center to guide you to the right information.


Calibration often fails due to:
  • Changes to the output MIG UCF/Pin-Out, RTL, Parameters.
  • Board related issues such as improper terminationand not adhering to the Memory Implementation Guidelines specified for the MIG design.
  • Not running SI Simulations using IBIS models.

The first steps in any calibration debug is to:

Once the design and board have been verified, the next step is to determine during which stage, calibration fails.
  • For general information on the different calibration stages, see (Xilinx Answer 43630).
  • For information on determining the calibration stage that caused calib_done to not assert (signifying a calibration failure), see(Xilinx Answer 43557).

Linked Answer Records

Associated Answer Records

AR# 43537
Date 02/05/2013
Status Active
Type General Article
People Also Viewed