TamaPoke v3.22

Backups on the installer page now happen as part of flashing instead of being something you have to remember, and they are checked before you are told you have one.

Back up, then install

• The installer has a new Back up, then install button, and it is the primary one. It reads the save off the board, verifies it, downloads it as a .tpsave file and keeps a copy in your browser, and only then hands over to the flasher. Install without backup is still there if you want it.
• Your browser may ask you to choose the board twice: once to read the save, once to flash. That is a limitation of how the two connections work and cannot be avoided from the page.
• A brand-new board, or one sitting in download mode, has no save to read. The page says so and goes straight through to the flasher rather than getting in the way.

Backups are now verified, not just downloaded

• A backup is checked before you are told it worked. The board reports how many bytes it produced; the page now compares that against what actually arrived and verifies the save's checksum. Previously a capture was accepted if it merely ended with the right line, so a read that stopped early could be downloaded and presented as a complete backup. A partial backup is worse than no backup, because you only find out when you need it.
• Restoring runs the same check before anything is sent, so a truncated or corrupted file is refused up front with a reason rather than after the whole upload.
• Restoring now waits for the board to acknowledge every chunk instead of assuming a fixed delay was long enough.

Recent backups, kept in this browser

• The Save vault now lists your recent backups with the date, trainer name and creature, and each one can be restored to a connected board or downloaded again in one click. Twelve are kept.
• This is a convenience, not a backup, and the page says so. They live only in that browser on that computer, and are lost if you clear site data, use private browsing, or move to another machine. The downloaded .tpsave file is the real backup.
• Nothing is uploaded anywhere. There is no account, no server and no copy of your save outside your own machine, which is deliberate.

Firmware

• STATS now reports a board= line, taken from the chip's own hardware ID. It exists so the installer can tell two devices' backups apart in that list. It identifies nothing else and authorises nothing.

Under the hood

• The page's save-handling code has tests for the first time, run against a save exported by the real firmware. The checksum is pinned to the published check value for its algorithm rather than to a second copy of it.
• The page could previously hold the serial port open after it believed it had disconnected, which would have stopped the flasher claiming the device. Fixed, and it is what makes the backup-then-install handoff work.
• The .js cache keys the page uses to defeat CDN caching are now computed at build time instead of being typed by hand, and a release is refused if they have drifted.

Installer

• Published rebuilt v3.22 firmware and an updated web-installer manifest. Existing NVS saves remain outside the installer write ranges.

Full changelog: v3.21...v3.22