Share via

Wireless Display Verify Miracast Support

  • Article

This automated test verifies that basic support for wireless display is present and that the UMDF driver for Miracast is implemented in its own DLL.

Test details

   
Specifications
  • Device.Graphics.WDDM13.DisplayRender.WirelessDisplay.BasicWirelessDisplay
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (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) 10
Category Compatibility
Timeout (in minutes) 600
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: Graphic Adapter or Chipset Testing Prerequisites.

Troubleshooting

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

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

The test generates an RTSP message log file: virtualsinklog.{…}.txt. The actual name of this file can be found in the test log file. For example:

Message 6/13/2013 7:39:22.724 PM RTSP log file: virtualsinklog.{3D55759A-4BB2-43C6-9AD6-9D98D6726908}.txt

The test job captures WirelessDisplay.etl and WPP.etl files. You can find these files by selecting Child Job Results in Windows Hardware Lab Kit (Windows HLK) Manager and then browsing job logs for Wireless Display Cleanup Trace.

WirelessDisplay.etl contains information about the Miracast session from start to stop. Most events are aligned with DDI calls for both the user mode driver (UMD) and kernel mode driver (KMD).  IHV investigating issues might find it useful to look for errors in these DDI events.  The event names should be familiar to the developer because they closely match the DDI names that are used for the wireless feature.  This file can be analyzed by using Windows Performance Analyzer (WPA).

WPP.etl contains WPP traces that are captured for the display kernel events related to Miracast. These traces are highly detailed, and should provide adequate information about session failures that is sufficient to debug most issues. These files require access to symbols to decode them. Symbols for the OS should be available to IHVs. The following command line should be used to decode WPP.etl in wpp.txt is: netsh trace convert overwrite=yes tmf=..\symbols.pri\TraceFormat WPP.etl.

All test cases return PASS or FAIL. The test details are available in the test log (Te.wtl), which you can view in Windows HLK Studio.

Error Description/Workaround

Miracast UMD name is not unique.

Miracast UMDF driver should be implemented in its own DLL.

 

More information

Parameters

Parameter name Parameter description
LLU_NetAccessOnly LLU Name of net user
ConfigDisplayCommandLine Custom Command Line for ConfigDisplay. Default: logo
WDKDeviceID Device id of DUT