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

CC256x service packs and BlueStone One software stack memory requirement

Engineer1
Intellectual 660 points

Other Parts Discussed in Thread: CC2564

Some questions regarding CC2564 (and CC256x in general) service packs and the StoneStreet One software stack.

The TI web page indicates the service packs are in "BTS" format and must be loaded upon power-up of the CC2564.

1)  Is "BTS" format a TI creation?

 2)  Where is the documentation for firmware developers regarding the loading of service packs into the CC2564 -- are there functions to do it through the Stonestreet One SDK?  Or is loading of vendor-specific "service packs" covered in the Bluetooth 4.0 HCI spec?

 3)  Does the service pack need to be reloaded after assertion and deassertion of nSHUTD if power is maintained or only after power cycling?

 4)  Does the entire service pack need to be loaded, or can a subset be loaded for a particular implementation?

5)  Does the StonestreetOne stack reside (in full) in flash memory of the MSP430, or are only the functions used linked in to minimize memory resource requirements?

6)  Is there any information about how much flash and RAM memory the StoneStreet One stack for MSP430 controlling the CC2564 requires?

7)  Can the StoneStreet One stack be used with any MSP430 processor that meets requiremets, or is it limited to use with only one specific member of the MSP430 family, and if so what is that specific processor?

  • 0
    TI__Mastermind 25035 points

    Hi,

    1. yes.

    2. It is done in the SSO stack once during initialization.

    3. Yes, you should reload the SP on both cases. 

    4. Entire SP should be reloaded.

    5. Entire SSO stack resides in MSP430 flash. It depends on the compiler for different optimizations.

    6. Yes. What profiles are you planning to use?

    7. Yes, it can be used with any MSP430 as long as it meets the memory requirements.

  • 0 in reply to Zahid Haq
    Intellectual 660 points

    Thanks for the answers above.

    We were planning to use a simple SPP for cable replacement.  Initially probably using only classic Bluetooth, possibly in the future BLE for some connections.  Planning to use the CC2564 to give the option of using BLE in the future.  Do you have an estimate of code size for classic BT implementation of SPP using CC2564?  Please also indicate whether your number includes or excludes the size of the service pack.  Interested in both flash and RAM requirement.

    Also, the current CC2564 service pack version 2.8, after unpacking, is 23,440 bytes, but much of that appears to be overhead (comments, white space, etc.).  Is this the image of what would need to be placed into flash memory, so the current MSP430 flash memory usage just for the service pack is 23,440 bytes?

  • 0 in reply to Engineer1
    TI__Mastermind 25035 points

    Hi,

    Our device is perfect for cable replacement. Our SPPDemo takes up about 110 KB Flash and about 7KB RAM including the SP2.8.