I did not have the winning bid, but I obtained another XO with a very loose battery holder.
Waiting 31 days will not yield a bootable XO. TOO bad
I set up a test arrangement using Sparkfun (sparkfun.com) USB to serial breakout board (BOB-00718) and a three wire null modem cable (do not connect XO 3.3 volt pin -- power supplied from USB). Used a second XO with YUM install of minicom ( see
http://wiki.laptop.org/go/Serial_adapters and
http://wiki.laptop.org/go/Fix_Clock ). All the drivers are included in the XO linux kernel. The only additional setup from the links is to change the configuration of flow control to software (YES) and hardware (NO).
I set times to a few minutes below roll over time with days 28, 30, or 31 (month 00) and waited well beyond what should have been roll over time to month 1. The "bricked" XO would never boot. Simply changing the month to 01 (and all other to 00) was sufficient to get booting (does display "time error" message, but time can be set using the linux "date" command).
I do not have documentation for the RTC circuit, but it appears that a month value of 00 is an undefined state or defines another counting modulus.
As a side bar, the driver ttyUSB0 is recreated in /dev on each boot of the XO used as a terminal, so if the breakout board is not wired correctly (my mistake of hooking up 3.3 volt pin), the driver never appears in /dev. Also, you can see the breakout board as device "fdti_sio" by using the linux command : lsmod on the XO used as a terminal.