Search the Community

Showing results for tags 'jtag hs2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Test and Measurement
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. So, I got this dialog box when I tried to use the Adept to program a custom Spartan 6 board: The Device this configuration file was made for is not known. Associate Config File with device anyway? Hmm, I created the *.bit file from the Xilinx ISE 14.7 software suite and I made a *.mcs file from the Impact application, so I'm wondering how Adept associates files anyway? The Setup: The board is a custom Spartan 6 board, with routes between a Spartan 6 tq144 fpga and a s25fl128 flash. The jtag ports of the Spartan 6 fpga are configured to a header, where I connect a jtag-hs2
  2. Due to the nature of my project, I need to program the cmod a6 with the use of a JTAG programmer. I have a HS2, which is configured AND recognized by iMPACT AND Adept. Unfortunately, when I attempt to program the cmod a6 board, I get the following: // *** BATCH CMD : Program -p 1 -dataWidth 4 -spionly -e -v -loadfpga INFO:iMPACT:583 - '0': The idcode read from the device does not match the idcode in the bsdl File. INFO:iMPACT:1578 - '0': Device IDCODE : 00001111111111111111111111111111 INFO:iMPACT:1579 - '0': Expected IDCODE: 00000100000000000000000010010011 PROGRESS_S
  3. Hello, I was working with a JTAG HS-2 REV A programming device in combination with Vivado 2017.4 to program my device recently. Today i could not open a target in vivado anymore. The JTAG programmer gets detected by windows normally and also shows up in FT_Prog (i use this for programming the FTDI chip of another device). Im not sure but i assume that FT_Prog overwrote some FTDI configuration of the JTAG, although i never changed the configuration myself (My assumption is made because the status-message of FT_Prog reads that both devices get programmed even though i only change the
  4. debugasm

    JTAG-HS2

    Hi, I have bought JTAG-HS2 or the laboratory to program Xilinx Spartan-3A DSP FPGA. I installed the driver and then connected to the PC HS2 but Windows 7 installs a "FTDI USB Serial Port". After open Xilinx iMPACT the software detect Digilent PlugIn but do not find JTAG cable. INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4 INFO:iMPACT - Digilent Plugin: no JTAG device was found. I tried several times but I can not make it work. Someone managed to make it work ? Thanks very much. debugasm
  5. Hi All, I am using the HS2 to drive ARC based system through the metaware debugger. Some target require low speed communication so I use metaware speed reduction switch -prop=dig_speed which must be translated to some Digilent speed settings call. The issue is that although the speed gets globally reduced, looking on the scope, one can see short TCK pulses of 200ns, irrespective of the speed settings, inserted in an otherwise reduced clock signal. Even at speed as low as 200KHz this issue remains. This causes target attach failure. Picture describing the issue is attached. I downloaded the la