Drivers Mcci USB Devices

ASUS ASM USB 3.0 Driver V1.12.9.0: ASUS Asmedia USB 3.0 Driver: ASUS Asmedia USB3.0 Driver: ASUS USB 3.0 Driver: ASUS USB 3.0 Host Controller Driver: ASUS USB3.0 Driver: EVGA P67 Series: Generic USB Hub: Installation Readme for Asmedia 104x USB3.0 Host Controller Drive: Intel(R) USB 3.0 Controller Driver V1.0.4.225 for Windows 7 32bit & 64bit. When you plug the device into your USB, Windows will look for the associated driver, if it cannot find this driver then you will be prompted to insert the driver disc that came with your device. Common USB Device errors are ‘ usb port not working ‘, ‘device descriptor request failed error’ or ‘bugcodeusbdriver’ issues.

MCCI recently has invested a lot of energy supporting the project. This project has a simple (and possibly silly-sounding) goal: get “real” Windows 10 running on a Raspberry Pi 3.

With a USB-C connection, you can charge your Windows 10 PC, and you can also connect to other USB Type-C devices such as mobile phones, docking stations, display adapters, and other devices that have a USB-C port. The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf. The driver will identify in device manager as 'USB Audio Class 2 Device.' This name will be overwritten with a USB Product string, if it is available. The driver is automatically enabled when a compatible device is attached to the system. The MCCI® USB 3.0 Connection Exerciser Model 2101 automatically connects and disconnects a USB 2.0 or 3.0 host and device under push-button or software control. Connections can be single-stepped or repeated. The manual modes are useful for debugging attach/detach scenarios. QA teams find the automatic repeat modes useful for regression tests.

Many people have posted about the technical advances that have made this possible. Here’s a partial list.

  • The Raspberry Pi 3 supports the 64-bit ARM64 architecture.
  • Microsoft ported Windows 10 IoT Core (as a 32-bit operating system) to the Raspberry Pi, but targeted using the system for deploying embedded applications (kiosks, single-function computers). They omitted the features that make Windows 10 desktop a general-purpose system. (MCCI did the USB drivers for that project.)
  • Microsoft ported Windows 10 desktop to ARM64 systems. In this port, they included the key low-level drivers, apart from USB, needed for the Raspberry Pi.
  • Microsoft open-sourced the key ACPI / UEFI code needed to boot Windows 10 on a 32-bit Raspberry Pi.
  • Andrei Warkentin then adapted that and make a real ARM64 UEFI BIOS — this enables booting all kinds of “professional” operating systems on the Pi, not just Windows 10. He also managed to make USB work “well enough” to support keyboard and mouse — kind of important for setting up the BIOS!
  • José Manuel Nieto Sánchez organized a group of volunteers, and wrote an tool that would prepare an SD card with the required information from a Windows distribution, available through Windows Insider, MSDN, and other sources for non-commercial use.
  • Bas Timmer posted simple drivers that were enough to get Windows through the boot.
  • The group convinced Microchip to release ARM64 drivers for the USB Ethernet controller that’s on the Pi 3 mainboard.
  • Finally, the group hammered on me until I agreed to take the time to bring up the MCCI host stack (TrueTask USB) on ARM64.

The result was a flurry of world-wide attention. Perhaps predictably, there has been a lot of grumbling about performance. On the other hand, it looks a great demo for MCCI drivers; almost everything tested works. (It’s also a good demo for MCCI’s portability techniques; after four days of wrestling with the build system, the very first build we put on the hardware was the final version, apart from changing the version.)

