Hey there! Let me break down what you've stumbled on and walk through your questions step by step—this is a super cool deep dive into ChromeOS's internals, nice catch!

What's that test device feature actually for? #

That USB test device tool in chrome://usb-internals/ is part of ChromeOS's built-in USB testing framework, designed primarily for developers. Its main job is to let you simulate USB device behavior without needing physical hardware. This is huge for testing things like:

• How ChromeOS handles different USB device classes (HID, storage, custom devices)
• Whether web apps using the WebUSB API can properly communicate with a device
• Debugging driver compatibility issues for new USB hardware

The URL bar you noticed? That's meant to link to a test web app. When you create the test device, the notification prompts you to open that app because it's supposed to interact with the simulated device—think of it as a way to pair your test device with a piece of software that can send/receive data to it, validating the full workflow.

Can you create your own version and run it on your Chromebook? #

Absolutely! Here's how to get started:

• Enable Developer Mode on your Chromebook: This unlocks access to deeper system tools and removes some restrictions on USB debugging.
• Tweak the test device settings: In chrome://usb-internals/, you can customize the test device's VID/PID (Vendor/Product ID), device descriptors, and endpoint configurations to match whatever device type you want to simulate.
• Build a simple web app with WebUSB API: Write a basic web app that uses the WebUSB API to request access to your simulated device, send test commands, and read responses. This lets you replicate the interaction you saw with the default test setup.

Note: Google has shifted to the WebUSB API for modern web-based USB interactions (moving away from older Chrome Apps), so focus on that framework for your projects.

Making a physical USB device that replicates the test device behavior #

This is totally doable, but it requires a bit of hardware know-how. Here's a high-level plan:

• Pick a microcontroller: Cheap options like Arduino (boards with native USB device mode) or ESP32 work great. These can be programmed to mimic almost any USB device type.
• Program the firmware: Write code for your microcontroller to simulate the USB device parameters you used in the chrome://usb-internals/ test (same VID/PID, device descriptors, etc.). For example, if you want to simulate a custom data device, you'd set up USB endpoints to send/receive data packets.
• Pair with your web app: Once you plug the physical device into your Chromebook, you'll need to grant your web app access to it (via Chrome's USB permission prompt). Then your app can interact with it just like the simulated test device—sending commands, reading data, etc.

A quick heads-up: By default, Chromebooks might restrict access to uncertified USB devices. Enabling Developer Mode will help bypass most of these restrictions, making it easier to test your custom hardware.

备注：内容来源于stack exchange，提问作者LilData777