Topics

Presentation on AGL and ELISA collaboration: AGL base for Instrument Cluster & IVI telltales safety function


Lukas Bulwahn
 

Dear all,

Naoto-san has shared his presentation from the Open Source Software in Safety-Critical Systems Summit.

I have placed it here in the Google Drive: (Technical Community -> Presentations -> 20191031 - Open Source Software in Safety-Critical Systems Summit)

https://drive.google.com/open?id=1WMOKV68Y3yrxrsekJVsdFFZzunzynWlC

Thanks, Naoto-san, for sharing.

Best regards,

Lukas


Lukas Bulwahn
 

Dear Naoto-san,

At ELISA, we are all happy to help and use the "Linux kernel for the AGL instrument cluster" as an object of investigation and the telltales safety function as use case for discussion.

To do so, we need a bit more information to get started. So, I would like to immediately kick off the discussion here with the following questions:

- Following AGL's mantra "Code First", where can we find the repository in which you define the Linux kernel for the AGL instrument cluster?

A pointer to the bitbake recipe in a AGL git repository would be great. Then, we can build the Linux kernel for the AGL instrument cluster for our investigation purpose. If you have not decided for a different kernel than the AGL unified base or have not created a separate config for the AGL instrument cluster, a confirmation that using the IVI kernel and the IVI config from AGL is a good way to continue the investigation for now would be great. Also, it would be good to know if and when you plan to provide a dedicated kernel and kernel config for the instrument cluster.

- To your slide "Case study : Telltale", I would like to know a bit more details:

- What is the safety requirement of the telltale functionality exactly?
- What is the "fail-safe" state of the overall system?
- How is this safety requirement assumed to be broken down to the different components?

I can see different ways of breaking down the requirements, some break-downs require less requirements on the overall systems, other break-downs might require availability requirements of some system elements, which are really difficult to achieve.

I am happy to assist in structuring the description of the use case to allow the group in ELISA to understand the requirements towards the Linux kernel.

Thanks for helping us to get together and figuring out how ELISA can contribute to your working group.


Best regards,

Lukas


i33399_yamaguchi@...
 

Hi Lukas

Sorry to delay response. I missed the email.

- Following AGL's mantra "Code First", where can we find the repository in which you define the Linux kernel for the AGL instrument cluster?
Current AGL Cluster target is only demo use. It was developed before starting IC-EG. It is not including safety and QM isolation futures.

Last week, I presented IC-EG architecture. ICーEG started to aim with the developing a real cluster platform. IC-EG plans to release first code about September 2020.
Currently, we try to prove the QM Isolation concept.

Lucas taught us the need to share kernel versions and configs at last week's meeting. The same is true for user space libraries that require quality.
I agree with this opinion. This issue was shared with IC-EG. But this topic is not including in current AGL UCB. We will tackle this issue from now on, and will reflect to first code release.


- To your slide "Case study : Telltale", I would like to know a bit more details:
We will share this in EG.

/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Senior Specialist Doctor of Infomatics
Software Fundamental Technology Group
Software Development Department I
Electronics Division
AISIN AW CO.,LTD.
YAMAGUCHI Naoto
E-mail: i33399_YAMAGUCHI@...
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


-----Original Message-----
From: devel@... [mailto:devel@...] On Behalf Of Lukas Bulwahn
Sent: Friday, November 15, 2019 10:16 PM
To: devel@...; I33399 Yamaguchi Naoto
Cc: myu@...
Subject: Re: [ELISA Technical Community] Presentation on AGL and ELISA collaboration: AGL base for Instrument Cluster & IVI telltales safety function

Dear Naoto-san,

At ELISA, we are all happy to help and use the "Linux kernel for the AGL instrument cluster" as an object of investigation and the telltales safety function as use case for discussion.

To do so, we need a bit more information to get started. So, I would like to immediately kick off the discussion here with the following questions:

- Following AGL's mantra "Code First", where can we find the repository in which you define the Linux kernel for the AGL instrument cluster?

A pointer to the bitbake recipe in a AGL git repository would be great. Then, we can build the Linux kernel for the AGL instrument cluster for our investigation purpose. If you have not decided for a different kernel than the AGL unified base or have not created a separate config for the AGL instrument cluster, a confirmation that using the IVI kernel and the IVI config from AGL is a good way to continue the investigation for now would be great. Also, it would be good to know if and when you plan to provide a dedicated kernel and kernel config for the instrument cluster.

- To your slide "Case study : Telltale", I would like to know a bit more details:

