515425_515425_SCT_4_1_Compliance_Test_Plan_Rev0_9

Intel? Smart Connect

Technology 4.1

Compliance Test Plan

January 2013

Revision 0.9

Intel Confidential

Document: 515425

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO

LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY

RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND

CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND

INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF

INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A

PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR

OTHER INTELLECTUAL PROPERTY RIGHT.

A "Mission Critical Application" is any application in which failure of the Intel Product could result,

directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S

PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD

INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS,

OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND

EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY

CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH

MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS

NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS

PARTS.

Intel may make changes to specifications and product descriptions at any time, without notice.

Designers must not rely on the absence or characteristics of any features or instructions marked

"reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility

whatsoever for conflicts or incompatibilities arising from future changes to them. The information

here is subject to change without notice. Do not finalize a design with this information.

The products described in this document may contain design defects or errors known as errata which

may cause the product to deviate from published specifications. Current characterized errata are

available on request.

Contact your local Intel sales office or your distributor to obtain the latest specifications and before

placing your product order.

Copies of documents which have an order number and are referenced in this document, or other

Intel literature, may be obtained by calling 1-800-548-4725, or go to:

https://www.sodocs.net/doc/148288434.html,/design/literature.htm

Chief River and other code names featured are used internally within Intel to identify products that

are in development and not yet publicly announced for release. Customers, licensees and other

third parties are not authorized by Intel to use code names in advertising, promotion or marketing of

any product or services and any such use of Intel's internal code names is at the sole risk of the

user.

Intel Core, Intel Management Engine (Intel ME), Intel Rapid Start Technology, Intel Smart Connect

Technology, Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other

countries.

*Other names and brands may be claimed as the property of others.

Copyright ? 2013, Intel Corporation. All rights reserved.

2 Intel Confidential 515425

Contents

1 Introduction (6)

1.1 Purpose of this Document (6)

1.2 Reference Documents (6)

2 Configuration (7)

3 Installation (8)

4 BIOS/EC/HW (9)

5 Basic Functionality (11)

5.1 Objective (11)

6 System Battery Testing (15)

6.1 Objective (15)

7 System Thermal Testing (17)

7.1 Objective (17)

8 NetDetect (20)

8.1 Objective (20)

9 Intel? Rapid Start Technology (25)

9.1 Objective (25)

10 Remote Wake (26)

10.1 Objective (26)

11 Intel? Smart Connect Technology Compliancy Tool (31)

11.1 Compliancy Test Settings: (32)

11.2 Battery Life Test: (36)

11.3 Periodic Cycle Test: (36)

11.4 Brand Test (38)

12 Intel? Smart Connect Technology Interface Exerciser (40)

Figures

Figure 2-1. Test Setup (7)

Figure 11-1. Intel? Smart Connect Technology Compliancy Tool UI (31)

Figure 11-2. Test Settings (32)

Figure 11-3. Compliancy Test Settings for Periodic Wake (33)

Figure 11-4. Compliancy Test Settings for NetDetect (34)

Figure 11-5. Successful Test Results (37)

Figure 11-6. Failed Test Results (38)

Figure 12-1. Intel? Smart Connect Technology Interface Exerciser (40)

Tables

Table 3-1. Installation Verification (8)

Table 4-1. BIOS/EC/HW Verification (9)

515425Intel Confidential 3

Table 5-1. Basic Functionality Verification (11)

Table 6-1. System Battery Threshold Testing (15)

Table 7-1. System Thermal Testing (17)

Table 8-1. NetDetect Verification (20)

Table 9-1. Intel? Rapid Start Technology Verification (25)

Table 10-1. Intel? Remote Wake from S3 Power State (26)

4 Intel Confidential 515425

Revision History

Document Number Revision

Number

Description Revision

Date

515425 0.5 ?Initial release November 2012 0.8 ?Updated Basic Functionality test (BAS-011) as optional

test (Chapter 5)

?Updated Intel? Smart Connect Technology Compliancy

Tool (Chapter 11) December 2012

December 2012

0.9 ?Updated test BAT 001 for 15% battery degradation

(Chapter 6)

?Updated test BAS-016 PwrTest formula for 1200 seconds

(Chapter 5)

?Added Brand Test in Intel? Smart Connect Technology

Compliancy Tool (Chapter 11.4)

January 2013

§

515425Intel Confidential 5

