© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Wayne,
You misunderstand the purpose of this post. I didn't come here to have you to do me favor. I took time to submit a legitimate bug report. Instead of addressing the issue you came up with explanations why it is not an issue and not in so many words conveyed the idea that I'm incompetent to distinguish a bug from a bad hardware design. Which caused me to take more time to explain the post that seemed to me pretty self-explanatory in the first place. I might've responded in kind, which I shouldn't have, for which I'm sorry. However nobody likes their time wasted. I did my part in reporting it though. It is entirely up to you to decide if this particular issue needs to be fixed.
Now to the matter at hand. I didn't need you to circumvent the issue for me. I can and have done it myself. As I mentioned before I run into this all the time, thus the reason for posting it.
I created several screen captions for you to show that pads with "unconnected" pads are clearly connected to the power ground pin (which is P3). There is no J2 in my design. If you are referring to P2 then it is just another connector which also has a clear ground path to the GND pin of P3, which I showed on the picture as well.
You mentioned that
> "The problem was that your top plane (GND) copper poor was broken so you had isolated copper areas."
Technically it is not the problem. The problem is that DRC doesn't recognize pads connected through multiple filled zones and vias and it SHOULD. Here is the quintessence of the bug report - the pad has physical copper connection to the net but DRC doesn't detect it.