Please add support for the megaavr architecture

[SpenceKonde]

Any feature request raised here MUST be submitted according to this template or it will be flagged with 'Not enough information'. No action will be taken till all the prerequisite information is provided. If no information is provided for over a month after the 'Not enough information' label is applied, the issue will be closed.

Feature request

Is your feature request related to a problem? Please describe.
I need to add a a large flash chip to a AVR128DB128 microcontroller to release tje standalonr programer that which is in very high demaid

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The modern parts and all future AVR develices will be what arduino calls "megaavr". this plaform

Describe the solution you'd like
Souppty for megavr, which, if works for any one such part will work for all post 2016-revolution AVRs (including nano every and uno wifi rev to official boards.

A clear and concise description of what you want to happen.
I would like to know what is blocking support on these new parts - i would expect thing to work with minimal modifications.

Describe alternatives you've considered
None are suitable. Users are cryng to me for a solution so incessantly that I can't even spare the time to respond to their emails!
A classic AVR does not provide the high performance that users demand in a modern standalone programer. Modern AVRs with the befefit of the half duplex serial and generous memory, as well as their excellent overclocking capably should get standalone programminmg speed to within a few parentage points of the theoretical maximum (twice the speed fo Optiboot ad and six times the speed of microchip NEDBG. I know how to implement UPDI programming (i've done it 3 times). But for standalone, I aloo need a large data storage space. And this librarly looked perfect until i saw megaavr was unsupported :(
Additional context
A clear and concise description of any alternative solutions or features you've considered.
I2C EEPROMs and flash are too small and too slow; I wamt to be able tp stpre df gfasj o,kages. bit ,ovrp SR os Micro SD cards in microcontroller setings are plagued with cionstant problems

So the options are either 1) there will be no standalone UPDI/ISP (supporting both at once would be rtivial - but only if the large storage space issue is solved om tje megaavr platform

Additional context
I am extremely familiar with the modern AVR parts;would reallt likw to get thsi implemented I just don't know how to fix it and hence were tp start. it is my belief that, were I to know what wa wrong, I could efficiently add support for tinyAVR0/1/2. AVR DA. AVR DB. amd AVRDD witj a single set of changes. (if any changes are needed at all other tha modifying library properties. As far as SPI amd I2C stiff gp I sped

DO NOT DELETE OR EDIT anything below this

---

_{Note 1: Make sure to add all the information needed to understand the bug so that someone can help. If any essential information is missing we'll add the 'Needs more information' label and close the issue until there is enough information.}

_{Note 2: For support questions (for example, tutorials on how to use the library), please use the Arduino Forums. This repository's issues are reserved for feature requests and bug reports.}

---