Introduction

6 Intel Confidential 515425

1 Introduction 1.1 Purpose of this Document

The Intel ? Smart Connect Technology Compliance Guide is designed to provide

original equipment and device manufacturers with the compliancy requirements for platform implementation and the methodology and tools to verify compliance Intel ?

Smart Connect Technology. This document contains the compliance requirements to meet Intel ? Smart Connect Technology quality requirements. This will reduce the number of issues seen in the implementation of this technology.

It also provides the test environment setup information, the procedure for each test,

and the expected results for the purpose of validating compliancy. Requirements

contained in this document target the system BIOS/EC and other aspects of overall platform implementation.

Any issues found within Intel ? Smart Connect Technology should be promptly reported

to your Intel contact for further assessment.

Note: Intel ? Smart Connect Technology is referred to (for brevity) as “ISCT” in various table

entries throughout this document.

Some of the tests may require changes to the registry. If changes are made, a restart

of the ISCT Agent is required. This can be accomplished by rebooting the system under test (SUT).

1.2 Reference Documents Document Document No./Location

Intel ? Smart Connect Technology 4.0 Platform Design Specification

503702 Intel ? Smart Connect Technology 4.1 Setup & Configuration Guide 515415

§

Configuration

515425 Intel Confidential 7

2 Configuration

Test setup is pictured below. For the tests described in the test plan, the connection

from the system under test (SUT) to the content server can be over a wired

connection. The content server or router/gateway will need to supply the IP address for the SUT. The Wireless Access Point (AP) is required for the NetDetect testing section. If the AP has security enabled, before conducting these tests ensure the SUT is configured properly and has connectivity.

The configuration values for Intel ? Smart Connect Technology should be configured

with the settings the customer plans to ship (periodic wake, OS unattended sleep, password required on resume). For battery tests, battery must be fully charged.

Figure 2-1. Test Setup

§

Installation

8 Intel Confidential 515425

3 Installation

Table 3-1. Installation Verification Test Case

Objective Test Procedure Pass/Fail Criteria INS-001 Verify ISCT virtual

