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.
See the section, "µVision2 Restrictions when using Monitor-51" in the Getting Started giude, GS51.pdf.
(accessible, as always, via the 'Books' tab in the uVision Project window).
Actually, we had this feature enabled for a while and it caused too many technical support issues.
The problem is that with trace recording, the monitor must single-step each instruction and transmit the register contents and other data to the PC. If this is only 16 bytes per instruction, you can see that at 9600 baud, you'll only execute 60 instructions per second (960 CPS / 16).
At that rate, it takes several seconds to make it thru the startup code. This is usually unacceptable for most software development.
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?
Given what you said regarding the degradation of performance via the serial interface when trace recording is turned on, I'd agree that the feature wouldn't be very useful in most cases. However, I'd still like to know how to enable the feature in case there's a situation where I can use it. How did you enable it?
I didn't see anything in the restricted functionality that included the trace buffer.
Maybe I missed it, but are you sure? If you are correct, then I wonder why the Application Note for Monitor-51 says that 5 kbytes of memory is required for the trace buffer.
I just noticed that the list provided is a partial list of restricted features. However, I still can figure out why the Application Note would say 5 kbytes is needed for trace recording.
View all questions in Keil forum