VL53L1X ULD API license question

[gschorcht]

We plan to implement a VL53L1X driver based on this API for our Open Source Real-Time OS (community project) and would have to publish the API source code (content of directory STSW-IMG009_v3.5.4/API only) either as part of the GitHub repository of the OS or as a separate GitHub repository to use it as a package.

I had to accept the PLLA (SLA0081) to get the VL53L1X ULD API (STSW-IMG009) which restricts the use and the distribution of the code a lot. On the other hand this PLLA (SLA0081) also says that some portions of the licensed materials might contain Open Source Software subject to Open Source Terms.

The files in the API itself tell

  * This software is licensed under terms that can be found in the LICENSE file
  * in the root directory of this software component.
  * If no LICENSE file comes with this software, it is provided AS-IS.

And the `License.txt` in directory `STSW-IMG009_v3.5.4/API` says

This software component is provided to you as part of a software package and
applicable license terms are in the Package_license file. If you received this
software component outside of a package or without applicable license terms,
the terms of the BSD OPEN SOURCE SLA0103 license shall apply.
You may obtain a copy of the BSD OPEN SOURCE SLA0103 at:
https://www.st.com/SLA0103

I'm completely confused by the very complex PLLA license agreement. I'm wondering what license applies to the files in directory `STSW-IMG009_v3.5.4/API`. Is it possible to publish them in our GitHub repository of our Open Source OS or as standalone repository to use them as a package? We usually don't integrate vendor code directly but use it as a package downloaded from GitHub.

[John_Kvam]

I don’t work at st anymore having just retired. But this is my take. ST does not sell software. They would much rather sell the silicon and give away the software. They are good at that model. But they want to make sure some clown does not publish ST’s code and then get into a legal fight over whose code it is. So if you publish the code with ST’s SLA at the top ST would be overjoyed that you were using the code- and the hardware.

There are a huge number of publications on GitHub just like this. 

Everyone wins. You get your project done and ST sells parts. 
-John.