Problems flashing with dfu-programmer

[shazzner]

I picked up a Micropendous-32u2, and compiled dfu-programmer.
Following this guide on Ubuntu 10.10:
http://code.google.com/p/micropendous/wiki/ProgramAndTestLinux

Only when I got to 'make dfu' dfu reports 'No device present'. I
assume this is because I'm not properly entering the bootloader mode.
As far as I know, there is no visual confirmation that you're in
bootloader mode, but dmesg is reporting a disconnect everytime I hit
reset so that's at least working. Is there some sort of 'trick' to
enter bootloader mode?

My makefile is set correctly, and I see Atmel as a device using lsusb.
Any ideas? Thanks!

[Chris Hardee]

I actually figured out the answer to the problem soon after I posted this. I need to set the udev rule:

http://dorkbotpdx.org/blog/feurig/98_all_your_atmel_belong_to_us

I can get by with sudo dfu-programmer atmega32u2 ...

Might be good to update the wiki to note this.

[Opendous Inc.]

If you see an Atmel device when running lsusb (03eb:2ff?) that means
the board is connected in DFU mode. The most likely problem is that
the makefile is not set to MCU=atmega32u2 or that you have not enabled
permissions with a .rules file:
http://code.google.com/p/micropendous/wiki/SettingUpUbuntu904Linux

Try running dfu-programmer directly with sudo and see what happens:

sudo dfu-programmer atmega32u2 erase
sudo dfu-programmer atmega32u2 flash YourFirmwareName.hex
sudo dfu-programmer atmega32u2 reset

If the above work then you can either run sudo make dfu each time
you program your device or you can add your device to a .rules file:
http://code.google.com/p/micropendous/wiki/SettingUpUbuntu904Linux

One other possibility is that the picture in the instructions is for
an AT90USB128-based board on which the buttons are in the reverse
order to the Micropendous-32U2. Make sure you press HWB and RESET,
then release HWB, then RESET.

If you are still having problems please post the relevant lsusb and
dmesg text.