UART Controller Test(Stress)

This automated test verifies requirements of Universal Asynchronous Receiver/Transmitter (UART) controllers. This test performs the following tasks:

• One-hour stress test that uses random read, write, IOCTL, and cancel operations. Data transfer failure is expected and is ignored by the test during the time that the test is checking for driver stability issues under stress conditions.

• Basic write/read IO is run after the stress test.

Test details

Prerequisites

This test requires external connectivity pin-outs. The test also requires that you change the Advanced Configuration and Power Interface (ACPI) firmware to enumerate the UART test.

Before you run the test, perform the following steps. For all steps, <hckcontrollername> is a Windows HCK controller and <architecture> is the architecture of the device under test (DUT); these are ARM, AMD64, or x86.

1. Perform the system changes that are described under the Device.BusController.UART.HCKTestability requirement.

2. Update the ACPI table for UART test drivers based on the template that is located at \\<hckcontrollername>\Tests\<architecture>\UART\Sample-UART.asl.

3. Install the UARTTest test peripheral driver from \\<hckcontrollername>\Tests\<architecture>\UART\UARTTest.inf.

4. Edit the UART capabilities XML file to match the UART controller capabilities. The XML file is located at \\<hckcontrollername>\Tests\<architecture>\UART\UartCapabilities.xml.

   The fields in the UartCapabilities.xml file are defined as follows:

   Parameter	Description	Default value
   SettableStopBitsMask	DWORD value that maps to the supported stop bits settings from the SettableStopParity bitmask of the SERIAL_COMMPROP structure.	7
   SettableParityMask	DWORD value mapping to the supported parity settings from the SettableStopParity bitmask of the SERIAL_COMMPROP structure.	7936
   SettableWordLengthMask	DWORD value mapping to the supported word length settings from the SettableData bitmask of the SERIAL_COMMPROP structure.	15
   SettableBaudRates	Supported baud rate values.	1152003000000
   DmaMtu	DMA MTU	4
   DmaMaxTransferSize	DMA maximum transfer size. Note that multiple transfers can be performed in a single request.	4096
   FifoHighWatermark	Hardware FIFO size.	16
   IdleTimeout	Activity timeout before UART DUT goes from D0 to Dx.	200

    

Running the test

This automated test runs one time as it is detected and scheduled by Windows Hardware Certification Kit (Windows HCK) Studio. In Windows HCK Studio, on the Device selection page, select Microsoft UART Test Peripheral device to select UART-specific Windows HCK tests.

Alternately, you can run the test from the command line. To run the test from the command line, you must copy the following files from the Windows HCK controller to the DUT:

Where <architecture> is the platform of the DUT; these are ARM, AMD64, or x86.

To run the test from the command line, type the following command from a command prompt that has administrative privileges:

te.exe SerCxTestHarness.dll /p:InternalLoopback=[EnableLoopback] /p:Capabilities=Table:[CapabilitiesFileName]#[ CapabilitiesTableId] /p:Category=Reliability /p:UartDriver=[UartDriver] /p:Timeout=[StressTimeout] /p:FlowControl=[StressEnableFlowControl] /p:ThreadCount=[StressThreadCount] /p:InstanceID=[UartDeviceInstanceID]

Where the command line parameter definitions are as follows:

For more information how to run test commands by using the Test Authoring and Execution Framework (TAEF) service, see TAEF: Executing Tests and Te.exe Command Options.

Test parameter descriptions

Troubleshooting

For troubleshooting information, see Troubleshooting Bus Controller Testing.

Related topics

UART Controller Test(Basic tests)

UART Controller Test(Functional tests)

Send comments about this topic to Microsoft