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

Size of .bin, size of .out and size on flash

yl
Expert 1215 points

Hi,

Is there any predictable relation between these sizes?

My bin file is about 726kB, the AISgen generated out file is about 190kB. When I burn it to flash, what will be the size on SPIFlash?

I am using EVM6747 with CCS3.3 and latest updates.

Thanks

  • 0
    TI__Guru*** 125430 points

    The out file is a poor predictor of the size of your code/data.  Besides the actual code/data there is also tons of information like symbols, call stack info, etc.  There should also be a map file generated along-side the out file which should contain the specific info related to your build, i.e. how much code/data is being allocated and to what addresses.

    I'm not sure exactly what the difference is between your AISgen out file and your bin file.  Where exactly is this bin file coming from?  Ultimately what you are burning to flash will be an Application Image Script (AIS), so it would make sense that the output of AISgen would be the best indicator of the size.  The only thing to be careful about is to ensure that the output is actually a binary output and not an ascii representation of the output.  If it's in ascii it will be significantly bloated.

    Based on what you've said above my best guess would be that the 190KB file from AISgen is the size of what's being burned to flash.

    Brad