Use of Teensy in a commercial project and licensing fees

A

Aston

New member
Hello Teensy community, is there any resource about licensing fees or obligations attached to using a) the teensy hardware in a commercial project and b) parts of the code. For the latter I am especially thinking about the use of libraries use, such as Audio.h, Wire.h, SPI.h, SD.h, SerialFlash.h

Any pointer would be greatly appreciated.

Adrian
 
Aston said:
Still leaves me ambiguous about the Arduino part though.
Click to expand...

Each open source library has license terms which allow you to the use the code. Usually this can be found in the comments at the beginning of the code. Some have a separate license file.

I need to emphasize the official word is in those license terms. There is no single file or web page with an official summary.

Speaking informally, certainly not a substitute for checking the actual license terms for every library your program incorporates, most of them are MIT or MIT-like. MIT license is generally understood to impose minimal restrictions with terms most people find acceptable for incorporating into proprietary commercial software. But again, these words are only an informal explanation. See the actual license for the actual terms.

Of the libraries you mentioned, in old versions (Teensyduino 1.53 and earlier) the SD library was GPL. It changed to MIT starting with version 1.54.
 
PaulStoffregen said:
Each open source library has license terms which allow you to the use the code. Usually this can be found in the comments at the beginning of the code. Some have a separate license file.

I need to emphasize the official word is in those license terms. There is no single file or web page with an official summary.

Speaking informally, certainly not a substitute for checking the actual license terms for every library your program incorporates, most of them are MIT or MIT-like. MIT license is generally understood to impose minimal restrictions with terms most people find acceptable for incorporating into proprietary commercial software. But again, these words are only an informal explanation. See the actual license for the actual terms.

Of the libraries you mentioned, in old versions (Teensyduino 1.53 and earlier) the SD library was GPL. It changed to MIT starting with version 1.54.
Click to expand...
Hello Paul, thanks for taking the time to answer my question. I have reviewed all the libraries and their respective licenses. For those under the MIT license, everything seems straightforward.

However, with libraries licensed under LGPL 2.1, the situation appears more complex. My understanding is that the LGPL does not require the disclosure of the entire code that uses these libraries. Nonetheless, it must be ensured that the program can be recompiled using modified versions of these libraries. How is this requirement typically met in cases of static linking, especially for compiled code running on a Teensy microcontroller?

I’m curious to see how others in the community have addressed this issue.
 
You must log in or register to reply here.
Back
Top