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.

CAPTIVATE-FR2633: About Captivate Design Center Copyright

Part Number: CAPTIVATE-FR2633


Hi team,

I found the following statement in the library. If I add sample code as part of the source code as a deliverable, is it necessary to include a copyright statement?
I have decided that it is not required since we are not redistributing it as is, but I would like to confirm.

Sincerely.
Ryu

  • Hi team,

    How about this case?
    I would like a reply.

    Sincerely.
    Ryu

  • Hi Ryu,

    I apologize for the delayed response.

    Are you speaking of the Captivate Design Center GUI (Java code) or the Captivate Capacitive Touch Library?  I'll assume you mean the Touch library, since you are adding a sample.  Are you redistributing internally (within your company) or to public users?

  • Hi Dennis,

    Thanks for the reply.
    The subject is Captivate Capacitive Touch Library.
    We will be selling a product designed with the Library code incorporated into the product.

    Sincerely.
    Ryu

  • Hi Ryu,

    Ok, I'm being told that based on the BSD license for the Captivate Library, you are free to modify and re-distribute, however, you must also follow the licensing agreement that you can find in all of the source code files (copied for convenience).

    /* --COPYRIGHT--,BSD
     * Copyright (c) 2017, Texas Instruments Incorporated
     * All rights reserved.
     *
     * Redistribution and use in source and binary forms, with or without
     * modification, are permitted provided that the following conditions
     * are met:
     *
     * *  Redistributions of source code must retain the above copyright
     *    notice, this list of conditions and the following disclaimer.
     *
     * *  Redistributions in binary form must reproduce the above copyright
     *    notice, this list of conditions and the following disclaimer in the
     *    documentation and/or other materials provided with the distribution.
     *
     * *  Neither the name of Texas Instruments Incorporated nor the names of
     *    its contributors may be used to endorse or promote products derived
     *    from this software without specific prior written permission.
     *
     * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
     * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
     * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
     * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
     * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
     * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
     * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
     * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
     * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
     * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
     * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
     * --/COPYRIGHT--*/
    //*****************************************************************************

  • Hi Dennis,

    Thanks for the reply.
    I understand that we have to follow the copyright, but in this case, since we are not redistributing the library as is, I don't think we have to include the copyright in the deliverables, is that correct?

    Sincerely.
    Ryu

  • Hi Ryu,

    In parallel I have reached out to our legal team for guidance on this question.  This may take a day or two to get a response.

  • Hi Ryu,

    Here is the comment from our SW legal engineer.

    ============================================
    You are correct the TI license should still be in place, but if they modified the code substantially, then they can also add their own license terms.   They would just be an additional copyright holder.  Since it is BSD, I see no reason not to spike it out in the product.  It would help their customers to know what is in the application.
    ============================================

    Does this make it clear?  You will need to keep the TI copyright, but if needed, you can add your own.

    Is this a problem for your release?

  • Hi Dennis,

    Thanks for the reply.
    Just to confirm, you are saying that this needs to be stated in the instructions included with the product, etc., correct?
    Or do you mean that it must be in the source code of the software?
    The software is essentially for making the product work, not for distributing the software.

    Sincerely.
    Ryu

  • Hi Ryu,

    Instructions are fine.

    Sounds like I can go ahead  mark this posting as RESOLVED. If this isn’t the case, please click the "This did NOT resolve my issue" button and reply to this thread with more information.  If this thread locks, please click the "Ask a related question" button and in the new thread describe the current status of your issue and any additional details you may have to assist us in helping to solve your issues.

  • Hi Dennis,

    Thanks for the reply.
    Thanks for the reply.
    I'm sorry to keep asking this question, but I just want to confirm one last point.
    This is software that is used to run the product and the customer will not be able to see what is in this software.
    Is it still necessary to include it in the manual?

    Sincerely.
    Ryu

  • Hi Ryu,

    Ok, I see now. In this case you don't need to include it in the manual.

  • Hi Dennis,

    Thanks for the reply.
    My problem is solved.

    Sincerely.
    Ryu

**Attention** This is a public forum