• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 202 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.

PROCESSOR-SDK-AM335X: License part for the tisdk9.1

Manu kumar
Intellectual 510 points
Part Number: PROCESSOR-SDK-AM335X

Tool/software:

Dear [TI Support/Team],

As part of our project, we have used TISDK 9.1 (cloned from the official sources), and during our OSS license audit, we noticed that several components included in the SDK—such as curl, Python, lighttpd, and others—are under various open-source licenses.

We would like to clarify the following:

  • Are these components included in TISDK 9.1 under valid open-source licenses?
  • Do we, as users of TISDK, need to obtain any separate commercial licenses for any of these components?
  • Is TI responsible for vetting the licensing of bundled components, or is it expected that downstream users handle OSS clearance individually?

We are raising this question as part of our internal OSS clearance process, where we encountered license-related queries and would like to ensure we are compliant.

Looking forward to your clarification.

  • 0
    TI__Mastermind 44306 points

    Hi Manu,

    not sure if we can answer that easily. I have a problem understanding what you mean with "valid open source licenses".

    The relevant licensing info for that SDK is available here:

    https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-9sG0TixXvC/09.03.05.02/software_manifest_am335x-evm.htm

    The examples you mentioned are not TI code I assume and you need to use the included links to go to the original sources. Some of them may contain commercial licenses based on conditions (for example QT Libs...). We do not obtain any commercial licenses for customers. And we do not know which of the provided sources finally end up in your product as the SDK is a larger subset of SW. You most likely will use a different kernel config and file system. I highly recommend that you work with your OSS team on this directly. In case you have questions for any TI generated license we can help here.  Please make sure you also understand the disclaimers in our files. In no way I can provide legal advice and would need to defer to our legal team in such a case.

    Regards, Frank

  • 0 in reply to Frank Walzer
    Intellectual 510 points

    H ,

    Below is my question with the continuation of the above,

    1. OpenEmbedded / BitBake
    License: GPLv2 or later + permissive licenses (MIT, BSD, etc.)
    Action Required: GPLv2-only components cannot be used in our project. We need to verify if any such components are present and replace/remove them accordingly.
    2. OpenEmbedded / BitBake (Toaster UI Components)
    License: GPLv2-only
    Action Required: Not allowed under our license policy. Please confirm if any Toaster UI components are included in our build and suggest removal or alternatives if found.
    3. OpenEmbedded / openembedded-core
    License: Mix of MIT and GPLv2-only
    Action Required: Most metadata is MIT licensed and fine. However, any GPLv2-only code (e.g., in recipes) must be identified and removed or replaced to stay compliant.
    4. sources/bitbake/lib/toaster/toastergui/static
    License: MIT License
    Attribution: Bootstrap (Twitter)
    Status: This appears to be under MIT and likely acceptable for use, provided proper attribution is included in our documentation. The origin of this library is unclear. Please confirm whether it was obtained under a valid license agreement or through any open-source channel.

  • 0 in reply to Manu kumar
    TI__Mastermind 44306 points

    Hi Manu,

    non of the above is TI owned or sourced I assume. It is fully under your control what sources to use and what not. Don't think this is a job for our support team.. As such we can close here.

    Regards, Frank