flashrom: Cyan FW update failing |
|||||
Issue descriptionTouch(/mnt/stateful_partition/.install_completed) FAILED Starting firmware updater (/tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery) Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery Starting Google_Cyan firmware updater v4 (recovery)... - Updater package: [Google_Cyan.7287.57.64 / EC:cyan_v1.1.3499-2565067] - Current system: [RO:Google_Cyan.7287.57.64 , ACT:Google_Cyan.7287.57.64] - Write protection: Hardware: off, Software: Main=off EC=off One-time RO+RW update from unstable EC firmware. Try to update with recovery mode... mode_recovery: update RO+RW * invoke: flashrom -p host --fast-verify -w bios.bin mode_recovery: update ec/RO+RW * invoke: flashrom -p ec --fast-verify -w ec.bin Execution failed (1): flashrom -p ec --fast-verify -w ec.bin Messages: flashrom v0.9.4 : 467b825 : Jun 03 2016 10:00:12 UTC on Linux 3.18.0-12390-g860bb18 (x86_64), built with libpci 3.1.10, GCC 4.9.x 20150123 (prerelease), little endian disable_power_management: Failed to open /var/lock/flashrom_powerd.lock for writing: No such file or directory Mapping BYT IBASE at 0xfed08000, unaligned size 0x200. Mapping BYT SBASE at 0xfed01000, unaligned size 0x200. Missing Chromium EC memory map. Error: Programmer initialization failed. ERROR: Execution FAILED. ERROR: Execution failed: ./updater4.sh (error code = 1) Finished after 29 seconds. Failed Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery - Exit Code 1 Firmware update failed (error code: 1). Rolling back update due to failure installing required firmware. Successfully updated GPT with all settings to rollback. ... Could this CL have broken things? https://chromium-review.googlesource.com/#/c/348841/
,
Jun 7 2016
The file locking error may be harmless. "Missing Chromium EC memory map" is the real error here, I think. Also, here's a log from Vincent's machine: Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate --mode=recovery Starting Google_Cyan firmware updater v4 (recovery)... - Updater package: [Google_Cyan.7287.57.64 / EC:cyan_v1.1.3499-2565067] - Current system: [RO:Google_Cyan.7287.57.64 , ACT:Google_Cyan.7287.57.64 / EC:cyan_v1.1.3497-b6940dc] - Write protection: Hardware: off, Software: Main=ON EC=ON mode_recovery: update RO+RW * invoke: flashrom -p host --fast-verify -w bios.bin mode_recovery: update ec/RO+RW * invoke: flashrom -p ec --fast-verify -w ec.bin Execution failed (1): flashrom -p ec --fast-verify -w ec.bin Messages: Erasing and writing flash chip... Good. It seems nothing was changed. FAILED flashrom v0.9.4 : 467b825 : Jun 03 2016 10:00:12 UTC on Linux 3.18.0-12391-gc495817 (x86_64), built with libpci 3.1.10, GCC 4.9.x 20150123 (prerelease), little endian disable_power_management: Failed to open /var/lock/flashrom_powerd.lock for writing: No such file or directory Mapping BYT IBASE at 0xfed08000, unaligned size 0x200. Mapping BYT SBASE at 0xfed01000, unaligned size 0x200. ERASE FAILED at 0x00020000! Expected=0xff, Read=0x43, failed byte count from 0x00020000-0x00020fff: 0x80 ERASE FAILED! FAILED!
,
Jun 7 2016
,
Jun 7 2016
On Vincent's machine, the system was protected and the write protect screw was removed. We see the WP switch deasserted, so we try to flash RO, but the physical protection on the EC SPI ROM was never removed. A quick fix is to re-insert the write-protect screw before running recovery. Running "flashrom -p ec --wp_disable" prior to recovery should also do the job. Regarding the original reported error, that's an LPC issue. It seems different. Do we have kernel logs as well?
,
Jun 8 2016
Thank you, Shawn. We will follow the instruction to reflash it.
,
Jan 26 2018
,
Nov 2
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bhthompson@chromium.org
, Jun 7 2016