• Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 322 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS V5 not running code.

Jerry Bonner
Intellectual 385 points

Other Parts Discussed in Thread: MSP430F233

Ran OK on previous CCE CCS versions. CCS V5 compiles C++ code, loads some of memory, executes to point where no code is loaded.

  • TI__Guru**** 173310 points

    Jerry,

    There is not enough detail here to understand what the issue is or why it may be happening. Could you please provide more details?
    Which specific version of CCSv5 are you using? And what issue are you observing? How you do see it "execute to point where no code is loaded"?

  • in reply to AartiG
    Intellectual 385 points

    Running CCS V5 5.3.0.00090

    1280 lines of C++ code and comments.

    Am using MSP430F233 chip.

    Builds with no errors showing in "Problems" or in "Console"

    Click on "Run--Debug" and it loads with no errors. 

    However, "MSP430: Loading complete. Code Size - Text: 514 bytes Data: 8 bytes" message is shown. The code is much bigger than this.

    Click on "Step Into" about 20 times and it steps into memory cells loaded with "FF"

    Have found nothing wrong in "Project Properties" ----- But, something is wrong somewhere.

  • in reply to Jerry Bonner
    TI__Guru**** 173310 points

    To confirm code size of your application, you can take a look at the link map file generated as part of the build. The .text section is the size of your code section, if you have constants they will also go into Flash. Comparing the map file with the amount of code that is displayed as being loaded to the target you can determine if there are discrepancies.

    Since you are familiar with the application, you would be in the best position to debug exactly where/why it is going off into invalid memory. Are you able to determine when stepping through the code which instruction is causing it to go off into the weeds?