diff options
| author | Doug Anderson <dianders@chromium.org> | 2014-06-19 13:20:50 -0700 |
|---|---|---|
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-06-21 00:14:37 +0000 |
| commit | 4702a1d19bef7da427dc05b3675d53b76b0c979b (patch) | |
| tree | a90469f3e1f145e70d17378bba67ab1cb4fdee2b /util/ectool.c | |
| parent | 323273daeb437387957c7f736b5764e3e38e1168 (diff) | |
| download | chrome-ec-4702a1d19bef7da427dc05b3675d53b76b0c979b.tar.gz | |
watchdog: Help ensure that the stm32 watchdog help prints
On stm32 we were programming the WATCHDOG_HELP timer with the same
value as the independent watchdog (which automatically resets the
CPU). That means we weren't guaranteed to see the WATCHDOG_HELP. It
happened to work most of the time due to the the LSI oscillator fudge
(we assumed the watchdog was on a 56 kHz oscillator when it was
probably on a 38 kHz one), but let's give ourselves a guaranteed gap.
It's unlikely that this extra gap will actually help on most machines
(if we're running at 53 kHz or lower we already had this much margin),
but it's nice to be safe.
BRANCH=ToT
BUG=chrome-os-partner:29162
TEST=Increase margin to 400 (instead of 50) and type "waitms 300".
Sometimes hit watchdog warning.
Change-Id: I7f876757c15d7775116720c408a4127b4b94adfa
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/204894
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Diffstat (limited to 'util/ectool.c')
0 files changed, 0 insertions, 0 deletions