Author Topic: which ARM rtos?  (Read 16641 times)

0 Members and 1 Guest are viewing this topic.

Offline Marco

  • Super Contributor
  • ***
  • Posts: 4600
  • Country: nl
Re: which ARM rtos?
« Reply #50 on: February 22, 2017, 11:28:10 am »
Of which the incompatible part is the Tivoization clause that forces you to provide ways to change the firmware.

Forcing this on developers is not a bad thing with IoT. This is an industry in which people still program internet facing code in C after all.
 

Offline donotdespisethesnake

  • Super Contributor
  • ***
  • Posts: 1021
  • Country: gb
  • Embedded stuff
Re: which ARM rtos?
« Reply #51 on: February 22, 2017, 02:34:06 pm »
This discussion is confusing, because there are at least 4 different types of licenses that might be called "GPL", and many meanings to the word "free". The advice I would give depends on the type of company, a "traditional" engineering company probably couldn't cope, other companies who already contribute to Open Source projects might have no problems.

As someone with a foot in both camps, I would be wary about including any GPL code in a proprietary microcontroller program. I'm not saying it can't or shouldn't be done, it just requires careful checking of the actual license and how that would impact the product, e.g. if it says "GPLv2" or "GPLv2 or later", there is a significant difference. Even if I am satisfied myself it is OK, I would still want to run it past legal dept. Everyone including management needs to be on board with the idea of using GPL code, and what requirements and responsibilities that entails, if there is *any* risk that proprietary code might need to be published. I don't want to be doing a hurried rewrite because someone misunderstood, nor find myself on the block for pushing "company code" to a public repo because the GPL requires it.

Even BSD code could be problematic, if it requires notices in the product manual for example.

tldr; Open Source code can bring a big advantage in development time to proprietary products, but be very aware of all the implications first.



Bob
"All you said is just a bunch of opinions."
 

Offline Jeroen3

  • Super Contributor
  • ***
  • Posts: 3400
  • Country: nl
  • Embedded Engineer
    • jeroen3.nl
Re: which ARM rtos?
« Reply #52 on: February 23, 2017, 07:32:38 am »
Of which the incompatible part is the Tivoization clause that forces you to provide ways to change the firmware.

Forcing this on developers is not a bad thing with IoT. This is an industry in which people still program internet facing code in C after all.
I completely agree, as end-user. But my employer does not want the core features of the products to be available as source code or assembly bin. This means JTAG lock.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf