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
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

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 3 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. Please note, that I've pull ups (100k resistors) on TDI, TDO, and TMS. A pull down (100k resistor) is on the TCLK pin. The Firmware: I've created a simple pass through from one pin to another, it 'compiled' successfully with no warnings or information statements. I was able to then generate a *.bit file with no issues. The issue: I used Impact to initially try and program the board. I 'know' I got a successful connection, because the Get device ID option worked and it correctly identified the flash and fpga configuration. When it came to uploading the bit-stream, it failed with "Done did not go high' error. So, I decided to try the Adept software..... and I got the aforementioned Dialog box. I did press the "OK" button and the status console on the Adept software stated that it was 'successful.' However, the board was obviously not programmed. By the way, I have the mode pins set at 00. So, I'm wondering if I've not setup the mode pins correctly, missed a setup step on Impact or the ISE? Any questions or answers to help me along would be great. Love to learn!
  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_START - Starting Operation. INFO:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File. INFO:iMPACT:1578 - '1': Device IDCODE : 00001111111111111111111111111111 INFO:iMPACT:1579 - '1': Expected IDCODE: 00000100000000000000000010010011 PROGRESS_END - End Operation. Elapsed time = 0 sec. When I use Adept, I get this: ===== Digilent Adept ===== Adept System Rev 2.7 Adept Runtime Rev 2.20 Adept Application Rev 2.4.2 Copyright © 2010 Loading board information... Warning: Could not find specific board information Initializing Scan Chain... Default information loaded. Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Found device ID: ffffffff Initialization Failed. ------------------------------------------------------------------ I've soldered the header to the J4 holes on the CMOD A6 correctly. I know that this board work because I've programmed it when I connected it DIRECTLY to my Windows laptop's usb port, by way of cable. Am I missing a file? I did put the DLL files in the proper place and was able to have iMAPCT able to see the HS2's SN. Why is this not working?
  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 settings of one device (our device we work with) ). I hope my question is clear so far. I tried analyzing the JTAG programmer with Adept 2.0, however i cant connect to any device, as there are no devices enlisted under the connect dropdown. Best, Matthias