[flashrom] FAILED: grunt

[Charles Marslett]

Hi folks, I have, for the first time ever, tried to flash the EC
firmware on a Google Grunt EVT platform.  I have succeeded in the past
flashing the coreboot image but the command sequence to flash the EC is
somewhat different.  Here is the output I see:

(cr) ((8ccc569...)) ***@5000G ~/trunk/src/scripts $
../platform/ec/util/flash_ec --board=grunt
--image=../../grunt-build/ec.bin
INFO: Using servo_micro.
INFO: Using ec image : ../../grunt-build/ec.bin
INFO: Flashing chip npcx_spi.
1+0 records in
1+0 records out
16252928 bytes (16 MB, 16 MiB) copied, 0.0563104 s, 289 MB/s
flashrom v0.9.9  : 622128c : Jul 05 2018 14:19:12 UTC on Linux
4.15.0-24-generic (x86_64)
Calibrating delay loop... OK.
Raiden: Serial number SNCQ01007 matched device bus=0x02,address=0x05
| Servo Micro
Erasing and writing flash chip... Verifying flash... VERIFY FAILED
at 0x00000000! Expected=0x5e, Read=0xff, failed byte count from
0x00000000-0x00ffffff: 0xc32c8
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
mail ***@flashrom.org with FAILED: your board name in the
subject line!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
FAILED
INFO: Restoring servo settings...

I did not reboot or poweroff, but it did finally shut down (at least all
the LEDs went off).

What do you recommentd next?

Thanks,
Charles Marslett

[Charles Marslett]

Well, never mind, I rebooted the target and the host systems, did a
"repo sync" of my chromeos setup, did a full firmware rebuild (described
in the care and feeding doc) then did a flash of the coreboot firmware,
followed by a flash of the ec firmware and the target system
automatically booted successfully after the ec firmware flash.

Perhaps it could have been an issue with unsynchronized ec and coreboot
firmware?

Anyway, I no longer have a flashing issue.

--Charles

Post by Charles Marslett
Hi folks, I have, for the first time ever, tried to flash the EC
firmware on a Google Grunt EVT platform.  I have succeeded in the past
flashing the coreboot image but the command sequence to flash the EC
../platform/ec/util/flash_ec --board=grunt
--image=../../grunt-build/ec.bin
INFO: Using servo_micro.
INFO: Using ec image : ../../grunt-build/ec.bin
INFO: Flashing chip npcx_spi.
1+0 records in
1+0 records out
16252928 bytes (16 MB, 16 MiB) copied, 0.0563104 s, 289 MB/s
flashrom v0.9.9  : 622128c : Jul 05 2018 14:19:12 UTC on Linux
4.15.0-24-generic (x86_64)
Calibrating delay loop... OK.
Raiden: Serial number SNCQ01007 matched device
bus=0x02,address=0x05 | Servo Micro
Erasing and writing flash chip... Verifying flash... VERIFY FAILED
at 0x00000000! Expected=0x5e, Read=0xff, failed byte count from
0x00000000-0x00ffffff: 0xc32c8
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
subject line!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
FAILED
INFO: Restoring servo settings...
I did not reboot or poweroff, but it did finally shut down (at least
all the LEDs went off).
What do you recommentd next?
Thanks,
Charles Marslett

[David Hendricks]

On Mon, Jul 9, 2018 at 5:05 AM, Charles Marslett

Well, never mind, I rebooted the target and the host systems, did a "repo
sync" of my chromeos setup, did a full firmware rebuild (described in the
care and feeding doc) then did a flash of the coreboot firmware, followed by
a flash of the ec firmware and the target system automatically booted
successfully after the ec firmware flash.
Perhaps it could have been an issue with unsynchronized ec and coreboot
firmware?

Possibly. I am guessing that the EC was unable to jump to the other
copy for some reason (this isn't in the output you posted, just a
guess), and the EC locks down its active copy which would explain why
attempting to flash it failed. You should also check the EC serial
console whenever you see EC firmware upgrade failures.