10.7.2.1.6. Intermittent Issue Evaluation
Errors that occur during run-time indicate a data-related issue, which you can identify by the following actions:
- Add the Signal Tap II logic analyzer and trigger on the post-trigger pnf
- Use a stress pattern of data or transactions, to increase the probability of the issue
- Heat up or cool down the system
- Run the system at a slightly faster frequency
If adding the Signal Tap II logic analyzer or modifying the project causes the issue to go away, the issue is likely to be placement or timing related.
Errors that occur at start-up indicate that the issue is related to calibration, which you can identify by the following actions:
- Modify the design to continually calibrate and reset in a loop until the error is observed
- Where possible, evaluate the calibration margin either from the debug toolkit or system console.
Note: Refer to the External Memory Interface Debug Toolkit chapter in volume 3 of the External Memory Interface Handbook.
- Capture the calibration error stage or error code, and use this information with whatever specifically occurs at that stage of calibration to assist with your debugging of the issue.
Did you find the information on this page useful?