Recommend way for standalone ERIKA OS export

Forum related to ERIKA Enterprise and RT-Druid version 2

Moderator: paolo.gai

Post Reply
MatzeB.
Newbie
Posts: 14
Joined: Fri Jul 08, 2016 11:19 am
Contact:

Recommend way for standalone ERIKA OS export

Post by MatzeB. » Wed Nov 08, 2017 10:10 am

Hi,

I've wrote a "Logical Execution Time" implementation which supports ERIKA OS as a possible underlying operating system. My current test setup consists of an AURIX TC275ED and ERIKA OS 2.7. General idea is, to publish the LET implementation on github, licensed under LGPL. For this it would be nice if the repository would include a complete setup with the configured Infineon iLLD (as a static lib) and a configured ERIKA OS. Is their an easy way to export my the current ERIKA workspace, in order to provide a standalone setup, which doesn't need an Eclipse Framework?

Best regards
Matthias

e.guidieri
Full Member
Posts: 166
Joined: Tue May 10, 2011 2:05 pm

Re: Recommend way for standalone ERIKA OS export

Post by e.guidieri » Wed Nov 08, 2017 2:14 pm

Hi Matthias,

it is possible for sure to invocke RT-Druid from command line to generate the configuration, but if you need to change the .oil you need some form of generator.
Indeed there is a stripped down version of RT-Druid with only the generator invockable in command line.

If you want just provide only ONE configuration (no changes to the .oil file allowed) just copy what is in folder out/Debug and publish it.
It contains a makefile that can be invocked in cygwin shell.

Errico

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: Recommend way for standalone ERIKA OS export

Post by paolo.gai » Fri Nov 10, 2017 5:57 pm

This is quite interesting! there are in fact ongoing discussions on the LET also inside the AUTOSAR consortium.

just some additional notes:

- if you are using the command line rt-druid, you'll need both the tool and a copy of the repository

- in the GitHub if you are going to put a pre-built version of ERIKA, you need to cite which version of the repository you are using (or you need to keep the original sourcecode in case someone is going to ask it to you).

- Just a curiosity: are you sure about the LGPL license? it is not that suited for static linking (that is the reason why ERIKA2 opted for the linking exception)

Ciao,

PJ

MatzeB.
Newbie
Posts: 14
Joined: Fri Jul 08, 2016 11:19 am
Contact:

Re: Recommend way for standalone ERIKA OS export

Post by MatzeB. » Mon Nov 13, 2017 9:57 am

Hi
paolo.gai wrote:This is quite interesting! there are in fact ongoing discussions on the LET also inside the AUTOSAR consortium.
I know ;-). We (the group of Rolf Ernst) already collaborated with some of the involved partners from industry and in order to consolidate the work between academia and
industry, there will also be a Dagstuhl Seminar in 2018 http://www.dagstuhl.de/no_cache/en/prog ... emnr=18092
paolo.gai wrote: - if you are using the command line rt-druid, you'll need both the tool and a copy of the repository
Ok, got it. Therefore also a repo, including my sources and a script to download the standalone rt-druid version should work for me.
paolo.gai wrote: - in the GitHub if you are going to put a pre-built version of ERIKA, you need to cite which version of the repository you are using (or you need to keep the original sourcecode in case someone is going to ask it to you).
Ok, also an option.
paolo.gai wrote: - Just a curiosity: are you sure about the LGPL license? it is not that suited for static linking (that is the reason why ERIKA2 opted for the linking exception)
Well, I picked the LGPL to the best of my knowledge and belief ;-). As no code has been published yet, I can change this easily. It is important to me, that my implementation is open source, as I believe in the general idea of free and open software. But since most software suppliers in the automotive domain do not share my view on open software (ERIKA is the only exception I know ;)), I need a license which can be linked to binary blobs. Also the published LET implementation should always stay open source. I always thought that the LGPL was made for this case, but I'm definitely no license expert.

At the moment I don't plan to make this a product. I just realized during our collaboration with partners from the industry, that often the OEMs have heard of LET but they don't know how to imagine the implementation. My simple implementation should provide them some kind of sandbox to play with, same for academia. For a real integration into the series, I don't want to be responsible. For this case there are other experts available (and I think, I also violated MISRA-C way to often 8))


Best regards
Matthias

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: Recommend way for standalone ERIKA OS export

Post by paolo.gai » Mon Nov 13, 2017 10:42 am

