ZackSchilling

Ok, I was able to build the edge firmware. I’m on Mac OS X, so it was a little bit of an adventure, I should share how I did it. Basic steps I followed:

0.) Already had XCode and all the Apple dev tools pre-installed

1.) Signed up for Github (been meaning to do this!)

2.) Installed and configured GitHub for Mac (http://mac.github.com)

3.) Cloned tinyg GIT repo using the “Clone in Desktop” link

4.) Switched to edge branch using GitHub for Mac’s nice GUI

5.) Installed “MacPorts” (http://www.macports.org/install.php)
Used MacPorts to get the relevant AVR tools:
sudo port install avr-libc
sudo port install avrdude

6.) Installed the Mac OS X USB driver (http://www.ftdichip.com/Drivers/VCP.htm)

7.) Edited the tinyg makefile to work with the MacPorts version of avr-bintools

In the file …/TinyG/firmware/tinyg/default/Makefile

find
@avr-size -C –mcu=${MCU} ${TARGET}
replace with
@avr-size -A ${TARGET}

8.) Navigate to …/TinyG/firmware/tinyg/default/ and run the make command

9.) Success! The make process completes! I get a tinyg.hex that looks just like the master branch’s tinyg.hex file!

:100000000C94A7410C94C8410C94C28E0C94C84126
:100010000C94C8410C94C8410C94C8410C94C8413C
:100020000C94C8410C94C8410C94C8410C943B8B6F
:100030000C94C8410C94C8410C9487830C94C8411B
etc…

Ok, so I’ve got a firmware file. The only step above that looks dicey to me is 7. I have absolutely no idea what I’m doing. My avr-size tool simply lacked the -C option and I don’t know what –mcu=${MCU} does. I assume something important. Googling around I saw the suggestion to substitute the -A command, so I did.

Throwing caution to the wind, I decide to try and flash my board with this file. I connect my board, fine the USB device name, and follow the wiki instructions. I hit the reset button on my board and execute the following command.

$ avrdude -p x192a3 -c avr109 -b 115200 -P /dev/tty.usbserial-DA00CQ4M -U flash:w:tinyg.hex

Connecting to programmer: .
Found programmer: Id = “XBoot++”; type = S
Software Version = 1.7; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
Device code: 0x7b

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e9744
avrdude: NOTE: Programmer supports page erase for Xmega devices.
Each page will be erased before programming it, but no chip erase is performed.
To disable page erases, specify the -D option; for a chip-erase, use the -e option.
avrdude: reading input file “tinyg.hex”
avrdude: input file tinyg.hex auto detected as Intel Hex
avrdude: writing flash (109382 bytes):

Writing | | 0% 0.00s ***failed;
***failed;
***failed;
***failed;
***failed;
(The failed message repeats over 109,000 times. I will spare you.)
Writing | ################################################## | 100% 0.44s

avrdude: 109382 bytes of flash written
avrdude: verifying flash memory against tinyg.hex:
avrdude: load data flash data from input file tinyg.hex:
avrdude: input file tinyg.hex auto detected as Intel Hex
avrdude: input file tinyg.hex contains 109382 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 16.49s

avrdude: verifying …
avrdude: verification error, first mismatch at byte 0x0002
0x14 != 0xa7
avrdude: verification error; content mismatch

avrdude done. Thank you.

So the flashing fails but does so especially gracefully. My board is still functional. Thoughts?