Unable to establish serial connection using USB type C port X66 with my windows host PC

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello,

To establish a serial connection between your Verdin development board and a Windows PC using the USB Type-C port, please follow these steps:

  1. Verify Driver Installation: Ensure that the FTDI driver is correctly installed. The presence of ftd2xx.dll in C:\Windows\System32 is a good sign. However, double-check that the driver is properly associated with the USB device by:

    • Opening Device Manager on your Windows PC.
    • Expanding the ‘Universal Serial Bus controllers’ section.
    • Looking for any devices with a yellow exclamation mark, which indicates a driver issue.
  2. Check USB Connection: Confirm that the USB Type-C cable is functioning correctly. Try using a different cable or port on your PC to rule out hardware issues.

  3. Device Recognition: If the device is not recognized at all, it might be due to a power issue or a faulty connection. Ensure the board is powered on and the connection is secure.

  4. Alternative Connection Methods: If the USB Type-C port continues to be unrecognized, consider using another method to establish a serial connection:

    • Use a different USB port on the development board if available.
    • Try connecting via Ethernet and using SSH if the board is network-enabled.
  5. Terminal Emulator Setup: Since your PuTTY connection is working, ensure that the correct COM port is selected in PuTTY. If the device is recognized, it should appear as a COM port in Device Manager.

  6. Reinstall Drivers: As a last resort, uninstall the FTDI drivers and reinstall them. Sometimes, a fresh installation can resolve recognition issues.

By following these steps, you should be able to troubleshoot and establish a serial connection between your Verdin development board and your Windows PC.

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

DBG_CTRL and unexpected board shutdown.