Automated lab testing considerations
System designers should consider automated lab testing scenarios when they design the power and battery charging subsystem. The most relevant consideration is platform recovery from crash or unresponsive system scenarios.
Platforms that are designed for automated lab testing, including platforms that are targeted for co-engineering programs with Microsoft, must implement configurable support for automatically booting the system when power is applied. Such automatic booting conflicts with the user experience goal that the platform remains off until the user physically turns it on; however, it is a requirement to achieve a fully automated test environment.
In Microsoft test labs, platforms are recovered from crash and unresponsive system scenarios by remotely removing and applying system power. The platform must be capable of ignoring the presence and charge capability of the internal battery and use only the presence of AC power to determine if the platform should automatically boot. This behavior is for lab-enabled systems only and can be configured by using a UEFI variable that Windows sets.
Note
Systems that are designed for users must not power on automatically when power is applied unless they are required to detect the power capability of the Universal Serial Bus (USB) charger.
UEFI DISABLEBATTERY variable definition
The DISABLEBATTERY variable is created under VendorGuid {0x77fa9abd, 0x0359, 0x4d32, {0xbd, 0x60, 0x28, 0xf4, 0xe7, 0x8f, 0x78, 0x4b}}. When the variable is present (that is, when GetVariable() returns EFI_SUCCESS), the requested platform behavior must be modified from the default battery behavior when the value is set.
When DISABLEBATTERY is set | When DISABLEBATTERY is not present or not set |
---|---|
|
|