|ARM Technical Support Knowledge Articles|
Applies to: uVision Debugger
Information in this article applies to:
When I view my program in the uVision Debugger, a line of my C code seems to have been incorrectly compiled. I have written the following statements:
TL0 = 0x80; TH0 = 0x6F;
When I review the code in the disassembly window of the uVision debugger, it appears as:
TL0 = 0x80; MOV MyValue(0x8A),#P0(0x80) TH0 = 0x6F; MOV TH0(0x8C),#0x6F
It looks like the line TL0 = 0x80; is not correctly translated. Is this a compiler bug?
No. This is not a compiler bug. The disassembly tries to insert symbolic values. However, your program has already a symbolic equate statement or other variables with the value 0x8A. Therefore, the disassembly shows the wrong symbol. Note that the code is fully correct, since 0x8A is the memory location for TL0.
Article last edited on: 2004-05-03 19:28:37
Did you find this article helpful? Yes No
How can we improve this article?