• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 415 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.

Original question:

CCS: How to check Code size in CCS 8

CCS: Program / code size without Stacks and RTOS

Lars Heinrichs1
Prodigy 190 points

Tool/software: Code Composer Studio

Using View -> Memory allocation (or while uploading firmware to the device) I can see the total size of the program.

Is there an option to see the code size without RTOS and BLE Stacks? (using a CC2642 in my case).

The information is interesting as the firmware is an example implementation of a generic/hardware-independent SDK for embedded devices,
and I would like to provide estimates on ressource requirements for just the SDK itself.

How good of an estimate is using a base example project (e.g. the simple peripheral one) and simply substracting that from my code size?

  • 0
    TI__Guru**** 163045 points

    Lars,

    You can expand the Memory Allocation view and identify everything that is contributing to the code size.  So you add up your functions to see what your application is contributing to the overall size.  That would be a bit tedious though.

    I do not know of a way to Exclude TI-RTOS or the BLE stack from the count.

    I think your idea of using another project as a reference is a good one.  Something very simple that has RTOS and the BLE stack.  I believe that the RTOS size is pretty constant for this device.  I am not sure on the BLE stack.  I will loop in someone from the device side to comment.

    Regards,

    John

  • 0
    TI__Guru** 101540 points

    Hi Lars,

    The size occupied by the BLE stack is highly dependent of the functionalities used. For example, not using bonding will give a significantly lower flash size (this is only one example over dozens). As a result, it's important for you to make sure to have the same functionalities used in the base project and the real project. 

    An other solution that is coming in my mind (never did it before) would be to stub all the functions of the RTOS and of the BLE stack to make the measurement. Of course it would be a bit long the first time but it would provide the best result possible.

    Let us know if you need additional assistance,