Forum Discussion

dsmirnov's avatar
dsmirnov
Icon for Occasional Contributor rankOccasional Contributor
6 years ago

What is JTAG Debug Level 3 for Nios II?

Hello everyone, I would like to trace program execution on the Nios II. One way - to buy Lauterbach - not interesting. Second way - use SignalTap II and .objdump file - pretty well, but still. And n...
Ahmed_H_Intel1's avatar
Ahmed_H_Intel1
Icon for Frequent Contributor rankFrequent Contributor
6 years ago
Hi, The debugger level shows the level of targeted components in the debugger. The following video show you how to debug a NIOS II application https://www.youtube.com/watch?v=VExM1gtWUCA Note: Normally you must set the optimization and debug levels the same for the application, the BSP, and all user libraries in a software project. If you mix settings, you cannot debug those components which do not have debug settings. For example, if you compile your BSP with the -O0 flag and without the -g flag, you cannot step into the newlib printf() function
  • dsmirnov's avatar
    dsmirnov
    Icon for Occasional Contributor rankOccasional Contributor
    6 years ago

    Dear Embedded_guy,

    Thank you for your answer. I watched the video and it is just about regular software debug, while I'm asking

    about Tracing mode and profiling the code. I understand how to use Debug, but sometimes it is not enough.

    I found trace working in Nios II EDS with Quartus 10.0, but in fresh Nios SBT there is nothing about it.

    I can choose on of five levels of debug, anf the 3rd one tells, that I can use On-chip trace.

    I also don't understand your phrase "The debugger level shows the level of targeted components in the debugger."

    By the level of targeted components - what do you mean?

    Also thank you for your note, I've checked flags for compilation, they are identical

  • ABola2's avatar
    ABola2
    Icon for New Contributor rankNew Contributor
    6 years ago

    Thanks Embedde guy for this Note.