HACK: cr50: make sure manufacturing sequence is invoked only once
HACK: cr50: make sure manufacturing sequence is invoked only once

While the proper manufacturing initialization is in the works, we need
to be able to initialized the device, but do not want to run
manufacturing process on every reboot.

Let's store the state in the lowest location of the NVRAM, this patch
will be reverted when the proper initialization procedure is in place.

BRANCH=none
BUG=chrome-os-partner:50115
TEST=used the device in Kevin. Observed that factory initialization
     sequence was invoked only on the first boot, the following boots
     had no problems reading rollback counters.

Change-Id: I812cbad4d91db47de76ecfa5a14c56ae9c0efdab
Signed-off-by: Vadim Bendebury <5515d6d2d0829cbe0dd0dcf2094aaded06d58514@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/358680
Reviewed-by: Nagendra Modadugu <5dc366ddbf8fb5981f46478e8436ef712a08b71b@google.com>
Reviewed-by: Scott Collyer <7d40b3eb9e17bf55d972074a5e77a7ea4159f9dd@chromium.org>

coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec