I finally got a chance to wire up the first of my ATMega32U4 samples (see atmel doc7766). Like all of atmel’s usb chips it comes up as a bootloader. Now we get to go through the list of things that are probably broken (starting with dfu-programmer which I already know from fixing it for the at90usb647 is broken).
- dfu-programmer
- the bootloader itself (as was the case with the 90usb647)
- avr-gcc
- avr-libc
- LUFA (soon to be formarly known as MyUSB)
Let the games begin…
abcminiuser
Donald,
Could you please post the PID of the new bootloader? Atmel haven’t got back to me when I asked for the PID of the new ATMEGA32U4, so the current MyUSB/LUFA DFU bootloader just uses my best guess as to the PID.
Lucky you to get the new device first!
– Dean
feurig
On page 2.
http://www.atmel.com/dyn/resources/prod_documents/doc7618.pdf
I noticed dfu-programmer still doesnt have the correct PID for the 646/647 or the 82 either. I am keeping a more verbose log at http://blog.tempusdictum.com/index.php/don/uncategorized/testing-the-atmel-mega32u4
abcminiuser
Cheers! I had the ancient version of that document that I pulled off my USBKEY last year – figures that they’d update it with new information (and new devices). Fixed for the next LUFA release.
Will keep an eye on your other blog. Don’t forget to report any LUFA bugs you encounter while using it ;).
– Dean
feurig
They keep updating the documentation to reflect what is happening rather than creating a new document or version-ing it. (zb Note the addition of the Mega32U6 which mysteriously slipped into the at90usbXX6/7 Document a few months ago doc7593) Fortunately their naming scheme is so completely arcane that its easier to download the new one than find the old.