I really wanted to attend a paper titled “Why doesn’t my board work?” presented by John Milks, president of Cadence partner Adiva at CDNLive! held recently in Silicon Valley. My EDA roots are in pcb design, going back to my engineering work at Cadnetix back in the early 1980s, so I’ve got a soft spot for pcb design. But I missed the presentation, so Richard Goering has provided the next best thing to being there with his new blog post about that paper. It provides a lot of detail that you don’t want to miss if you’re involved in pcb design.
For example, Richard’s list of nine pcb design error causes sounds very familiar to me:
- Poorly defined design rules
- Warnings are not seen, or are ignored
- Mismatched revisions
- Checking not available or turned off
- Hiccups in data generation
- Rule set conflicts between software packages
- Mistakes in interconnect design
- Insufficient designer training
- Mistakes in part generation
There are some great graphical illustrations of design errors in the post as well. Check out Richard’s blog post here.