- What is the safety requirement of the telltale functionality exactly?
- What is the "fail-safe" state of the overall system?
- How is this safety requirement assumed to be broken down to the different components?

I can see different ways of breaking down the requirements, some break-downs require less requirements on the overall systems, other break-downs might require availability requirements of some system elements, which are really difficult to achieve.

I am happy to assist in structuring the description of the use case to allow the group in ELISA to understand the requirements towards the Linux kernel.

Thanks for helping us to get together and figuring out how ELISA can contribute to your working group.


Best regards,

Lukas


Jan Simon Moeller
 

Hi Yamaguchi-san & Lukas,

Let me propose something:

>- Following AGL's mantra "Code First", where can we find the repository in which you define the Linux kernel for the AGL instrument cluster?


Maybe as an intermediate starting point look at the current kernel/recipe that is used for the Instrument Cluster POC for CES. The reason I bring this up is that we could work on possible FUSA requirements that need changes to the sources, documentation or workflow upfront. So when we enter the next phase in 2020 we won't have to go back and 'fix' things in retrospective (doc or workflow for now).

IIRC the current PoC targets a Rcar-E3 SoC from Renesas similar or equal to https://elinux.org/R-Car/Boards/Ebisu .

The kernel comes (as for all Rcar-*3) out of the

which we slightly 'impedance-match' to AGL (topmost commits), add config options and host at

More specifically the kernel recipe is:

A prepatched kernel-tree is here:
The kernel .config  (IVI config set, not IC config set!)  is here:

Keep in mind, this means the kernel is *not* tailored for the intended IC use-case in terms of config options and such, but it is a start for discussing what we have or (will) need. The tailored configuration and new kernel can be provided by the IC-EG later on as we go. I'm pretty sure the kernel is the same but with less options enabled of course.

Again, this might not be the final platform, kernel or config. But we'll have a starting point and learn as we go.

HTH!

Best,
Jan-Simon


Lukas Bulwahn
 

Thanks, Jan Simon.

 

This REALLY helps A LOT to get started.

 

Lukas

 

Von: devel@... [mailto:devel@...] Im Auftrag von Jan Simon Moeller
Gesendet: Freitag, 22. November 2019 13:14
An: i33399_yamaguchi@...
Cc: Bulwahn Lukas, JC-20 <Lukas.Bulwahn@...>; devel@...; myu@...
Betreff: Re: [ELISA Technical Community] Presentation on AGL and ELISA collaboration: AGL base for Instrument Cluster & IVI telltales safety function

 

Hi Yamaguchi-san & Lukas,

 

Let me propose something:

 

>- Following AGL's mantra "Code First", where can we find the repository in which you define the Linux kernel for the AGL instrument cluster?

 

Maybe as an intermediate starting point look at the current kernel/recipe that is used for the Instrument Cluster POC for CES. The reason I bring this up is that we could work on possible FUSA requirements that need changes to the sources, documentation or workflow upfront. So when we enter the next phase in 2020 we won't have to go back and 'fix' things in retrospective (doc or workflow for now).

 

IIRC the current PoC targets a Rcar-E3 SoC from Renesas similar or equal to https://elinux.org/R-Car/Boards/Ebisu .

 

The kernel comes (as for all Rcar-*3) out of the

 

which we slightly 'impedance-match' to AGL (topmost commits), add config options and host at

 

More specifically the kernel recipe is:

 

A prepatched kernel-tree is here:

The kernel .config  (IVI config set, not IC config set!)  is here:

 

Keep in mind, this means the kernel is *not* tailored for the intended IC use-case in terms of config options and such, but it is a start for discussing what we have or (will) need. The tailored configuration and new kernel can be provided by the IC-EG later on as we go. I'm pretty sure the kernel is the same but with less options enabled of course.

 

Again, this might not be the final platform, kernel or config. But we'll have a starting point and learn as we go.

 

HTH!

 

Best,

Jan-Simon

 


Lukas Bulwahn
 

Dear Naoto-san,

Thank for you for your presentation and your response and thank you for further interacting with our group.


Last week, I presented IC-EG architecture. ICーEG started to aim with the
developing a real cluster platform. IC-EG plans to release first code about
September 2020.
We are looking forward to your first release and we are happy to employ the envisioned quality assurance and measurement methods on your kernel release and configuration. I hope this information will support to build a high-quality cluster platform and will motivate you to use these methods, acknowledge the value of our work, and support and contribute to the advance of those methods.


Lukas