cancel
Showing results for 
Search instead for 
Did you mean: 

SAVE THE STM32: an appeal for sanity

lanchon
Associate II
Posted on June 23, 2008 at 16:38

SAVE THE STM32: an appeal for sanity

33 REPLIES 33
lanchon
Associate II
Posted on May 17, 2011 at 12:35

hi,

ST recently released v2 of the firmware lib and usb kit. this post makes two comments about them.

1) packaging:

the previous versions were posted in a reasonably open and de facto standard packaging file format: zip files. unbelievably, the new versions are win32 exe files. I'm sure some lawyer who has to justify his paycheck demanded that the files be distributed using a click-through license and an exe was just the simplest way to comply.

unfortunately now users are exposed to the aggravation of having to run untrusted and potentially unsafe code on their machines and *install software* just to get to a couple of text files. of course users who avoid microsoft OSes for kiddies and choose various other options are completely denied access and left behind. BTW, I believe from personal experience that this category includes some of the most talented developers.

so please ST, if you really have to make us click through, at least implement the click-through in the web server and republish the files using an open format.

2) license:

I've never seen the click-through license of the new files, but I strongly suspect it exists. (could someone post it?) I've seen the earlier license of the firmware lib though; here it is:

********************************************************************************

* THE PRESENT SOFTWARE 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 SOFTWARE AND/OR THE USE MADE BY CUSTOMERS OF THE CODING

* INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS.

*******************************************************************************/

a simple, *SANE* license. it just says, hey, we want to help you. it says, you know, this code is so completely linked to our STM32 product that you won't be able to use it in any useful way without buying our product, so just have fun with it: learn, build on it, improve it, and share.

however I suspect there's a new license will all sorts of crap in it. at a minimum, you probably won't be able to share the source code: forget about open source software based on the lib, forget about publishing bug-fixes to the lib, hey, even forget about *discussing* bugs and features in ST's forum like it's been done until now (by posting a line of the lib's source code and asking ''is this right?''). heck, are we even allowed to discuss the prototypes of the functions? they sure are copyrighted! how about just their names?

anyway, a while back I published a little c++ build environment for the stm32 in this forum which at the time was the only fully open source solution (is it still?). it included the fwlib 1.0. unfortunately it won't be updated to support the high-density devices due to these issues. even if it were, it probably couldn't be published and wouldn't be open source.

I've also posted an easy way to route stdio via a USB CDC COM port, it's great help for debugging. it included the usb kit and some sample code with many bug-fixes. I can't upgrade it to usb kit 2.0, though. tough luck!

again, I'm supposing a restrictive license applies. if that's the case, for me the high-density devices and the new software releases just don't exist. I'm sticking with v1.0 software and medium density until ST (hopefully soon) assumes a sane position on these issues.

ST: don't let some lawyers who ignore how the developer community works and behaves run things, they'll ruin the STM32. if you need lawyers with insight, maybe you could ask

http://en.wikipedia.org/wiki/Lawrence_Lessig

for recommendations.

please forgive me if I got a little carried away with the language, this is just too important for me. if the STM32 looses its openness I'll move on to another supplier, like I've done many times in the past.

thanks for reading.

st3
Associate II
Posted on May 17, 2011 at 12:35

Quote:

unfortunately now users are exposed to the aggravation of having to run untrusted and potentially unsafe code on their machines and *install software* just to get to a couple of text files.

Absolutely! :|

Surely, the whole point of releasing such stuff is to encourage potential customers to use the product?!

I can't imagine this having any effect other that to discourage potential users! :|

juraj
Associate II
Posted on May 17, 2011 at 12:35

I had to find some Windows station to have new FWlib extracted.

sjo
Associate II
Posted on May 17, 2011 at 12:35

I must have to agree that having to install source code is not a good way forward.

there are many users using nix based dev platforms, including me!!

Cheers

sjo

gommel
Associate II
Posted on May 17, 2011 at 12:35

Being a Mac user I have to agree that the .exe format is not the best solution for packaging some files 😉

miles
Associate II
Posted on May 17, 2011 at 12:35

The original post was too long to process during our migration. Please click on the provided URL to read the original post. https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006I6Y4&d=%2Fa%2F0X0000000bqQ%2FhOQ04ue748tvhPkOzcan0ttVyAoSj5Uqbnrqz44BcDg&asPdf=false
st3
Associate II
Posted on May 17, 2011 at 12:35

Quote:

No source code and/or object code relating to and/or based upon Licensed Firmware is to be made available by You to any third party for whatever reason.

In other words, you cannot use this if you are a subcontract developer - because to deliver your work to your customer would violate this term!! :o :o

How absolutely and completely ridiculous!! :| :| :| :|

It may not be too late to design-out the STM32... :|

lanchon
Associate II
Posted on May 17, 2011 at 12:35

hi miles, thanks for posting the license. I see I was right supposing there was a restrictive license, but I never would have expected such an extremely abusive crap.

> In other words, you cannot use this if you are a subcontract developer - because to deliver your work to your customer would violate this term!!

actually it's much worse: YOU CAN'T EVEN CREATE A FIELD-UPGRADABLE DEVICE BECAUSE YOU CAN'T GIVE THE ENCRYPTED FIRMWARE IMAGE TO YOUR CUSTOMERS! can you believe lawyers this ignorant? and ST letting them have their way?

here are a few things you can't do:

-release free software for the stm32

-sell stm32 software

-sell a project or work unit

-release bug-fixes for the libs

-discuss lib bugs and features in ST's forum if it involves pasting code

-develop for contractor

-contract development

-end-user firmware upgrades

-3rd party maintenance if it includes upgrades

wow! no simley available for the face I'm putting right now... and take a look at this part, it's really funny: ''You agree that ST shall have the right [...] upon reasonable notice to enter Your's official premises in order to verify your compliance with this Restriction clause.'' say what?

> It may not be too late to design-out the STM32

you can still use v1 of the libs. I mean, this *has* to be a temporary mistake, right?

slawcus
Associate II
Posted on May 17, 2011 at 12:35

So ST firmware library is useless but that doesn't mean that one can't use STM32 at all. Markenting guys can't advertise STM32s advantage in quick development startup.

However how many manufacturers do you know that provide firmware library?