device is created 1. Boot into BIOS menu of the SUT and turn on ISCT (optional if BIOS

doesn't support this feature)

2. Locate an "Unknown device" with

Hardware ID "ACPI\INT33A0" from

windows device manager

Device with Hardware ID "ACPI\INT33A0" should not exist if boot with ISCT disabled INS-002 Verify that ISCT can be

installed on your SUT

properly 1. Un-install previous installation if exists 2. Open windows explorer and

navigate to ISCT installation

directory

3. Execute "Setup.exe" as

Administrator

4. Follow the GUI instructions to

complete installation

1. Installation complete without error message.

2. Check Windows Service Manager and verify ISCT agent is started INS-003 Verify ISCT device is

consumed in device

manager properly by

the driver

1. Execute Windows* Device Manager

2. Expand "System devices" and try locating "Intel(R) Smart Connect Technology Device" ISCT device existed and version matched INS-004 Verify ISCT Agent is

installed 1. Open a Command Prompt with Administrator privilege

2. Execute "Net Stop ISCTAgent"

3. Execute "Net Start ISCTAgent"

Command should complete without error message

INS-005 Verify all drivers

resume properly when

waking from S3 1. Open Device Manager and make sure no yellow bang exists on ISCT device

2. Put SUT in S3 state

3. Wake up SUT by power button

4. Verify S3 resume correctly and

there is no yellow band devices in

Windows Device Manager S3 cycle complete with error message

§

BIOS/EC/HW

515425 Intel Confidential 9

4 BIOS/EC/HW

Table 4-1. BIOS/EC/HW Verification Test Case Objective Test Procedure Pass/Fail Criteria BES-001 Verify GABS ACPI method 1. Select "ISCT BIOS Enable Settings (GABS)" in pnpExcerciser tool

2. Click on "Get Value" and verify return values

are correct for the platform supported

settings

BES-002 Verify GAOS/SAOS ACPI method 1. Select "Set ISCT Function Status (GAOS/SAOS)" in pnpExcerciser tool

2. Check "ISCT Mode Enabled" and “ISCT Mode

Selection” and click "Set Value"

3. Click "Get Value" and verify the "ISCT Mode

Enabled" and “ISCT Mode Selection” check

box is selected

BES-003 Verify GANS/SANS ACPI method 1. Select "Set ISCT Notification Status (GANS/SANS)" in pnpExcerciser tool

2. Check "ISCT Notification Enabled" and click

"Set Value"

3. Click "Get Value" and verify the "ISCT

Notification Enabled" check box is selected

BES-004 Verify GWLS ACPI method 1. Select "WLAN Module Status (GWLS/SWLS)" in pnpExcerciser tool 2. Click on "Get Value" 3. Verify that no error is returned by calling the

GWLS ACPI method

Test not required if no

WLAN power control

(non-mobile)

BES-005 Verify GWWS ACPI method 1. Select "WWAN Module Status (GWWS/SWWS)" in pnpExcerciser tool 2. Click on "Get Value" Test not required if no

Intel WWAN support

for platform

BES-006 Verify SASD ACPI method 1. Select "Sleep Duration (SASD)" in pnpExcerciser tool 2. Enter either a non-zero duration in seconds or select a wake-up time

3. Put the platform into S3 and verify the wake

occurs within the specified duration or

selected time

Platform wakes via

EC/RTC timer

programmed value

BIOS/EC/HW

10 Intel Confidential 515425 Test Case Objective Test Procedure Pass/Fail Criteria

BES-007 Verify GPWR ACPI method 1. Select "Platform Wake Reason (GPWR)" in pnpExcerciser tool 2. Click on "Get Value" and verify that the correct wake reason was returned (should be

"EC Timer" or "RTC Timer" selected and

"BIOS Programmed Timer" selected)

3. Place platform into S3 and once in S3,

resume platform by user method (power

button, HID event, ...)

4. Click on "Get Value" and verify it returns

"User Pressed Power Button"

5. This is true for P/S2, USB 2.0 keyboard and

mouse. It is not true for USB 3.0 keyboard

and mouse. If the keyboard and/or mouse

are plugged in to USB 3.0 port, the GPWR

will report the wake reason as PME.

Platform Wake

Reason is correct for

periodic wake timer

value and user

resumed cases BES-008

(Mobile Only) Verify GPCS ACPI Method 1. Select “Get Platform Component State (GPCS)” in pnpExcerciser tool

2. Click on “Get Value” and verify that “Lid

State” is checked (lid open).

3. Connect an external monitor to the SUT and

close the lid.

4. Click on “Get Value” and verify that “Lid

State” is not checked (lid closed).

WLAN-001 Verify SWLS ACPI method 1. Select "WLAN Module Status (GWLS/SWLS)"

in pnpExcerciser tool

2. Check "WLAN Powered in S3 Enabled"

3. Select "Set Value"

4. Put platform into S3 and verify power is

applied to WLAN module in S3

5. Repeat steps 2-4 with S4 sleep state if

supported

6. This is valid only if GABS indicates the

BIOS/EC supports the dynamic power

control of WLAN NIC (GABS.bit2)

Test not required if no WLAN power control (non-mobile) WWAN-001 Verify SWWS ACPI method 1. Select "WWAN Module Status(

GWWS/SWWS)" in pnpExcerciser tool

2. Check "WWAN Powered in S3 Enabled"

3. Select "Set Value"

4. Put platform into S3 and verify power is

applied to WWAN module in S3

5. Repeat steps 2-4 with S4 sleep state if

supported

6. This is valid only if GABS indicates the

BIOS/EC supports the dynamic power

control of WWAN NIC (GABS.bit3) Test not required if no WWAN power control

§

Basic Functionality

515425 Intel Confidential 11

5 Basic Functionality

5.1 Objective

Verify platform supports the basic functionality of Intel ? Smart Connect Technology.

Table 5-1. Basic Functionality Verification Test Case Objective Test Procedure Pass/Fail Criteria BAS-001 Verify SUT will wake up in S0-ISCT state 1. Clear registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\...\Intel Smart Connect Technology\OEM\WhiteList" if it exist 2. Ensure there is at least one network adapter as connection established (IP assigned) 3. From ISCT Configuration utility, enable updating every 15 minutes 4. Put SUT in S3 state. Verify whether SUT will resume to S0-iSCT state within 15

minutes

SUT should resume

to S0-iSCT state

within 15 minutes.

After a about 30

seconds (give or

take) the system will

transition back to S3

and continue cycling

until interrupted by

user

BAS-002 Verify display is off during S0-iSCT state 1. Following the BAS-001 test case to put SUT in S0-iSCT state 2. Verify screen is off during S0-iSCT state Screen should be off

