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

How much the size of binaries file for debugging is when the compilation is completed?

Jo yonhghyun
Prodigy 80 points

Hi my name is Benjamin, Jo  nice to meet you.

I have a question I want to ask of you.

1. How much the size of binary files (for debugging / for download) is when the compilation is completed by using CCS5.1?

    We have used CC430 Embedded board as our target board which have about 4KB RAM, 32 KB Flash memory.

    But When I check the the size of ".out" file which has been appeared after compiling, it was approximately 200IKByte.

    But if you think about the size of CC430 Memory(4KB/32KB), it doesn't make sense to being able to run the ".out" code.

    But interesting thing is that it seems like work well even though its size is still larger than the size of flash memory that CC430 has.

    So I think that there are some other binary files I haven't known.

    Blow picture is showing the size of  ".out" file

   

     I'm looking forward your reply. and thanks for reading this.

  • 0
    TI__Guru*** 130875 points

    Hi Jo,

    the best way to see the actually size of the code being loaded onto the device is to look at the .map file that gets generated, not the .out.   The .out file, especially if you have built in debug mode, also contains the debug and symbol information.  Ie it has information in addition to the code.

    I hope this helps explain!  So please have a look at the bottom of the .map file instead.

    Best Regards,

    Lisa