mirror of
https://github.com/Telecominfraproject/OpenCellular.git
synced 2025-12-29 18:11:05 +00:00
d136fd9282
CL 31370 almost fixed the power on bug except in the sysjump mode. While EC firmware is being updated, the EC would sysjump between RO and RW. So that gaia_power_init() would be called and accidentally set auto_power_on to 1, which makes the next shutdown reboot instead. Thus, clear the auto_power_on if the system is already on. Also added more debug for future debug and fixed the XPSHOLD message output. Signed-off-by: Louis Yung-Chieh Lo <yjlou@chromium.org> BRANCH=Snow BUG=chrome-os-partner:14183, TEST=On snow: ; reboot successes. power on 1 (XPSHOLD seen) ssh root@snow_ip "ectool reboot_ec RO; ectool reboot_ec A; reboot" ; ; system halts (no more automatical power-on, ending loop 3) ssh root@snow_ip "ectool reboot_ec RO; ectool reboot_ec A; shutdown -h now" Change-Id: Iad54377d53701b986ff4f0c9996f02f8f17f070a Reviewed-on: https://gerrit.chromium.org/gerrit/33601 Reviewed-by: Vincent Palatin <vpalatin@chromium.org> Commit-Ready: Yung-Chieh Lo <yjlou@chromium.org> Tested-by: Yung-Chieh Lo <yjlou@chromium.org>
- 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_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
- CONFIG_CONFIGURE_BOARD_LATE
Define this to call configure_board_late() after initial system init
is complete (and after GPIOs are set up).
- CONFIG_AC_POWER_STATUS
Monitor the state of the AC power input and drive out a GPIO to
the AP indicating this state. The GPIO will be driven low when
AC power is not connected, and high when it is connected. This
uses GPIO_AC_STATUS for this purpose.