David Allen

  • Content Count

  • Joined

  • Last visited

  1. Sorry for the late reply on this. I was on vacation then other work priorities intervened. I was only able to test JTAG-SMT2-NC with the daughter card and JTAG-HS3 without the daughter card installed. I have checked and JTAG_REQ_N and VPX_JTAG_EN_N are at the correct levels and remain stable while accessing the chain through the daughter card.
  2. Hi Michael, Below is a block diagram of the JTAG chain. There are three ways to access it. One on the PCB header, the VPX backplane, and through the daughter card from the ZFMC site. When plugging into the PCB header or backplane header I have used both the JTAG-HS3 and the standard Xilinx programmer. Both work. It is only through the daughter card that we have issues.
  3. We have a 1.8/3.3V level translator between the FPGA and the daughter card with as well.
  4. The Adept chain returns a device ID of 14B31093 with an instruction register length of 18. It shows up as an unknown CPLD but this is the correct ID and IR length (same IDs and IR lengths reported in Vivado when I scan the chain though the PCB header (not through the daughter card)). VCC0_0 is set to 1.8V. VREF on the JTAG SMT2 NC is set to 3.3V.
  5. I've slowed the JTAG clock down to its lowest setting in Vivado and still have the same issue. David
  6. Hi JColvin, Depends on how you define custom! The JTAG SMT2 NC is integrated into a daughter card that we use as a solution for front panel JTAG access to two of our dual FPGA carrier boards. These are products our company produces. The daughter cards have worked in the past on all board except these latest two with VU9P FPGAs. Interesting thing is I can never see the chain correctly from Vivado. In Vivado it will always show devices with the wrong device ID. Using Adept or Impact I can scan the chain and see all four devices. Occasionally in Adept it will behave as Vivado does. Do you h
  7. We are using a JTAG-SMT2-NC for JTAG access through one of our daughter cards. This has worked in the past using KU115 and VU5P FPGAs paired with a Zynq. However now the VU9P the JTAG chain is unstable in Adept and Vivado hardware manager where most of the time it will not correctly scan the chain and give device IDs that do not match with devices in the chain. Is there an incompatibility with the JTAG-SMT2-NC and the VU9P FPGAs? Thanks, David