Forum Discussion

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

Arria II GX JTAG Configuration Failure

Our JTAG interface has failed on multiple boards during bring-up. We would load .sof and .jic files several times successfully. Then, after a few days the programmer would fail to load the .sof or .jic files with the error message: "Can't configure device. Expected JTAG ID code 0x025030DD for device 1, but found JTAG ID code 0x00000000.

We are able to configure the Arria via the AS and PS intefaces. We ran the key_verify_aii.jam file and we're pretty sure the FPGA was not programmed with a non-volatile security key. We are also able to program the other devices via JTAG later in the chain, suggesting that the signal integrity and electrical stuff is working properly.

Any suggestions?

3 Replies

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

    Hello icarlson,

    I am experiencing exactly your same error message: "Can't configure device. Expected JTAG ID code 0x025030DD for device 1, but found JTAG ID code 0x00000000", with the same target:

    Arria II Gx.

    Some days ago we managed to program successfully the FPGA via jtag (altera USB blaster), then it seems it stopped working.

    Did you manage to solve the problem?

    Thanks on advance

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

    Just encountered the same problem in our two Arria II GX boards. The interesting thins is that we have downloaded program via AS every time before the problem happens. However we did not enable any security feature or key in it. And JTAG debug tools report jtag works however usercode is 0x000000000.

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

    Hi RiverLiu,

    thanks for your reply.

    Our Altera FAE suggested to us some tests to do to verify that the anti tampering bit had been (erroneously) programmed via JTAG. It seems that if the JTAG signals are dirty this can happen :(

    It happened to us in 2 boards. We replaced the 2 FPGA and we went on working...

    Bye