Blackaddr
Well-known member
My Teensy MicroMod took a bootloader update from using the latest Teensyduino and now some functionality I was relying on seems to no longer be the case.
I have some data I need stored across reboots, but I DO need it wiped when reprogramming the board. That seemed to be the behavior with the Teensyduino 1.54 bootloader but now after building something with 1.56 it looks like the LittleFS_Program area is no longer getting wiped, it's preserved, and this also is stated in the 1.56 release notes if I'm interpreting correctly.
Okay, so anybody have some ideas now on how I can detect if this is the first boot after programming? My tricking of detecting if the LittleFS_Program area was clean or dirty seems to be off the table. It would be nice if this was an option I could pass to the bootloader from teensy_loader_cli tool.
I have some data I need stored across reboots, but I DO need it wiped when reprogramming the board. That seemed to be the behavior with the Teensyduino 1.54 bootloader but now after building something with 1.56 it looks like the LittleFS_Program area is no longer getting wiped, it's preserved, and this also is stated in the 1.56 release notes if I'm interpreting correctly.
Okay, so anybody have some ideas now on how I can detect if this is the first boot after programming? My tricking of detecting if the LittleFS_Program area was clean or dirty seems to be off the table. It would be nice if this was an option I could pass to the bootloader from teensy_loader_cli tool.