when in S0-iSCT

state

BAS-003 Verify fan is off during S0-iSCT state 1. Following the BAS-001 test case to put SUT in S0-iSCT state 2. Verify fan is off initially during S0-iSCT state and if turned on, the acoustic level

of the fan is below 30 db

Fan should be off

when in S0-iSCT

state

BAS-004 Verify audio is muted during S0-iSCT state 1. Following the BAS-001 test case to put SUT in S0-iSCT state 2. Verify audio is muted during S0-iSCT state

Audio should be

muted when in S0-

iSCT state

BAS-005 Verify S0-iSCT state indicator LED (Optional) 1. Following the BAS-001 test case to put SUT in S0-iSCT state 2. Verify LED is indicating that system is in S0-iSCT state

LED should indicate

SUT is in S0-iSCT

state

BAS-006 Verify S0-iSCT state and S3 state have exactly the same system behavior. (Backlights, panel, LED indications,

keyboard, etc.)

1. Following the BAS-001 test case to put SUT in S0-iSCT state

2. Verify LED’s do not change state (visual appearance) between S3 and S0-ISCT

All SUT LED’s have

the same state as

when the platform

was in S3

Basic Functionality

12 Intel Confidential 515425 Test Case

Objective Test Procedure Pass/Fail Criteria BAS-007 Verify ISCT never

wakes from OS

Hibernate (S4)

1. Follow instructions in test case BAS-001 to enable ISCT

2. Put SUT in S4 state in step 4 of BAS-001 ISCT should not wake in hibernate (S4) mode BAS-008

Verify SUT will not

resume to S0-iSCT

state as expected

when operated in

Extended Power

Saving mode 1. From ISCT Configuration utility, modify current SUT time to fall within extended power saving time 2. Follow test case BAS-001 to enable ISCT 3. Verify SUT did not wake to S0-iSCT state

in 15 minutes, but instead in 2 hours

4. Restore SUT time to current time

SUT wakes every 2 hours BAS-009 Verify SUT will not

resume to S0-iSCT

state if under

Battery threshold in

DC mode 1. Power up SUT with DC battery 2. Deplete battery to less than 90% 3. Add the registry key value of ""HKEY_LOCAL_MACHINE\SOFTWARE\...\

Intel Smart Connect

Technology\OEM\DCBatteryThresholdHalt"

and set to 95 (5Fh) and restart the SUT

for the Agent to use the new setting

4. Follow the instruction in test case BAS-

001, verify SUT won't resume to S0-iSCT

state

5. Delete the added

"DCBatteryThresholdHalt" registry key

and restart the SUT for the Agent to use

the original setting

Wait 15 minutes and SUT should never resume to S0-iSCT state BAS-010 Verify power button

will trigger SUT

state transition

from S0-iSCT to S0 1. Follow the instructions in test case BAS-001 to enable ISCT 2. Press power button while SUT is in S0-

iSCT state

3. Verify SUT will resume to S0 state

SUT should resume to S0 state correctly and stay as in S0 per the unattended windows power policy BAS-011

(Optional) Verify HID event will trigger SUT

state transition

from S0-iSCT to S0. 1. Follow the instructions in test case BAS-001 to put system in S0-iSCT state 2. Trigger every HID event which could

invoke S3-resume (keyboard, mouse

click, mouse swipe on track pad)

3. Verify SUT will resume to S0 state

SUT should resume to S0 state correctly and stay as in S0 per the unattended windows power policy BAS-012 Verify after HID

event when SUT is

in S0-iSCT mode

and password is

required upon

resume, entering a

password triggers

state transition to

S0 1. Repeat steps from BAS-011 2. Enter password 3. Verify SUT will resume to S0 state SUT should resume to S0 state correctly and stay in S0 per the unattended windows power policy

Basic Functionality

515425 Intel Confidential 13 Test Case Objective Test Procedure Pass/Fail Criteria BAS-013 Verify SUT will not resume to S0-iSCT state if none of applications in whitelist are

running (optional) 1. Examine registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\...\Intel Smart Connect Technology\OEM\WhiteList"

2. If there are no applications in the registry

entry, add an application name (can be

any application name, e.g. livemail.exe)

3. Ensure none of the application listed are

running

4. Follow the instruction in test case BAS-

