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.

TM4C123GH6PM: Legal question about software export controls involving projects derived from TivaWare example code

Part Number: TM4C123GH6PM

I am writing an article for publication regarding a hardware/software application that features code from one of the TivaWare examples.  According to the rules of the publisher, the source code must be available for publication and distribution.  As the author, what responsibility do I own for ensuring that I do not violate TI's software export control license?  Can the TivaWare code be encapsulated into a compiled library to meet the non-export requirements? Sorry, I am only a protocol droid, and not very knowledgeable about such things...

  • Hello Joseph,

    I need to ask around about this, I am not a legal expert, but I will see what I can find out for you. It may take a couple days, but I will update what I can on Friday even if I don't have an answer by then.
  • Ralph,

    No worries. I am early in the process, so a few days is not an issue.

    Cheers,

    Joe
  • Hello Joseph,

    The feedback I received is that TI does not provide specific guidance on export controls.

    The ECCN for TivaWare outlines the following for export control, hopefully this is helpful for determining what you need to do:

     Any use made of Texas Instruments (TI) classifications; whether it be ECCNs or HTS; is without recourse to TI and at the risk of the user. HTS and export classifications are subject to change. Your company; as the exporter of record; is responsible for determining the correct classification of any item at the time of export.

    Any HTS or export classification by TI is for TI internal use only and shall not be construed as a representation or warranty regarding the proper export classification nor relied upon to make licensing determinations.

  • Ralph,

    Thank you for the info.

    Cheers,

    Joe