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.

CC2511: Open-source agreements using TI libraries

Part Number: CC2511
Other Parts Discussed in Thread: CC2538

Hi there,

We've designed an active RFID unit for wildlife monitoring applications that uses a Texas Instruments CC2511 chip, and relies upon some code libraries from TI. We want to release the design to open-source (via a peer-reviewed scientific publication, hopefully, and on GitHub), but we are confused by some of the user terms in the licence agreement. Specifically, it seems we can't release proprietary code that TI has created, unless it's exclusively for a TI product. We designed the entire device exclusively around the CC2511, so we feel like we would be honouring the agreement, as there's no case in which a different chip could be used, nor would we ever recommend or suggest it. Is our interpretation correct, and if not, are there any possible work-arounds?

Thanks very much in advance.

Rob

  • Hi,

    Thanks for bringing this to our attention.

    Can you specify which software installation this is for CC2511?

    Do the source code have a clause at the top of the files?

    Regards,
    Toby

  • Hi Toby,

    Thanks very much for getting back to me. I am not quite sure what you mean by which software installation it is re: CC2511, but, the licence agreement says the following:

     Copyright 2007-2008 Texas Instruments Incorporated.  All rights reserved.    
                                                                                       
       4   IMPORTANT: Your use of this Software is limited to those specific rights granted under
       3   the terms of a software license agreement between the user who downloaded the software,
       2   his/her employer (which must be your employer) and Texas Instruments Incorporated (the
       1   "License"). You may not use this Software unless you agree to abide by the terms of the
    11     License. The License limits your use, and you acknowledge, that the Software may not be
       1   modified, copied or distributed unless embedded on a Texas Instruments microcontroller
       2   or used solely and exclusively in conjunction with a Texas Instruments radio frequency
       3   transceiver, which is integrated into your product. Other than for the foregoing purpose,
       4   you may not use, reproduce, copy, prepare derivative works of, modify, distribute,
       5   perform, display or sell this Software and/or its documentation for any purpose.
       6                                                                                
       7   YOU FURTHER ACKNOWLEDGE AND AGREE THAT THE SOFTWARE AND DOCUMENTATION ARE PROVIDED <93>AS IS<94>
       8   WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY
       9   WARRANTY OF MERCHANTABILITY, TITLE, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE.
      10   IN NO EVENT SHALL TEXAS INSTRUMENTS OR ITS LICENSORS BE LIABLE OR OBLIGATED UNDER CONTRACT,
      11   NEGLIGENCE, STRICT LIABILITY, CONTRIBUTION, BREACH OF WARRANTY, OR OTHER LEGAL EQUITABLE
      12   THEORY ANY DIRECT OR INDIRECT DAMAGES OR EXPENSES INCLUDING BUT NOT LIMITED TO ANY
      13   INCIDENTAL, SPECIAL, INDIRECT, PUNITIVE OR CONSEQUENTIAL DAMAGES, LOST PROFITS OR LOST
      14   DATA, COST OF PROCUREMENT OF SUBSTITUTE GOODS, TECHNOLOGY, SERVICES, OR ANY CLAIMS BY
      15   THIRD PARTIES (INCLUDING BUT NOT LIMITED TO ANY DEFENSE THEREOF), OR OTHER SIMILAR COSTS.
      16                                                                                
      17   Should you have any questions regarding your right to use this Software,      
      18   contact Texas Instruments Incorporated at www.TI.com.   

    Since our design exclusively uses the CC2511, we are hoping releasing our complete code (which includes some TI libraries) to open-source honours the agreement, but thought it best to first clarify with you. Thanks for your help.

    Rob

  • By software installation, I was wondering what software you were referring to, or what link was used to install it.

    For example, CC2538 has the foundation firmware: 

    This doesn't look like a BSD-3 clause, so I'm hesitant to say whether it may be used in that way.

    Let me check internally and get back to you on this.

  • Thanks very much Toby, it's appreciated.

    Rob

  • No problem at all.

    Can you confirm what software package you're using for the CC2511 so I can specify this?

    For example, is it SWRC088C as found here: https://www.ti.com/product/CC2511#design-development##software-development  ?

  • Hi again Toby,

    Just checked with our old engineer and he said he used SmartRF™ Studio to generate the code. Does that help at all?

    Cheers,

    Rob

  • From SmartRF Studio, the generated code are values to be written to the radio registers:

    I'm guessing there is other code which is used to run your specific application on the CC2511. This code would probably include some drivers (e.g. ADC, UART, ...).

    Can you elaborate from where you copy/pasted the license agreement above?
    I can pass along that language as-is, but I think it'd be useful to know exactly where the software was installed from (the name of the installer could also help).

  • Hi Rob,

    An update from my side:
    As-is, this license language does not permit sharing the TI code in open source.
    I have inquired further as to whether there is a workaround, and will update you if there is.

    From my perspective (and you and your team may have considered this already):
    If the application is designed such that your application specific source files are separate from the TI source files, the application could be open sourced on github. Then you could have some note stating that the TI specific code (e.g. drivers, RF register settings, ...) may be installed from a TI website (perhaps from this page: https://www.ti.com/product/CC2511#design-development##software-development).



    Regards,
    Toby

  • Hi Toby,

    I've just spoken with our former engineer again and he said it would be difficult to separate our application code from the example code it was built upon. Instead would sharing the compiled binaries without any source code be in alignment with the license? 

    Cheers,

    Rob

  • That may be a good alternative, I will check for you.

    In the meantime, I've sent you an E2E friend request so we can continue this discussion offline.

  • Thanks heaps Toby. Have accepted the friend request. Is that all I have to do?

    Cheers,

    Rob

  • No problem!

    Yes, let's continue the conversation offline.

  • I have not heard back, and recommend you create a TI support case here: 

    Hopefully they will have a better idea on who to contact for this issue.