Search the Community
Showing results for tags 'jtag-smt2-nc'.
Found 3 results
I have designed a board to program serial flash memories using the JTAG-SMT2-NC operated as an SPI master. This works fine but now I want to use the same board to program an I2C EEPROM (on a different target). FTDI's document "USB to I2C Example using the FT232H and FT201X devices" suggests that this should be possible and I belive that the JTAG-SMT2-NC uses the FT232H. Has anyone tried this? What would the mapping of the connections be? I imagine that it would be:- TMS - connect to Write Protect on the EEPROM TCK - connect to I2C's SCK TDI, TDO - tie together and connec to I2C's SDA alternatively I suppose that one could bit-bash the GPIO pins (GPIO0, GPIO1, and GPIO2) but this would require a hardware change to my adapter that I'd prefer to avoid.
Hi, I have the JTAG-SMT2-NC part on my board, interfacing to a Xilinx FPGA. I'm setting up the manufacturing line tests for my board, and wanted to test the USB to JTAG path as part of that. I want to avoid having the test engineer open up Vivado and manually discover the target, etc. Is there a command line utility for the JTAG-SMT2-NC that can be used to discover the target and do some basic commands such as reading its JTAG ID? Thanks, Amrith
We have a number of Digilent boards with this built in so we decided to put one an a new design. When trying to connect using Xilinx Impact 14.4 initialize chain, a message comes up that it found multiple devices and when i hit continue, it wants me to enter .BSD files. does this device require any programming before it can be used. I wired it up according to the data sheet when using the Xilinx 14 pin JTAG header in parallel with the JTAG-SMT2-NC. We have it connected to a Xilinx XC7Z020-1CLG400C. I would think Impact would have found this device. as the PS processor and the PL logic side as it does on the Digilent development boards. No other devices are in the chain. At this time we are having the JTAG-SMT2-NC removed and see if we can detect the chain with just the Xilinx JTAG header and programming pod. with the device installed, the pod doesn't see the chain either. any Ideas? It is possible the XC7Z020-1CLG400C has a soldering problem but it's to early to tell.