topic Re: 9S12XE: Debugger tracing data writes in CodeWarrior for MCU

9S12XE: Debugger tracing data writes

davekellogg — Fri, 26 Mar 2010 20:23:54 GMT

I'm using 9S12XEQ512 with CodeWarrior 5.0. Has anyone been able to set up the debugger to trace only writes to a particular memory location? If so, what is the set up?

The underlying hardware certainly supports this capability -- But I can't see how to set it up in the debugger.

Thanks!!

Re: 9S12XE: Debugger tracing data writes

J2MEJediMaster — Fri, 26 Mar 2010 21:35:00 GMT

In the S12(X) Debugger Manual (Debugger_HC12.pdf), check the section starting at page 178, the Watchpoints Tab, for information on how to set up the debugger to monitor reads or writes to memory.

---Tom

Re: 9S12XE: Debugger tracing data writes

davekellogg — Fri, 26 Mar 2010 22:18:50 GMT

Hi Tom,

Aren't watch points like breakpoints, except that the execution halts only momentarily?

What I want to do is use the on-chip trace buffer to capture a series of writes to a variable, and then view the trace buffer in the debugger. I've studied pg 427 - 446, but something seems to be missing. What I really want is something like figure 15.48 on pg 447 "Trace Window - Recorded Data Display".

BTW - I'm of the opinion that Table 15.11 "Memory Access Triggers Available" pg 430 - 432 does not apply to the S12X part. I think it is a cut-and-paste error from the section on S12 (Table 15.2, pg 413 - 415). Am I correct?

Re: 9S12XE: Debugger tracing data writes

J2MEJediMaster — Mon, 29 Mar 2010 20:34:02 GMT

When a watchpoint fires, it halts the program's execution, which is the same behavior as a breakpoint in code. It sounds like you want the trace feature instead. My mistake on interpreting what you were looking for, sorry.

I'm not familiar with the S12(X) part to say anything about that trace table. However, I will agree that something doesn't quite look right with table 15-11. I will report this to the documentation people.

---Tom