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

Issue 761557 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

cr50 firmware release breaks eve

Project Member Reported by sonnysasaka@chromium.org, Sep 1 2017

Issue description

eve keeps rebooting itself starting from 9831.0.0.
I bisected the problem and turns out that replacing the cr50 firmware (/opt/google/cr50/firmware/*) with the ones taken from 9830.0.0 solves it. So it may be a regression of the cr50 firmware.
 
Status: WontFix
There was a problem with the VPD RLZ setting on this device, it was fixed by reprogramming the VPD code and the Cr50. 

This will have to be done manually with every device which exhibits this problem, here is the PSA sent to chromeos-eve:

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
with introduction of board locked Cr50 images for Eve it became important that the RLZ code stored in the VPD is correct. 

The problem is that early Eve devices were manufactured with a default RLZ code (ZZCR) instead of Eve assigned code of ZZAF.

Incorrect RLZ code prevents the board locked Cr50 images (versions 0.0.22 and newer) from running, if Chrome OS installs this image on your Eve, it would reboot a few times and fall back to whatever Cr50 image it was running before.

This command executed on the Eve allows to see what its RLZ setting is:

$ mosys platform brand

It should return "ZZAF", if it returns anything else the Eve and its Cr50 need to be fixed, which requires manual intervention. Bring your device to me or Mary (mruthven@) for help.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Sign in to add a comment