LARS (Acer Chromebook 14 for Work): cold boot hangs after full USB-C power loss, dead battery – recovers after power-button override

System Details

  • Device: LARS (Acer Chromebook 14 for Work, CP5-471), Intel Celeron 3855U
  • OS: Home Assistant OS 18.3 (Linux); the issue occurs before the OS loads
  • Firmware Type: UEFI Full ROM
  • Firmware Version: MrChromebox-2609.1 (2026-10-01)
  • Internal storage type: eMMC (64 GB)
  • EC RO: lars_v1.9.180-8167b12
  • EC RW: lars_v1.9.445-ae4f2c9 (built 2026-09-28)
  • Battery: original battery is defective; the system shuts off immediately when USB-C power is disconnected

Summary of the Issue

After a complete loss of USB-C power, the device powers on automatically when USB-C power returns, but hangs before the UEFI splash screen. The display shows a very faint backlight and nothing else, even after waiting more than five minutes. Holding Power for ~10 seconds, releasing it and then briefly pressing Power lets the system boot normally.

What works:

  • Power-on after a clean OS shutdown with USB-C kept connected
  • Warm reboot with the kernel parameter reboot=efi (reboot=acpi and reboot=pci hang with a backlit black screen)
  • Normal boot after a 10-second power-button override

The device is intended to run Home Assistant unattended, so automatic recovery after a power outage is essential.

Steps to Reproduce

  1. Shut down the system normally, with USB-C connected
  2. Disconnect USB-C power for ~30 seconds
  3. Reconnect USB-C power
  4. The device powers on by itself and hangs before the UEFI splash screen (faint backlight)

Expected Behavior

Either the system boots completely after power is restored, or it stays off until Power is pressed and then boots normally.

Tests Performed

  • Delta ADP-45FE B USB-C PD adapter (45W, 20V/2.25A); another power arrangement produced the same symptom
  • Reconnecting the original (dead) battery did not help
  • EC reset with Refresh + Power did not help
  • EC Software Sync: Enabled; Use EC-RW Firmware: Enabled (no firmware settings changed)

Coreboot observations (recovery boot)

Full console log captured with cbmem -c on the first boot after recovering from a failed cold boot (10 s hold, then Power):

  • EC was already running RW at the start of the recovery boot (“running image: 2”); SW sync reported EC_RW up to date; no RO→RW jump logged
  • GEN_PMCON_A had DISB set at romstage entry (GEN_PMCON: e0850200 00001808)
  • GBLRST_CAUSE0 = 0x2 (PB_OVR) and PM1_STS = PRBTNOR PWRBTN, consistent with the 10 s power-button override, not a spontaneous reset
  • No PCH_PWROK or SYS_PWROK global-reset cause recorded
  • No obvious EC errors in the log; the EC does not report uptime info

The EC being in RW and DISB being set may suggest that the failed boot got past memory init and performed the EC RW jump before hanging, but I can’t establish that (unless EC/PCH state can survive the power loss).

Questions

  1. Is this a known issue on LARS with 2609.1?
  2. Is reliable cold boot without a functional battery expected on this board?
  3. Could the EC RO→RW jump during ramstage be involved?
  4. Is there a safe way to capture diagnostics from the failed cold boot itself?
  5. Would you recommend trying a healthy replacement battery before changing any EC settings?

A complete 39 KB cbmem console log is available on request.

  1. it’s a known issue for all devices designed for use with a battery
  2. no
  3. that’s literally what is causing the issue - the PD contract does not survive the RO-RW jump
  4. ectool console, maybe. cbmem -2
  5. a working battery or disabling the ECRW jump in the setup menu should resolve the issue. disabling ECRW will lose all of the fixes/features in the RW firmware though, so I’d replace the battery

Thanks a lot for the quick and clear answer that explains everything, including why it only happens after a full power loss and not after a normal shutdown.

I’ll go with your recommendation and replace the battery rather than disabling the EC-RW jump. I’ll report back once the new battery is in and I’ve tested cold boots after power loss.

Thanks also for all the work on the firmware!