New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 635682 link

Starred by 1 user
Status: WontFix
Owner:
aaboagye@chromium.org
Closed: Aug 2016
Cc:
█ alexpau@chromium.org
█ alberto@chromium.org
█ dhend...@chromium.org
█ kevcheng@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

cele fw update failure

Project Member Reported by kevcheng@chromium.org, Aug 8 2016 
 I get the following error on my celes trying to update the firmware (I've booted from a USB with CHROMEOS_RELEASE_DESCRIPTION=8670.0.0 (Official Build) dev-channel celes test).  Any idea how to get this to succeed?

# chromeos-firmwareupdate --mode=factory
Starting Google_Celes firmware updater v4 (factory_install)...
 - Updater package: [Google_Celes.7287.92.35 / EC:celes_v1.1.3540-ebe1169]
 - Current system:  [RO:Google_Celes.7287.92.3 , ACT:Google_Celes.7287.92.3 / EC:celes_v1.1.3532-466d2bd]
 - Write protection: Hardware: off, Software: Main=off EC=off
 * invoke: flashrom -p host --fast-verify -w bios.bin
 * 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... FAILED
flashrom v0.9.4  : 915e741 : Jul 30 2016 02:22:27 UTC on Linux 3.18.0-12757-g6c45955 (x86_64)flashrom v0.9.4  : 915e741 : Jul 30 2016 02:22:27 UTC on Linux 3.18.0-12757-g6c45955 (x86_64)Mapping BYT IBASE at 0xf
ed08000, unaligned size 0x200.
Mapping BYT SBASE at 0xfed01000, unaligned size 0x200.
__cros_ec_command_dev(): Command 0x13 returned result: 4                                                                                                                                                  [13/133]
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
__cros_ec_command_dev(): Command 0x13 returned result: 4
cros_ec_need_2nd_pass() failed. Stop.
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
mail flashrom@flashrom.org with FAILED: your board name in the subject line!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
ERROR: Execution FAILED.
ERROR: Execution failed: ./updater4.sh (error code = 1)

Comment 1 by kevcheng@chromium.org, Aug 8 2016

Cc: alexpau@chromium.org

Comment 2 by reinauer@chromium.org, Aug 9 2016

Cc: dhend...@chromium.org
Owner: aaboagye@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by aaboagye@chromium.org, Aug 9 2016 

[pasting my reply from the email]

Host command 0x13 is flash erase and it appears that it's failing with the error of EC_RES_ACCESS_DENIED. Looking at the code, I believe this happens if the flash is protected or if we're running from the image that you're trying to overwrite. Although, the MEC1322 runs out of SRAM so erasing flash should be okay...

Comment 4 by aaboagye@chromium.org, Aug 11 2016 

I haven't had time to dig in further. Kevin, were you able to get it flashed or is it still in this state.

It looks like we are running FAFT for celes in the lab, so I'll take a look and see if any errors like this appeared.

Comment 5 by kevcheng@chromium.org, Aug 11 2016 

My celes is in a weird state (sometimes boots up after resetting the EC, doesn't return from a reboot after it boots up) so  I just left it alone.  I'll try again to see if I can flash it.

Comment 6 by aaboagye@chromium.org, Aug 11 2016 

Also, could you elaborate on what you mean by "doesn't return from a reboot"? Does that mean, the device doesn't seem to power on at all? Goes to recovery mode?

Comment 7 by kevcheng@chromium.org, Aug 15 2016

Status: WontFix (was: Assigned)
doesn't return from a reboot -> doesn't seem to power on at all.

Buuut... the system is acting normal now and flashed successfully.  I'm not able to reproduce this right now and I don't want to waste any more of your time than I already have.   Thanks for looking into this!
►

Sign in to add a comment