Boards get into a RED LIGHT state, usually corrupt flash - No easy guidance / fix

[tyeth]

Happened to Loren on FunHouse, and drive wouldn't show in Mac Finder - advised to factory reset via esptool-web.

I saw enough times on the M4 airlift, even to the point of trying to aggressively reinitialise the filesystem on this PR #523 , here's my previous notes:

Describe the bug
Can't connect to Adafruit IO using WipperSnapper v73/74 using UF2 images or debug uploads without manually formatting external flash first.

Arduino board
M4 Air lift Lite

To Reproduce
Use arduino ide or vscode to build and flash the board. Expect no drive to show up.
Format extrernal flash correctly and drive will show up after using uf2 of wippersnapper.

Desktop (please complete the following information):

• OS: Windows 11
• Browser: chrome
• Version 120.0.6099.71 (Official Build) (64-bit)

Debugging got stuck in two places, one at https://github.com/adafruit/Adafruit_SPIFlash/blob/master/src/qspi/Adafruit_FlashTransport_QSPI_SAMD.cpp#L230
and also after successfully calling fatfs.begin then failing to remove + create bootlog (after believing file system was initted okay - unlikely). If filesystem manually formatted with FatFS format sketch (3rd party ff.h mkfs format), like init would do if failed to call begin on flashfs, then script continues to secrets parsing.
Not seeing flash drive show up to allow secret editing, but when I did see it I also got a lot of corruption issues when saving and resetting. Will resume another time, this is more of a notes doc for myself when taking another gander, and @brentru

--- In the past we talked about having the WipperSnapper device page do some basic diagnostics, which would detect serial, listen to boot messages / read bootlog.

[tyeth]

Closing this after release of v1.0.0-beta.76 which brought in more robust file system initialisation (potentially wiping the flash if corrupt), and better repeated logging in the event of a halt situation (red light) along with reattaching USB serial (tinyusb) first if applicable.

Technically solved by #540

May continue in this ticket with related notes / issues