Stefan Rueger

OK, I am now using `Microchip.AVR-Dx_DFP.2.3.272.atpack` and `Microchip.AVR-Ex_DFP.2.2.56.atpack` and copy their `specs-*` files into my own directory `device-specs-dx` then I do the following in bash ``` touch pre.c # empty...

And that leaves the business of distinguishing xmega devices from Dx/Ex in the C pre-processor. There are plenty of macros/register names etc that will differ. There are even some differences...

Not two USARTs at the same time: I am not even sure how the bootloader would know which USART to listen to after reset. Poll both RX lines and then...

I think I understand what the idea is and how it's implemented. I wonder whether a similar thing can be achieved outside the bootloader and for applications > flash/2. Say...

Good point about the interrupts for the OTA comms. I had not thought about that. But you have! So, my suggestion is to farm off some interrupt routines and other...

Thanks for the PR. > this fixed the problem I have no doubt it did, but what makes us sure that the change doesn't introduce a problem when programming other...

> all the output pins to 0 without regard for any inversions in the programmer configuration Does the current PR address this? The AVRDUDE project prefers PR code to be...

I just checked: The AT89S51/2 have active *high* reset. So, that's a marked difference to all the other AVRs.

> contribute [...] for everyone's benefit rather than keeping it all to myself. I would welcome any feedback. Thanks. Yes, this is great, and we welcome PRs. In absence of...

Seeing that there is no progress in this PR (both testing other parts and making the change a command line option) I am closing it for now. Can be reopened...