Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
November 7, 2017
Fault Tree Analysis (FTA) uses tree structures to decompose system level failures into combinations of lower-level events, and Boolean gates to model their interactions. The objective of the PCIe link training FTA is to provide the techniques required to troubleshoot the PCIe link training issue with Arria 10 device and resolve it effectively.
Some of the common PCIe link training issues are:
i) LTSSM failed to reach/stay stably at L0.
ii) Link failed to negotiate to expected speed.
iii) Link failed to negotiate to the expected width.
This FTA consists of five different tabs:
Tab 1 - First level debug:
First level debug steps which lead you to the correct hypothesis/debug steps in FTA_Table_View tab or FTA_Diagram_View tab.
First level debug
Tab 2 - FTA_Table_View:
The comprehensive debug steps in table form to debug the Arria 10 PCIe link up issue.
FTA_Table_View
Tab 3 - FTA_Diagram_View:
The comprehensive debug steps in Diagram form to debug the Arria 10 PCIe link up issue.
FTA_Diagram_View
Tab 4 - HIP_PIPE_Interface_Signals:
Procedure to monitor PCIe PIPE interface signals in HIP
6/62/Tab4.png ( Tab4.png - click here to view image )
HIP_PIPE_Interface_Signals
Tab 5 - Diagram:
Examples/diagram of the debug steps stated in FTA_Table_View
Diagram
© [2013] Altera Corporation. The material in this wiki page or document is provided AS-IS and is not supported by Altera Corporation. Use the material in this document at your own risk; it might be, for example, objectionable, misleading or inaccurate.
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.