mirror of
https://github.com/Telecominfraproject/OpenCellular.git
synced 2026-01-10 17:41:54 +00:00
55073a0a84
Needed for EC software sync so the AP can verify the EC's RW code and tell the EC to jump to RW when necessary. If the AP then decides it doesn't need to stay booted, the AP can shut back down. (The AP verifying the EC's code and/or shutting back down are NOT part of this CL...) Also add a Power+Refresh+DownArrow key combination which causes the EC to reset WITHOUT powering on the AP; this will be needed for debugging the AP power-on sequence. BUG=chrome-os-partner:10892 TEST=manual 1) power+refresh+down -> ec reboots, system stays down 2) power+refresh+esc -> ec reboots, system to recovery 3) power+refresh -> ec reboots, system boots 4) hibernate, then open lid -> ec reboots, system boots 5) hibernate, then power button -> ec reboots, system boots 6) yank battery, then reconnect -> ec reboots, system boots 7) reboot ec -> system boots 8) 'sysjump A' when AP already booted -> system stays on 9) 'sysjump A' when AP shut down -> system boots Change-Id: I65d2f7d9cca3acb84b76302cdcd8c8a800f03253 Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/26158
- EC Lib
This wraps Blizzard driverlib and implements the EC chip interface defined
by Google. See below diagram for architecture.
+--------------------+
| Host BIOS/OS |
+--------------------+
---- host interface ----
+--------------------+
| Google EC features |
+--------------------+
---- chip interface ---- The interface is defined in
src/platform/ec/chip_interface/*.
+--------------------+ But the real implementation is in EC Lib.
| EC Lib |
+--------------------+
| Blizzard low level |
| driver, the |
| driverlib. |
+--------------------+
Build Options
=============
- CONFIG_WATCHDOG_HELP
Try to detect a watchdog that is about to fire, and print a trace.
This is needed on STM32, where the independent watchdog has no early
warning feature and the windowed watchdog has a very short period.
- CONFIG_PANIC_NEW_STACK
When reporting a panic, change to a completely new stack. This might
help get a useful trace out a situation where the stack or stack
pointer has been corrupted.
- CONFIG_PANIC_HELP
Report extra information about a panic, such as the fault address,
here shown as bfar. This shows the reason for the fault and may help
to determine the cause.
=== EXCEPTION: 03 ====== xPSR: 01000000 ===========
r0 :0000000b r1 :00000047 r2 :60000000 r3 :200013dd
r4 :00000000 r5 :080053f4 r6 :200013d0 r7 :00000002
r8 :00000000 r9 :200013de r10:00000000 r11:00000000
r12:00000000 sp :200009a0 lr :08002b85 pc :08003a8a
Precise data bus error, Forced hard fault, Vector catch, bfar = 60000000
mmfs = 00008200, shcsr = 00000000, hfsr = 40000000, dfsr = 00000008
- CONFIG_ASSERT_HELP
Report assertion failures in a vebose manner to aid debugging. When
enabled an ASSERT() which fails will produce message in the form:
ASSERTION FAILURE '<expr>' in function() at file:line