Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32


SW4STM32 projects on Bitbucket, Github, etc?

Hi folks,
Are there licensing issues with putting SW4STM32 projects up on public repositories such as Github, Butbucket and similar?

Right now I’m working on integrating board support with an MX generated project and using the OpenSTM32 IDE to build on Linux. It seems to me that this might be useful to others as well.

There’s a myriad of licenses involved including HAL libraries, board support, code produced by MX, third party libraries like STemWin, FreeRTOS, LwIP and probably more. I’ve reviewed the licenses I could find and for the most part it seems that if I include the licenses distributed with the various parts, I remain compliant.

Is there anything I need to do to not violate any license for OpenSTM32?

Any other licensing issues I need to explore? I do plan to ask at the ST forum as well.

Thanks!

France

Hi,

There is no strings attached to the use of System Workbench for STM32. You can publish your code the way you want, on any platform you like. The licenses that are displayed apply to the tool itself or the firmware code provided by ST (that can only be used on STM32X MCUs) or others, but your code can be licensed on the licensing terms you prefer, as long as your license is only applying to your code (a license that would request licensing all code linked to your code to be licensed similarly may conflicts with the firmware license); however this is only a question fo choice for the licensing you apply to your code, not to constraints of the source code hosting platform.

Hoping this woll clarify things,

Bernard (Ac6)

PS: Note that this means that GPL may not be appropriate, while Apache will most certainly be. However, as usual, IANAL (I am not a lawyer wink)


Hi Bernard,
Thank you for confirming that.

As for my code, there is actually very little at this point. I’m just combining MX output with HAL library examples and trying to get something that works. Eventually I will code something useful and will need to address license for my coda at that point and I will keep your copmments in mind.

Apologies for the typos in the message. The forum editor has put the cursor several characters to the right of the actual insert point and that makes editing a bit difficult.