How to install Silicon labs CP210x USB to Serial driver on Windows 10 IoT Core

2018-01-18

Question

_{Thursday, January 18, 2018 9:43 AM}

I am trying to connect a PCB with a CP2102 IC to an RPi 3 running windows 10 iot core but it does not get detected. I followed the steps described in "Lab 1a: Create a basic image" (https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-a-basic-image) to build an image. The CP2102 driver is supposed to be included by default ( IOT_CP210x_MAKERDRIVER in TestOEMInput.xml) but it appears that this is not the case. Can you please help!

All replies (12)

_{Thursday, January 18, 2018 10:22 AM}

Where does I say it is included by default? Last time I looked this was a third party driver from the maker community.

It can be added quite easily but is not included by default?

Dave

_{Friday, January 19, 2018 7:39 AM | 2 votes}

Hello Mtheolog,

You can create your own BSP with CP210X drivers by following this guide. In the feature list of Windows IoT Core, OT_CP210x_MAKERDRIVER has been added for SiliconLabs CP210x-based USB to Serial adapters, it is new in Windows IoT Core 15063.

Best Regards

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Friday, January 19, 2018 10:24 AM | 1 vote}

hello

beside creating your own BSP Michael Xu-MSFT mentioned you could manually install the driver on to your device

download "Windows 10 IoT Core Packages - Build 16299" from https://www.microsoft.com/en-us/software-download/windows10iotcore#! and install the ARM msi and follow "Step 3" at /en-us/windows/iot-core/build-your-image/createinstallpackage#step-3-install-on-device

(you will find the installed available packages at C:\Program Files (x86)\Windows Kits\10\MSPackages\retail\arm\fre)

br
Andre

_{Friday, January 19, 2018 12:51 PM}

Thanks both of you.

Michael, I followed the suggested guide and I created an new product based on BSP CustomRpi2 (provided at IoT-ADK-AddonKit\Source-arm\BSP) and created its image. Our PCB with a CP2102 IC is still not detected.

Andre, I followed the suggested steps by copying the C:\Program Files (x86)\Windows Kits\10\MSPackages\retail\arm\fre\Microsoft-IoTUAP-CP210x-MakerDriver-Package.cab to c$\OemInstall folder. After applyupdate -commit command, the Rpi3 reboots, but the problem remains. Our PCB with a CP2102 IC is still not detected.

regards, Maria.

_{Monday, January 22, 2018 9:09 AM}

Hello Mtheolog,

Have you checked the driver in Windows Device Portal? When the device is plug-in, please save the file of device information in device portal.

In the downloaded file(DeviceTree.txt), please check whether there is the device information as following:

(ID:USB\VID_0424&PID_9514&DWCHSOTGHUB\4&B947FD8&0&1, Class:USB, Manufacturer:(Generic USB Hub), StatusCode:25182218)
                        >Silicon Labs CP210x USB to UART Bridge
                        (ID:USB\VID_10C4&PID_EA60\0001, Class:Ports, Manufacturer:Silicon Labs, StatusCode:25190410)

If the information exist,it indicates that the driver for CP210x is installed successfully and the device can be detected, you need to check your code. You can refer to the sample of SerialUART. I have tested on Raspberry Pi3 running with Windows IoT Core 15063, it works without installed the driver manually.

Best Regards,

Michael

_{Tuesday, January 23, 2018 1:36 PM}

Hello Michael,

In the DeviceTree.txt there is no such information. I have tried out on a Raspberry pi 3 with windows iot core 16299 and a Dragonboard 410c (with same release of OS).

I have also re-run your first suggestion to create a new product based on CustomRpi2 BSP (provided at IoT-ADK-AddonKit\Source-arm\BSP) . During this, I've noticed that some cab packages are explicitly listed in the CustomRPi2FM.xml (such as RASPBERRYPI.RPi2.BootFirmware.cab, RASPBERRYPI.RPi2.dwcUsbOtg.cab etc). So I modified the CustomRPi2FM.xml with the following entry

in the <BasePackages> section. But the createimage command fails with the following:

........

info: FeatureAPI: Successfully validated the Feature Manifest XML: C:\Users\Mtheolog\iot-adk-addonkit-master\Build\arm\MergedFMs\CustomRPi2FM.xml
ThreadId1 ERROR: CbsPackage::CheckCBSFeatureInfo: Feature(featureId:BASE) inside FM(featureManifestId:CustomRPi2) contains multiple FIP packages:
ThreadId1 ERROR: Microsoft.IotUAP.MS_IOT_CP210x_MAKERDRIVER.IOT.FIP
ThreadId1 ERROR: Nydor.BASE.CustomRPi2.MainOS
fatal error : Imaging!ProcessCompDBPackages: FIP information in FM 'CustomRPi2FM.xml' packages for the following Features are incorrect:
fatal error : Error : BASE
info: Imaging: See Flash.cbs.log and Flash.csi.log for details.
info: Imaging: Performance Results:
info: Total Run Time: 00:00:00.8100923
info: Storage Stack Time: 00:00:00
info: CompDB Total Time: 00:00:00.4701479
ImageApp: Error log can be found at 'C:\Users\Mtheolog\IOT-AD~1\Build\arm\TEO\Test\Flash.ImageApp.log'.
"CreateImage TEO Test" failed with error 1