001, verify SUT won't resume to S0-iSCT

state

SUT should not

resume to S0-iSCT

state

BAS-014 Verify HID event will trigger SUT state transition from S3 to S0 1. Clear registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\...\Intel Smart Connect Technology\OEM\WhiteList" if it exist. 2. Ensure there is at least one network adapter as connection established (IP assigned)

3. From ISCT Configuration utility, enable

updating every 15 minutes

4. Manually place system into S3

5. Once system is in S3, wake system by

HID event (power button, keyboard,

mouse click, mouse swipe on track pad)

6. Mouse swipe or click on track pad does

not wake the system.

7. Verify SUT will resume to S0 state for

each HID event

SUT should resume

to S0 state correctly

and stay as in S0 per

the unattended

windows power

policy

BAS-015 Verify co-existence with RTC wake event before ISCT wake 1. Ensure that Microsoft* pwrtest.exe is available on the SUT. 2. From ISCT Configuration utility, enable

updating every 15 minutes

3. From administrative command prompt,

change directory to where pwrtest.exe

resides.

4. Invoke “pwrtest /sleep /p:60” to have the

SUT transition to S3

5. Verify SUT will wake after 60 seconds

instead of the ISCT 15 minutes

SUT will wake after

60 seconds instead

of 15 minutes

Basic Functionality

14 Intel Confidential 515425 Test Case Objective Test Procedure Pass/Fail Criteria

BAS-016 Verify co-existence with RTC wake event after ISCT wake 1. Ensure that Microsoft* pwrtest.exe is available on the SUT. 2. From ISCT Configuration utility, enable updating every 15 minutes

3. From administrative command prompt,

change directory to where pwrtest.exe

resides.

4. Invoke “pwrtest /sleep /p:1200” to have

the SUT transition to S3

5. Verify SUT will wake after 15 minutes for

S0-ISCT and not after 20 minutes for

pwrtest wake

SUT will wake after

15 minutes instead

of 20 minutes §

System Battery Testing

515425 Intel Confidential 15

6 System Battery Testing

6.1 Objective

This section verifies that the system battery protection mechanisms work as expected

under Intel ? Smart Connect Technology on the SUT.

Table 6-1. System Battery Threshold Testing Test Case Objective Test Procedure Pass/Fail Criteria BAT-001 To verify that iSCT Agent periodic wake timer is disabled when battery is at less than 15% 1. Add the registry key value of ""HKEY_LOCAL_MACHINE\SOFTWARE\...\Intel Smart Connect Technology\OEM\ LoggingEnabled" and set to 2 Add the registry key value of ""HKEY_LOCAL_MACHINE\SOFTWARE\...\Intel Smart Connect Technology\ OEM\ LoggingLevel" and set to 16 (0x10) 2. Restart the SUT for the Agent to use the

modified setting

3. Drain the battery to 18% of its battery

power

4. Put system to S3 to initiate iSCT cycling

of S0->S3->S0_ISCT for overnight

testing

5. Check debuglog in the morning to

confirm periodic wake service was

disabled at 15% battery.

6. SUT should not wake up from S3 to

S0_ISCT on expiration of the periodic

wake timer

If the Agent detects

the battery threshold

while on battery (no

AC present) falls

below 15% (default

registry setting for

DCBatteryThreshold

Halt), the platform

transitions to S3.

System Battery Testing

16 Intel Confidential 515425 Test Case

Objective Test Procedure Pass/Fail Criteria BAT-002 To verify extended

power saver mode

is active 1. Add the registry key value of""HKEY_LOCAL_ MACHINE\SOFTWARE\...\IntelSmartCon

nectTechnology\OEM\LoggingEnabled"

and set to 2 Add the registry key value

of

""HKEY_LOCAL_MACHINE\SOFTWARE\..

.\Intel Smart Connect

Technology\OEM\LoggingLevel" and set

to 16 (0x10)

2. Set the extended power saver mode in

iSCT agent GUI (e.g.: set Start At:

10:00PM and End At: 6:00 AM)

3. Set periodic wake in the iSCT agent GUI

@ 15 mins (in Basic tab of the GUI)

4. Cycle S3-S0_ISCT overnight

5. Check the debug log in the morning to

confirm system did S0_ISCT cycles in

regular intervals of 15 mins before

transitioning to extended power mode.

Also check that in Extended power mode

the system sleeps for 2 hours

