9S12XE: Debugger tracing data writes

cancel
Showing results for 
Search instead for 
Did you mean: 

9S12XE: Debugger tracing data writes

Jump to solution
904 Views
davekellogg
Contributor II

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!!

Labels (1)
Tags (1)
0 Kudos
1 Solution
172 Views
J2MEJediMaster
Specialist I

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

View solution in original post

0 Kudos
3 Replies
173 Views
J2MEJediMaster
Specialist I

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

View solution in original post

0 Kudos
172 Views
davekellogg
Contributor II

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?

 

 

0 Kudos
172 Views
J2MEJediMaster
Specialist I

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

0 Kudos