at least for the pi4, the .bin file covers the entire eepromDoes that completely nuke or replace all EEPROM content or, as with uploading a '.uf2' file to a Pico, only update parts of it ? Re-flashing MicroPython for example leaves the complete file system intact, needs nuking to remove any secrets that may contain.
but the recovery.bin will compare each erase-block between the .bin and the eeprom, and only erase/program when differences are found
i would assume the pi5 works the same
and on the pi4, it prints progress to the serial (gpio 14/15 on the pi4), including which blocks differed
pi5 may do the same on its debug header (between the 2 hdmi ports)
Statistics: Posted by cleverca22 — Fri Jan 17, 2025 12:26 am