flipperzero-firmware VS stm32-bootloader

Man I got really excited thinking this was about the Flipper Zero device https://flipperzero.one/

We use littlefs in Flipper Zero's firmware[1] for storage in leftover flash space after the main firmware image. Flipper implements a virtual FS, where both external SD card and internal storage have own mount points. SD card is used for storing apps and user-created data, and internal littlefs contains persistent data like BLE pairing, system services configs and such.

We never had any issues with littlefs - however, it cannot be easily repartitioned when amount of available leftover space changes with firmware updates. So on installing an update, it gets fully backed up to SD card, reformatted and later restored.

1- https://github.com/flipperdevices/flipperzero-firmware/blob/...

Issue opened.

It is used in FlipperZero with FreeRTOS to handle the data structure.

Here's a bootloader "library" that might be useful. You need to add your own code to get the actual firmware image from somewhere (UART, an SD card, or whatever), and then you just pass it off to the "library" for flashing.

Yes, unless you have something like an STM32 with a built-in bootloader. This can be used to update the regular bootloader. For example, this bootloader is capable of jumping to the built-in bootloader from software (as opposed to the "regular" method of pulling certain pins high or low at reset to cause the processor to run the built-in bootloader from ROM rather than the regular bootloader from flash).