Forum Discussion

simozz's avatar
simozz
Icon for New Contributor rankNew Contributor
4 years ago
Solved

DE0-Nano Quartus Lite 19.1.0 Linux - Programming Failed - Error (209040): Can't access JTAG chain

Hello, I am trying to use my DE0-Nano board with Quartus version Lite 19.1.0 (Debian 10) and my_first_fpga example, but I cannot achieve to successfully program the FPGA. Quartus correctly detec...
  • simozz's avatar
    simozz
    4 years ago

    The problem seems to be caused by a SW issue..

    Following the suggestion posted here

    https://electronics.stackexchange.com/questions/239882/altera-cyclone-ii-jtag-after-as-programming

    I installed libudev:i386:

    $ sudo apt-get install libudev1:i386
$ sudo ln -sf /lib/x86_64-linux-gnu/libudev.so.1 /lib/x86_64-linux-gnu/libudev.so.0

    Then, after pluggin the board:

    $ sudo killall jtagd
$ jtagd --user-start
$ jtagconfig 
1) USB-Blaster [1-10]
  020F30DD   10CL025(Y|Z)/EP3C25/EP4CE22

    The above script can be placed the bin directory of installation, for example /opt/intelFPGA_lite/20.1/quartus/bin/usbblaster.sh (yes, I switched to 20.1 version):

    #!/bin/sh
/usr/bin/killall jtagd
/opt/intelFPGA_lite/20.1/quartus/bin/jtagd --user-start
​

    and udev rules set as follows:

    SUBSYSTEMS=="usb", ACTION=="add", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6001", MODE="0666", GROUP="plugdev", SYMLINK+="usbblaster", RUN+="/opt/intelFPGA_lite/20.1/quartus/bin/usbblaster.sh"

    Works like a charm.

    Simon

JohnT_Altera's avatar
JohnT_Altera
Icon for Regular Contributor rankRegular Contributor
4 years ago

Hi,


From the message you provided, you are only able to detect the blaster but not the device. May I know if you have try to performed auto-detect or "jtagconfig" to see if it is able to detect any device on device chain? Have you confirm if the connection to the JTAG port is correct?


  • simozz's avatar
    simozz
    Icon for New Contributor rankNew Contributor
    4 years ago

    Hi @JohnT_Intel ,

    Sometimes jtagconfig detects the device, many times it doesn't.

    Here are three consecutive jtagconfig executions. After unplugging the board (2nd one), it has been (luckely) detected:

    :~$ jtagconfig 
1) USB-Blaster [1-5]                          
  Unable to read device chain - JTAG chain broken

:~$ jtagconfig 
1) USB-Blaster [1-5]
  020F30DD   10CL025(Y|Z)/EP3C25/EP4CE22

:~$ jtagconfig 
1) USB-Blaster [1-5]
  Unable to read device chain - JTAG chain broken

:~$

    Between the 2nd and the 3rd execution, the board has not been unplugged.

    This is of course particularly annoying because the successful detection is unpredictable.

    Simon