apro: fail if the V1 data is corrupted

It shouldn't be possible to have an unsupported ap_ro_check type and
the data shouldn't get corrupted. Fail verification, so the user can
tell that something is wrong. If the space is empty or the board id is
blocked, still treat verification as unsupported and allow the device to
boot.

Move the AP RO failed processing into a function, so cr50 can fail
immediately.

BUG=none
TEST=manual
	use a DBG image to write ap_ro_check data with the wrong type.
	Verify verification fails immediately
	[65.918056 RO Validation triggered]
	[65.920169 ap_ro_check_unsupported: unable to read ap ro space]
	[65.922733 do_ap_ro_check: bad v1 data]
	[65.924049 enable_spi_pinmux: AP]
	[65.927314 spi_hash_pp_done: AP]
	[65.928829 spi_hash_disable]
	[65.929904 AP RO FAILED!]

	Erase V1 data. Check verification is skipped because it's
	unsupported.
	[3.724384 RO Validation triggered]
	[3.726524 ap_ro_check_unsupported: RO verification not programmed]
	[3.728363 do_ap_ro_check: unsupported]
	[3.906272 AP UART on]
	[4.296054 deferred_tpm_rst_isr]
	[4.297027 AP on]
	[4.297588 tpm_reset_request(0, 0)]
	[4.298374 tpm_reset_now(0)]
	[4.299095 Committing NVMEM changes.]

	Write V1 data normally. Check verification runs normally.
	[35.977050 RO Validation triggered]
	[35.978744 do_ap_ro_check: found v1 data]
	[35.979732 enable_spi_pinmux: AP]
	[35.982574 spi_hash_pp_done: AP]
	[35.983276 get_saved_gbbd: not programmed]
	[36.145401 validate_gbb_flags: ok]
	[36.146457 Using 0 for GBB flags.]
	[36.147239 usb_spi_sha256_update: c00000:500c]
	[36.190986 usb_spi_sha256_update: c05010:3faff0]
	[43.365467 matched gbb 0]
	[43.367374 do_ap_ro_check: saved gbbd]
	[43.368988 spi_hash_disable]
	[43.370231 AP RO PASS!]

Change-Id: I9be2a900dc69009b40c32e12dec250e54977a08a
Signed-off-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/4004357
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>

0 files changed, 0 insertions, 0 deletions