Forum Discussion

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

system console returns empty jtag_debug service.

I want to leverage the system console to help resolve what looks like a jtag chain issue.

After programming the .sof file into the fpga, I open the system console. I tried the same commands than in jtag example section of chap12: Analyzing and debugging designs with the system console.

typing:

> get_service_paths jtag_debug

... returns an empty string, which makes this command fail:

> set jd_path [lindex [get_service_paths jtag_debug] 0]

... since lindex returns -1

There is obviously a nios2 proc in the design with lev3 debug interface and a jtag_uart too.

Any ideas why this occurs? This is using Quartus 11.0.

Any help welcomed,

--M

2 Replies

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

    --- Quote Start ---

    > get_service_paths jtag_debug

    ... returns an empty string, which makes this command fail:

    Any ideas why this occurs? This is using Quartus 11.0.

    --- Quote End ---

    The SystemConsole jtag_debug service uses registers that exist in the JTAG-to-Avalon-ST bridge component. The JTAG-to-Avalon-MM master uses this component too.

    I suspect that the UART or NIOS processor debug interfaces do not use the JTAG-to-Avalon-ST component as part of their design, so no jtag_debug service is available.

    Drop a JTAG-to-Avalon-MM master into your design, resynthesize, download, and try again - you'll get a jtag_debug service.

    Cheers,

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

    Hey Dave,

    I am looking at the jtag_pio_cii available from Altera and all there is in the sopc is a jtag-to-avalon-master bridge and PIOs for LEDs.

    So your suggestion seems highly appropriate!

    Thanks a bunch, I will try this out.

    --M