New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XMega Bootloader Support #51

Chillance opened this Issue Mar 13, 2015 · 1 comment


None yet
2 participants
Copy link

Chillance commented Mar 13, 2015


I'm wondering what is going on with XMega support with this library. XMega's are better than the regular AVR8s in many ways in my opinion and they aren't exactly new anymore.

I noticed there is a pull request from 2013 for some XMega Bootloader support, but not merged here yet. Any plans of doing that?

Anyway, I would be glad to hear your thoughts on XMega series support with this library and I hope there will be some. Especially the Bootloaders.



This comment has been minimized.

Copy link

abcminiuser commented Nov 8, 2015

Hi Chillance,

Yes, this one's old, I forgot about it. Sorry :(.

The gist is that LUFA is, well, old and not well suited for porting. The XMEGAs, UC3s and now SAM series devices have a wildly different USB controller design, are more capable, and otherwise much better than the geriatric USB AVR8 devices, which are mostly still popular due to the Arduinos. As such, there will never be a good LUFA implementation for them unless I completely started from scratch - so while the current code works on the XMEGAs, it is far from optimal. I strongly recommend migrating to the ASF stack where possible if not using the AVR8s to get better performance.

I've been pondering the XMEGA bootloader support for a long time, but I'm not sure of the legal implications of accepting patches that use third party code (Atmel) which bears a different license and set of restrictions to my own.

@abcminiuser abcminiuser added the question label Nov 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment