none
Release version still does not support popular USB serial devices? RRS feed

  • Question

  • I connected a pl2303 and ft232 usb to serial cable on the release version of core IoT from today.. Iotcore still doesn't seem to support or include drivers for these usb - serial devices.

    I've read somewhere that only silicon labs is supported, but can't find any official reference about it.

    Anyone has more information?


    • Edited by Flores Eken Tuesday, August 11, 2015 12:50 PM
    Monday, August 10, 2015 8:27 PM

Answers

  • Yes FTDI is definitely not supported at the moment.

    I have tested it and it doesn't load at all

    (Some USB devices will load but not function .. FTDI does not get to first base)

    It should be possible but not now.

    The Silicon labs one is what is used in the example/s

    The list of supported devices is here but for USB-Serial isn't specific

    It should say YES Silicon labs and No FTDI

    http://ms-iot.github.io/content/en-US/win10/SupportedInterfaces.htm

    "Silicon Labs CP210x chips will be supported on Raspberry Pi with an inbox driver" MS

    I am looking at the FTDI and other USB  issues.

    Watch my blog on Embedded101.com

    Cheers David Jones 
    Please vote if you find this helpful, thx.


    Embedded MVP



    Tuesday, August 11, 2015 12:13 PM

All replies

  • Yes FTDI is definitely not supported at the moment.

    I have tested it and it doesn't load at all

    (Some USB devices will load but not function .. FTDI does not get to first base)

    It should be possible but not now.

    The Silicon labs one is what is used in the example/s

    The list of supported devices is here but for USB-Serial isn't specific

    It should say YES Silicon labs and No FTDI

    http://ms-iot.github.io/content/en-US/win10/SupportedInterfaces.htm

    "Silicon Labs CP210x chips will be supported on Raspberry Pi with an inbox driver" MS

    I am looking at the FTDI and other USB  issues.

    Watch my blog on Embedded101.com

    Cheers David Jones 
    Please vote if you find this helpful, thx.


    Embedded MVP



    Tuesday, August 11, 2015 12:13 PM
  • thanks, this is helpfull.
    Tuesday, August 11, 2015 12:49 PM
  • Here's a sample project with an FTDI usb-to-serial device: https://github.com/Jark/FTDISample

    It won't work via the standard api's but it works via a FTDI device driver that you have to install yourself, all instructions can be found on the link above.

    Any questions let me know.


    Saturday, August 22, 2015 8:49 PM
  • It is up to FTDI, Silicon :Labs, Prolific etc to provide drivers. While MSFT might be able to prod them, it is not MSFT that supplies those drivers.

    The FTDI solution posted above uses http://www.ftdichip.com/Drivers/D2XX.htm, not the Virtual Com port that we would all prefer to use. But it does seem to work on Win IoT /Raspi so for now it might be your only way. I will be making that decision son for my Xbee project since my adapters all use FTDI chips :-(

    Saturday, August 22, 2015 11:32 PM
  • Great work Jack.

    I was considering working through doing what you have done.

    You've saved me the effort. I'll give it a try.

    I'm blogging an extended series of RPI2 USB peripherals and am currently doing a serial blog so this is quite timely.

    PS Gerrit, I note your comment in the blog as well.

    http://embedded101.com/blogs/david-jones


    Embedded MVP

    Sunday, August 23, 2015 10:12 AM
  • Excellent blog, I will add it to my reading list :-)

    Regarding the built in serial pins, there is a hint here that provides info on enabling/disabling WinDbg on those pins.

    And thanks to Jack I have a Plan B for my sensor network.

    Gerrit

    Sunday, August 23, 2015 12:26 PM
  • I copied those files using FTP:

    ftdi.d2xx.winrt.cat and FTDI.D2xx.WinRT.inf from lib\D2xx WinRT 1.0.2\driver

    I then connected via Powershell and ran the following:

    [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

    ????????


    Embedded MVP

    Sunday, August 23, 2015 2:23 PM
  • Can you double check that the files exist in the c:\windows\system32 folder on the raspberry pi?

    Also, I'm not familiar with using ftp to put files on the raspberry pi and don't know what kind of security permissions the files would get.

    If the files do exist in the c:\windows\system32 folder try copying them over using the smb protocol (\\minwinpc\c$).

    I've turned alerts on, so I should be able to reply a bit quicker now :) Good luck and let me know how you get along.

    Sunday, August 23, 2015 11:37 PM
  • I copied them across via smb as above.

    An issue (for others) was login credentials.
    Has to use minwinpc\administrator for the login name when prompted.

    The driver is now "sort of" loaded:

    ==================================
    [minwinpc]: PS C:\Users\Administrator\Documents> devcon status "USB\VID_0403&PID_6001"
    USB\VID_0403&PID_6001\FTG71BUI
        Name: US232R
        The device has the following problem: 28
    1 matching device(s) found.
    ==================================

    This is more than yesterday but not enough.
    A web search found the following:
    ===================================
    Re: DevCon & USB Device ErrorCodes
     
    http://msdn.microsoft.com/library/de...2be629.xml.asp
     CM_PROB_FAILED_INSTALL The device's drivers are not installed. Error Code 28

     Examine setupapi.log for exact reason of failure.
    ===================================

    If I examine the USB peripheral drivers on minwinpc via the web interface:

    ACPI\Microsoft DWCHSOTG USB Host Controller\DwcHsOtg USB Root Hub\Generic USB Hub

    I now get US232R on this USB branch

    But I get a similar result to the devcon status query when expanded:

    ==========================

    Properties:

    ID : USB\VID_0403&PID_6001\FTG71BUI

    Description : US232R

    StatusCode : 25191424

    ProblemCode : 28

    ===========================


    Embedded MVP

    Monday, August 24, 2015 12:24 PM
  • Thanks for the info, I'll amend the steps on https://github.com/Jark/FTDISample#installing-the-ftdi-d2xx-drivers-on-the-raspberry-pi to mention that.

    Did you do a restart after installing the device drivers? This is necessary to let the device function properly.

    Also, what version of Windows IOT are you using? When I get home I'll have a look and see with what version of Windows IOT the drivers are working.
    • Edited by Jark.Reijerink Monday, August 24, 2015 12:40 PM added extra question
    Monday, August 24, 2015 12:34 PM
  • - Yes I did a restart , a couple

    - I'm using the RTM version 10240

    Device Name: minwinpc
    Device Model: Raspberry Pi 2 Model B
    OS Version: 10.0.10240


    Embedded MVP


    Monday, August 24, 2015 12:45 PM
  • For my tries I was using an FTDI USB-RS232 Dongle.

    I just tried another FTDI device and got:

    [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.

    What FTDI device are you using?


    Embedded MVP

    Monday, August 24, 2015 1:00 PM
  • Did you try the test app to see if it works anyway? I can have a look tonight and see what version I'm using, but that version number looks like what I have.

    Other than that only things I can think of is:

    - the pi might not like it when you keep usb-to-serial connected during boot (haven't tested it with that)

    - there is no ftdi.d2xx.winrt.cat file next to the inf file in the c:\windows\system32 folder (but you seeing the adapter in the device manager would suggest otherwise)

    - your version of the ftid usb-to-serial is a "fake" chip and the drivers don't work properly with that, ftdi have a history of creating drivers that detect "fake" chips and make them fail in subtle (or less subtle) ways ( https://thecounterfeitreport.com/product/562/FTDI--Chip-FT232RL-Chips.html).

    - you could try removing the driver (https://msdn.microsoft.com/en-us/library/windows/hardware/ff545861(v=vs.85).aspx) and reinstalling it without the ftdi adapter attached

    Sorry I can't provide more help than this, the driver did work for me and a friend of mine.

    Monday, August 24, 2015 1:08 PM
  • For my tries I was using an FTDI USB-RS232 Dongle.

    I just tried another FTDI device and got:

    [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.

    What FTDI device are you using?


    Embedded MVP

    I'm using a F232R ->  see https://github.com/Jark/FTDISample/blob/master/screenshot1.png for the version string, vid/pids look to be the same.

    • Proposed as answer by gerrit_v Tuesday, August 25, 2015 12:31 PM
    Monday, August 24, 2015 1:10 PM
  • I tried all of that, no luck.

    I even tried a fresh image (same outcome):

    [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.

    [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.

    I'll raise this with other Embedded MVPs and see if they have any ideas. 

    Thx Jark for your assistance.


    Embedded MVP



    Monday, August 24, 2015 1:12 PM
  • Problem solved. You need a full path to the .inf file.
    Works now... Yeah

    Just updated my blog on this issue:

    http://embedded101.com/Blogs/David-Jones/entryid/666/Win-10-IoT-FTDI-Serial-Driver


    Embedded MVP



    Tuesday, August 25, 2015 5:00 AM
  • See my post ay bottom for update.

    Thanks Jark for doing the leg work.


    Embedded MVP

    Tuesday, August 25, 2015 6:58 AM
  • Problem solved. You need a full path to the .inf file.
    Works now... Yeah

    Just updated my blog on this issue:

    http://embedded101.com/Blogs/David-Jones/entryid/666/Win-10-IoT-FTDI-Serial-Driver


    Embedded MVP



    Devcon could've thrown a relevant exception... I guess I didn't realise I was in the c:\windows\system32 folder when I entered the command! Again, will update the github repository with the added info.
    Tuesday, August 25, 2015 8:01 AM