This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
A customer reported problems visualizing the correct values when he hovers around a pointer or check its value in a Watch window. However, if he uses printf() or go to the pointer address in memory browser the value is OK.
I think the problem is related to how the watch window value is set. Looks like it is set to big endian (instead of little endian) but I was not able to change it in the IDE. Please see attached snapshot, it shows printf() value different to watch window value.
As additional information the project was compiled using "Full symbolic debug" and not optimization.
I was wondering if there is any way to change the watch window settings value to little endian or if you think the actual problem is a different one and you can guide me how to debug it. I can share the CCS project if it is required.
Thanks a lot for your help,
Paula
Hi,
Now we think we understand why the IDE is having a hard time. It has to do with the mis-alignment of pcdc->ctu.cuArray. Once it is fixed then everything is ok.
Thanks,
Paula
Hi,
i'm programming for msp430 and also face endian issue. MSP430 is little-endian. OK with that. But in CCS studio I get the following (see picture). timeBetweenCurvesInFlash is 1280 (which is endian swap for 5). *tmpPtr16 in watch window shows my 5. If I use __data20_read_short(paramsAddress+3) it is the same 1280. Btw, I checked this both in large data model and a small one. It is the same behavior.