Updates for MITT v9.0.0 Release

Author: joespallMS

windows-driver-docs-pr/spb/audio-playback-fidelity-tests-in-mitt.md

@@ -1,10 +1,13 @@
 ---
 title: Audio Playback Fidelity Tests in MITT
 description: The audio module on the MITT board is used to detect errors that occur at the transport level of the audio device by detecting sine wave frequency accuracy (at zero cross) and counting instances where the frequency or offset is incorrect.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: how-to
 ---
 
+> [!CAUTION]
+> The following tests are deprecated and are not included in MITT software package versions after 9.0.0.
+
 # Audio playback fidelity tests in MITT
 
 The audio module on the MITT board is used to detect errors that occur at the transport level of the audio device by detecting sine wave frequency accuracy (at zero cross) and counting instances where the frequency or offset is incorrect. Lack of a signal or missed packets results in a shifted waveform that is audible and detectable automatically via this mechanism.
@@ -35,10 +38,10 @@ The audio module on the MITT board is used to detect errors that occur at the tr
 
 **HKEY\_CURRENT\_USER\\Software\\Microsoft\\MITT\\AudioUnit** \\**** = RunAudioTest
 
-Data type  
+Data type
 REG\_DWORD
 
-Description  
+Description
 Set to 0.
 
 This will play a series of test tones, from 500hz to 18khz and report the number of glitches detected. If a high number of glitches, such as 10000+, is detected, verify that the cable is connected correctly and that the volume is not muted. Any interrupted signal is detected with a glitch per expected crossing so the number can be very high.

windows-driver-docs-pr/spb/capacitive-touch-tests-in-mitt.md

@@ -1,10 +1,13 @@
 ---
 title: Capacitive Touch Tests in MITT
 description: Capacitive touch tests in the MITT software package require MCATT (Microsoft Capacitive Applications Test Tool).
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: concept-article
 ---
 
+> [!CAUTION]
+> The following tests are deprecated and are not included in MITT software package versions after 9.0.0.
+
 # Capacitive touch tests in MITT
 
 Capacitive touch tests in the MITT software package require MCATT (Microsoft Capacitive Applications Test Tool). It's an automation tool for validating capacitive based touch hardware (touchpads and touchscreens). MCATT includes a simple interface for programming the MCATT device and automated tests. You can use the tests to detect ghost points or determine the time table for the first touch input to propagate after system wake.

windows-driver-docs-pr/spb/download-the-mitt-software-package.md

@@ -1,23 +1,30 @@
 ---
 title: Download the MITT Software Package
 description: Download the MITT software package.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: install-set-up-deploy
 ---
 
 # Download the MITT software package
 
-The MITT software package contains several tools to be used to test simple peripheral buses such as I2C, SPI, and GPIO with the MITT board. The suite of tools include utilities to update firmware, send requests to simulate test cases, and test driver packages, test the functionality of the bus, its controller and devices connected to the bus.
+The MITT software package contains several tools to be used to test simple peripheral buses such as I2C and SPI with the MITT board. The suite of tools include utilities to update firmware, send requests to simulate test cases, and test driver packages, test the functionality of the bus, its controller and devices connected to the bus.
 
