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 did a couple of searches and found some references to the problems I am having. But I don't think this is fully addressed, so I'll ask here.
I am using the contest eval board from Luminary Micro that includes an eval copy of the Keil tools for the Cortex-M3. I have seen variables in the local watch window display the wrong value as I step through a program. There are a couple of threads here from last summer about this, so I guess this is a known (and fixed) problem. I am surprised they circulated an old version of the tools for this contest. I just got my board in early December.
The other problem is that in one case, I was not able to view a variable in a watch window. It was a local variable and did not show in the Locals window. I also could not add it to the other Watch windows. This variable was being used, so it should not have been optimized away. I was compiling at optimization level 0, so that should not be the problem. Is this a known problem? Is it fixed in a current version of the tools?
Rick,
I had the same problem too, the one where the data displayed in the 'locals' watch window had no bearing at all on what the real value of the variable was. I seem to recall that when I reported this to KEIL in the form of a bug report the answer I got back was something like "it's harder to keep all these variables and the values for them right than you might think, plus, our optimizer optimizes too well even at it's lowest possible setting, we're working on it." I tried all sorts of things, but I never could get this problem satisfactorily resolved. I gave up on the debugger and went back to using printf and a dumb terminal connected to a serial port to debug. Quite primitive, but at least it worked.