• Content Count

    3
  • Joined

  • Last visited

About [email protected]

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  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. So, the J4 header is not to be used for JTAG ing with a HS2 programmer. Why have this header?
  3. 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