Amega328p-au shorted pins ?

Hi James,

James Zelazny jr wrote:

 

Finally motivated myself into trying Eagle files only to see my original instincts told me NOT to bother.

I get it you are feeling frustrated, the first time I tried to use EAGLE it didn't go so well. I had to sit down and read the manual and tutorials to understand how it works as previously I had spent a lot of time with DxDesigner/PADS and OrCAD, and EAGLE was quite a change from both of these.

James Zelazny jr wrote:

 

The last thing I expected was not finding common components in the library.My first mistake to assume that an Atmega328p-au would be one of the easiest to find.Not so and had to search the ends of the earth to find it and manually place it into the LIBR directory.After a 4 hour search and finally having this IC in my schematic layout

So the issue here is assuming the bundled parts library is useful. As with the "free" parts libraries that are bundled with absolutely all ECAD packages, not just EAGLE, you get what you pay for. If you value your time and the integrity of your designs you'll just create your own libraries. It's actually quite easy once you've done a few parts. There are great tutorials to get you started on Adafruit and Dangerous Prototypes. To start this from scratch and do it properly yourself would have been a fraction of the time you spent searching.

James Zelazny jr wrote:

 

.After a 4 hour search and finally having this IC in my schematic layout I now see "shorts" on several pins of this chip in the BRD window.The worse possible places no less on 3.3v and ground !!

I can probably modify this file but now getting far deeper into a simple project I thought would be straight forward.

Is it a software glitch causing this or a bad library file ?

Anyone know where to find a working Atmega328p-au footprint

See attached screen shot of the issue.

It looks like it's just showing air wires between pins on the same net, not between nets i.e. it's connecting all the GND and separately all the 3.3V but I am a little perplexed why as it doesn't look like you have any nets added on the schematic and dropping in a part with multiple pads on the same pin of the part doesn't show air wires for me until I connect up a net in the schematic. Could you put the lib/sch/brd files up on here so we can take a look at what you have done please?

Best Regards,

Rachael

The screenshot is just me adding the very first component into the work space.I did nothing but add the library file for the Atmega328p-au,started the program and was the very first component selected.I did nothing but check the board view to find these pins already wired.

I spent an entire day downloading as many components for my project as possible and had it just about completed on the second day when I discovered many wires in places that should not have been.So,cleaned the slate and even re-installed Eagle and started over.

This time I wanted to place a component and do little at a time while checking for bogus traces.That is when I finally discovered these connections right off before even starting the project...just merely adding the component and this shows up.

I also would like to note that sometimes the program crashes and will lose my work unless I save each and everything I do.

Frustrated is a mild term at this point.

So basically,I open the program,create a project and the first thing I do is select the Atmega328p-au and put it into the schematic work space.and that is what I am getting.I have done nothing else

Here is the file I used and wonder if it is just a bad file itself ?

https://www.snapeda.com/parts/ATMEGA328P-AU/Atmel/view-part/

Give it a try and see what you get ?

Hi James,

I've downloaded it and what it is doing isn't wrong as such. The VCC and GND pins on that part have their pin type set to PWR. When you place them on the board they try and connect up to identically named power nets from other devices with pins of type PWR. As soon as you connect them up to what you want them to connect to then if they are different they will no longer connect to the other devices. Does that make sense?

I tend to not use the PWR pin type in my devices (although I was experimenting with it recently to make a ULP simpler, I will go for the hard approach now I have seen this but that's a different story) so I haven't had this happen before. It's not a problem as log as you fully connect everything up how you want in the schematic and don't end up with connections you didn't intend because it used device PWR pin names to guess at connections.

Best Regards,

Rachael

What a journey for both you and the project.

Thanks for sharing the ups and downs,

What a journey for both you and the project.

Thanks for sharing the ups and downs,