Honored Contributor
Honored ContributorGood post, Brad. (Whoever you are...). I like the Design Assistant to look for potential issues, but if you actually are having hardware failures, I would recommend debugging it like a hardware failure. Analyze the failure state. Run sims. Use SignalTap and/or SignalProbe. Etc. I've seen many users spend a lot of time "trying different things". Occasionally it works. Often it doesn't and you've wasted time. But the worst case scenario is if it randomly starts working, and you attribute it to the change you just tried, but they're not really related. Now your design marginally works, and might fail in the field, with any design change at all, etc.. If you identify the problem, you can be certain of creating the correct solution.
Of course, this depends on the application. If you're trying to get something to work for a university course, that's probably fine. If you're making medical equipment... Good luck.
