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.
July 27, 2016
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 this debug FTA example is to help troubleshoot and identify issue related to Quartus license setup issue and resolve it effectively. User often encounter license setup issue when first time using Quartus software and fail to identify the root cause. This FTA help to summarize the common root causes of this problem.
The FTA example : FTA_quartus_license_setup_issue consists of a FTA diagram and table used to debug and find root cause for the Quartus complaint no license issues. In the FTA diagram, multiple hypothesis are made based on the failure symptom as described. For each of the hypothesis, it can have second level or up to third level suspects. The FTA diagram will then be converted into a table format to proper keep track of the debug progress. In the FTA table, for every suspect listed , it needs to have some action items to be performed to verify it together with some additional category information to be filled in such as Owner, Target completion date, status/Results, Possible Next Step and Priority level.
© [2016] 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 during standard business hours (Monday to Friday 7AM - 5PM PST). 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.