none_such was right, if you take off the plastic guard and mount it sideways you can make it work!
Anyways, I kind of skipped posting my work for an in-between step. Since there seem to be a lot of people having trouble with the Atmel AVR programming, I'll try to give a detailed description of how I went about it . . . .Step One: The Programmer
GHETTO is the word of the day! I didn't feel like dropping yet more cash for an AVR programmer, so I hacked together an el-cheapo unbuffered parallel port programmer. The schematic I used is here
. Cost me $3 for a few resistors and some perfboard from Radio Shack, and chopping up an old printer cable.
Note: Using an unbuffered programmer can damage your comp! Build the buffered one if you're at all unsure of what you're doing!2: The software
This part seems to generate a lot of confusion. I think part of the problem is people are making things overly complicated by using more/different software than they need to!You need
(for Win XP/etc):
. This has pretty much EVERYTHING YOU NEED, and is probably what's used for the examples on the Make pages. Download it and install it and pretty much everything will "just work"!
Get it here: http://winavr.sourceforge.net/
-The wavebubble firmware(duh)
-For my ghetto programmer, I also needed the GiveIO system file, to let avrdude use the parallel port directly. Not needed on all systems, or if you're using a "real" programmer. Get it here: http://tigertass.net/~rolemodel/lsdjawki/awki.cgi/GiveIO3: Programming!
Edit the "Makefile" that came in the firmware download. You'll need to tell it what programmer and port you're using. My ghetto programmer (or the buffered version) are "pony-stk500", on port lpt1 in my case. Therefore, I changed the following lines:
AVRDUDE_PROGRAMMER = pony-stk200
AVRDUDE_PORT = lpt1
Next, start a command shell window (Start: Run: cmd), and change over to the directory where you put the firmware. Plug up the AVR programmer to the header on the Wavebubble. TURN ON the Wavebubble (it needs to be hooked up to a power source and turned on for programming, unless you're using a programmer that supplies VCC!). Then simply run the following command:
The output should look like what's shown on the Make pages. Error messages are bad, and mean you screwed up (duh). After that's done, you just need to edit "main.c" to run whatever tests you want, and run "make program" to download the code to the AVR. Main.c is the ONLY firmware file you need to edit, leave the other ones alone unless you know what you're doing!
I think part of the reason people are having so much trouble is because they're overcomplicating things. You DON'T need AVR Studio, etc or complicated programming software . . . the Makefile ladyada has included does everything for you!