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.

CCS5.3 and MSP-FET430UIF - variables not updated



When I step through code in CCS5.3, my expressions are not updating properly while debuggin, as shown on the bottom.  Below is the summary of combinations that I tried.  The question is, can my FETUIF be faulty?

MSP-FET430UIF CCS5.3 on Windows 7 - Debugger does not update

MSP-FET430UIF CCS5.3 on Linux Ubuntu 12.03 - Debugger does not update

MSP-FET430UIF IAR Workbench Windows 7 - Debeger does update

MSP-EXP430FR5739 Launchpad - CCS5.3 and Windows 7 - Debugger does update

My FET has white label on the back "V1.4a" and another label says "10086552009R", so what the heck is going on?  Are there other revisions of MSPUIF?


Below is more detailed description of what is going on.  All four scenarios above were done the same way.

The g_time_msec is initialzed and set to zero on line 17, but when main is entered g_time_msec is at 9.  Why? 

when line 22 is executed, g_time_msec changes to zero.

When line 25 gets executed, g_time_msec goes back to 9 Why? there is no interrupts on the background that would do that.

As I step through program the g_time_msec stays at 9.

Int ital post is located here:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/262643.aspx

  • Hi,

    is there a reason you are poting your question a second time?  It seems you have a live thread ...


    Also, I do not believe it to be your FET.   For sure this is either an expressions view bug or possibly your optimization settings/something with the code.

    Please continue in the thread this is already being dealt with by some helpful colleagues.

    Best Regards,

    Lisa

  • Lisa,

    I was not getting my question answered, so put together a more clear question, I am banning my head against the wall and cannot go anywhere.  You know about the previous thread, code is right there.  If you do not believe it is the FET, then what is it?   The previous thread says that optimization is off.