Jump to content
  • 0

JTAG-SMT2 Connection Issue to Xilinx Vivado


nicol

Question

We have a board that uses the JTAG-SMT2 module to interface a Xilinx Zynq device. Most modules work without any issues, however one refuses to connect to the Zynq device. When first plugged into a computer (reproduced on 3 separate systems), it installs the FTDI driver for ‘USB serial converter’ properly. The misbehaving module installs an additional COM port driver and shows up as COMx. All the other working modules don’t install the COM driver.

Disabling the VCP option did not make a difference.

Version of the FTDI driver is 2.12 but also 2.10 and 2.8 did not seem to work.

Is there any settings to make the driver work, either in Windows device manager or FTDI FT_PROG?

Link to comment
Share on other sites

Recommended Posts

We have a board that uses the JTAG-SMT2 module to interface a Xilinx Zynq device. Most modules work without any issues, however one refuses to connect to the Zynq device. When first plugged into a computer (reproduced on 3 separate systems), it installs the FTDI driver for ‘USB serial converter’ properly. The misbehaving module installs an additional COM port driver and shows up as COMx. All the other working modules don’t install the COM driver.

Disabling the VCP option did not make a difference.

Version of the FTDI driver is 2.12 but also 2.10 and 2.8 did not seem to work.

Is there any settings to make the driver work, either in Windows device manager or FTDI FT_PROG?

Some more details:

A good SMT2 device enumerates with:

Vid: 0x0403 (=FTDI Limited)

Pid: 0x6014

Manufacturer string: "Digilent"

Product string: "Digilent USB Device"

Serial #: "210251A00BD4"

The misbehaving device enumerates with:

Vid: 0x0403 (=FTDI Limited)

Pid: 0x6014

Manufacturer string: "FTDI"

Product string: "Single RS232-HS"

Serial #: "0"

 

Looks like the 'bad' device did not get programmed with SMT2 specific data.

Is there a way to program correct data into the module?FTDI's FT_PROG did see this module as FTDI device of unknown type and did not open the window with all device information present.

Thanks in advance.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...