atmega168PA-AU vs atmega168-20AU

Go To Last Post
13 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

I have a hex file the call out is for a atmega168PA-AU supplier shipped me atmega168-20AU?

Will I have any issues?

 

 

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

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


Contract_Pilot wrote:

I have a hex file the call out is for a atmega168PA-AU supplier shipped me atmega168-20AU?

 

The only difference is that that the PA- part is lower power.

 

 

Only you know if that is important.

#1 Hardware Problem? https://www.avrfreaks.net/forum/...

#2 Hardware Problem? Read AVR042.

#3 All grounds are not created equal

#4 Have you proved your chip is running at xxMHz?

#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."

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

The Signature will be different.

The "Sleep" current will be different.

 

If the hex file does not use any of the PA "PicoPower" features you will be ok.

 

What does the hex file do?

Can you ask the Author?

 

If you have a link to the source code,   a reader might check to see whether "PicoPower" is relevant.

There is a Migration document: AVR515: Migrating from ATmega48/88/168 and ATmega48P/88P/168P/328P to ATtiny48/88

 

There is little functional difference between 328P and (later released) 328

But 168 was first.  And (later released) 168P added extra hardware features.

 

David.

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

VCC on circuit is 3.3V.

No no access to the source code sent e-mail to author.

 

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

david.prentice wrote:

But 168 was first.  And (later released) 168P added extra hardware features.

 

I'm not sure it did. I can see nothing on the feature list of note.

 

 

#1 Hardware Problem? https://www.avrfreaks.net/forum/...

#2 Hardware Problem? Read AVR042.

#3 All grounds are not created equal

#4 Have you proved your chip is running at xxMHz?

#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."

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

david.prentice wrote:
The Signature will be different.
You sure? I seem to remember that a lot of the "A" parts, as long as they retained the exact functionality and were simply a die shrink to a new fab process kept the same signature - all that differed was power consumption and noise immunity as I recall.

 

EDIT: looking at the transition app note linked in #2 it does not mention a signature change. That should give some hope of total binary compatibility I believe.

 

(but you are surely right, 168P added "picopower" over previous 168 - I thought that meant new stuff like sleeping BOD?)

Last Edited: Tue. May 4, 2021 - 08:23 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Contract_Pilot wrote:
no access to the source code

what is it with all these "no source" hex files: https://www.avrfreaks.net/forum/have-hex-file-unknown-avr-chip-can-we-find-chip-form-hex-code ?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil this is a different project. 

Was given a schematic, and hex code for the avr.

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

Brian Fairchild wrote:

david.prentice wrote:

But 168 was first.  And (later released) 168P added extra hardware features.

 

I'm not sure it did. I can see nothing on the feature list of note.

 

And nothing is mentioned in the Microchip database (CSV file attached)...

 

 

Attachment(s): 

#1 Hardware Problem? https://www.avrfreaks.net/forum/...

#2 Hardware Problem? Read AVR042.

#3 All grounds are not created equal

#4 Have you proved your chip is running at xxMHz?

#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."

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

Contract_Pilot wrote:

Was given a schematic, and hex code for the avr.

 

Does the unit require low power operation from a small battery? No? Then you'll be fine.

#1 Hardware Problem? https://www.avrfreaks.net/forum/...

#2 Hardware Problem? Read AVR042.

#3 All grounds are not created equal

#4 Have you proved your chip is running at xxMHz?

#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."

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

AVR512: Migration from ATmega48/88/168 to ATmega48P/88P/168P mentions:

3 Register and bit names
Between ATmega48/88/168 and ATmega48P/88P/168P some register bits has been
added, but none of the existing bits has been removed, nor moved to different
locations.

It does not say which bits are added.  

4 Low-frequency Crystal / Timer/Counter Oscillator

might be important.

 

AVR515: Migrating from ATmega48/88/168 and ATmega48P/88P/168P/328P to ATtiny48/88 mentions the different Signatures.

 

There is nothing sinister in "just having the HEX file".    And I bet that it will work just fine.     Remember to set the Programmer for the correct ATmega168 chip.

If the public project is well proven you don't need the source code.    The user just needs HEX and list of components.

 

David.

 

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

Author said does not use Picopower and should be ok using the -20AU.
 

Awaiting on another OLED think I have a bad one.

But reading and learning a little.

 

Last Edited: Wed. May 5, 2021 - 02:52 AM