Hello, I have a variable of type Nat16 (unsigned int) which is called PulseWidth. In the function that fills the variable PulseWidth, there's some assembler code (#pragma asm/endasm included in the .c file), so I have to indicate to the compiler to generate an assembler src file and to assemble this src file too. Because of that, I have to open the corresponding .src file to put breakpoints (apparently, I can't put breakpoints in the 'normal' .c file). When the breakpoint is hit, I would like to see the content of this variable in the watch window #1. However, I only see the value of one byte of this variable iso the whole variable. I have to open the memory window after looking where in the memory this variable is located, and only then I can see the two bytes (so, the 'complete' variable). My question: how to show the complete variable when you have hit a breakpoint in a .src file? Is there something like PulseWidth and PulseWidth+1 to be defined in the watch window? The example I gave just now certainly does not work, because if you put PulseWidth+1, the watch window simply adds 1 to the value of PulseWidth. Is there some other way to represent the second byte (or better, the whole variable at once)? Rgds, --Geert PS.: uVision version 2.33, C-compiler version 7.03.
Hi Geert! I had the same problem a year or two ago. So, the answer was not to be so curious. And God save you to call it a bug - Jon Ward will never allow it. M.
I do not use/know about the simulator; however by emulator does not show local variables in assembly files. Glad, to hear that the problem exist in the simulator, that help me where to point the finger Erik
Mikhail??? What do you mean: not to be so curious??? I know, curiosity killed (sometimes) the cat... But I've always been teached that curiosity is a healthy disease, if you know what I mean. This phenomenon, though, is quite annoying and I should not know why Jon would not allow me to call it --at least-- a nasty thing (= synonym for bug???). How did you continue in your case? Also look up where the variable is located and then chase it in the memory window? Rgds, --Geert PS: Erik, you see IDE is not (always) the end of the world!!! Although we can't really complain (I know too we're lacking a CodeWright interface,I know...).
Geert, Unfortunately, I was forced to make a choice: either to use asm...endasm or see variables in the watch window. I've chosen the first option. Yes, the only way to see what's going on is the memory window - a good and probably useful exercise, anyhow. As for Jon - I can't answer for him, but when I called it a bug he looked frustrated and explained me two things: that I didn't understand the difference between the .src and .obj files (I never even wanted to understand it) and that his car (Ford Explorer at that time) was not sufficiently dynamic. Anyhow, no other explanation. Regards, M.
Sorry Geert, I fail to see the connection PS: Erik, you see IDE is not (always) the end of the world!!! Although we can't really complain (I know too we're lacking a CodeWright interface,I know...). I am referring to ICE Erik
What I meant by this, Erik, is that also with an IDE you can indeed have problems seeing what you want to see (or just not...). And I gave a kind of a 'wink' to you, because I read (and understood) on other forums that you are one of the (maybe many) developpers that would like to use another powerful editor from within the Keil environment. That's all :-) Rgds, --Geert