CP210x USB to UART Bridge VCP Drivers (code 10 in windows device manger)

Greetings

I'm trying to establish communication between Digilent FPGA board with Xilinx Zynq platform and matlab for my university project. As per matlab instruction, it is required to assign USB UART connection such as Silicon Labs CP210x USB to UART Bridge or Cypress Serial. However, I'm geting code 10 in windows (8.1, 10, 11) device manager. I tried different solutions suggested in the internet but they didn't work.

I appreciate your support to share with me what kind of computer specificaiton and windows version have been tested to have successful installation of Silicon Labs CP210x USB to UART Bridge or Cypress Serial. I have tried different computers and virtual machine but no result to install the drivers without errors

Answer 1

[Tom Richter]

Hello Ali,

I had to install the driver recently to connect the ZCU102 board to a computer with no Vivado Installation (that often installs the driver already). I downloaded the driver here: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers?tab=downloads (CP210x Universal Windows Driver). After installation I had to go to the device manager to update the driver for the device(s). After that, the UART interface worked. I tested it with PuTTY (the com-Port can be found through the Device Manager as well). It looked then like this:

After opening the connection, I have access to the linux shell.

Best regards,

Tom

[Ali Alramadhan]

Thank Tom for your response. I started over by uninstalling all drivers first, then I followed your guide, but it didn't work

please see the attached PDF, where I showed 7 brief steps on what I did, it might be something missing.

I appreciate your feedback

[Tom Richter]

Can you try to update the driver again after installing? On page 3 of your PDF, the last image shows an exclamation mark. Right-click this device and say update driver, manual path, and enter the path to the installation or unzipped files. If this still fails and you also find no one else who can successfully get it running, you device could be broken.

Best regards,

Tom

[Ali Alramadhan]

I believe I'm one step a head now, thanks to your hints

updating CP210x driver already done by uninstalling, reinstalling, update driver manually several times and PC restarted several times during the process, but didn't resolve anything.

I believe the device is healthy since I programmed zybo board by completing the tutorials from digilents through Vivadio software. Also, I notice once I connect the board to the PC, FTDI driver comes as COM4 port. I'm not sure how CP210x can be linked to zybo board and if it is actually needed to establish the communication as per matlab instructions. FTDI is also virtual com port driver like CP210x.

I manage to establish successul communiction between Putty to zybo board by selecting FTDI port (COM4).

however, when I tried to ping from matlab to zybo board or establish ethernet commenction (SSH) from putty to zybo borad, the communication failed using the obtained IP adress "192.168.1.101" from above picture.

I ensured ethernet cable is heathy and connected between PC and the board, also the board can recognize once ethernet cable is connceted (link up) or disconnection (link down)

I appreciate if you can share with me any more hints to resolve IP communication, and if CP210x is needed in this process.

Answer 2

[Steve Kuznicki]

Hi Ali,

Did you resolve this issue?

I did not see how you are connecting the Ethernet between the Zybo board and your PC.

The FTDI driver (USB to UART) is not needed to resolve any eth0 communications. That is used to connect a terminal application like PuTTY to the zybo using the Serial (USB) port. It's convienent so you have a terminal to further set up your board.

If you are using an Ethernet-to-USB adaptor on your PC, make sure that you set this to a STATIC IP Address of something like 192.168.1.100 (mask 255.255.255.0). You should be able to ping both ways (PC to Zybo and Zybo to PC). If you can only ping one way, then you may have issues with Firewall software running on your PC.

Thanks! Hope this helps.