6. Ensure system is back to regular periodic

wake cycles after 6:00 am (end of

extended power saver time)

In extended power saver mode the system should sleep for 2 hours When system is NOT in extended power saver mode it should wake to S0_ISCT every 15 mins

BAT-003

(If FFS is

enabled)) To verify system enters S4 sleep in extended power

saving time 1. Add the registry key value of ""HKEY_LOCAL_MACHINE\SOFTWARE\...\IntelSmart Connect Technology\OEM\LoggingEnabled" and

set to 2

2. Add the registry key value of

""HKEY_LOCAL_MACHINE\SOFTWARE\...\

Intel Smart Connect

Technology\OEM\LoggingLevel" and set

to 16 (0x10)

3. Set the extended power saver mode in

iSCT agent GUI (e.g.: set Start At:

1:00PM and End At: 4:00 PM)

4. Start iSCT periodic wake cycling before

1:00PM

5. Confirm the system in extended power

saver mode transitions from S3 to DS3

as per FFS time setup (between 1:00PM

to 4:00PM).

Note : In order to transit to DS3 the SUT

needs to run on battery. In extended power saver mode the system should enter S4 sleep enabled by FFS

§

System Thermal Testing

515425 Intel Confidential 17

7 System Thermal Testing

7.1 Objective

This section verifies that the system thermal protection mechanisms work as expected

under Intel ? Smart Connect Technology on the SUT.

Table 7-1. System Thermal Testing Test Case Objective Test Procedure Pass/Fail Criteria

THRM-001 To verify that iSCT Agent changes wake timer and correctly employs an exponential thermal back-off algorithm when Tj exceeds temperature threshold during iSCT cycling 1. Measure the room temperature for test 2. Add the registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\... \Intel Smart Connect Technology\ OEM\ ThermalThresholdCentigrade" and set equal to (100 - room temperature - 2) for Shark Bay (e.g., if room temperature is 19°C, then value will be 100 – 19 - 2 = 79 so set to 79 (0x4F)) 3. Add the registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\... \Intel Smart Connect

Technology\OEM\LoggingEnabled" and set to 7 Add the registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\...\Int el Smart Connect Technology\OEM\ LoggingLevel" and set to 16 (0x10) 4. Restart the SUT for the Agent to use the new registry settings 5. Run iSCT concurrent workload (email, Twitter etc.) Start ‘Debugview.exe’ and start logging to a data file 6. Put SUT to S3 to initiate iSCT periodic wake cycling 7. Put system in a closed backpack/bag/ briefcase. Run test over a recommended period of ~4hrs 8. Review DebugView output log file to ensure successful network connection and information has been collected during iSCT cycling 9. Analyze DebugView output log file to ensure wake timer multipliers are correctly applied as per Tj is reached to the target threshold value 10. Remove the registry keys added and restart the SUT for the Agent to use original values Check CPU

temperature

readout reported

in log…

when CPU

temperature

readout

is numerically

lower than 79°C,

the sleep duration

for the next

sleep cycle should

double.

(e.g., for a GUI

selection of 15MIN

sleep, the

expected sleep

durations in

current test =

15MIN, 30MIN,

60MIN, 60MIN,

….).

Note exponential

back-off does not

extend sleep

duration longer

than 1HR

If you have

implemented any

other

additional thermal

protections based

on other system

thermal sensors,

check them

according to your

platform design

specifications.

System Thermal Testing

18 Intel Confidential 515425 Test Case Objective Test Procedure Pass/Fail Criteria

THRM-002 To verify that, while the system is on battery, iSCT Agent controls iSCT wake duration within the allowed maximum value. 1. Ensure that the system is running on battery and battery is charged for more than 70% (since this test will take an approximate time of 3 hours) 2. Ensure the system can establish a wireless connection(WLAN or WWAN) and can successfully obtain IP 3. From iSCT Configuration utility, enable remote wake 4. Start an app to register a session with Wake Service 5. Start ‘Debugview.exe’ and start logging to a data file 6. Put the SUT to s3 sleep, and start iSCT cycling

7. Use Wake Service (Remote Wake) to only

wake the SUT, but don’t execute any other

operations remotely

8. System should go back to sleep immediately

at maximum wake duration

Alternately:

1. Ensure that the system is running on battery

and battery is charged for more than 70% (since

this test will take an approximate time of 3

hours)

2. Ensure the system can establish a wireless

