On Thu, Feb 5, 2009 at 5:43 PM,  <[email protected]> wrote:
> Erasing flash chip... Some block protection in effect, disabling
> Invalid OPCODE 0x50
> spi_write_status_enable failed
> spi_disable_blockprotect failed

IIRC that "block protection" is implemented by the flash chip. If
opcode 0x50 succeeded, erase may work.

The problem is our prepared OPMENU does not contain 0x50. My idea is
to improve the opcode generating mechanism further. It may be better
to do lazy opcode programming and minimal opcode programming. That is,
do not program opcode at chipset initialization even when programming
is allowed. Only when we found a failed opcode, we try to modify one
opcode in OPMENU to the failed one, and then resend the opcode.

yu ning

--
coreboot mailing list: [email protected]
http://www.coreboot.org/mailman/listinfo/coreboot

Reply via email to