There is currently no support for FTDI USB Serial with Windows 10 IoT although I suggested that the FTDI Surface 2 D2XX ARM driver might work. Jark has developed a Universal (UWP) app along with installation instructions using this idea. He has been able to make it work which I originally couldn’t do .. I now can!
…Solved. FTDI now works on RPI2.
This is also a good intro to loading custom drivers
:
Attempt to load driver then to get its status:
[minwinpc]: PS C:\Users\Administrator\Documents> devcon.exe dp_add FTDI.D2xx.WinRT.inf Adding the specified driver package to the machine failed. devcon.exe : devcon.exe failed. + CategoryInfo : NotSpecified: (devcon.exe failed.:String) , RemoteException + FullyQualifiedErrorId : NativeCommandError
[minwinpc]: PS C:\Users\Administrator\Documents> devcon status "USB\VID_0403&PID_6001" USB\VID_0403&PID_6001\GTB8EJM9 Name: USB I/O 24 II The device has the following problem: 28 1 matching device(s) found.
Copied the two files to C:\temp on the device.
[minwinpc]: PS C:\Users\Administrator\Documents> devcon.exe dp_add c:\temp\FTDI.D2xx.WinRT.inf Driver package 'oem0.inf' added.
Seems it needs a full path.
After rebooting (this IS required):
[minwinpc]: PS C:\Users\Administrator\Documents> devcon status "USB\VID_0403&PID_6001" USB\VID_0403&PID_6001\GTB8EJM9 Name: USB I/O 24 II Driver is running. 1 matching device(s) found. [minwinpc]: PS C:\Users\Administrator\Documents>
And Jark’s app now works:
FTDI on RPI2: We now have a lift off!
Actually... I think I may have figured it out. I think my device ID is different from the one you and Jark used. Instead of typing: devcon status "USB\VID_0403&PID_6001" I typed: devcon status "FTDIBUS\COMPORT&VID_0403&PID_6015" And this returned more hopeful output: FTDIBUS\VID_0403+PID_6015+\0000 Name: USB Serial Port Driver is running. 1 matching device(s) found. Unfortunately, I can't get Jark's FTDISample app to work. His Github page now says "As of version 10556.0 the ftdi driver does no longer seem to work." Have you had any luck with subsequent builds of Win IoT?
Thanks for this helpful guide, Dave. Unfortunately it doesn't seem to be working for me. I've got Windows IoT Core running on a new Raspberry Pi 3, started up ftpd.exe so I could transfer the files over to C:\Temp, as you suggested. After running the dp_add command you have, I got the same Driver package 'oem0.inf' added" message that you did. However, even after a restart, the devcon status command always returns "No matching devices found." Any tips?