Hello Vasiliy,
can you try something? In ichspi.c line 1083, change result = run_opcode(flash, *opcode, addr, count, data); to result = run_opcode(flash, *opcode, addr | 0x800000, count, data);
It might help, it might fail completely, but it's at least something you can try.
Good luck!
Regards, Carl-Daniel
Am 07.08.2013 19:51 schrieb Vasiliy Vylegzhanin:
Oh, I see now, FLOCKDN is set. The only write command that effects protected regions is chip erase. Damn. I wonder, how vendor tool flash this.
On Wed, Aug 7, 2013 at 6:48 PM, Stefan Tauner < stefan.tauner@student.tuwien.ac.at> wrote:
On Wed, 7 Aug 2013 14:42:40 +0400 Vasiliy Vylegzhanin 6vasia@gmail.com wrote:
And I failed. There are some (modified?) phoenix flash tools, but they refuse to flash the same BIOS version. I've added W25x64 REMS ID and tried to flash it. Somehow flashrom managed to erase whole chip and yes, it failed to write @0x00580000. Is there any way to write write-protected regions on W25X64? I really don't want to desolder it, and I can't reboot cause BB is erased. Write log attached.
Hello Vasiliy,
there are no write-protected regions that are specific to the flash chip, it all depends on the Intel chipset configuration only (i.e. the same would have happened with another flash chip).
TBH I dont totally grasp your log. Your overall analysis seems to be correct though: the erase opcode might have got through. I wonder what your changes are exactly. Can you please post your patch? I also wonder how your images look like. If you can please upload them to http://paste.flashrom.org (they will be password protected there because we are not allowed to redistribute vendor images of course...)