• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 289 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.

CCSv5.2.1 is suspiciously tolerant.

Bo Nystedt102116
Prodigy 240 points

Other Parts Discussed in Thread: MSP430F5438A

Hi,

I'm new CCSv5.2.1 Linux and confused how its reacts to the test program I have made from 'scratch' as a mini FFT program.with only FFT. c,FFT_430.asm, main.c, and lnk_msp430f5438a.cmd and their header files

It compiles without errors, but has 27 warnings. The size of the .out file is 39 KB. It  debugs over MSP-FET430UIF without complaining, but after loading the Console tells the loaded Code Size is:Text 492 bytes Data 2 bytes. How come there are no complains at all? I use the size-limited 16B compiler. What's the explanation?

Regards Bo

  • 0
    TI__Guru**** 483451 points

    Bo Nystedt102116 said:
    It compiles without errors, but has 27 warnings.

    There are three types of compiler messages that I am aware of: remarks/warnings/errors. remarks and warnings will not cause a build to fail. But you can escalate them to cause a build to fail if you so wish with the various diagnostic options in the build options for the compiler.

    Bo Nystedt102116 said:
    The size of the .out file is 39 KB. It  debugs over MSP-FET430UIF without complaining, but after loading the Console tells the loaded Code Size is:Text 492 bytes Data 2 bytes. How come there are no complains at all? I use the size-limited 16B compiler. What's the explanation?

    The 16KB limit is for the actual code and data that gets loaded on to the target. The *.out file not just has code and data, but also debug symbols. The debug symbols do not count against that 16KB limit.

    Thanks

    ki