I am using version 5.05 of the C166 compiler and am seeing a strange problem displaying 8 bit variables in the Watch window. Rather than the value I expect, I see only the lower nibble with the upper nibble stuck at 0 (0x45 displays as 0x05). I can see that the processor has the correct value because it is correctly shown in the Register window. This is a local function variable that has been optimized to be placed in a register rather than the stack. Anybody else have this problem and know of a solution? Thanks, Barry
I am still having a problem displaying the correct values for 8 bit variables and it is causing a lot of wasted time having to examine register values to see if the byte value shown in the Watch window is correct. The upper nibble of these variables will be displayed as zeros (i.e. 0xFF is displayed as 0x0F). I am using UV3.05e which came with the ULINK driver UL2OCDS.dll (V1.00). I am using the USB ULINK tied to a custom board having the XC167 uP, 2Mb external program flash and 512Kb of RAM. Is there a newer driver for ULINK (I don't even see ULINK listed on the Product Update page).
Can you provide an example since we are not aware of such problems. Send a test case to support.intl@keil.com. Reinhard
I use 3.11e, where the UL2OCDS.dll is shown as V1.0.0.1. ( I actually not work on 16-bit ) As far as I know, only some improvements in the timings were done. Newer versions are not separatly downloadable, as I mean, but comes, if newer versions available within the updates for C166 package. Stefan