Connected standby testing prerequisites
The System on a Chip (SoC) platform should meet a set of basic software and hardware requirements before you try to test and validate connected standby operation. These requirements help to ensure that any problems that might arise are quickly identified and easily debugged.
Effective connected standby testing cannot be accomplished without first ensuring that the system under test has the basic physical setup that is required to capture diagnostic information. The setup for this system should include the equipment listed in the following table.
|Kernel debug board and cable||
Supports Windows kernel debugging.
Consult with your SoC vendor to determine what type of debugging is supported and what equipment is necessary. Some systems require a specialized debugging board.
|Connect the kernel debugger between a host PC and the system under test.|
|Hardware debug device and cable||
Supports SoC hardware debugging.
Consult with your SoC vendor for necessary hardware debugging equipment.
|Connect the hardware debugger to the system under test.|
Serves as the host for kernel and hardware debugging.
You can have the same or separate PCs for kernel and hardware debugging.
|Connect the PC(s) to the kernel and hardware debuggers.|
A power meter is required to measure power consumption on a power-instrumented system.
If you are unsure about the appropriate device to measure power, consult with your SoC vendor.
|When measuring the power floor, connect the power meter to the platform that is being tested.|
A SIM card is required to test mobile broadband (MBB) connectivity during connected standby.
|When testing MBB operation, plug the SIM card into the SIM card slot.|
The system under test must be built of hardware components that are suitable for a connected standby PC and that can operate at low power during connected standby. Work closely with your SoC and power-management IC (PMIC) vendors to identify the appropriate version of SoC and PMIC to use for connected standby testing. All off-SoC device components—such as Wi-Fi, Bluetooth, and near-field communication (NFC) devices—must also support low power.
Before you start connected standby testing, verify the following:
- The system is built with the appropriate version of SoC for low-power/connected-standby testing.
- The system is built with the appropriate version of PMIC for low-power/connected-standby testing.
- All off-SoC device components support low-power operation and are wired to switchable power planes.
- The system is capable of kernel debugging and hardware debugging. In particular, the system must have physical ports for the kernel and hardware debugging connections.
Drivers and firmware play a critical role in connected standby operations and are therefore an important part of connected standby testing.
The system must have the appropriate drivers and firmware installed to allow the system to enter low-power states. The easiest way to verify that all firmware and drivers are properly installed is to open Device Manager and check that no devices have active problem codes (yellow ! symbols) and that no devices are missing drivers.
Do not proceed with connected standby testing unless all of the following is true:
- All system and device firmware is properly installed.
- All device drivers are properly installed.
- All devices in Device Manager do not show a problem code (yellow !).
- There are no missing drivers for devices in Device Manager.
The system must have a stable and functioning graphics driver before you start connected standby testing. Similarly, the Wi-Fi and mobile broadband (MBB) devices must be capable of functioning correctly when the screen is on before they can be properly tested for low-power and connected standby operation.
Before starting connected standby testing, make sure that your system has the following:
- A stable graphics driver.
- Reliable Wi-Fi connectivity when the screen is on.
- Reliable MBB connectivity when the screen is on (if the system is equipped with MBB).