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 have a compiled key scan program I wrote using the latest full version of C51. I went to the debugger (added my variables to watch window 1) and ran the code successfully. I returned to uVisionII. After looking the code over (no changes) I returned back to the debugger for a more thorough test of the code. Now debug refuses to accept some of the variables it previously accepted. I get an error 34 'undefined identifier' any time I try to add (specific variables) to the watch window. I'm using XP Pro. Is this a bug or what? Please help Brian
If you want to view the values of local variables (automatics and function arguments), you must step into that function. Local variables are out of scope and are undefined until that function is executing. There is a Locals Tab in the Watch Window. It shows the values of all local variables in a function. If you add local variables to a watch window, uVision (be default) attempts to restore those watch points when you re-enter the debugger. However, if those variables are local, you will receive the error that you do. Jon