Difference between ATmega328, 328P and 328PU

Last post
15 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I got some chips in from Digi-Key, which were giving me the wrong signature byte. Here's what avrdude said about them:

avrdude: Device signature = 0x1e9514 
    avrdude: Expected signature for ATMEGA328P is 1E 95 0F 
    Double check chip, or use -F to override this check. 

I sent a query about this to Digi-key. Their response is confusing me a bit, hoping someone could clarify.

The order was for 4 ATMega328p processors - Digi-key part #ATMEGA328-PU-ND.

The response from Digi-key was

"The ATMEGA328-PU-ND is NOT a ATMEGA328P it's a ATMEGA328 so the signature should NOT
match"

Aside from the fact that what I ordered was a 328p and they seem to be telling me they sent a 328, I can't find a definitive statement of what the difference between -P and -PU is. Clarification would be welcome.

Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Not -P but just P. ATMega328 and ATMEGA328P are almost same chips but manufactured with different tecnological processes. The suffix (-P, -PU etc.) shows just a package related information which is clearly described in RTFM.

Warning: Grumpy Old Chuff. Reading this post may severely damage your mental health.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

328P is not the same as 328-PU. The P in the first case indicates picopower. The P in the second case indicates the package (PDIP). If you wanted the picopower chip in a PDIP package, you should have gotten ATMEGA328P-PU.

Regards,
Steve A.

The Board helps those that help themselves.

Last Edited: Tue. Oct 18, 2011 - 07:21 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think you'll find the differences are just in the silicon and affect the power consumption. In terms for functionality and pin compatibility (and programming) there is no difference.

--greg
Still learning, don't shout at me, educate me.
Starting the fire is easy; the hardest part is learning how to keep the flame!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Koshchi wrote:
328P is not the same as 328-PU. The P in the first case indicates picopower. The P in the second case indicates the package (PDIP). If you wanted the picopower chip in a PDIP package, you should have gotten ATMEGA328P-PU.

So the signature bytes will be different then?

Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
In terms for functionality and pin compatibility (and programming) there is no difference.
Not quite true. There are a couple of differences that could be important when using the picopower functionality. For one, the BOD disable is not available on the non-P part.
Quote:
So the signature bytes will be different then?
Yes, they are different chips.

Regards,
Steve A.

The Board helps those that help themselves.

Last Edited: Tue. Oct 18, 2011 - 07:30 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
There are a couple of differences that could be important when using the picopower functionality.
Granted.
Very, very similar, though not identical, then ;)

--greg
Still learning, don't shout at me, educate me.
Starting the fire is easy; the hardest part is learning how to keep the flame!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I got caught out by this at first, confusing the PU with picopower. IIRC the part of TFM (or datasheet) you need to refer to is Ordering Information. :wink:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Koshchi wrote:
Quote:
So the signature bytes will be different then?
Yes, they are different chips.

Bummer, doesn't look like avrdude supports 328. Guess I'll have to do some reading to add it to my config file.

Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Guess I'll have to do some reading to add it to my config file.
It's trivial. Just copy the existing 328x entry, and paste it after that section, then replace the sig bytes. Done.

--greg
Still learning, don't shout at me, educate me.
Starting the fire is easy; the hardest part is learning how to keep the flame!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Great, easy is good, avrdude sees them now.

Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Greg,

  Sorry could you give me more information as to how I would go about doing this?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

uptime,

  Were you able to get avrdude to work with the 328-pu?  I am fine with power consumption of these chips I just want to be able to program with avrdude.  If you got this to work can you get me detailed information as to how I would go about doing this?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

@avrhick, you do realize that you have asked for information in a thread that is 3 years old.wink

 

The latest versions of Avrdude support the 328-pu.  What version of Avrdude are you using and on what OS?

"Scientists investigate that which already is; engineers create that which has never been" - Albert Einstein               

Last Edited: Tue. Jan 27, 2015 - 08:12 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

@Laryvc,  I did not notice that the thread was that old.  My bad. Perfect first impression right lol. 

 

I am using the avrdude version 5.1 on windows 8.1... I might have to look at updating my avrdude, but until then.

 

I actually found my own answer.  For anyone looking at this post in the future ->

1) Find your avrdud.conf file

2) Make an original copy of .conf file

3) edit original file in Notepad or Notepad++

-> Find Atmega328P configuration and copy it below... change your id to m328x and change your signature to 0x1e 0x95 0x14. 

 

Hope this might help someone out in the future if this comes up again.

Last Edited: Tue. Jan 27, 2015 - 09:07 PM