Forum Discussion

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

BAD_JTAG_CHAIN again

Dear All,

running eclipse-nios2 I try to debug an application. Using ethernetblaster. When I open the Debug Configurations and fill all what is needed, I cannot find the target. Instead it says '[Target connection]: System Console: Unable to scan chain: BAD_JTAG_CHAIN'

Anyone knows where the problem lies?

It needs to be said, that from:

a) quartus programmer it works out of the box

b) signal tap from quartus works out of the box

c) all my command line tools, including nios-terminal work out of the box.

The only issue is with eclipse when I try to debug or run it....

I have imported the BSP and application into eclipse as normally I'm using command line driven compilation and testing, but this time I need to dig into debugging as well....

any help kindly appreciated

.d.

as well, all my command line tools always specify 'cable', i.e. to which cable the tool should be attached

if I issue jtagconfig, I get the information correctly (i'm using the second device):

belohrad@beesknees:~/Downloads$ /opt/altera-current/nios2eds/nios2_command_shell.sh

------------------------------------------------

Altera Nios2 Command Shell [GCC 4]

Version 12.0sp2, Build 263

------------------------------------------------

belohrad@beesknees:~/Downloads$ jtag

jtagconfig jtagd

belohrad@beesknees:~/Downloads$ jtagconfig

1) EthernetBlasterII on aceb055e [EthernetBlasterII]

Unable to read device chain (JTAG chain broken)

2) EthernetBlasterII on didtethblaster04 [EthernetBlasterII]

020F70DD EP3C120/EP4CE115

1 Reply

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

    Okay guys,

    I know the answer:

    the reason for this is, that eclipse fails to look for the second ethernet blaster because the first one is unable to be scanned.

    In my command line tools of course it works, because I specify correct cable.

    In eclipse apparently it does not work because if it fails to scan the first one, it assumes that there is no other server. This is wrong assumption. I file a bug at altera

    So I removed the broken connection, and everything magically started to work.