ErrType(3): Pin connected to some others pins but no pin to drive it
@ (161.29 mm,33.02 mm): Pin 42 (power_in) of component U7 is not driven (Net 77).
ErrType(3): Pin connected to some others pins but no pin to drive it
@ (154.94 mm,33.02 mm): Pin 46 (power_in) of component U7 is not driven (Net 78).
This generally happens if the U7 component hasn’t defined those pin 42, 46 as power input. But that is not the case here. I got the U7 symbol externally and those pins are defined as power input. What am I missing here?
Hi there, for some reason I can’t view those pictures at all. Looks like it’s trying to show me pictures from my own account or something. Try doing a “private browsing” session and see if you can see them.
As far as the errors are concerned:
This occurs very often. You can only have one Power Out pin per net (otherwise it comes up as an error) so there are very few components that define Power Out, a few regulators is about all. However if you have Power In pins with no Power Out in a net that is also an error as you see. The way to fix this error if you know power is coming from somewhere in that net (e.g. a connector or other “passive” pin) is to place a PWR_FLAG with the power symbols tool. This is a special power symbol that doesn’t have a net name but provides a Power Out pin to “drive” the net. Since it is a DRC thing only I usually leave it off the page somewhere. It helps spot mistakes where you’ve joined multiple voltage rails etc.
Not sure about this one, I’ll have to see the picture. Sometimes if you use net names or global connections and have a typo in the name this is the error you get.
It really depends on what they are. You need to understand the errors to decide if it is safe to ignore them. I do regularly ignore DRC warnings, but only once I’m happy with why they’ve happened. “Input/Output is connected to Tri-State” is common when interfacing with microcontrollers but is fine because the plan is to make the pin input/output with software. As a general rule though getting as few errors and warnings ignored as possible is the best way to work.
Is a classic case of where the power net is interrupted by a passive component. The design rule checker knows that the input should be powered, but because the resistor is in the way (e.g. for the AVDD) it can’t tell that it is powered. You can either attach a PWR_FLAG from the “Place power port” or just ignore these errors as long as you’re sure you got the circuit right.
I’m not sure why this isn’t passing. Is there another global label for DBGMOD and is it correctly connected? Global labels aren’t components and as far as the design rule checker is concerned don’t exist, so if there’s not another one connecting to another component, that’s just a dead-end bit of wire.