MCCI has also put a lot of effort into organizing a website ( and a discussion site ( for the community, in collecting statistics, running the Twitter feed (@Pi64Win), and helping to publicize the effort.

So, the New York City question is: why do it? What’s your angle?

Of course, there is the basic commercial reason: to demonstrate that our drivers really are industrial strength in 2019. It was a big deal that our drivers were used in Windows 10 IoT Core, but that was a few years ago now. We can now point to a more recent success. In addition, there are a lot of device classes that were impossible to test on Windows 10 Core IoT, because of the difficulties in running regular Windows applications. It’s one thing for a webcam to enumerate; its another for it to actually stream interesting data to the application of your choice. It’s a lot easier to test if you can just spin up a video capture app. We can now point to public results from people testing our work. This is good, and so I thank the group for doing all the work to test and post results.

But there’s another reason, linked to MCCI’s social mission. We want to make a difference to people, not just to our customers.

Right now, cheap computing for people with few economic resources is subsidized (students are a prime example, but just one such group). Things like Chromebooks are subsidized by harvesting data; and they are limited in terms of what they can do (beyond the limitations imposed by their price).

That strikes me as wrong, and as a 19th-century way of solving the problem.

It’s already clear from group experiments that the Pi 3 is not that far away from being able to do significant work with Windows 10. If the group can make something useful to students and people with limited financial resources, it’s not a hobby: it can change lives.

The project very likely will not, in itself, put a $35 computer in every student’s backpack (though I wish it would). But it demonstrates what can be done with very low-cost hardware, and it serves as a proof of concept. It may motivate some of the other (larger) members of the ecosystem (Microsoft, the Raspberry Pi Foundation, the Mozilla Foundation) to come together to create a production version.Sometimes a proof of concept is what’s needed to break through inertia and doubt.

Drivers Mcci USB Devices

The easy way to test and debug driver load/unload problems.


Tired of manually plugging/unplugging USB devices to test or debug driver load/unload problems? Are you wearing out the connectors on your development PC? Is your prototype so fragile that plugging and unplugging risks damaging the unit? Want to run connect/disconnect tests overnight?


The MCCI® USB 3.0 Connection Exerciser Model 2101 automatically connects and disconnects a USB 2.0 or 3.2 gen1 host and device under push-button or software control. Connections can be single-stepped or repeated. The manual modes are useful for debugging attach/detach scenarios. QA teams find the automatic repeat modes useful for regression tests.

It’s an ideal tool for finding and debugging connect or disconnect bugs in host drivers and devices. Simply connect your host and device to the connection exerciser, supply power, and you’re ready to test. A single button push will connect or disconnect your device. Select “auto” mode to automatically repeat enumeration testing. Connect USB 3.2 Super Speed devices in high-speed mode to test backwards compatibility. Use a test control computer to automatically vary the test cycle time.


  • A single button push connects or disconnects your device from the host.
  • Tests low speed, full speed, high speed and super speed devices and hosts.
  • An impedance controlled, low loss USB data path. The Exerciser is transparent when in the connected state.
  • Data relays are rated to 7 GHz.
  • Data lines float when in the disconnected state.
  • VBUS and Data signals are connected and disconnected in the same sequence as if connected manually. Real USB connectors have different lengths for VBUS/ground versus D+/D-. This timing is mimicked.
  • The ground connection between host and device is never broken.
  • Connection time can be controlled down to 10 ms.
  • Device Under Test (DUT) VBUS is optionally configurable for flow-through or buffered operation. (In flow-through mode, your host provides the power to the device; in buffered mode, the connection exerciser provides power to your device. This is very useful if the host has a limited power supply or is battery powered.)
  • Can be powered from any of these three sources:
    • External 5 V power supply.
    • Control PC VBUS connection.
    • Host Under Test (HUT) VBUS power supply (optional).
  • No drivers need to be installed on the Control PC. The OS native HID drivers are used. The Control PC can be running Windows, macOS, or Linux (x86, amd64, or ARM – even a Raspberry Pi).

Block Diagram

What Is A Usb Devices

Table 1. Specifications

Size H x W x D111.25 x 75 x 25.2 mm (4.38 x 2.95 x .99”)
Weight9 oz
Power dissipation (all relays on; VBUS pass-through mode)1.75 W
Max Device VBUS current switch (VBUS pass-through mode)900 mA
Max Device VBUS current (VBUS buffer mode)900 mA
To UUT Host (on case front)USB 3.2 Std “B”
To UUT Device (on case front)USB 3.2 Std “A”
DC Input (on case back)2.1 mm round, center positive
To Control PC (on case back)USB 2.0 Std “B”
VBUS IN (on case front)On when Host VBUS is detected
Connect (on case front)On when Host is Connected to Device
VBUS OUT (on case front)On when VBUS is supplied to Device
Main Power (on case back)On when Exerciser is fully powered
PC Link (on case back)On when Control PC has enumerated Exerciser
Soft LEDs 1 through 4 (on case top)Used by Exerciser FW for various functions (see User Manual)
Mode Buttons
Momentary soft switches 1 through 4 (on case top)Used by Exerciser FW for various functions (see User Manual)
DC supply Input100 to 240 V AC; 50 to 60 Hz
DC supply Output5 V DC, 2.5 A max
Control PC4 foot STD “A” to STD “B” USB 2.0
Patch Cables1 foot STD “A” to STD “B” USB 3.2 gen1.

Kit Contents

Best Usb Devices

  • Model 2101 MCCI USB 3.0 Connection Exerciser
  • International Power Supply
  • USB 3.2 Patch Cable (for use from HUT to 2101 or 2101 to DUT) . The Connection Exerciser supports low speed, full speed, and high speed devices, but the patch cable uses a SuperSpeed B connector. If your product has a regular B connector, or a mini-B or micro-B connector, you’ll need to supply your own patch cable(s).
  • USB 2.0 Cable (for use from 2101 to Control PC)

Software and Documentation Downloads

Although no software is needed for standalone operation, MCCI provides scripting support for Windows, OS X, and Linux (x86, amd64 and ARM). The most recent software release is available as a free download. One distribution includes software for all supported platforms.