diff options
| author | Patryk Duda <pdk@semihalf.com> | 2022-02-21 13:49:12 +0000 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2022-02-28 16:27:57 +0000 |
| commit | 190a365409031e901708136da85ef38ceb95bcf6 (patch) | |
| tree | bb25e06ba425cc83e9751aa4604ab5581118c58c /util | |
| parent | e8c4ea58619019e202ff5cac29c61b4a04d9ed44 (diff) | |
| download | chrome-ec-190a365409031e901708136da85ef38ceb95bcf6.tar.gz | |
stm32: Introduce define to control extended reset flags
Some ROs don't support extended reset flags saved in backup RAM.
BKPDATA_INDEX_SAVED_RESET_FLAGS_2 (introduced in CL:1295890) was added
in the middle of bkpdata_index enum, so it breaks compatibility between
RO and RW. In some cases, extended reset flags in backup RAM are cleared
because RO wrongly recognizes flags as panic reason.
BUG=b:119131962
BRANCH=none
TEST=Compile FPMCU firmware for nami with RO nami_fp_v2.2.144-7a08e07eb.
Issue 'reboot ro' command from RW part. FPMCU shouldn't stop
in RO, because that was not implemented when RO was released.
After jump to RW, check if panic data doesn't exist.
Signed-off-by: Patryk Duda <pdk@semihalf.com>
Change-Id: Ifcefa463c80ec1b498546589dcfc704eba8dfe60
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3477957
Reviewed-by: Bobby Casey <bobbycasey@google.com>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Tested-by: Patryk Duda <patrykd@google.com>
Commit-Queue: Patryk Duda <patrykd@google.com>
Diffstat (limited to 'util')
| -rw-r--r-- | util/config_allowed.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/util/config_allowed.txt b/util/config_allowed.txt index 4f6bcb6a95..a4128c7a4a 100644 --- a/util/config_allowed.txt +++ b/util/config_allowed.txt @@ -854,6 +854,7 @@ CONFIG_STM32L_FAKE_HIBERNATE CONFIG_STM32_CHARGER_DETECT CONFIG_STM32_CLOCK_HSE_HZ CONFIG_STM32_CLOCK_LSE +CONFIG_STM32_EXTENDED_RESET_FLAGS CONFIG_STM32_SPI1_CONTROLLER CONFIG_STM_HWTIMER32 CONFIG_STREAM_SIGNATURE |