cancel
Showing results for 
Search instead for 
Did you mean: 

Software License for Firmware provided by ST

rvmail-st
Associate
Posted on April 24, 2010 at 08:04

Software License for Firmware provided by ST

5 REPLIES 5
Andrew Neil
Evangelist III
Posted on May 17, 2011 at 13:48

There was a big fuss about this a couple of years ago when ST apparently got some over-keen young lawyer on the case, and came up with a totally unworkable mountain of legalese.

They had to withdraw that licence, and I don't think things have changed since then.

There are 2 basic principles

1. No warranty;

2. You must not use it on non-ST processors.

But, of course, I am not a lawyer - so you really do need to speak direct to ST about this.

If you don't have a direct ST contact, then go through your Distributor.

I don't know if the old forum discussions are still available now - but you could try a search.

Nickname12657_O
Associate III
Posted on May 17, 2011 at 13:48

Dear valuable contributors,

Thank you for the interest of using our products. @page Section1 {size:8.5in 11.0in;margin:1.0in 1.25in 1.0in 1.25in;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 P.MsoNormal {margin:0in 0in 0pt;font-family:'Calibri','sans-serif';font-size:11pt;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 LI.MsoNormal {margin:0in 0in 0pt;font-family:'Calibri','sans-serif';font-size:11pt;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 DIV.MsoNormal {margin:0in 0in 0pt;font-family:'Calibri','sans-serif';font-size:11pt;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 A:link {color:blue;text-decoration:underline;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 SPAN.MsoHyperlink {color:blue;text-decoration:underline;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 A:visited {color:purple;text-decoration:underline;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 SPAN.MsoHyperlinkFollowed {color:purple;text-decoration:underline;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 SPAN.EmailStyle17 {font-family:'Calibri','sans-serif';color:windowtext;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 .MsoChpDefault {;} .ExternalClassA32CE19B60CF4FCF9663D6AC6D8738B9 DIV.Section1 {page:Section1;}

  In General, our standard libraries , enclosed firmware and related documentation published

on web

are not covered by a License Agreement but just with the Following

disclaimer

:

''THE PRESENT FIRMWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE TIME. AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING FROM THE CONTENT OF SUCH FIRMWARE AND/OR THE USE MADE BY CUSTOMERS OF THE CODING INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS.''

 

But if one of our customer needs such License  for his special usage for example to sub-license some parts of our software in his code , He can contact his local STMicroelectronics office to get a hard-copy and agreement with our sales groups.

In that case, We will send him  The attached LICENSE AGREEMENT  for our STM32F10xx product families.

This is quite standard format of Agreement used by all silicon/micro manufacturers to be protected by illegal use  ''on products'' not from STMicroelectronics.

Hope it is clear for you, even you are not a lawyer.  as the case of most of all of our contributors in these Forums.

Cheers,

STOne-32.    { Your STM32 Moderator}

picguy2
Associate II
Posted on May 17, 2011 at 13:48

I think what the license / disclaimer says is roughly, “You are 100% on your own but we hope this helps.  Please buy our parts.  Try our code on non-ST parts?  Feel free (how would we ever know) but remember our support code is closely tied to our products.�?

Andrew Neil
Evangelist III
Posted on May 17, 2011 at 13:48

''Try our code on non-ST parts?  Feel free''

No. What it's saying, specifically, do

not

use this on non-ST parts.

But you're right - how would they know...?

Andrew Neil
Evangelist III
Posted on May 17, 2011 at 13:48

For more licence controversy, see:  

http://blogs.techrepublic.com.com/programming-and-development/?p=2486&tag=nl.e055