mborgerson

For the OP's case, erase time should not be an issue. I think that writing 33 bytes five times per second should not show any major delays due to block erase time. The block erases, when required. should be covered by the internal RAM buffers...

One problem that I see is that your data structure is either 33, 34, or 36 bytes in length---depending on whether you've done anything to adjust the structure packing size. None of those sizes will fit evenly into a 512- byte SD sector. At some...

I have developed a wildlife image-capture app for the FLIR Lepton thermal imaging camera. It is designed to capture about 8 38Kbyte frames /second when an object above a threshold temperature is in the frame. I must have set the threshold too...

One thing to remember with these LTC ADCs is that they get the channel for the NEXT conversion in the SPI command word you send. Thus, the first result you get will not be the result for the channel you specified. You always get a dummy...

I added a line to my test program to print the sizeof(time_t). It returned 8, so you are correct that the something in the current compiler or libraries is setting time_t to a long-long 64-bit variable type. All the versions of time.h...

I was using printf() to show some intermediate results in a data collection program. I found that using printf() to show the time and two other variables didn't work as expected: var1 = 1; var2 = 2; Serial.printf("now: %lu var1: %u var2...