-**[Download the MITT software package](https://download.microsoft.com/download/7/7/0/7703F03C-9D1F-45FC-A625-9647DC495EE2/MITT.msi)**
+**[Download the MITT software package](https://www.microsoft.com/en-us/download/details.aspx?id=108567)**
 
 ## Tools in the software package
 
 | Modules | Description |
 |---|---|
 | MuttUtil | MuttUtil.exe</br><ul><li>Sends requests to communicate with various programmable blocks on the MITT board, such as the GPIO, I2C, SPI interfaces.</li><li>Updates the firmware on the MITT board.</li></ul></br>MuttUtil.dll is the user mode library that sends requests to the MITT board, which are initiated by MuttUtil.exe. |
 | MITTI2CTest.dll</br></br>MITTSPITest.dll</br></br>WITTTest driver package</br></br>SPBCmd.exe | <ul><li>MITTI2CTest.dll &mdash; Test binary for I2C controller and bus verification.</li><li>MITTSPITTest.dll &mdash; Test binary for SPI controller and bus that validates bus-level activity.</li><li>WITTTest driver package &mdash; Installation (.inf), catalog (.cat), and binary (.sys) for the test driver for devices connected to simple peripheral buses.</li><li>SPBCmd.exe &mdash; Sends requests to the test driver to manually validate data transfers over I2C and SPI buses.</li></ul> |
-| WinUSB driver package | Installation (.inf), catalog (.cat), and binary (.sys) for the WinUSB driver required to update MITT firmware to run tests included in the MITT software package. |
+
+### Deprecated modules (removed after version 9.0.0)
+
+> [!CAUTION]
+> The following modules are deprecated and are not included in MITT software package versions after 9.0.0.
+
+| Modules | Description |
+|---|---|
 | WDTFMittSimpleIoAction.dll</br></br>AudioUnitSimpleIo.dll</br></br>SimpleIO_MITT_Audio_Sample.vbs</br></br>GpioSimpleIoExtension.dll</br></br>SimpleIO_MITT_GPIO_Sample.vbs</br></br>McattSimpleIoExtension.dll</br></br>SimpleIO_MITT_MCATT_Sample.vbs | <ul><li>WDTFMittSimpleIoAction.dll is a helper module.</li><li>SimpleIO module for audio testing.</li><li>SimpleIO module for GPIO button testing.</li><li>SimpleIO module for MCATT testing.</li></ul> |
 
 > [!NOTE]

windows-driver-docs-pr/spb/get-started-with-mitt---.md

@@ -1,7 +1,7 @@
 ---
 title: Get Started With MITT
 description: To run MITT tests, you must install the MITT firmware on a new MITT board. These steps describe how to update the MITT firmware and prepare the host machine for running MITT tests.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: get-started
 ---
 
@@ -19,33 +19,28 @@ To run MITT tests, you must install the MITT firmware on a new MITT board. These
 
 To run MITT tests, you need a computer that will run as the host and system under test (SUT).
 
-- The computer must be running Windows 8.1 version of the operating system.
+- The computer must be running Windows 10 or later.
 - The computer must have the MITT software package installed.
 - The computer must be connected as a target to a kernel debugger running on a separate machine. For more information about how to get Windbg, see [Windows Debugging](../debugger/index.md).
 
 > [!NOTE]
 > Windbg can be installed as a standalone tool set.
 
->[!NOTE]
->If your SUT is a phone, then the host computer, SUT, and MITT board must be configured as shown in this image.
-
-![mitt computer setup.](images/mitt-computer-setup.jpg)
-
 ## Install WDTF Runtime Library
 
-To run the MITT tests, you need Windows Driver Test Framework (WDTF). When you install the Windows Driver Kit (WDK), the runtime is installed automatically. For complete installation instructions, follow the steps described in [WDTF Runtime Library](/windows-hardware/drivers/wdtf/wdtf-runtime-library).
+To run the MCATT/GPIO/Audio MITT tests, you need Windows Driver Test Framework (WDTF). When you install the Windows Driver Kit (WDK), the runtime is installed automatically. For complete installation instructions, follow the steps described in [WDTF Runtime Library](/windows-hardware/drivers/wdtf/wdtf-runtime-library). I2C, SPI, and UART MITT tests do not require WDTF.
 
 **Download location**: [WDK and WinDbg downloads](../download-the-wdk.md)
 
-The runtime is installed here %ProgramFiles(x86)%\\Windows Kits\\8.1\\Testing\\Runtimes\\TAEF
+The runtime is installed here %ProgramFiles(x86)%\\Windows Kits\\10\\Testing\\Runtimes\\TAEF
 
 The system under test must be connected to a kernel debugger. Debugging tools are installed with the WDK. For more information, see [Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](../debugger/index.md) and [Windows Debugging](../debugger/symbols.md).
 
 ## Install MITT firmware
 
 1. Connect the MITT board to a USB 2.0 port on the host computer. We recommend that you use root hub ports and avoid controllers with embedded hubs.
 2. Make sure that the board power switch (next to the audio jack) is turned on. The red Power LED should be on.
-3. In Device Manager, locate the device node.
+3. In Device Manager, locate the device node. If the device node enumerates as "MITT", you can skip to step 13. If it enumerates as "ONBOARD USB", continue to step 4.
 
     ![device node for mitt.](images/install-mitt.png)
 
@@ -54,10 +49,10 @@ The system under test must be connected to a kernel debugger. Debugging tools ar
 6. Select **Let me pick from a list of device drivers on my computer**.
 7. Select **Show All Devices** and click **Next** in the **Select your device's type from the list below** page.
 8. Click on **Have Disk...** on the **Select the device driver you want to install for this hardware** page.
-9. Browse to the MITT installation directory (Program Files\\MITT\\*<architecture>* or Program Files (x86)\\MITT\\*<architecture>*) in the **Install From Disk dialog** and click **Ok**.
+9. Browse to the MITT installation directory (Program Files (x86)\\MITT\\*<architecture>*) in the **Install From Disk dialog** and click **Ok**.
 10. Under **Manufacturer** select **Microsoft**. Under **Model** select **USB MUTT DEFAULT** from the list and click **Next**.
 11. Click **Yes** and install the driver. Ignore the warning about the driver might be compatible with the hardware. Close the final page.
-12. In a command prompt from Program Files\\MITT\\*<architecture>*, run this command:
+12. In a command prompt from Program Files (x86)\\MITT\\*<architecture>*, run this command:
 
     **MuttUtil.exe -List**
 

windows-driver-docs-pr/spb/gpio-tests-in-mitt.md

@@ -1,10 +1,13 @@
 ---
 title: GPIO Tests in MITT
 description: GPIO test modules that are included in the MITT software package can be used to test the following buttons volume up, volume down, power, and rotation lock.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: how-to
 ---
 
+> [!CAUTION]
+> The following tests are deprecated and are not included in MITT software package versions after 9.0.0.
+
 # GPIO tests in MITT
 
 GPIO test modules that are included in the MITT software package can be used to test the following buttons volume up, volume down, power, and rotation lock. You can use these tests to detect issues with the GPIO drivers and microcontrollers and determine if the systems response to a short or long push is the desired response. The lines attached to the buttons are physically pulled low by the MITT board.

windows-driver-docs-pr/spb/images/mitt-computer-setup.jpg

@@ -1,7 +1,7 @@
 ---
 title: Buy Hardware for Using MITT
 description: To you use Multiple Interface Test Tool (MITT), order you need a MITT board and bus-specific adapter boards that plug into ports on the MITT board. The type of adapter board depends on the bus you want to test.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: checklist
 ---
 
@@ -23,18 +23,21 @@ To use the Multiple Interface Test Tool (MITT), you need a MITT board and bus-sp
 
     :::image type="content" source="images/uart1.png" alt-text="Picture of a UART adapter board.":::
 
-- **GPIO adapter board**
-
-    See [GPIO adapter board from JJG Technologies.](http://www.jjgtechnologies.com/GPIO.htm)
-
-    :::image type="content" source="images/gpioadapter.jpg" alt-text="Picture of a GPIO adapter for MITT.":::
-
 - **I2C adapter board**
 
     See [I2C adapter board from JJG Technologies.](http://www.jjgtechnologies.com/I2C.htm)
 
     :::image type="content" source="images/i2cadapter.jpg" alt-text="Picture of an I2C adapter for MITT.":::
 
+> [!CAUTION]
+> The following modules are deprecated and are not included in MITT software package versions after 9.0.0.
+
+- **GPIO adapter board**
+
+    See [GPIO adapter board from JJG Technologies.](http://www.jjgtechnologies.com/GPIO.htm)
+
+    :::image type="content" source="images/gpioadapter.jpg" alt-text="Picture of a GPIO adapter for MITT.":::
+
 - **MCATT expansion board**
 
     See [MCATT expansion board from JJG Technologies.](http://www.jjgtechnologies.com/mcatt.htm)

windows-driver-docs-pr/spb/multi-interface-test-tool--mitt--.md

@@ -1,7 +1,7 @@
 ---
 title: I2C Controller Tests in MITT
 description: I2C test modules that are included in the MITT software package can be used to test data transfers for an I2C controller and its driver. The MITT board acts as a client device connected to the I2C bus.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: how-to
 ---
 
@@ -80,7 +80,7 @@ Perform these steps on the system under test that has the I<sup>2</sup>C control
           Return(RBUF)
         }
     }
-    
+
     //TP2 400Khz  Fast Target
     Device(TP2) {
         Name (_HID, "STK0002")
@@ -94,7 +94,7 @@ Perform these steps on the system under test that has the I<sup>2</sup>C control
           Return(RBUF)
         }
     }
-    
+
     //TP3 1 Mhz  FastPlus Target
     Device(TP3) {
         Name (_HID, "STK0003")
@@ -108,7 +108,7 @@ Perform these steps on the system under test that has the I<sup>2</sup>C control
           Return(RBUF)
         }
     }
-    
+
     //TP4 1.4 Mhz High Speed, optional target
     Device(TP4) {
         Name (_HID, "STK0004")
@@ -122,7 +122,7 @@ Perform these steps on the system under test that has the I<sup>2</sup>C control
           Return(RBUF)
         }
     }
-    
+
     //TP5 3.4 Mhz High Speed, optional target
     Device(TP5) {
         Name (_HID, "STK0005")
@@ -144,7 +144,7 @@ Perform these steps on the system under test that has the I<sup>2</sup>C control
 ## I<sup>2</sup>C automation tests
 
 1. Create a folder on the system under test.
-2. Copy the TAEF binaries to the folder and then add it to your PATH environment variable. The required TAEF binaries are in %ProgramFiles(x86)%\\Windows Kits\\8.1\\Testing\\Runtimes\\TAEF .
+2. Copy the TAEF binaries to the folder and then add it to your PATH environment variable. The required TAEF binaries are in %ProgramFiles(x86)%\\Windows Kits\\10\\Testing\\Runtimes\\TAEF .
 3. Copy Muttutil.dll and Mitti2ctest.dll from the MITT software package to the folder.
 4. View all MITT I<sup>2</sup>C tests by using the **/list** option:
 

windows-driver-docs-pr/spb/run-mitt-tests-for-an-i2c-controller-.md

@@ -1,7 +1,7 @@
 ---
 title: SPI Tests in MITT
 description: SPI test modules that are included in the MITT software package.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: how-to
 ---
 
@@ -93,7 +93,7 @@ Perform these steps on the system under test that has the I<sup>2</sup>C control
 ## SPI automation tests
 
 1. Create a folder on the system under test.
-2. Copy the TAEF binaries to the folder and then add it to your PATH environment variable. The required TAEF binaries are in %ProgramFiles(x86)%\\Windows Kits\\8.1\\Testing\\Runtimes\\TAEF .
+2. Copy the TAEF binaries to the folder and then add it to your PATH environment variable. The required TAEF binaries are in %ProgramFiles(x86)%\\Windows Kits\\10\\Testing\\Runtimes\\TAEF .
 3. Copy Muttutil.dll and Mittspitest.dll from the MITT software package to the folder.
 4. View all MITT SPI tests by using the **/list** option:
 

windows-driver-docs-pr/spb/spi-tests-in-mitt.md

@@ -1,7 +1,7 @@
 ---
 title: UART Tests in MITT
 description: The MITT software package includes tests for validating data transfers to a UART controller and its driver. The MITT board's UART interface acts as a UART loopback device.
-ms.date: 01/12/2024
+ms.date: 02/27/2026
 ms.topic: how-to
 ---
 
@@ -35,7 +35,7 @@ The MITT software package includes tests for validating data transfers to a UART
 
 ## Test driver and ACPI configuration
 
-To modify the ACPI tables, install Windows Hardware Certification Kit (HCK) 8.1. Perform these steps on the system under test that has the UART controller:
+Perform these steps on the system under test that has the UART controller:
 
 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 provided under \\\\<hckcontrollername>\\Tests\\<architecture>\\UART\\Sample-UART.asl or use this example. You can use the [Microsoft ASL compiler](../bringup/microsoft-asl-compiler.md).
@@ -76,7 +76,7 @@ To modify the ACPI tables, install Windows Hardware Certification Kit (HCK) 8.1.
 
 1. Perform steps described in Test driver and ACPI configuration.
 2. Create a folder on the system under test.
-3. Copy these files from %ProgramFiles(x86)%\\Windows Kits\\8.1\\Testing\\Runtimes\\TAEF to the folder.
+3. Copy these files from %ProgramFiles(x86)%\\Windows Kits\\10\\Testing\\Runtimes\\TAEF to the folder.
     - Wex.Common.dll
     - Wex.Communication.dll
     - Wex.Logger.dll
@@ -89,11 +89,11 @@ To modify the ACPI tables, install Windows Hardware Certification Kit (HCK) 8.1.
 
     Example 1: To run the tests at 115200 bps (default)
 
-    `C:\\uart> UtsSanity.exe –mitt`
+    `UtsSanity.exe –mitt`
 
     Example 2: To run the tests at 3Mbps:
 
-    `C:\\uart> UtsSanity.exe -mitt –baudRate 3000000`
+    `UtsSanity.exe -mitt –baudRate 3000000`
 
 ## UART adapter schematic