Hi! I was wondering if the next revision could include a breakout for the RTC's battery backup pin? It's pin 49, Vbat, which is currently tied to Vcc. I'm making do with including the number of seconds since I've reset the RTC on each log entry, but it would be helpful to produce actual timestamps as well.

Thanks!

I'm trying to migrate this over from arm-elf-gcc to arm-none-eabi-gcc, and I've updated the makefiles to change the compiler / mcu settings and remove the WinARM settings, so that I can get a proper elf / FW.SFE out of it. However, the code does not execute properly after the bootloader loads it. Do you know of anything else that must change when moving to this different compiler?

"Saftey"

File: FW.SFE
Saftey On = Y

File: main.c
strcpy(stringBuf, "MODE = 0\r\nASCII = N\r\nBaud = 4\r\nFrequency = 100\r\nTrigger Character = $\r\nText Frame = 100\r\nAD1.3 = N\r\nAD0.3 = N\r\nAD0.2 = N\r\nAD0.1 = N\r\nAD1.2 = N\r\nAD0.4 = N\r\nAD1.7 = N\r\nAD1.6 = N\r\nSaftey On = Y\r\n");

1.) U4 needs to be renamed U3

2.) BOM in sparkle is missing one BATT-10373 and two DIO-08053

3.) one 90 degree trace on top route on VCC net near main IC just off C9.

4. one 90 degree trace on bottom route on USBVIN near coin cell pads.

I found a problem with a Nokia FAT16 (non-SDHC) mcirosd card where the Logomatic Boot Loader gets caught in an endless loop trying to open the partition on the SD card. Windows can read and write to this card type with no problems. The loop starts inside the openroot() routine after the line fs = fat_open(partition); has been entered. I found that re-partitioning the Nokia card with a new FAT16 partition fixed the looping problem(just a format does not work) but if an error using rprint could be generated that would be better than endless looping. I hope this of some help.