Correctly report firmware update failure if RO needs update.
If the RO Firmware needs updating but can't be because it's
really RO, then report a new erro code (43) back to Omaha.
This normally only happens during board bringup when the RO
firmware is locked prematurely. We want to know these devices
exist so we can replace them.
BUG=chromium:218555
TEST=Build/unittests. Did NOT test on hardware with bug.
Change-Id: I383a999f1b175c378bef936c55d87565d8113336
Reviewed-on: https://gerrit.chromium.org/gerrit/63841
Commit-Queue: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
diff --git a/payload_state.cc b/payload_state.cc
index f7c75da..6d6791f 100644
--- a/payload_state.cc
+++ b/payload_state.cc
@@ -246,6 +246,7 @@
case kErrorCodeNewRootfsVerificationError:
case kErrorCodeNewKernelVerificationError:
case kErrorCodePostinstallBootedFromFirmwareB:
+ case kErrorCodePostinstallFirmwareRONotUpdatable:
case kErrorCodeOmahaRequestEmptyResponseError:
case kErrorCodeOmahaRequestXMLParseError:
case kErrorCodeOmahaResponseInvalid: