diff options
| author | Craig Hesling <hesling@chromium.org> | 2020-06-02 09:54:33 -0700 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-06-04 20:08:07 +0000 |
| commit | 5c59954533908ce7cb6adc44cf5260e57e2bc7e8 (patch) | |
| tree | a5f2c32866ab3483fa162f9a6146cb62ff321208 /util/flash_jlink.py | |
| parent | 0fb5ededcf63703334aee46ddb94f6e3b38d5166 (diff) | |
| download | chrome-ec-5c59954533908ce7cb6adc44cf5260e57e2bc7e8.tar.gz | |
util/flash_jlink.py: Reset after flashing
You must reset the chip after flashing to start the new code.
It is possible that the chip was resetting without this fix
due to a double fault after flashing. In cases where the CPU
is hung before flashing, the CPU would not reset.
BRANCH=none
BUG=none
TEST=# Ensure that the chip is hung in on b/147520242
./local/flash_jlink.py --ip ''
# The UART console should reflect a reset and become interactive again
Signed-off-by: Craig Hesling <hesling@chromium.org>
Change-Id: I5006eff5d3a955ba9b8e6ecee4f72d7ad851f239
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2226520
Commit-Queue: Tom Hughes <tomhughes@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Diffstat (limited to 'util/flash_jlink.py')
| -rwxr-xr-x | util/flash_jlink.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/util/flash_jlink.py b/util/flash_jlink.py index 3dd731bf7d..cf7c570fdb 100755 --- a/util/flash_jlink.py +++ b/util/flash_jlink.py @@ -20,6 +20,7 @@ import tempfile JLINK_COMMANDS = ''' r loadfile {FIRMWARE} +r go exit ''' |