The two level priority interrupt is a step down from the 3 Level interrupt controller in the Xmegas, but is a big step up from a single level controller in the classic AVR Mega and Tiny micros.
Additionally to the CVT [Compact Vector Table] feature, the AVR Dx interrupt controller offers a non-maskable interrupt for critical functions, one selectable high-priority interrupt, and an optional round robin scheduling scheme for normal priority interrupts.
The AVR DA datasheet says that VDD and AVDD are internally connected. What's the point of L200 on AVDD on the AVR128DA48 CURIOSITY NANO if they are not going to do the same on VDD? Is this just cargo cult PCB design? Or does it really serve a purpose?
Posted by ron_sutherland: Sat. Nov 14, 2020 - 10:44 PM
1
2
3
4
5
Total votes: 0
Maybe the AVDD domain is diode connected to the VDD domain. Consider the MVIO domain on the DB series; it is new to me, so I am mostly clueless, but the AVDD domain would probably need some changes to work like that. I don't even know if ADCs can be done like the MVIO stuff, but who knows? If so, I am confident Microchip will get it to us, but as someone will point out, I should not hold my breath.
I appreciate the guesses -- I can guess too -- but I need something a little more definitive.
Does anyone from Microchip ever provide definitive answers to questions like this here? For all its flaws, I can actually count on STMicro to provide useful support on their community forum when needed.
I measure 3.3 ohm resistance between VCC and AVCC in both directions with a multimeter on an AVR128DA28. This is the best I can do for you... this forum is made up mostly of users of AVRs, we didn't design them...
I measure 3.3 ohm resistance between VCC and AVCC in both directions with a multimeter on an AVR128DA28. This is the best I can do for you... this forum is made up mostly of users of AVRs, we didn't design them...
Thank you. That's quite helpful. And a bit disappointing for my use case.
Also wanted to point out that someone else asked where to find the Microchip support forum for AVR chips and was directed here: https://www.microchip.com/forums...
Interesting. I hadn't realized that the MVIO features would work with both VCCio > VCC AND VCCio < VCC, or that they had gone to such lengths to monitor and detect assorted separate VCCio failures...
Posted by ron_sutherland: Wed. Dec 9, 2020 - 01:23 AM
1
2
3
4
5
Total votes: 0
I am finalizing a board with a DB that will run at 5V and interface to an R-Pi at 3V3 with the MVIO port. A previous setup (324pb) let out some smoke when I did not do the power-up sequence correctly; this MVIO seemed like a natural solution and should allow any power sequence to be valid.
Updated the GitHub repository links. Added the AVR® DA Family Overview, References, and Revision History sections. Added MCC versions for each use case, running on AVR128DA48. Minor editorial corrections.
Updated the GitHub repository links. Added the AVR® DA Family Overview, References, and Revision History sections. Added MCC versions for each use case, running on AVR128DA48. Minor editorial corrections.
Do you see guys any reason Microchip went for Tiny0, Tiny1 series, them Mega0 (Mega1 doesn't get it it seems) and now DA, DB and DD?
I thought Mega0 was the final touch for the famous 8bit AVR... The best you can get it for a 64K address range for an 8bit micro (sort of).
At least they limit the Dx series to 128K flash, which is natural for the architecture.
In the era of small, cheap, low power 32bit micro's I don't know what is the reason of Dx. If you want simple peripherals (let's say the 8bitters have that), put them around a cortex-m0+... Just saying...
In the era of small, cheap, low power 32bit micro's I don't know what is the reason of Dx. If you want simple peripherals (let's say the 8bitters have that), put them around a cortex-m0+... Just saying...
There is still a big market for 8 bit MCUs because they have some advantages. The 32 bit ones, mostly ARM, can't match them on power consumption in many applications. They can sometimes compliment more powerful MCUs as well, e.g. you might have an ARM that has variable interrupt latency so you throw in an 8 bit MCU to handle some particular task.
They just work, they are solid and well understood, and you don't have to rely on buggy libraries. AVR assembler is much nicer than ARM too. I still prefer 8 bit where possible.
Posted by rammon: Sun. Jan 24, 2021 - 08:29 AM(Reply to #231)
1
2
3
4
5
Total votes: 0
5V Cortex mcus:
Atmel SAMC20 and SAMC21 (2% internal OSC)
NXP E-series (1.5% internal OSC)
Nuvoton - well, lots, they seem to have more 5V than 3V (2%)
GD32, HK32 from China, not so common though
I also still prefer 8bitters, even some 8051 based ones. My wonder is why Microchip develops so many AVR variants. For a while I thought Mega0 would be a perfect replacement for some of my older designs (mega8, 88pb, mega644) now I'm not sure. I feel I would go for already an obsolete choice. And I don't prefer Dx series over Mega0 because their internal oscillator spec is just worse - a small step down that can put an entire cpu family off for me.
Posted by Brian Fairchild: Sun. Jan 24, 2021 - 09:04 AM
1
2
3
4
5
Total votes: 0
rammon wrote:
And I don't prefer Dx series over Mega0 because their internal oscillator spec is just worse - a small step down that can put an entire cpu family off for me.
How so? I think that there are four different requirements for uC oscillators...
1) +/-10% for applications when any output event is triggered by an input event. The uC doing nothing timing related
2) Good enough for serial comms, so +/-2%
3) Crystal type accuracy, 20/50ppm or so
4) RTC type accuracy, errors measured in a few seconds a year
Both the Mega0 and Dx series will do the first three, no general purpose uC will ever do 4)
#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."
Posted by ron_sutherland: Sun. Jan 24, 2021 - 06:57 PM
1
2
3
4
5
Total votes: 0
rammon wrote:
I don't prefer Dx series over Mega0 because their internal oscillator spec is just worse
The DB crystal oscillator worse than Mega0??? Maybe you can point out something in the datasheet; I am unsure what you are looking at. The DA does not have a crystal driver, but the DB has one with a very informative description for how to layout the crystal that would probably pass an EMI test. I wonder if people get jailed or fined for designs that fail EMI testing.
I don't prefer Dx series over Mega0 because their internal oscillator spec is just worse
The DB crystal oscillator worse than Mega0??? Maybe you can point out something in the datasheet; I am unsure what you are looking at. The DA does not have a crystal driver, but the DB has one with a very informative description for how to layout the crystal that would probably pass an EMI test. I wonder if people get jailed or fined for designs that fail EMI testing.
"internal oscillator". I don't know how to say that clearer.
#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."
The GitHub repository links are updated. Added the AVR® DA Family Overview, References and Revision History sections. Added MCC versions for each use case running on AVR128DA48. Other minor editorial corrections.
Spence Konde ("Dr Azzy") has put together an impression amount of sort-of user-level documentation the AVR-Dx series chip as part of his implementation of an Arduino Core for them: https://github.com/SpenceKonde/D...
Yes, a lot of this is oriented toward "how do these chips play in an Arduino environment, since many of the peripherals are differemt?", but ... that has a lot of overlap (IMO) with other AVR users as well.
I like these boards, basically just all the I/O on pins and a built in programmer. Of course I liked it more when the debuggers were $30 as well.
Also glad to see they will keep supporting Atmel Studio. Not a fan of MPLAB X and my worry is that one day they try to force everyone onto that, or just stop putting any effort into AS and letting it slowly die.
Thanks, I'll take a look at the Snap. Kinda odd they don't offer a case for a few pennies, in volume it wouldn't cost much. Also you need adaptor cables if you are already using the Atmel standard headers...
you need adaptor cables if you are already using the Atmel standard headers...
Although, to give credit where it is due, it's much easier to make adapter cables for the SNAP or PicKit4 8-pin 0.1inch single-inline connector than it is for the finer-pitch connectors on an Atmel-Ice type board...
you need adaptor cables if you are already using the Atmel standard headers...
Although, to give credit where it is due, it's much easier to make adapter cables for the SNAP or PicKit4 8-pin 0.1inch single-inline connector than it is for the finer-pitch connectors on an Atmel-Ice type board...
That's certainly true, although I standardized on a 0.1" pitch header for prog/debug so only need an off-the-shelf ribbon cable assembly, with optional pogo plug board. Only needing 3 wires to program is very nice.
"Increased Current Consumption May Occur When VDD Drops
The device may experience increased current consumption of approximately 1.5 mA if VDD drops below 2.1V and is held in the range of 1.9-2.1V. This will only occur if VDD is originally at a higher level and then drops down to the mentioned voltage range."
So if you are running from 2 alkaline batteries you are in trouble.
via Dev Tool Deals | Microchip Technology
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopAVR DB :
AN3725 - Buck Converter Design and Feedback Controller Using Core Independent Peripherals
Buck Converter Design and Feedback Controller Using Core Independent Peripherals (web doc)
edit :
Switch Mode Power Supply - YouTube (8m51s)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topin Migration from the megaAVR® to AVR® Dx Microcontroller Families
or AN3731 - Migration from the megaAVR to AVR Dx Microcontroller Families (PDF)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopThe compact vector table is a nice feature for small memory AVRs.
- Log in or register to post comments
TopThe AVR DA datasheet says that VDD and AVDD are internally connected. What's the point of L200 on AVDD on the AVR128DA48 CURIOSITY NANO if they are not going to do the same on VDD? Is this just cargo cult PCB design? Or does it really serve a purpose?
Reference: http://ww1.microchip.com/downloa... , page 29 for schematic.
- Log in or register to post comments
TopAlthough internally connected, there may be some impedance between VDD and AVDD that is not stated.
Providing external isolation between the analog and digital domains may improve the noise on those circuits when using analog signals.
(Or the inductor could just be a cut and paste from earlier designs...)
David
- Log in or register to post comments
TopMaybe the AVDD domain is diode connected to the VDD domain. Consider the MVIO domain on the DB series; it is new to me, so I am mostly clueless, but the AVDD domain would probably need some changes to work like that. I don't even know if ADCs can be done like the MVIO stuff, but who knows? If so, I am confident Microchip will get it to us, but as someone will point out, I should not hold my breath.
my projects: https://github.com/epccs
- Log in or register to post comments
TopI appreciate the guesses -- I can guess too -- but I need something a little more definitive.
Does anyone from Microchip ever provide definitive answers to questions like this here? For all its flaws, I can actually count on STMicro to provide useful support on their community forum when needed.
- Log in or register to post comments
TopI was not under the impression that this was Microchip support? It is more like a group of cranky old people that occasionally talk about AVRs.
https://www.microchip.com/en-us/support
https://microchipsupport.force.com/s/support-resources?tabName=Community
my projects: https://github.com/epccs
- Log in or register to post comments
TopIf you want an answer from Microchip you need to open a support question on their website.
Moderator
- Log in or register to post comments
TopGood to know.
I measure 3.3 ohm resistance between VCC and AVCC in both directions with a multimeter on an AVR128DA28. This is the best I can do for you... this forum is made up mostly of users of AVRs, we didn't design them...
- Log in or register to post comments
TopAtmel (now Microchip) points people here for support. This is how I ended up here looking for infomation on AVR DA parts.
https://community.atmel.com/
There is no support forums on Microchip's site dedicated to AVR chips. It's still very much PIC-land.
- Log in or register to post comments
TopThank you. That's quite helpful. And a bit disappointing for my use case.
- Log in or register to post comments
TopAlso wanted to point out that someone else asked where to find the Microchip support forum for AVR chips and was directed here: https://www.microchip.com/forums...
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopTraining Getting Started with AVR® DB OPAMP, XOSHF and MVIO - Atmel Studio
Training Getting Started with AVR® DB OPAMP, XOSCHF and MVIO - MPLAB®
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopAVR128DA :
Silicon Errata and Data Sheet Clarification
AVR64DA :
Silicon Errata and Data Sheet Clarification
AVR32DA :
Silicon Errata and Data Sheet Clarification
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopUsing the MPLAB® Mindi™ Analog Simulator with the 8-Bit Operational Amplifier Module
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMVIO is digital only
Multi-Voltage I/O (MVIO) on 8-bit Microcontrollers - YouTube (3m54s)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopInteresting. I hadn't realized that the MVIO features would work with both VCCio > VCC AND VCCio < VCC, or that they had gone to such lengths to monitor and detect assorted separate VCCio failures...
- Log in or register to post comments
TopI am finalizing a board with a DB that will run at 5V and interface to an R-Pi at 3V3 with the MVIO port. A previous setup (324pb) let out some smoke when I did not do the power-up sequence correctly; this MVIO seemed like a natural solution and should allow any power sequence to be valid.
my projects: https://github.com/epccs
- Log in or register to post comments
TopWith DB line the MVIO fuse may
defaultbe factory programed to enabledhttps://github.com/SpenceKonde/DxCore/issues/45#issuecomment-742853995
That makes sense to me, but is it true?
my projects: https://github.com/epccs
- Log in or register to post comments
TopAVR DA added :
TB3229 Getting Started with GPIO
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topweb pages for the future AVR DD :
AVR64DD32 - 8-bit Microcontrollers
AVR64DD28 - 8-bit Microcontrollers
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopThose look very nice. I wish they had USB though. Maybe I'm the only one doing USB on 8 bit any more...
- Log in or register to post comments
TopTB3216 Getting Started with USART
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top- Log in or register to post comments
TopDo you see guys any reason Microchip went for Tiny0, Tiny1 series, them Mega0 (Mega1 doesn't get it it seems) and now DA, DB and DD?
I thought Mega0 was the final touch for the famous 8bit AVR... The best you can get it for a 64K address range for an 8bit micro (sort of).
At least they limit the Dx series to 128K flash, which is natural for the architecture.
In the era of small, cheap, low power 32bit micro's I don't know what is the reason of Dx. If you want simple peripherals (let's say the 8bitters have that), put them around a cortex-m0+... Just saying...
- Log in or register to post comments
TopThere is still a big market for 8 bit MCUs because they have some advantages. The 32 bit ones, mostly ARM, can't match them on power consumption in many applications. They can sometimes compliment more powerful MCUs as well, e.g. you might have an ARM that has variable interrupt latency so you throw in an 8 bit MCU to handle some particular task.
They just work, they are solid and well understood, and you don't have to rely on buggy libraries. AVR assembler is much nicer than ARM too. I still prefer 8 bit where possible.
- Log in or register to post comments
TopInstruction Set Summary | AVR® Instruction Set Manual
How to search for Microchip PCNs
New PIC32CX and PIC32CZ? | AVR Freaks
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top5V Cortex mcus:
Atmel SAMC20 and SAMC21 (2% internal OSC)
NXP E-series (1.5% internal OSC)
Nuvoton - well, lots, they seem to have more 5V than 3V (2%)
GD32, HK32 from China, not so common though
I also still prefer 8bitters, even some 8051 based ones. My wonder is why Microchip develops so many AVR variants. For a while I thought Mega0 would be a perfect replacement for some of my older designs (mega8, 88pb, mega644) now I'm not sure. I feel I would go for already an obsolete choice. And I don't prefer Dx series over Mega0 because their internal oscillator spec is just worse - a small step down that can put an entire cpu family off for me.
- Log in or register to post comments
TopHow so? I think that there are four different requirements for uC oscillators...
1) +/-10% for applications when any output event is triggered by an input event. The uC doing nothing timing related
2) Good enough for serial comms, so +/-2%
3) Crystal type accuracy, 20/50ppm or so
4) RTC type accuracy, errors measured in a few seconds a year
Both the Mega0 and Dx series will do the first three, no general purpose uC will ever do 4)
#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."
- Log in or register to post comments
TopAlso a bunch of Cypress parts, including PSOC4 and PSOC5.
- Log in or register to post comments
TopThe DB crystal oscillator worse than Mega0??? Maybe you can point out something in the datasheet; I am unsure what you are looking at. The DA does not have a crystal driver, but the DB has one with a very informative description for how to layout the crystal that would probably pass an EMI test. I wonder if people get jailed or fined for designs that fail EMI testing.
my projects: https://github.com/epccs
- Log in or register to post comments
Top- Log in or register to post comments
TopI'm genuinely interested in how it is not as good as the mega0 series.
#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."
- Log in or register to post comments
TopTB3217 Getting Started with TCA
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopSpence Konde ("Dr Azzy") has put together an impression amount of sort-of user-level documentation the AVR-Dx series chip as part of his implementation of an Arduino Core for them: https://github.com/SpenceKonde/D...
Yes, a lot of this is oriented toward "how do these chips play in an Arduino environment, since many of the peripherals are differemt?", but ... that has a lot of overlap (IMO) with other AVR users as well.
Of particular interest is an interpretation of the substantial errata of the initial chips: https://github.com/SpenceKonde/D...
- Log in or register to post comments
TopFeels like one step forwards two steps back with Microchip. Every time you get something they take something else away.
- Log in or register to post comments
Topon sale this month
Part Number: EV35L43A - AVR128DB48 Curiosity Nano Evaluation kit | Welcome to Microchip Technology | Microchip Technology Inc.
via Dev Tool Deals | Microchip Technology
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopI like these boards, basically just all the I/O on pins and a built in programmer. Of course I liked it more when the debuggers were $30 as well.
Also glad to see they will keep supporting Atmel Studio. Not a fan of MPLAB X and my worry is that one day they try to force everyone onto that, or just stop putting any effort into AS and letting it slowly die.
- Log in or register to post comments
TopWhat are the AVR28DA128 AVR32DA128 AVR48DA128 AVR64DA128 ?? | Page 2 | AVR Freaks (MPLAB X, MPLAB Snap)
Digi-Key's Oh Snap! Enclosure for MPLAB® SNAP Debugger by DigiKey - Thingiverse
AS7.0.2389 Pickit4 and Snap support | AVR Freaks
SNAP with Atmel Studio | AVR Freaks
Getting SNAP to work with AVR on AS7.0.2542 | AVR Freaks
Microchip Studio 7.0.2542 | AVR Freaks
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopThanks, I'll take a look at the Snap. Kinda odd they don't offer a case for a few pennies, in volume it wouldn't cost much. Also you need adaptor cables if you are already using the Atmel standard headers...
- Log in or register to post comments
TopPICkit 4 - Waveshare Wiki
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topmore AVR128DA48
TB3211 - Getting Started with AC (PDF)
Getting Started with Analog Comparator (AC) (web doc)
TB3213 - Getting Started with RTC (PDF)
Getting Started with Real-Time Counter (RTC) (web doc)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopAlthough, to give credit where it is due, it's much easier to make adapter cables for the SNAP or PicKit4 8-pin 0.1inch single-inline connector than it is for the finer-pitch connectors on an Atmel-Ice type board...
- Log in or register to post comments
TopThat's certainly true, although I standardized on a 0.1" pitch header for prog/debug so only need an off-the-shelf ribbon cable assembly, with optional pogo plug board. Only needing 3 wires to program is very nice.
- Log in or register to post comments
TopAVR64DB28/32/48/64 Silicon Errata and Data Sheet Clarifications
AVR32DB28/32/48 Silicon Errata and Data Sheet Clarifications
PDF :
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Increased Current Consumption May Occur When VDD Drops
The device may experience increased current consumption of approximately 1.5 mA if VDD drops below 2.1V and is held in the range of 1.9-2.1V. This will only occur if VDD is originally at a higher level and then drops down to the mentioned voltage range."
So if you are running from 2 alkaline batteries you are in trouble.
- Log in or register to post comments
TopDoes reduce the battery's usable capacity; another workaround is an alternate battery electrochemistry.
l92.pdf (Li/FeS2)
Increased Current Consumption May Occur When VDD Drops | AVR32DB28/32/48 Silicon Errata and Data Sheet Clarifications
Search | Energizer Battery and Charger Technical Information
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopPages