COM Port Redirection not detecting TI board in AVD

Question

This is a follow-up query of this post: https://learn.microsoft.com/en-us/answers/questions/2275784/running-ccs-on-azure-vm-with-local-board-connectio

I have set up a host pool & configured AVD. As per the suggestion in the above post, I have tried out the USB redirection mechanism following this documentation. Since I've Windows 11 home edition, the group policy wasn't there by default, so have used the Policy Plus (taking reference from other resources available on the net, with one being this).

In step 4 of Test USB redirection, the Remote Desktop app has been used to configure something further but since its support will end soon, so I used Windows App for the remote connection and couldn't find those settings over there.

But what I could find is that my local C drive and the contents of HDD when connected to my laptop could be seen in the remote VM. Can I say that the USB redirection has worked successfully?

The issue is that when I connect the TI board, I see the COM ports in the local machine's device manager along with the XDS110 debug probes by TI.
\

But in the VM, even after I've installed the drivers, I see like this:

I have done COM PORT redirection as well following this.
On clicking one of the debug probes, I see this:

While the same thing on local machine shows "This device is working properly." under Device Status.
What am I missing?

Answer 1

Hi, you’re not seeing the board in your AVD session because the Windows App client doesn’t support USB redirection, only drive redirection. To get USB working (like for a TI XDS110), you need to:

-Use the MSI Remote Desktop client (or the Store UWP app), not Windows App or the web client.

-Run Windows Pro/Enterprise/Education locally, Home doesn’t support USB redirection.

-On your local PC, set these registry keys:

-EnableUsbDeviceRedirection = 1

-Whitelist the device with:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Terminal Server Client\USB]

-Reconnect with the MSI client, it’ll prompt you to pick USB devices before login. Tick both XDS110 entries.

-Inside the VM, open Device Manager, you should now see the board as a working USB RDP device and redirected COM ports.

The yellow “Code 10” error happened before because the Windows App installed the driver, but never passed through the actual device. With the right client and config, USB redirection works and CCS (or any serial tool) can talk to the board over the redirected COM port.

Switch to the MSI Remote Desktop client, set the right registry keys, whitelist the USB device, and enable redirection in the VM. That’s how to get hardware like XDS110 working over AVD.

Answer 2

Hey there!

Thanks for posting your question on the Microsoft Q&A portal it's great that you're working with com port redirection in avd and trying to connect your ti board ))

From what I see, your com port isn’t being detected properly in avd, which can be super frustrating. Let’s break this down step by step to figure out what’s going on.

Let's sure com port redirection is actually enabled in your avd setup. This feature isn’t turned on by default, so you’ll need to configure it in the remote desktop client or through group policy if you’re managing multiple machines. Here’s Microsoft’s guide on setting up com port redirection: Configure COM port redirection in AVD.

Next, check if the com port is available and correctly recognized on your local machine. Sometimes the port might be in use by another application or not properly installed. You can verify this in the device manager under "ports (com & lpt)." If it’s not showing up, you might need to reinstall the drivers for your ti board.

Also, make sure the remote desktop client has the right permissions to access the com port. Some security settings or admin restrictions can block redirection. If you’re using the web client, keep in mind that com port redirection isn’t supported there—you’ll need the full remote desktop client for this.

If you’ve checked all that and it’s still not working, maybe the ti board requires specific baud rate or port settings that aren’t being passed through correctly. You might need to configure the port settings manually in the remote session.

Let me know if this helps

Best regards,
Alex
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment
https://ctrlaltdel.blog/