![eeprom is write-protected eeprom is write-protected](http://www.softnology.biz/images/faq/wrprotect_im1.png)
If you then set the write-protect jumper nothing will be able to change those write-protect regions. Setting eeprom_write_protect=1 when flashing the EEPROM via recovery.bin tells recovery.bin to mark the EEPROM as write-protected. 140325.pdf (See section 8.1.7 Status Register Memory Protection) te_protect and the linked Winbond datasheet It's counterintuitive but unfortunately, that's just how these EEPROMs work. It just limits access to the *Write Status* register and it is the *Write Status* register which defines the write-protect regions which default to not protected.
#EEPROM IS WRITE PROTECTED SOFTWARE#
J2 is invisible to software and does NOT write protect the EEPROM. I added "eeprom_write_protect=1" in recovery/config.txt and when I flashed it, thought the specific version of bootloader did write to the EEPROM but when I use "sudo -E rpi-eeprom-config" in PI, I don't see eeprom-write protection anywhere.Īny kind of help would be highly appreciated. Also is there a way to verify via software maybe "rpi-eeprom-update" error perhaps that the SPI EEPROM is now write-protected.Ĥ. Ideally, shouldn't it say that the pin 3-4 is low and can't write to the EEPROM ?ģ. After connecting jumper wires on J2 (1-2, and3-4) I still can run. But when would these lights be flashed or when can I observe them?Ģ. There is this document which says if there are 3 long and 2 shot flashes it means the SPI EEPROM is write-protected. How can I ensure that my EEPROM is write-protected?. On my CM4, I am trying to achieve EEPROM write protection.