Code composer - unsigned int value and unsigned char displayed incorrectly

Hi Peter,

which window (i.e. watch window) gives you the incorrect reading? Maybe you can post a screenshot of it.

When right-clicking a variable (i.e. in Watch window) one can select the display format of it.

Rgds
aBUGSworstnightmare

Ok.  Here is an example.  Click on it for a full-screen view.  External to the code on the screen the following is also declared.
typedef unsigned char       uchar;
typedef unsigned short int  uint;

And which right-click Format option displays the value correctly?  I don't know.

TI, help please...

Hi Peter,

did you make the screenshot after downloading and the stepping into you program or did you make it after a RESET?

There are a few things which were looking stange indeed:

1.) your declaring a variable i of type uint; from your typedef uint = unsigned short int --> so, pls tell me which (dezimal) range your expecting from this declaration. If you want to have an unsigned 32-bit value change it to unsigned long.

2.) pls tell me the meaning of U in: i = 50000U;

3.) Shouldn't State3 be zero (as with State2)?

Rgds
aBUGSworstnightmare

P.S. Which MSP430 are you using? Do you use -v mspx silicon version (check Project properties-->compiler-->basic options)?

aBUGSworstnightmare said:

2.) pls tell me the meaning of U in: i = 50000U;

"50000" will be considered by the compiler as a signed long int value. The "U" tell the compiler to treat it as an unsigned short int. This makes a difference when resolving a formula. Without the U, the intermediate result will be expanded to long and the calculatiosn are done with long. While the result is usually the same (one can construct some cases where it won't, depending on shifts and sign extensions etc.), the generated code will be longer without the 'U' and slower.

 

Wrote a test program using unsigned int and unsigned char instead of the using the typedef uchar and typedef uint.  It works fine.  So that's a simple workaround - major auto search and replace across 35k lines project.  It still should work using the typedef but don't care if the workaround is easy and good.  If that was the only prob i'd be happy as.

Case closed.