MatzeB. wrote: I know ;-). We (the group of Rolf Ernst) already collaborated with some of the involved partners from industry and in order to consolidate the work between academia and
industry, there will also be a Dagstuhl Seminar in 2018 http://www.dagstuhl.de/no_cache/en/prog ... emnr=18092
Good. I met Prof. Rolf Ernst a few times, and I know a few colleagues of the Retis Lab in Pisa and of UNIMORE in Modena working on this!
MatzeB. wrote:.
paolo.gai wrote: - Just a curiosity: are you sure about the LGPL license? it is not that suited for static linking (that is the reason why ERIKA2 opted for the linking exception)
Well, I picked the LGPL to the best of my knowledge and belief ;-). As no code has been published yet, I can change this easily. It is important to me, that my implementation is open source, as I believe in the general idea of free and open software. But since most software suppliers in the automotive domain do not share my view on open software (ERIKA is the only exception I know ;)), I need a license which can be linked to binary blobs. Also the published LET implementation should always stay open source. I always thought that the LGPL was made for this case, but I'm definitely no license expert.
Hmmm... IMHO be careful on the licensing options... LGPL requires you to be able to re-link a different version of the source code. As a result it makes LGPL in my view not usable for static linking, but only for dynamic linking. On the other hand, the GPL+LE used in ERIKA2 (and its variation in ERIKA3) allows you to keep the implementation open and let companies link closed source code
MatzeB. wrote:.
At the moment I don't plan to make this a product. I just realized during our collaboration with partners from the industry, that often the OEMs have heard of LET but they don't know how to imagine the implementation. My simple implementation should provide them some kind of sandbox to play with, same for academia. For a real integration into the series, I don't want to be responsible. For this case there are other experts available (and I think, I also violated MISRA-C way to often 8))
I perfectly understand you...

Just as a note, please let us know whenever you will publish. We could add a project page in the ERIKA webpage, and we could also put some links / prebuilt demos in the ERIKA source tree so that everyone will see them when creating a new project...

(note: we just released ERIKA 2.8, which is a repackaging of the latest sources...)

Ciao,

PJ

MatzeB.
Newbie
Posts: 14
Joined: Fri Jul 08, 2016 11:19 am
Contact:

Re: Recommend way for standalone ERIKA OS export

Post by MatzeB. » Mon Nov 13, 2017 2:04 pm

paolo.gai wrote: Hmmm... IMHO be careful on the licensing options... LGPL requires you to be able to re-link a different version of the source code. As a result it makes LGPL in my view not usable for static linking, but only for dynamic linking. On the other hand, the GPL+LE used in ERIKA2 (and its variation in ERIKA3) allows you to keep the implementation open and let companies link closed source code
Ok, you are right. https://en.wikipedia.org/wiki/GPL_linking_exception LGPL on its own would not work for me. Thanks for the advice, I wasn't aware of that fact.
Did you modify the lic. by yourself or did you use a predefined text snipped in order to include the LE?
paolo.gai wrote: I perfectly understand you...

Just as a note, please let us know whenever you will publish. We could add a project page in the ERIKA webpage, and we could also put some links / prebuilt demos in the ERIKA source tree so that everyone will see them when creating a new project...

(note: we just released ERIKA 2.8, which is a repackaging of the latest sources...)
Yeah no problem. As the interaction between OS and LET is realized via the "default automotive task management API" (AUTOSAR OS/OSEK, ActivateTask, SetEvent, etc), an update to the newest ERIKA OS release should be easy.

Best regards
Matthias

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: Recommend way for standalone ERIKA OS export

Post by paolo.gai » Mon Nov 13, 2017 11:41 pm

About the license... at the time a used a predefined text... you can find the license in the ERIKA2 source code...

Ciao,

PJ

MatzeB.
Newbie
Posts: 14
Joined: Fri Jul 08, 2016 11:19 am
Contact:

Re: Recommend way for standalone ERIKA OS export

Post by MatzeB. » Sat Dec 09, 2017 10:55 pm

Hi

I just pushed my initial commit. The source code is available at https://github.com/matthiasb85/IDA-LET-Machine and a doxygen based gh-pages at https://matthiasb85.github.io/IDA-LET-M ... index.html
Not sure if everything is working correctly at the moment, but I think this will change over time ;) Have a nice weekend :-)

paolo.gai
Administrator
Posts: 864
Joined: Thu Dec 07, 2006 12:11 pm

Re: Recommend way for standalone ERIKA OS export

Post by paolo.gai » Mon Dec 11, 2017 9:19 am

Great! Thanks for the link!

I'll spread out the voice internally.

Thanks for your support to the ERIKA Project!

Ciao,

PJ

Post Reply