connection (WLAN or WWAN) and can

successfully obtain IP

3. From an email sender, start sending huge

sized emails (e.g., by embedding >4MB file in

every email) at a quick interval (e.g., 1 mail

every minute)

4. Start ‘Debugview.exe’ and start logging to a

data file

5. Put the SUT to s3 sleep, and start iSCT

periodic wake cycling. Run test over a

recommended period of ~2hrs

6. Review DebugView output log file to ensure

successful network connection and information

packet transfer during iSCT cycling

7. Analyze DebugView output log file to ensure

none of the wake durations exceeded allowable

maximum of 180SEC

Check system

wake duration

from debuglog.

The wake duration

should not exceed

180SEC in either

periodic wake, or

remote wake

Test checks to

ensure we are not

exceeding the

maximum wake

duration on

battery

System Thermal Testing

515425 Intel Confidential 19 Test Case Objective Test Procedure Pass/Fail Criteria

THRM-003 To verify that iSCT Agent constantly monitors CPU temperature, and terminates current wake & puts the SUT back to sleep once thermal suspend threshold limit is reached 1. Measure the room temperature for test 2. Add the registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\... \Intel Smart Connect Technology\ OEM\ ThermalThresholdCentigradeSuspend" and set equal to (100 - room temperature - 2) for Shark Bay (e.g., if room temperature is 19°C, then value will be 100 – 19 - 2 = 79 so set to 79 (0x4F)) 3. Add the registry key value of "HKEY_LOCAL_MACHINE\SOFTWARE\... \Intel Smart Connect

Technology\OEM\LoggingEnabled" and set to

7

Add the registry key value of

"HKEY_LOCAL_MACHINE\SOFTWARE\...\In

tel Smart Connect Technology\OEM\

LoggingLevel" and set to 16 (0x10)

4. Restart the SUT for the Agent to use the new

registry settings

5. Run iSCT concurrent workload (email, Twitter

etc.) Start ‘Debugview.exe’ and start logging

to a data file

6. Put SUT to S3 to initiate iSCT periodic wake

cycling

7. Put system in a closed backpack/bag/

briefcase. Run test over a recommended

period of ~4hrs

8. Review DebugView output log file to ensure

successful network connection and

information

has been collected during iSCT cycling

9. Analyze DebugView output log file to ensure

wake timer multipliers are correctly applied

as per Tj is reached to the target threshold

value

10. Remove the registry keys added and restart

the SUT for the Agent to use original values

Verify that when

thermal limit

(ThermalThreshol

dCentigradeSuspe

nd registry) has

been reached,

iSCT Agent

terminates current

wake and then

puts the SUT back

to sleep to help

cooling

§

NetDetect

20 Intel Confidential 515425

8 NetDetect 8.1 Objective

This section verifies NetDetect support on the SUT. To support these tests, you will

need to have an Access Point available and the SSID of the Access Point configured to be “Connect Automatically” in the Windows* Wireless Connection Manager.

Table 8-1. NetDetect Verification Test Case Objective Test Procedure Pass/Fail Criteria

ND-001 Verify NetDetect Functionality with ISCT Agent (AC) 1. Verify the Access Point can be connected to by the SUT and the SSID of the Access Point is checked for “Connect Automatically”. 2. Verify network connectivity exists via WLAN to the Access Point 3. Verify no other network connections exist

(LAN/WWAN)

4. From ISCT Configuration utility on the SUT,

enable updating every 15 minutes

5. Turn off AP and after a minute, verify no

network connections exist

(LAN/WLAN/WWAN)

6. Manually place platform into s3

7. After 15 minutes platform will wake into S0-

ISCT

8. Wait for platform to transition back to S3 by

ISCT Agent

9. Wait 30 mins to confirm system is NOT

resuming to S0_ISCT with AP turned off

10. Apply power to the AP

11. Platform will wake and transition to S0-

ISCT and transition back to S3 (typically

within 2-4 minutes).

Platform wakes up

shortly after AP

turned back on and

transitions to S0-

ISCT and then

backs to s3 again

with the SUT is on

AC power. ND-002 Verify NetDetect

Functionality with

ISCT Agent

(Battery) 1. R epeat test ND-001 with the SUT running on battery only Platform wakes up shortly after AP turned back on and transitions to S0-

ISCT and then

backs to s3 again

when the SUT is on

battery power.