7 ms·
> Because of this, the Boot ROM is now a 500K EEPROM [...] The USB Controller also has it's own EEPROM Can these two EEPROMs at least be flashed through test p
by cesarb 7y ago
> Because of this, the Boot ROM is now a 500K EEPROM [...] The USB Controller also has it's own EEPROM
Can these two EEPROMs at least be flashed through test points, so they can be recovered without de-soldering if they're corrupted? (The RPi4 schematics on the site are next to useless.) That would also allow dumping both EEPROMs to compare them with a "known good" copy, in case there's any suspicion they've been maliciously modified.
- gjsman-1000 7y agohttps://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md https://www.raspberrypi.org/documentation/hardware/raspberry... This is all documentation on the SoC EEPROM available. (I don't believe there is any USB EEPROM information publicly available at the moment.) The good news: You don't need de-soldering to fix them. If you should corrupt the EEPROM, you can plug in an SD card with a special 'recovery.bin' file on it and it will re-flash the EEPROM itself. (This does mean that the Pi _technically_ has an extremely tiny boot ROM permanently installed in it still, but all it does is repair the boot EEPROM if it is damaged and start that boot EEPROM if it isn't damaged). You can also write-protect the EEPROMs with a special soldiered-on resistor on the board. As for dumping, no public info yet.