The problem is that I want to be able to program the micro with my Mac, which presented a few problems. Here is how I got it working with Xcode on my Mac.

The first step was getting the programmer to work.

The only problem? The kit screams Windows. By default it includes a parallel programer. The last time I had a computer with a parallel port was… well it was when I had a PC. Not only that but SparkFun only carries Windows compatible USB programmers (a programmer in this case is a device that transfers your code to the chip, not the skinny kid from high school with a Redbull IV in him). In fact, there are almost no AVR programmers that are Mac compatible.

Not knowing the days of frustration that I was getting myself into, I bought the STK500 USB programmer. Other options would be the now discontinued Pololu programmer, or build it yourself.

Luckily, Olimex, the company that made the STK500 USB programmer, has released an update that makes it Mac compatible. You can find info and instructions on how to install it on their product page. Be sure to follow the instructions exactly. You will need a Windows computer to do the upgrade. It worked fine in VMWare Fusion.

The next step was to get the build tools woking in Mac OS X. These are the programs that will compile your code and transfer it to the microcontroller.

The easiest way to get the tools needed is to get CrossPack. CrossPack includes all the tools necessary to build and upload your projects. This also includes some tools to generate Xcode templates.

Basically, the Xcode templates create a project with an external build target. So in the background all that is happening is make is being called. I found two problems with the default templates. One is that you have to use the command line to generate your templates. That isn’t really necessary since Xcode has a built in template architecture. Basically place any templates you wan to show up in the new file window in “/Developer/Library/Xcode/Project Templates”. Just make sure to create a sub folder there to create the section. I called mine AVR.

The second problem I had was that there is no way to upload the code to the chip. Luckily there is an easy fix. Right click on executables and select “Add: New Custom Executable”. Use /usr/bin/make as the path. Under arguments, add “flash”. This will call make, just like the target does, but it will make for flash instead of compile. Now you can select Build and Go and it will upload the program to the connected microcontroller.

To get going, you need to edit the makefile in the project. Select your microcontroller, for DEVICE. Input the correct value for CLOCK. I also had to add a variable for the location of the tools. I called it TOOLS

DEVICE     = atmega168
CLOCK      = 8000000
PROGRAMMER = -c stk500v2 -P /dev/tty.usbmodem*
OBJECTS    = main.o
FUSES      = -U hfuse:w:0xd9:m -U lfuse:w:0x24:m

TOOLS      = /usr/local/CrossPack-AVR/bin/

AVRDUDE = $(TOOLS)avrdude $(PROGRAMMER) -p $(DEVICE)
COMPILE = $(TOOLS)avr-gcc -std=c99 -Wall -Os -DF_CPU=$(CLOCK) -mmcu=$(DEVICE)

In the PROGRAMMER line you will notice I used an asterisk (*) to select any connected programmer. I did this because the number changed on me a few times and I didn’t want to have to edit the makefile every time I plugged it in.

You should be good to go now. You can download my template, but you will still need the CrossPack tools.

Update: Jonathan mentioned in the comments that you can use http://www.engbedded.com/fusecalc/ to calculate the fuse bits.