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

flash size in CC2540 used in mini dev-kit

bob frankel
Expert 2460 points
Other Parts Discussed in Thread: CC2540

i may have missed this in the docs, but does the CC2540 used in the mini-dev kit have 128K or 256K of flash????  either way, i assume there is 8K of data RAM....

building the SimpleBLEPeripheral project yields about 103K of code and 5.8K of data....  given that the application/profile is relatively simple, i assume most of this code/data is taken up by the stack itself (and perhaps the OSAL/HAL layers)....  for planning purposes, is this the smallest footprint for the stack and its support code; or are there ways to shrink further???

related to this, what's the difference between the 128K and 256K devices in terms of:  1) price???  and 2) power-performance???  the answer can be in general terms; i'm just trying to roughly quantify the advantage of the smaller 128K device....

thanks in advance....

  • 0
    TI__Expert 7055 points

    Bob -

    For the relative pricing, I'd make some guesses based on the 1ku prices published on the CC2540 product folder - Those prices will stay updated over time.   http://focus.ti.com/docs/prod/folders/print/cc2540.html

    You'll find a few different part numbers, reel sizes, flash size there to make your tradeoff.

    I'll wait for someone else to comment on the miniimum flash size requirements.

    thanks,

    Jake

     



  • 0
    TI__Genius 17975 points

    There is no difference in power performance between the 128k and 256k parts. For details on how much code space each module in your application is consuming, take a look at the linker output "map" file and scroll to the very bottom. You will see a summary like this with the total code and memory consumed:

     

     57 920 bytes of CODE  memory
         26 bytes of DATA  memory (+ 73 absolute )
      2 970 bytes of XDATA memory
        192 bytes of IDATA memory
          8 bits  of BIT   memory
      4 022 bytes of CONST memory

    If you scroll up a bit you'll see a section labeled "Module summary" like this with more detailed information:

                   ****************************************
                    *                                      *
                    *            MODULE SUMMARY            *
                    *                                      *
                    ****************************************