It's the rebased code from CB:23840 with the following improvements: 1) "gingerly" --> "dangerous-bruteforce" 2) timeout implemented. As you could see from a NOTE added to its' commit message, this mode has turned out "more dangerous than expected": there is a chance that after attempting the erase/write operations you will not be able to revert their results by using this "dangerous-bruteforce" mode - or even to read again using this mode - until you will recover your target's bootable firmware by the other methods.

After encountering this roadblock I'm not sure when I'll be able to complete the rest of your suggestions mentioned at https://review.coreboot.org/c/flashrom/+/23840 , but at least I have never encountered any problems with the not-writing operations such as probe and read - these should be safe...

View Change

To view, visit change 31830. To unsubscribe, or for help writing mail filters, visit settings.