Re: [flashrom] FAILED: Soraka DVT1

[David Hendricks]

Hello Hongxia,
Were you able to get in touch with someone on the chromiumos team?

It appears that you attempted to write the entire firmware ROM, but it
failed to write the flash descriptor region. You should target the
region(s) you want updated using the -i option, along with --fast-verify,
so that flashrom does not attempt to write and verify regions that it might
not have access to.

On Mon, Apr 23, 2018 at 11:54 PM, Gao, HongxiaX 
wrote:
> Hi,
>
> It is failed on my board when flashing firmware R68 10599. Can you help me
> on it?
>
> *HW:* Soraka DVT1
>
> *Issue description:*
>
> Flash firmware 10431 without any problems, but it is failed when flashing
> firmware R68 10599. Steps are:
>   Download firmware R68 10599
>
> https://www.google.com/chromeos/partner/fe/#download:event=IMAGE_DOWNLOAD&url=image_download?version~E010599.0000.0000~Aboard~Esoraka~Achannel~Edev~Atype~EFIRMWARE_IMAGE_ARCHIVE&rel=true,
> then extract it.
>   Enter board terminal
>
> localhost /home # flashrom -w 10599/image.bin
>
> flashrom v0.9.9  : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128
> (x86_64)
>
> flashrom v0.9.9  : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128
> (x86_64)
>
> Calibrating delay loop... OK.
>
> coreboot table found at 0x7aac5000.
>
> WARNING: SPI Configuration Lockdown activated.
>
> Erasing and writing flash chip... Verifying flash... VERIFY FAILED at
> 0x00000081! Expected=0xff, Read=0x0b, failed byte count from
> 0x00000000-0x00ffffff: 0x9
>
> Your flash chip is in an unknown state.
>
> Get help on IRC at irc.freenode.net (channel #flashrom) or
>
> mail [e-mail] with FAILED: your board name in the subject
> line!
>
> DO NOT REBOOT OR POWEROFF!
>
> FAILED
>   Try to update firmware
>
> localhost /home/10599 # chromeos-firmwareupdate -m autoupdate
>
> Starting Google_Soraka firmware updater v4 (autoupdate)...
> Updater package: [Google_Soraka.10431.32.0 /
>
> EC:soraka_v1.1.8047-2c5917d7d]
> Current system:  [RO:Google_Soraka.10431.32.0 ,
>
> ACT:Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d]
> Write protection: Hardware: ON, Software: Main=off
> invoke: flashrom -p host -r _current/bios.bin
>
> RO Contents are different.
>
> autoupdate(recovery): update RO+RW
> invoke: flashrom -p host --fast-verify -w bios.bin
>
> autoupdate(recovery): update ec/RO+RW
> invoke: flashrom -p ec --fast-verify -w ec.bin
>
> autoupdate(recovery): EC may be restored or updated in next boot.
>
> Firmware update (autoupdate) completed.
>   Reboot the board, then power off and power on
>
>   Flash fw 10599 again
>
> localhost /home # flashrom -w 10599/image.bin
>
> flashrom v0.9.9  : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128
> (x86_64)
>
> flashrom v0.9.9  : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128
> (x86_64)
>
> Calibrating delay loop... OK.
>
> coreboot table found at 0x7aac5000.
>
> WARNING: SPI Configuration Lockdown activated.
>
> Erasing and writing flash chip... Verifying flash... VERIFY FAILED at
> 0x00000081! Expected=0xff, Read=0x0b, failed byte count from
> 0x00000000-0x00ffffff: 0x9
>
> Your flash chip is in an unknown state.
>
> Get help on IRC at irc.freenode.net (channel #flashrom) or
>
> mail [e-mail] with FAILED: your board name in the subject
> line!
>
> DO NOT REBOOT OR POWEROFF!
>
> FAILED
>
> Thanks
>
> Br,
>
> Hongxia
>
> flashrom mailing list
> [e-mail]
> https://mail.coreboot.org/mailman/listinfo/flashrom