Full write log attached.
On Wed, Mar 20, 2013 at 7:07 PM, Vasiliy Vylegzhanin coder@npo-echelon.ru wrote:
On Tue, Mar 19, 2013 at 9:33 PM, Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
On Tue, 19 Mar 2013 21:12:55 +0400 Vasiliy Vylegzhanin coder@npo-echelon.ru wrote:
Hi!
I've got HP EliteBook 9470m, which contains (according to ID, didn't check) Numonyx N25Q128. So I added this chip to flashrom, but anything except probe fails with transaction error:
Reading flash... Transaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=4 Running OPCODE 0x03 failed at address 0x003000 (payload length was 64). Read operation failed!
Can anything be done here? Logs attached. Patch (dirty) below.
Hi,
the transaction error comes from the chipset configuration which read-protects the ME region and has nothing to do with the flash chip/your patch. Please search the mailing list archive and take a look at the Documentation directory of flashrom regarding problems with the locked ME region. Short answer: if you need to access the whole chip, use an external programmer. There is a hard coded override in some HP firmwares that might be worth a try before that, try win, left arrow, right arrow (all at once i think) as you turn on the laptop.
Thanks very much for showing your patch. No need to clean it up and submit it again though, because we are working on our own version already, see also http://patchwork.coreboot.org/patch/3652/ Sorry for not having it integrated already :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Well, I've tried to read only BIOS region (ported patch 3 from http://patchwork.coreboot.org/user/bundle/37/) and succeeded. But erase operation fails with transaction error:
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:S, <snip> 0xd3e000-0xd3efff:S, 0xd3f000-0xd3ffff:ETransaction error! SSFS: SCIP=0, FDONE=1, FCERR=1, AEL=0 SSFC: SCGO=0, ACS=1, SPOP=0, COP=4, DBC=0, SME=0, SCF=4 Running OPCODE 0x20 failed at address 0xd3f000 (payload length was 0). spi_block_erase_20 failed during command execution at address 0xd3f000
Is it chip or laptop issue?