Bill Greiman

I can't help you debug your hardware. It appears that you are using a SanDisk 2GB card. I tested Fat16 on an Uno with a 2GB SanDisk card and a[...

Looks like the new Teensy EventResponder is causing the problem. I have decided it is not worth supporting FreeRTOS on Arduino. [See this](https://forum.pjrc.com/threads/46636-RTOS-no-longer-usable-with-Teensy?p=154625&viewfull=1#post154625).

This version of FreeRTOS catches a hard fault exception when using floating point on Teensy 3.5/3.6. I no longer support FreeRTOS or ChibiOS as an Arduino library. It is impossible...

ChibiOS is best for STM32. There is only limited support for Kinetis.

Impossible. exFAT requires full general write. My new [SdFat-beta](https://github.com/greiman/SdFat-beta) has the smallest exFAT implementation I know of.

PetitFS is not close to supporting exFAT. exFAT is far more complex than FAT16/FAT32.

Sorry I am not the author of PetitFS and no longer update it. See the author [here](http://elm-chan.org/fsw/ff/00index_p.html).

No, FAT file systems and SD cards are not designed to read from the end. You could improve the speed by using a very large buffer.

The best way to reduce the risk of corruption is to call file.sync() at key points in the program. This is the same as file.close() but the file is not...

sync() does a lot of I/O. It flushes the data cache, reads the files directory entry, updates the directory entry and writes it to the SD. sync() causes a huge...