eMMC Compliance Test

  • Article

This test verifies the correct operation of a SD host controller by ensuring that the features described in the requirements are implemented by the host controller.

Test details

   
Specifications
  • Device.Storage.Hd.EMMC.BasicFunction
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
Expected run time (in minutes) 2
Category Development
Timeout (in minutes) 120
Requires reboot false
Requires special configuration false
Type automatic

 

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Running the test

Before you run the test, complete the test setup as described in the test requirements: Hard Disk Drive Testing Prerequisites.

The test checks the current configuration of the eMMC disk and how it is attached to the system. It validates that the items described in the requirements are indeed implemented.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting Device.Storage Testing.

The logs are descriptive in what is being tested and where any failures occur. The first step in triaging failures should be to check the log file and determine which one of the requirement lines failed. The failure may also have more information about the root cause.

More information

The test will first do discovery on the SD host controllers and SD devices attached to the system to determine their capabilities. It will then specifically check the disk for the device specified to ensure that it conforms to the logo requirements. For each requirement item the device will be checked to see if it claims to support the features or modes required. Then if applicable, the device will be checked to ensure the operation of that feature is adequate. Failures will be logged for any error found.

Command usage

Command Description

SoCBootTest.exe eMMCComplianceTest Device [StorageDriveLetter]

Run the eMMCComplianceTest scenario on the specified device.

 

Command syntax

Command option Description

SoCBootTest

The binary that runs the test.

eMMCComplianceTest

Runs the eMMC Compliance test.

Device

Specifies the device to run the test against.

Note

   For command line help for this test binary, type /?.

 

File list

File Location

autocom.dll

<[testbinroot]>\nttest\driverstest\storage\

autocomManaged.dll

<[testbinroot]>\nttest\driverstest\storage\managed\

bigfile.exe

<[testbinroot]>\nttest\driverstest\storage\disk\

DiskStress.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\

MemoryChoke.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\

MemoryStress.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\

SoCBootTest.exe

<[testbinroot]>\nttest\driverstest\storage\sd\SDBoot\SocBootTest\

SDHelper.dll

<[testbinroot]>\nttest\driverstest\storage\sd\Tools\SDHelper\

EtwProcessor.dll

<[taefbinroot]>\

Wex.Common.dll

<[testbinroot]>\wextest\cue\testexecution\wlk\

Wex.Communication.dll

<[testbinroot]>\wextest\cue\testexecution\

ntlog.dll

<[testbinroot]>\nttest\commontest\ntlog\

ntlogger.ini

<[testbinroot]>\nttest\commontest\ntlog\

stresslog.dll

<[testbinroot]>\basetest\core_file_services\shared_libs\

fbslog.dll

<[testbinroot]>\basetest\core_file_services\shared_libs\fbslog\

rapidfile.exe

<[testbinroot]>\basetest\core_file_services\shared_tests\Wdk\

 

Parameters

Parameter name Parameter description
LLU_LclAdminUsr User account for running the test.
LLU_NetAccessOnly User account for accessing test fileshare.
WDKDeviceID Instance path of device to test.
DiskDeviceObjLink Assigned by Create Storage Parameters.
Destructive (0,1) 0=Passive, 1=Destructive