Surface Pro X USB-C to RS232 issues

I'm curious which USB to Serial adapter you've tried. I got one with an FTDI chip and Windows 10 (x64 or ARM) does not have built-in drivers, and they currently have no ARM64 driver available to download. Ironically they do have a driver for Windows RT (ARM32), so I emailed their support to see if they would release a driver for Windows 10 ARM.

Edit, I got a reply already with a link to a Beta driver. It's great to see they are working on supporting Windows ARM64 architecture!

Edit, I got a reply already with a link to a Beta driver. It's great to see they are working on supporting Windows ARM64 architecture!

Did you get the driver working? I would love to get this going also!

Hey all.

Yes and no. I got the driver to install, but for some reason I can't seem to use it. I'm not sure what COM it should be, but I never see another one show up other than the Pro X UART devices that were already installed and listed as COM3 and COM4. I was expecting to see a COM1 or COM2 be listed under Ports but it isn't:

Anyway, the driver link they sent me is on a public ftp server so I don't see an issue with sharing it:

CDM v2.12.32.B3for ARM64.zip

(edited with shortened link)

They also sent pdf instructions on how to disable the driver signature verification but that can be found on the internet, and I don't see a way to attach a pdf file to this forum.

These are the comments in the email I got back:

------------------------------------------------------------

This is a beta only and was tested on a Lenovo Yoga C630. There are a few known limitations:

 1. The serial enumerator hasn't been tested since there is no serenum.sys on this particular machine. FTDIPORT.inf has commented out the reference to serenum.  It was needed to fix a problem with installing on build 1903.

2. D2XX applications for x86 can run in emulation mode on Win10 ARM64, so we've bundled the x86 D2XX library in the release.

3. The ARM driver is digitally signed but the OS may complain ‘device not migrated’ and refuse to install the driver. In that case, disable the OS certification check. See attached document on how to do this.

The COM port works ok however and so may support your devices.

------------------------------------------------------------

I did have to disable the digital signature verification, and it's rather annoying to do that in windows 10 (which does not persist on a normal reboot), and that's compounded by the fact that these machines have bit locker enabled too.

Maybe I've done something wrong, not sure. I was trying to test this using an ARM64 build of Putty that I got from someone on XDA Developers and was trying to open the terminal of a network switch which in theory should work. What app are you guys using?

Maybe one of you will have better luck than I have so far.

Hi DomFriant,

That FTP Link you gave doesn't work? Any chance you could check and repost?

Weird. Ok, trying again, as a plain-test post instead of a link:

ftp://u45902898-ide:*** Email address is removed for privacy ***/CES/CDM%20v2.12.32.B3%20for%20ARM64.zip

Edit:

Argh, I'm not sure why this link is such a pain. 

I'm not sure why this link is such a pain

Because it includes an email address and the forum software strips that out.
--
--

Anyway, the driver link they sent me is on a public ftp server so I don't see an issue with sharing it

The forum rules here are that this is someone's intellectual property and don't
allow uploading to a personal drive and sharing, so in spite of your good
intentions, it was removed. Can you use a link shortener to link to the file on
the source ftp server?

Oh yeah, I'm sorry about that, I completely forgot about that forum rule. Not sure why I didn't think to use a link shortener; I guess I was in a hurry. It's not really an email address, but looks more like a user@site type of ftp login, but I guess the forum filters anything matching that form. Oh well.

Let's see if this link works.