The New AVRs. Dx and Ex Series Comparison.

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


 

 

I've been trying to get my head around the differences between the various new chip series and have scribbled out a crib sheet. Might be useful to someone else.

 

 

 

 

Updated to include...

OpAmps

MVIO

Adj Threshold Clarify HS Xtal

#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."

Last Edited: Tue. Nov 10, 2020 - 08:59 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I had not really looked at this new series of AVR's, but the EA's look very interesting.

What do the numbers in the ADC row mean?  #of analog channels?

Jim

 

(Possum Lodge oath) Quando omni flunkus, moritati.

"I thought growing old would take longer"

 

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

I'm interested in compiling a list of more subtle differences, i.e. DA has standard CMOS inputs while DB inputs can be individually set the TTL level inputs.

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

ki0bk wrote:
What do the numbers in the ADC row mean?  #of analog channels?

Yes.

#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

Missing MVIO and op-amps.

Xtal needs to include low freq and high freq...

 

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

westfw wrote:

Missing MVIO and op-amps.

 

Will update

 

 

westfw wrote:

Xtal needs to include low freq and high freq...

 

As far as I can see they all have low freq xtals. I was trying to highlight areas where they differ.

#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

As far as I can see they all have low freq xtals. I was trying to highlight areas where they differ.

Fair enough.  Do they all do the "clock auto-tuning" thing?

 

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

westfw wrote:

Do they all do the "clock auto-tuning" thing?

 

They all mention it.

#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

Top post updated to include missing features.

#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

I'm intrigued by all the green "note triangles". Do you intend to make the XLS itself available so one can see the hidden bits?

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

clawson wrote:

I'm intrigued by all the green "note triangles". Do you intend to make the XLS itself available so one can see the hidden bits?

 

I wouldn't get too excited. It's just Excel warning me that what it thinks is a date, eg '10-22' I have formatted as text.

#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

It's just Excel warning me that what it thinks is a date

I get the meme now!  I've only been using libreOffice and Google Sheets, and they're not nearly so bad.

 

 

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

Brian Fairchild wrote:
It's just Excel warning me that what it thinks is a date, eg '10-22' I have formatted as text.

I wish I could find a way to prevent Apple Notes from thinking a set of numbers is NOT a phone number, so Brian I feel you pain!

Jim

 

(Possum Lodge oath) Quando omni flunkus, moritati.

"I thought growing old would take longer"

 

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

Now that we're into the weeds...

 

Does anybody else find it counter-intuitive how the DA/DB datasheets slice up their family?

Lumping chips by memory size rather than pin count and peripheral set doesn't fit my design process.

I know what the inputs and outputs are; And I have a good idea of what peripherals are needed.

I won't know how much flash or RAM I need until the code is done.

I usual develop on a large memory chip then, once the code is mostly baked, sub in a lower-mem, pin-compatible chip on the final BOM.

 

If the datasheets were published with the family sliced by pin-count rather than memory:

The IO Mux table would be simpler.

The vector table would be simpler.

The peripheral address map would be simpler.

Fewer package drawings would be included.

 

Am I daft?

 

 

 

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

If the datasheets were published with the family sliced by pin-count rather than memory

I'm not entirely sure what you mean by "slice."

 

It's hard-core little-endian!  pinCount-family-memory-core.  48-DB-128-AVR; just read backwards, as usual!  :-)

 

Rejoice!  This is pretty much a more informative part numbering scheme than atmel has ever had before!

(I especially applaud putting the family in the middle of the part number, where it won't be confused with the packaging letters.)

 

 

Last Edited: Thu. Nov 12, 2020 - 12:17 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It looks lack of CAN within all Dx series, so sad.......