Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
15 years ago

Error: Can't access JTAG chain

When i try to program the FPGA cyclone III i get this error :

error: can't access jtag chain

error: operation failed.

I am using a FPGA cyclone III .I would be able to program it a few months ago with no problem but now it suddenly gives me that error.Can anyone help??

ps. I am using the usb blaster.

please can somebody help me?

19 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Turns out my main problem is that the FPGA isn't soldered to the board. Truely an epic fail. Will come back here and report after we get another board fabed.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    wswuda2007: I can't see any image you post.

    Did you try and check the signals with a scope?

    hines1957: what package is it? was it glued on the board?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    wswuda2007: I can't see any image you post.

    Did you try and check the signals with a scope?

    hines1957: what package is it? was it glued on the board?

    --- Quote End ---

    Sorry about that, I don't know how to put the images on the forum by easily giving the URL/.

    By the way,I've checked the CONFIG_DONE pin by scope ,but it has no change. Are there other pins do i need pay attention to?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Check the JTAG signals. Especially the clock, that must have clean edges.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    Check the JTAG signals. Especially the clock, that must have clean edges.

    --- Quote End ---

    Bad news for me! The JTAG's TCK pin has no signal at all. When I connect the USB-BLASTER to the JTAG's ten pins, the TCK is always 3.3v,and without the USB-BLASTER,it is always 0v.

    What's the real signal of the TCK as it should be? The TCK signal is given by the FPGA or the usb-blaster?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    It should be a clock signal. Are you looking while you are doing a configuration?

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    TCK is driven by USB-Blaster but only while something is using it. A quartus_pgm will drive it continually but something like the Nios debugger or terminal will drive it in bursts if it is just polling for activity

  • DevRuibin's avatar
    DevRuibin
    Icon for New Contributor rankNew Contributor

    I can relate to your issue. I attempted to resolve it and it appears to be functioning properly now.

    Below is my solution:

    1. Follow the steps in the link. It works initially, but the problem resurfaces after a day.

    2. It appears that the error message "Error: Can't access JTAG chain" was caused by a permission issue. In order to resolve the problem, I reinstalled Quartus (version 22) as the root user, and this successfully solved the issue.

    3. It's a good idea for a regular user to launch the program, as it avoids the need to constantly switch users. To grant others the same permissions as the root user, I utilized the command `ruibin@E590:/media/ruibin/Data/01/2531/quartus/quartus/bin$ sudo chmod u+s *`.

    4.If you come across this issue: Quartus displays an error message stating "error while loading shared libraries: libprotobuf.so.14: cannot open shared object file: No such file or directory." see: https://www.intel.com/content/www/us/en/support/programmable/articles/000093063.html

    I understand that launching the software as a root user may not be the best approach, but it seems like the most direct solution to my problem. If you have any other suggestions, please share them with me. Thank you!

    Also, I hope my response can be helpful to anyone else who is facing a similar issue.

  • For the USB Blaster 2 devices, if the USB cable is too long, this can happen especially if one uses a USB extension cable. Reducing the frequency to 6 MHz (the old Blaster's frequency) doesn't help either. But I never had this issue with the old Blaster, even with a USB extension.