Rich E

I tried programming the Xilinx configuration device (QSPI) in our hardware using a known xxx.bit file. I erased the configuration device prior to programming and Adept indicated programming was 'successful' but after rebooting the hardware did not function. What exactly is Adept capable of programming?

We wanted to use Adept to program configuration devices connected to Xilinx FPGAs without the need to download Vivado. Vivado requires a multi gigabyte download and is rather confusing for use in a production environment. Adept appeared to be an ideal solution - compact and straight forward. How is Adept capable of programming Xilinx XCFS devices using .mcs files when the GUI does not allow selection of a .mcs file?

I'm a little confused. The JTAG-HS3 we're using is used for communicating through a Xilinx (now AMD) FPGA. The Digilent JTAG-HS3 programs a Xilinx XCFS Platform Flash device (i.e. QSPI memory) using a .bit or .mcs file via through embedded code in the Vivado platform. The .bit is a proprietary file format organic to Xilinx whereas the .mcs is a hex file format (alternative). The stand-alone Adept 2 software is listed as supporting (webpage in first post) but when Adept 2 is executed: when the 'Browse' button is clicked: .mcs is NOT listed in the list. Is this an oversight in the Adept 2 application that needs to be patched or is the webpage for Adept 2 is flat out wrong? Obviously the JTAG-HS3 hardware can handle a .bit or .mcs file either in Vivado.

I just downloaded the latest version of Adept (v2.27.9-2). The website under 'Features' it indicates: 'Program Xilinx XCFS devices using .bit or .mcs files'. But .mcs is not listed in the drop down selection (.bit and .svf). Does Adept support .mcs files?

@JColvin ...you are effectively looking down the JTAG HS3 from the microUSB end towards the 2x7 header end... ...users did not have to do any mental gymnastics flipping an image around to see whether or not the headers lined up... Figures 3 and Figure 4 are mutually exclusive - without the provision in your last post the datasheet IS FLAT OUT WRONG. With the image I've attached, the Molex part indicates pin1 which matches Figure 4 with the correction I've noted. I'm an electrical guy and it is wrong. If were one to wire to Figure 3, it would not work. Isn't the above image how normal mechanical guys would view Figure 3?