• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 2258 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Strange License Issue (exceeds code size limit)

Krutarth Trivedi
Prodigy 90 points
Other Parts Discussed in Thread: MSP430F6638

I am very confused by this sudden problem. I've been coding with a licensed version of code composer for a while. Its been going great and then suddenly after I add a few lines of code this morning, the compiler throws an error saying my code exceeds size limit! It compiled just fine before I wrote those few lines...I checked the file size and it is 63 KB. So, is the license I have limited to below 63 KB or something? I am just surprised because I have a licensed version and it was compiling just fine before a few minutes with a ~60 KB file. So what's the deal?? Please help!

  • 0
    Prodigy 90 points

    I just commented out the code I added and it compiled. So, this means the code size limit is on the microprocessor?? I am using a MSP430F6638. Its just ~1900 lines of code...and that is with all the comments...is this the maximum size of the program I can load into my chip??

  • 0 in reply to Krutarth Trivedi
    TI__Guru**** 161520 points

    What is the error message that you are getting?  Is it something like "unable to place .text section in FLASH" or something that specifically mentioned the code size limit?  The first message means that you have run out of memory on the device, the second one means you are using the code size limited linker.

    F6638 has 256K of flash.  Keep in mind that your source lines are not the only thing that contributes to the size of your program.  Data will contribute but the biggest contributor is often libraries.  The C runtime support library can be quite big, are you using printf in your code?  That can lead to a big increase in code size.

    You can that a look at the .map file that is generated as part of the build to see what is contributing to the size.  The .map file will be in the \Debug or \Release folder depending on what configuration you are building.

     

    Regards,

    John