I cannot do an instruction trace with my Segger j-Trace for ARM Cortex-M using Segger's Ozone debugger. I connected my j-Trace to a Cortex-M3 LPC1778 processor. The processor does not have an ETB but has
four ETM trace data lines.
The
problem is the instruction trace does not show all the instructions that execute. It's hard to tell
but it may be showing every 20th instruction or so. Also the trace
shows addresses of instructions that did not execute.
Also, I have to go through a rather odd procedure to turn on the trace. First, start the processor with the instruction trace window closed. Open the trace window while the processor is running. Stop the processor. Start the processor. The trace begins. Is that the way it is suppose to work?
The
instruction trace does not skip instructions or show instructions that
did not execute when I use my j-Trace with an IAR
debugger. So I think I have a good connection.
I would much appreciate it if someone will advise me what might be wrong.
Thanks
four ETM trace data lines.
The
problem is the instruction trace does not show all the instructions that execute. It's hard to tell
but it may be showing every 20th instruction or so. Also the trace
shows addresses of instructions that did not execute.
Also, I have to go through a rather odd procedure to turn on the trace. First, start the processor with the instruction trace window closed. Open the trace window while the processor is running. Stop the processor. Start the processor. The trace begins. Is that the way it is suppose to work?
The
instruction trace does not skip instructions or show instructions that
did not execute when I use my j-Trace with an IAR
debugger. So I think I have a good connection.
I would much appreciate it if someone will advise me what might be wrong.
Thanks