diff options
| author | Vadim Bendebury <vbendeb@chromium.org> | 2016-09-08 19:29:09 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2016-09-09 02:58:49 -0700 |
| commit | 82f1f4187cabac1f179201231afb2e628ac94cd1 (patch) | |
| tree | 8c7c29918f5275590b078418fafee8f43f932c13 /include/system.h | |
| parent | 7be86267061c6ed71768c26fb7ba329274d1b761 (diff) | |
| download | chrome-ec-82f1f4187cabac1f179201231afb2e628ac94cd1.tar.gz | |
g: usb update: clear fallback counter after update finishes
There is no point in waiting for a reset to clear the fallback
counter, it can be cleared as soon as USB update is finished.
BRANCH=none
BUG=chrome-os-partner:56864
TEST=on a kevin-tpm2 device: set the reset counter to 7 by running
> rw 0x40000128 1
> rw 0x4000012c 7
on the cr50 console. Then try uploading a new RW image over Suzy-Q
and verify that it is running after reset.
Then verify that cr50 can still be updated
Change-Id: I098a87c48b2fe864143715b1e90d4bb2409b9eae
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/383077
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Diffstat (limited to 'include/system.h')
| -rw-r--r-- | include/system.h | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/include/system.h b/include/system.h index d6d2c063b7..5bca2c6321 100644 --- a/include/system.h +++ b/include/system.h @@ -462,6 +462,14 @@ int system_is_reboot_warm(void); */ int system_process_retry_counter(void); +/** + * On systems with protection from a failing RW update: reset retry + * counter, this is used after a new image upload is finished, to make + * sure that the new image has a chance to run. + */ +void system_clear_retry_counter(void); + + /* Board properties options */ #define BOARD_SLAVE_CONFIG_SPI (1 << 0) /* Slave SPI interface */ #define BOARD_SLAVE_CONFIG_I2C (1 << 1) /* Slave I2C interface */ |