Help with firmware update on green Galileo dev boards

Hey all,

I have gotten myself access to two of the green pre-Rome dev boards and I am having trouble updating the firmware on them.

I must stress that these are NOT the same as the blue boards from Maker Faire Rome that should work on the mac following basic instructions. My version is G87173-203 VER 01 and I know that makes it sort of unsupported but any advice on what my next step should be would be really very helpful.

Forgive me for giving y'all my whole process. I'm documenting so I won't forget what I did and so can help others at my local hackerspace.

My first mistake, apparently, was calling the IDE download Arduino_Intel which apparently is too long. Renaming the IDE applications name to Galileo changed the error message I got to "Firmware Upgrade Error: mkdir." That is a message that others with the dev board seem to have as well. Following the directions in section 12 of the Getting Started Guide I learned that I had to load the new firmware software on to the SD card (easy if you have a miniSD to USB adapter) and talk to it with SCO Ansi settings (harder) The step I followed for that second part:

1. Found my serial to USB adapter and a Null Modem Adapter to use with the included RS232-to-mini-jack adapter. (seriously, mini-jack? why mini-jack? Seems begging for misunderstanding)
2. Updated my Prolific PL2302 driver since I hadn't in awhile
3. Realized that I couldn't figure out how to get CoolTerm to "recognize special characters" (Function keys and Keypad to SCO)
4. Tried using the screen command the Terminal.app but wasn't sure how to configure it for special characters either. For me that meant using screen /dev/cu.usbserial 115200 but try leaving tail -f /var/log/system.log running in an open Terminal window while plugging in and unplugging your adapter to see what it identifies as.
5. Briefly debated buying MacWise or installing C-Kermit or minicom or something else listed on Robert Rau's list of serial options for the mac.
6. Walked over to the PC, launched PuTTY, used that instead.

I understood the directions in the guide, but unfortunately the first Galileo board was acting strangely (weird screen persistence in PuTTY that made it hard to tell if I was doing things right). Possibly my fault since I hadn't been grounding myself properly and am in artificially heated room with carpet doing this. I got mostly through the directions and Capsule.efi sysimage_Intel_Galileo_v0.7.5.cap started but hung up on ASSERT_EFI_ERROR and sadly do not have any of the DediProg hardware/software recommended to fix it.

I swapped the SD card to the second Galileo which behaved less weirdly than the first on start-up but simply refused to recognize the .cap file I had. Even redownloading the LITTLE LINUX IMAGE Firmware Update for Intel Galileo and reloading the .efi and .cap file I was using made no difference. Renaming the .cap file to not have periods in the name also made no difference.

Options I've thought of:

- Trying a different SD card

- ... well that is the only option I've thought of.

I have been using Arduino boards since 2005, pic chips before that, but I am not a EE by official training and work from home. Translation: I'm sharp and know how to compile C code outside of the Arduino IDE, but may not know something obvious to you and don't have access to a lot of pro-gear.  Even though I have access to both windows and linux boxes, I'd like to do as much as possible from my mac.

Thank you in advance!