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.

CC2564B: Open Source Licensing With Bluetooth Init Scripts

Part Number: CC2564B

I'm assisting with a group that is building an open source firmware for an existing product that uses the CC2564B. The question came up about licensing issues with TI's Bluetooth stack vs open source solutions. However, no matter what, the Init Script binary has to be loaded to the chip on power up and must be embedded into the source or distributed somehow.

How is the init script () licensed, and is it compatible with common open source licenses (such as MIT, BSD, or GNU)? Is there a difference between distributing sources with the scripts and distributing compiled firmware with the scripts embedded?

Thank you!

  • Hello Chris,

    The init script can only be issued by TI.
    This is not something you can access or get the code of.

    Please let me understand what exactly do you need and I would love to help you achieve that.

    BR,
    Chen Loewy
  • For example, if the source of our project is open and published publicly, is the data of that init script allowed to be embedded in that public source? What type of license is associated with distributing the init script data in either source or compiled binaries?

    Essentially we are building an open peice of software and want to know how the inclusion of the mandatory binary init scripts affect us from a licensing/copyright standpoint. I could not find any licensing info on the download page.

  • Hello Chris,

    Let me check with our legal department and get back to you on this issue.

    BR,
    Chen Loewy
  • Hello Chris,

    The init scripts are licensed using our TI Text File License which can be found in the download in the file “TILAW-#279184-v1-WBU_TSPA_Software_License.txt”.

    While we don’t consider this an open source license, as it has a use restriction to TI devices, we do feel it is only compatible with permissive open source licenses like BSD and MIT.

    We would urge you to consult your internal Open Source Experts and/or Legal for specific use cases.

    Concerning your second question:
    The firmware is subject to the TI text File license whether it is embedded in a script or a separate file

    Thanks,
    Chen Loewy