We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I'd like to measure how many instructions occur between successive visits to the same breakpoint. What is the easiest way to do this in uV2?
Now that I've used uVision2 a bit more, I'll be more specific: I see the states and sec when I'm running the simulator. They're not present when I'm running the Cygnal F005 DK with their plug-in for uV2. What I'd like to be able to do are: 1) get timing information when running real target hardware, not just in the simulator, and 2) be able to reset states and sec so that I can deduce the elapsed time without doing any math. Regards
To get this sort of information, you need a real ICE - this is one of the few points where things like the Cygnal on-chip JTAG debug fall short of a real ICE. I have the same limitation using the on-chip JTAG debug of the Triscend E5. Refer to the section "µVision2 Restrictions when using Monitor-51" in the uVision Getting Started Guide - the same restrictions apply here Perhaps Keil could make these notes more generic in the next revision?
Ahhh ... that makes sense. Thanks for your prompt reply -- over the weekend, no less! Regards,