We’ve recently obtained a Stellaris LM3S8962 evaluation kit for use with an electric vehicle project, and at this stage, I’m looking into options for developing the controller firmware. One possibility is to base the code on FreeRTOS. The end product would link some proprietary code we’ve written with FreeRTOS - I understand that so long as we publish the modifications to FreeRTOS and make it clear that the project is FreeRTOS-based, this is acceptable. There’s a few concirns however that I have regarding the libdriver.a and libgr.a files…
Does anyone happen to know where these files came from? To me they are binary blobs that seem to have mystically appeared in the FreeRTOS codebase. They look like they come from the StellarisWare package, but I’m unsure. Wouldn’t it be better to distribute the sources for these files?
There’s an EULA distributed with them, not being a lawyer, my legalese is very scratchy indeed. I can’t seem to quite make out what is being said, but they mention something about it not being permitted to combine their code (which I presume to mean in either source or binary form) with what they call “viral open-source” software (and they give the example, GPL-licensed software as being in this category).
Does this mean TI/Luminary Micro’s license is broken by linking their libraries with FreeRTOS since FreeRTOS is GPL?
I’m looking at writing my own library to do this (just purely based on the LM3S8962 datasheet) to get around this issue… and if I get that up and running, I may be able to contribute that as a fully GPL port to the FreeRTOS project. Is there any interest in replacing this code with a less restrictive alternative?