Forum Discussion

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

JTAG Warning

For some reason, my software doesn't run (using terminal mode for configuration) and I keep getting the following messages:

nios2-terminal: connected to hardware target using JTAG UART on cable

nios2-terminal: "USB-Blaster [USB-0]", device 1, instance 0

nios2-terminal: starting in terminal mode only (Control-C exits)

nios2-terminal: Warning: The JTAG cable you are using is not supported for Nios

nios2-terminal: II systems. You may experience intermittent JTAG communication

nios2-terminal: failures with this cable. Please use a USB Blaster revision B

nios2-terminal: cable or another supported cable. Please refer to the file

nios2-terminal: errata.txt included in the Nios II development kit documents

nios2-terminal: directory for more information.

I'm using the USB Blaster rev. B that the warning prompts me to use (I actually got this warning when my code ran successfully as well). I've tried running code I know works and still got nothing.

Has anybody had this happen? How'd you solve it.

Thanks.

3 Replies

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

    If you have a System ID peripheral I recommend turning on the check (better make sure that you have the right hardware first).

    Can you describe what your cable looks like? (short or long ribbon, shielded (yellow) ribbon, etc...)
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    21 years ago

    The output from the Nios II download window often explains what is going on better than the nios2-terminal window. If you can rerun your test and say what's in that window then it might be more obvious what's going on.

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

    Whatever caused the problem, it's wasn't the JTAG or Software (something subtle must have happened in the firmware). I took quite a few steps back (stripped my design) and was finally able to successfully run some code. Then I added my peripherals and software back, piece by piece, and I never ran into again! I'll post it if I find out what it was.

    Thanks