Just getting started with LUFA, getting "unable to enumerate" error

168 views
Skip to first unread message

Garratt

unread,
Dec 3, 2009, 8:37:00 PM12/3/09
to LUFA (Formerly MyUSB) Support
Hi,

I just am getting started with the LUFA library, and can't seem to get
the device to enumerate.

Board: BumbleB (at90usb162)
LUFA: 090924
Running Ubuntu 9.04 (64 bit version)

I unpacked LUFA, went to LUFA/Demos/Device/LowLevel/CDC
edited makefile to reflect board, programming style
compiled with make - no errors
programmed via "make program" (I'm using the sp12 wiring)

Then I plug the board in, and I get:
[1526732.116014] usb 7-1: device descriptor read/64, error -71
[1526732.340013] usb 7-1: device descriptor read/64, error -71
[1526732.556019] usb 7-1: new full speed USB device using uhci_hcd and
address 13
[1526732.964021] usb 7-1: device not accepting address 13, error -71
[1526733.076014] usb 7-1: new full speed USB device using uhci_hcd and
address 14
[1526733.484022] usb 7-1: device not accepting address 14, error -71
[1526733.484033] hub 7-0:1.0: unable to enumerate USB device on port 1

Things I believe to be ruled out:
The board:
The original software that came with the board was able to
successfully enumerate, so I think the chip, board setup is probably
OK.
The programming:
I programmed on some other test programs (to blink and such) using
avrdude, with similar commands as LUFA uses, so I'm sure that the
program (at least the .hex part) is getting on correctly

I'm unsure about the eeprom:
the .eep file is only 13 bytes, although make reports that the data
portion should be bigger:
Data: 104 bytes (20.3% Full)
(.data + .bss + .noinit)

Also, I don't think the makefile is set up to program the eeprom.
So far, I have been unable to get avr-objcopy to spit out a eeprom
file bigger than 13 bytes.

So, my question: What is wrong? Why won't this enumerate?
specifically, is the eeprom essential to enumeration, and am I doing
something wrong there? Or am I totally off base?

As you can tell, I've been beating my head against this for a while.
Any help would be appreciated.

Thanks,
Garratt




Dean Camera

unread,
Dec 3, 2009, 9:15:59 PM12/3/09
to LUFA (Formerly MyUSB) Support
Garratt,

That demo is known to work with the BumbleB, so my first guess is that
you have not set the F_CPU value in the makefile correctly. As far as
I can remember, the Bumble-B board uses a 16MHz crystal, while the
makefile is set by default to use 8MHz. Try setting the "F_CPU = "
line in the makfile to 16000000 instead of 8000000 and recompile.

> I'm unsure about the eeprom:
> the .eep file is only 13 bytes, although make reports that the data
> portion should be bigger:
> Data: 104 bytes (20.3% Full)
> (.data + .bss + .noinit)

EEPROM is not the same as the Data segment shown there. In that
output, the "Data" section refers to the static SRAM data usage of the
application, excluding the stack. When EEPROM is used, it will appear
as a seperate EEPROM section in the program size information output.
Most of the LUFA demos do not use the AVR's EEPROM (currently only the
AVRISP Clone project does), so you don't have to worry about it. When
EEPROM is used, the makefile will generate a seperate .EEP file
containing the EEPROM data which you can load into your Bumble-B via
FLIP.

- Dean

Garratt

unread,
Dec 3, 2009, 11:07:47 PM12/3/09
to LUFA (Formerly MyUSB) Support
I currently have the F_CPU at 16000000. (and I just tried 8000000 to
make sure. The result is the same)
I guess I can rule out eeprom issues.

any other suggestions?

thanks
Garratt

Dean Camera

unread,
Dec 4, 2009, 2:53:32 AM12/4/09
to LUFA (Formerly MyUSB) Support
Ok, my next question - did you set the makefile so that the MCU
parameter is changed to AT90USB162?


You are correct in that your board must be fine if the original
application worked, so it must be your build configuration. For the
Bumble-B, you need a MCU of at90usb162, a BOARD of BUMBLEB and a F_CPU/
F_CLOCK of 16000000. Remember to do a "make clean" before rebuilding
to make sure everything gets rebuilt properly from scratch.

Also, try some of the other demos to see if they will enumerate
correctly, to rule out unforseen issues in that demo (which isn't
likely, as it's one of the most tested).

Cheers!
- Dean

Garratt Gallagher

unread,
Dec 4, 2009, 11:01:24 AM12/4/09
to myusb-sup...@googlegroups.com
Ok, I feel dumb now. I did a make clean, and now it works fine.

Thanks for your help!
Garratt
> --
>
> You received this message because you are subscribed to the Google Groups "LUFA (Formerly MyUSB) Support" group.
> To post to this group, send email to myusb-sup...@googlegroups.com.
> To unsubscribe from this group, send email to myusb-support-l...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/myusb-support-list?hl=en.
>
>

Reply all
Reply to author
Forward
0 new messages