Architecture of the UEFI battery charging application provided by Microsoft
This topic provides information about the design of the UEFI battery charging application provided by Microsoft for devices that run Windows 10 Mobile. OEMs can use the battery charging application from Microsoft, or they can implement their own charging application. OEMs that implement their own UEFI battery charging application may use the information in this topic as a guideline for their design.
The UEFI battery charging application is one of the first Microsoft-owned applications that runs during the boot process. The UEFI battery charging application has the following main responsibilities:
Make sure the device has enough power to boot.
Provide power-off charging support if enabled by the OEM. For more information about power-off charging, see Battery charging in the boot environment.
The UEFI battery charging application uses key UEFI protocols and reacts to various states returned by the related drivers.
The term UEFI battery charging application in this topic refers to the UEFI battery charging library loaded by mobilestartup.efi. For more information about mobilestartup.efi, see Boot and UEFI.
UEFI protocols used by the UEFI battery charging application
The UEFI battery charging application (owned by Microsoft) uses the protocols (implemented by OEMs) discussed in the following sections.
UEFI battery charging protocol (EFI_BATTERY_CHARGING_PROTOCOL)
The following steps describe key aspects of how the UEFI battery charging application uses the UEFI battery charging protocol:
The UEFI battery charging application polls the real-time status of the battery hardware by using EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryInformation (in devices that support version 0x00010002 of the EFI_BATTERY_CHARGING_PROTOCOL) or EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryStatus (in devices that support version 0x00010001 of the EFI_BATTERY_CHARGING_PROTOCOL). It is important that these functions return an accurate state of charge (SOC) value whenever possible. SOC is an OEM-defined mapping from the amount of charge in the battery based on its state (including capacity, voltage, and temperature) to a value from 0 through 100.
OEMs define the Boot to Main OS threshold (a value from 0 through 100) . This value can be different for different device models. For more information about the Boot to Main OS threshold and other threshold values, see Battery charging in the boot environment.
The battery charging application uses the SOC from the driver and compares it to the Boot to Main OS threshold value to determine if it needs to block the boot process in order to charge in UEFI or to continue with boot. It receives no other information about the state of charge.
The UEFI battery charging application calls EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery to charge the device, and it waits for a CompletionEvent with a corresponding EFI_BATTERY_CHARGING_STATUS to be returned.
For more information about this protocol, see UEFI battery charging protocol.
UEFI display power state protocol (EFI_DISPLAY_POWER_PROTOCOL)
During the UEFI battery charging process, the UEFI battery charging application displays an alternating low power UI. After 10 seconds without the power button being pressed, the application calls EFI_DISPLAY_POWER_PROTOCOL.SetDisplayPowerState to turn off the display and backlight. This helps the device consume less power during UEFI battery charging, which helps the device charge and proceed to the main OS more quickly. If the user presses the power button while the display is turned off, the application calls EFI_DISPLAY_POWER_PROTOCOL.SetDisplayPowerState again to turn the display back on. For more details, see User experience later in this topic.
For more information about this protocol, see UEFI display power state protocol.
UEFI USB function protocol (EFI_USBFN_IO_PROTOCOL)
The UEFI battery charging application relies exclusively on EFI_USBFN_IO_PROTOCOL.DetectPort to determine the type of port that is connected. Based on the port type, the application calls EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery with either 1500 mA or 500 mA.
For more information about this protocol, see UEFI USB function protocol.
Application logic
The following diagram describes the logical procedure of the UEFI battery charging application.
The following notes expand on some key sections of the logic:
Before calling EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery, the application calls EFI_USBFN_IO_PROTOCOL.DetectPort to determine the maximum current that the USB charger can provide:
If there is a port present, the application uses 1500 mA for dedicated wall charger or 500 mA for other ports.
If there is no port present, the application uses 500 mA. A wireless charger is expected to ignore this value.
If there is no charger present, the application uses 500 mA. However, the application expects EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery to return an EFI_BATTERY_CHARGING_COMPLETION_TOKEN with a status of EfiBatteryChargingSourceNotDetected.
In all cases, the OEM must ensure that the device and the charger stay within safe operating regions.
If there is no battery in the device but there is a connected power source, when the application calls EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery to charge the battery, the UEFI battery charging driver should return EfiBatteryChargingStatusBatteryNotDetected. The application handles this error by displaying an error UI and shutting down the device.
The EFI_BATTERY_CHARGING_STATUS values are interpreted in the same way in both threshold charging and power-off charging modes except for EfiBatteryChargingStatusSuccess. For more information about these charging modes, see Battery charging in the boot environment.
When the device is in a charging mode, disconnecting the power source is expected to result in the firmware signaling the application with EfiBatteryChargingSourceNotDetected, which will result in the application shutting down the device.
If the firmware signals the application with a status of EfiBatteryChargingStatusOverheat or EfiBatteryChargingStatusTimeout, the device pauses charging for 5 minutes (but the application still calls EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryInformation or EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryStatus at approximately 1-second intervals). After 5 minutes, the device resumes charging by calling EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery. During these 5 minutes, the firmware is still expected to signal the event provided by the application with the appropriate EFI_BATTERY_CHARGING_STATUS value (for example, a source disconnect should signal EfiBatteryChargingSourceNotDetected).
In both charging modes, a relevant animated UI will be shown during the box labeled Stay in app in the previous diagram.
In power-off charging mode, if the firmware has signaled an event and provides a status of EfiBatteryChargingStatusSuccess, the UEFI battery charging application does not boot to the main OS until the user holds the power button for 3 seconds. However, if the application detects that the USB cable has been disconnected at this time, it will power the device off. The UEFI battery charging application expects that the driver maintains the battery at full in power-off charging mode.
In power-off charging mode, as long as the firmware has not signaled an error or a success event, the UEFI battery charging application does not power the device off.
Error handling
Every time EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery is called, an EFI_BATTERY_CHARGING_COMPLETION_TOKEN is specified. If the driver experiences an error, the event in the token is signaled with an EFI_BATTERY_CHARGING_STATUS. The following table illustrates how the UEFI battery charging application reacts to the different status values in different situations.
| Status | Threshold charging mode | Power-off charging mode (before and after the state of charge reaches the threshold) |
|---|---|---|
| EfiBatteryChargingStatusNoneNone | Not expected/invalid | Not expected/invalid |
| EfiBatteryChargingStatusSuccess | Boot to OS | Before the state of charge reaches the threshold: Continue in power-off charging mode. After the state of charge reaches the threshold: Stay in power-off charging mode until USB is disconnected. |
| EfiBatteryChargingStatusOverheat | Pause charging for 5 minutes and then resume charging | Pause charging for 5 minutes and then resume charging |
| EfiBatteryChargingStatusVoltageOutOfRange | Boot to OS | Boot to OS |
| EfiBatteryChargingStatusCurrentOutOfRange | Boot to OS | Boot to OS |
| EfiBatteryChargingStatusTimeout | Pause charging for 5 minutes and then resume charging | Pause charging for 5 minutes and then resume charging |
| EfiBatteryChargingStatusAborted | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingStatusDeviceError | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingStatusExtremeCold | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingStatusBatteryChargingNotSupported | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingStatusBatteryNotDetected | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingSourceNotDetected | Shut down | Shut down |
| EfiBatteryChargingSourceVoltageInvalid | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingSourceCurrentInvalid | Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EfiBatteryChargingErrorRequestShutdown | Shut down | Shut down |
| EfiBatteryChargingErrorRequestReboot | Reboot | Reboot |
The following table illustrates how the UEFI battery charging application reacts to the status values received from EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryInformation or EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryStatus.
| Status | Threshold charging mode | Power-off charging mode (before and after the state of charge reaches the threshold) |
|---|---|---|
| EFI_SUCCESS. This value is returned when no errors were detected. |
Not applicable | Not applicable |
| EFI_INVALID_PARAMETER. This value is returned when an input parameter is incorrect. This should theoretically not be possible in the production environment. |
Display error UI for 10 seconds and then shut down | Display error UI for 10 seconds and then shut down |
| EFI_DEVICE_ERROR or EFI_NOT_READY. These error conditions are handled in the same way. These values should be returned by EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryInformation or EFI_BATTERY_CHARGING_PROTOCOL.GetBatteryStatus in cases where the device may not be able to boot to the main OS due to some device error. In particular: EfiBatteryChargingStatusAborted EfiBatteryChargingStatusDeviceError EfiBatteryChargingStatusExtremeCold EfiBatteryChargingStatusBatteryChargingNotSupported EfiBatteryChargingStatusBatteryNotDetected EfiBatteryChargingSourceVoltageInvalid EfiBatteryChargingSourceCurrentInvalid EfiBatteryChargingErrorRequestShutdown EfiBatteryChargingErrorRequestReboot. Throwing EFI_DEVICE_ERROR or EFI_NOT_READY followed by a completion token of one of the errors listed above will cause the device to eventually shut down. |
Resume and call EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery | Resume and call EFI_BATTERY_CHARGING_PROTOCOL.ChargeBattery |
User experience
The following diagram shows how the UEFI battery charging application draws the UI to the screen if there is not enough charge in the battery, or if the device is in power-off charging mode.
The following steps describe how the application draws the UI to the screen:
The application clears the screen by writing the background fill color to every pixel in the frame.
The application draws the alternating low battery UI bitmaps by copying pixels from the bitmap buffers directly to the display. If 10 seconds pass without the power button being pressed, the application calls EFI_DISPLAY_POWER_PROTOCOL.SetDisplayPowerState to turn off the display and backlight. If the user presses the power button, EFI_DISPLAY_POWER_PROTOCOL.SetDisplayPowerState is called to turn the display back on.
When the application receives errors from the driver, the application clears the screen by writing the background fill color to every pixel in the frame buffer, and then the application draws the battery error screen by copying pixels from the appropriate bitmap buffer directly to the display.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for