summaryrefslogtreecommitdiff
path: root/chip
diff options
context:
space:
mode:
authorAlec Berg <alecaberg@chromium.org>2015-10-23 16:37:45 -0700
committerchrome-bot <chrome-bot@chromium.org>2015-10-23 22:49:29 -0700
commit9acd84460e953dd793c9594b141ca7e38568820d (patch)
tree5e12ae87e6f7c94fb49d74381adccabcdfb8b2e6 /chip
parent71e12124e5e5e54e921a6940ed93599a90b3035a (diff)
downloadchrome-ec-9acd84460e953dd793c9594b141ca7e38568820d.tar.gz
glados: oak: reboot EC if PD MCU crashes
If PD MCU crashes, it will go back to RO code and stay there until the next AP boot. So, if EC detects PD has crashed, then EC should panic reboot with debug message that it detected a PD crash. PD MCU crash is detected by EC by seeing the PD MCU transition from RW to RO, without it setting the flag that it got there from a sysjump. This CL also makes minor changes to oak_pd and glados_pd board.c files to make them identical, other than the few minor real differences between them. BUG=none BRANCH=none TEST=tested on glados using pdcmd console command on EC to test sysjumps and reboots: sysjump to RW: pdcmd 0xd2 0 2 0 sysjump to RO: pdcmd 0xd2 0 1 0 cold reboot: pdcmd 0xd2 0 4 0 Verified that PD can jump back and forth between RO and RW without EC panicing. Verified that if PD MCU is in RW and reboots, then the EC will panic and print 'PD crash'. Verify if PD MCU reboots while in RO, without ever going to RW first, then EC does not panic. Change-Id: Id3191f4005e70a6c61a9322bf535b4374e85eb9a Signed-off-by: Alec Berg <alecaberg@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/308586 Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Diffstat (limited to 'chip')
0 files changed, 0 insertions, 0 deletions