USB consol not working on Verdin dev board with Verdin AM62 512MB

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


Let me help you troubleshoot the USB console connection on your Verdin Development Board with Verdin AM62 512MB.

Troubleshooting Steps

1. Check USB Cable Quality

The USB Type-C cable you’re using may be missing data lines or be of poor quality(1). Many modern USB-C cables are charge-only. Try using a different USB-C to USB Type-A cable that you know supports data transfer(1).

2. Verify Power Supply

Ensure the Verdin Development Board is properly powered. The board should be powered on before you connect the USB cable to X66(2).

3. Identify the Correct Serial Port

The Verdin Development Board has an integrated Serial-to-USB converter that lists 4 serial ports on your computer(2).

The highest index is the Linux serial console(2). For example:

  • If you see /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, and /dev/ttyUSB3 listed, then /dev/ttyUSB3 is the serial console(2)
  • The same logic applies to Windows COM ports(2)

4. Install FTDI Drivers (Windows)

If you’re using Windows and no ports appear in Device Manager, you may need to install the FTDI drivers(1). Check Device Manager under “Ports” or “Universal Serial Bus controllers” for any devices with yellow exclamation marks(1).

5. Connection Parameters

Once you identify the correct port, use these serial parameters(2):

  • Baud Rate: 115200
  • Parity: none
  • Bits: 8
  • Stop bits: 1
  • Flow control: none

6. Important Warning

Do not connect to the first or second port (for example /dev/ttyUSB0 or /dev/ttyUSB1)(2). If you do, you will not be able to use the board because those ports are dedicated to power/reset control and FTDI JTAG(2). Just close those connections and reset the board if this happens(2).

Additional Information

Could you also confirm which OS and version you’re running on your Verdin AM62? This will help me provide more specific guidance if needed. You can use the tdx-info command on the module to get this information: tdx-info documentation

**


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.