I can not figure out what could be causing this error.

Best Regards,

Maria.

_{Wednesday, January 24, 2018 3:03 AM}

Hello Mtheolog,

Did you check the information while the device is plug-in on you board Raspberry Pi 3 or Dragonboard 410c with Windows IoT Core 16299? If it is plug-in and there is no such info, I think you need to check the device is fine or bad.

For the building error, I think you should use Microsoft-IoTUAP-CP210x-MakerDriver-Package.cab. and you should add the **PackageFile **node in <OEM> section like following:

    <OEM>
      <!-- Optional Device Drivers -->
      <PackageFile Path="Microsoft-IoTUAP-CP210x-MakerDriver-Package.cab">
        <FeatureIDs>
          <FeatureID>RPI2_DRIVERS</FeatureID>
        </FeatureIDs>
      </PackageFile>
      ...
      ...
    </OEM>

Maybe the driver has been included already in the BSP, if you encounter the below error when building the image:

The package 'C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\ARM\fre\Microsoft-IoTUAP-CP210x-MakerDriver-Package.cab' is contained in more than one feature specified by the OEMInput entries.

In fact, it is not necessary to build your custom image just for adding CP210X driver except there are other requirements for you.

Best Regards,

Michael

_{Wednesday, January 24, 2018 9:30 AM}

Hi Michael, thanks for the info.

I created a basic image ProductA based on rpi2 BSB and it appears that the driver is indeed included as specified in the ProductAtest.log:

info: [00:03:28] Queueing package install for: \?\C:\Users\Mtheolog\AppData\Local\Temp\IMG2328.tmp\Data\12312\USERS\System\AppData\Local\UpdateStagingRoot\mainos\TempSxS\Microsoft-IoT-PowerShell-Package_Lang_en-US~31bf3856ad364e35~ARM~en-US~10.0.16299.15.mum
info: [00:03:28] Queueing package install for: \?\C:\Users\Mtheolog\AppData\Local\Temp\IMG2328.tmp\Data\12312\USERS\System\AppData\Local\UpdateStagingRoot\mainos\TempSxS\Microsoft-IoT-Ssh-Server-Package~31bf3856ad364e35~ARM10.0.16299.15.mum
info: [00:03:28] Queueing package install for: \?\C:\Users\Mtheolog\AppData\Local\Temp\IMG2328.tmp\Data\12312\USERS\System\AppData\Local\UpdateStagingRoot\mainos\TempSxS\**Microsoft-IoTUAP-CP210x-MakerDriver-Package~31bf3856ad364e35~ARM10.0.16299.15.mum**
info: [00:03:28] Queueing package install for: \?\C:\Users\Mtheolog\AppData\Local\Temp\IMG2328.tmp\Data\12312\USERS\System\AppData\Local\UpdateStagingRoot\mainos\TempSxS\Microsoft-IoTUAP-DataPartition-ImageCustomization-Package~31bf3856ad364e35~ARM~~10.0.16299.15.mum

However the device is not recognized in RPi 3 (it is not included in DeviceTree.txt while the device is plug-in) although it is detected ok on laptops with windows 10 or ubuntu. I will try a new device as well and get back to you.

Regards,

Maria.

_{Thursday, January 25, 2018 1:47 PM}

Hello Michael,

We have tried two different devices with CP2102 and none of them are recognized by Rpi3 while they are working fine with Windows 10 and Linux laptops (Intel architecture). I am inclined to believe that either the Silicon labs windows 10 - arm driver is problematic or the windows 10 iot core support for CP2102 has a problem (although you said it worked fine for you in an older edition though!).

I have no idea what to try next. Any suggestions would be welcome.

Thanks, Maria.

_{Friday, January 26, 2018 8:03 AM}

Hello Maria,

Is it impossible due to the PCB? Is it customized ?

Best Regards,

Michael

_{Friday, January 26, 2018 8:42 AM}

Hi Michael,

The PCB is customized, but the peculiar thing is that the same PCB works fine with Windows 10 and Linux laptops (Intel architecture). This is what puzzles me. Could it be a problem with the current windows 10 iot core 16299 release that we are using?

Thanks, Maria.

_{Friday, January 26, 2018 9:54 AM}

Hello Maria,

I don't think it is a problem with current windows 10 IoT Core 16299,in fact it works on my device. You need to check the layout design of your PCB with CP2012 IC, especially about the GND pin. The Silicon Labs CP2102 based USB-to-TTL module is official recommended,you can see in this sample.

Best Regards,

Michael

Share via

How to install Silicon labs CP210x USB to Serial driver on Windows 10 IoT Core

Question

All replies (12)

Additional resources