• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 22 subscribers
  • Views 2269 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do you do Trace Recording with Mon51?

Mark Shelton

Has anyone figured out how to enable and view trace recording when using the UV2 debugger with Mon51?

These commands are disabled when I build my project for debug with Mon51. However, they do work if I use the simulator (including itrace=1 and itrace=0 at the debugger command line).

I'm running uVision2 v2.06 with C51/A51 v6.02.

Thanks,

Mark

Parents
  • 0 in reply to Andrew Neil

    I didn't see anything in the "µVision2 Restrictions when using Monitor-51" section that indicates Trace Recording or View Trace Records are disabled. All I see is that the Memory Map, Performance Analyzer, Call Stack, Code Coverage, Step Out, and Periodic Window Update functions and commands cannot be used with Monitor-51.

    The "Hardware and Software Requirements" section on p. 159 mentions that 5 kB of XDATA RAM are required if the optional trace buffer is to be used. I would think that this indicates it's possible to use the trace buffer with Mon51.

    Did I miss something?

    Mark

Reply
  • 0 in reply to Andrew Neil

    I didn't see anything in the "µVision2 Restrictions when using Monitor-51" section that indicates Trace Recording or View Trace Records are disabled. All I see is that the Memory Map, Performance Analyzer, Call Stack, Code Coverage, Step Out, and Periodic Window Update functions and commands cannot be used with Monitor-51.

    The "Hardware and Software Requirements" section on p. 159 mentions that 5 kB of XDATA RAM are required if the optional trace buffer is to be used. I would think that this indicates it's possible to use the trace buffer with Mon51.

    Did I miss something?

    Mark

Children
No data