User Tools

Site Tools


eg-ic:meetings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
eg-ic:meetings [2019/07/02 01:40]
ttharaki [June 25, 2019]
eg-ic:meetings [2022/07/22 15:59] (current)
waltminer change meeting time to link to project calendar
Line 1: Line 1:
 ==== Instrument Cluster Expert Group Meeting Info ==== ==== Instrument Cluster Expert Group Meeting Info ====
-The Instrument Cluster Expert Groups meets every other Tuesday at 12:00 UTCMeeting minutes the upcoming scheduled meeting dates are listed below+The Instrument Cluster Expert Groups meets every other Monday ​ The upcoming schedule can be found on the [[https://lists.automotivelinux.org/​g/​agl-dev-community/​calendar | project calendar]]
  
 Join Zoom Meeting Join Zoom Meeting
Line 11: Line 11:
  
  
-===== Meeting Minutes ===== +==== June 3rd, 2020 ==== 
 +Web meeting.
  
 +Attendees:​Honda,​ Mazda, BOSCH, Panasonic, Continental,​ Aisin-AW, NipponSeiki,​ DENSO, Suzuki
 +
 +    * We confirmed the task progress of each task. None of the tasks were noteworthy, but the need for funding for Fast Boot needs to be reconfirmed.
 +
 +
 +   * We are looking for a person in charge. If you oversee it, please issue a ticket individually at contact Haraki by email.
 +
 +    * The relationship between the profile of IC EG and the original profile of AGL should be clarified in the future. In the future, it is necessary to discuss the policy among the parties concerned.
 +
 +   ​* ​ Architecture over view : We has discussed function block assignment and cluster container overview. We plan to pursue three contents about discuss implement model. ​
 +
 +[Draft]Architecture overview
 + ​{{https://​confluence.automotivelinux.org/​display/​IC/​AGL+Instrument+Cluster+Physical+architecture}}
 +
 +
 +==== April 28, 2020 ====
 +Web meeting.
 +
 +Attendees:​Honda,​ Mazda, BOSCH, Panasonic, Continental,​ Aisin-AW, NipponSeiki,​ Suzuki
 +
 +  *We confirmed the state of each task on IC EG.
 +  ​
 +  *Participating in the ELISA workshop in Yamaguchi-San and Haraki, ICEG and ELISA shared information between each other.
 +  ​
 +  *We shared IC EG goal and output image for each task.
 +  ​
 +  *We will create schedule of each task and over all of IC EG.
 +  ​
 +  *Next meeting is June 3,2020.
 +
 +
 +
 +==== March 26, 2020 ====
 +Web meeting.
 +
 +Attendees:​Honda,​ Mazda, DENSO, BOSCH, Panasonic, Continental,​ Aisin-AW, NipponSeiki,​ Marelli, Suzuki
 +
 +  *We confirmed the status of each task on IC EG. For detail, please see the presentation material.
 + 
 +  *Participating in the ELISA workshop, IC EG and ELISA shared information between each other.
 +  ​
 +  *We have modified task list.
 +  ​
 +  {{https://​wiki.automotivelinux.org/​_media/​eg-ic/​ic-eg_status200403.pdf}}
 +
 +
 +==== February 18, 2020 ====
 +Face to face meeting@Suzuki Yokohama
 +
 +Attendees:​Mazda,​ DENSO, BOSCH, Panasonic, Continental,​ Aisin-AW, Nippon Seiki, Suzuki
 +
 +  *We confirmed the state of each task on IC EG.
 +
 +  *We shared information that workshop about collaboration with ELISA and IC EG is held.
 +
 +  *We will implement two presentation and one BoF as IC EG in AMM.
 +
 +  *We are creating IVI application API (radio and Bluetooth, etc), as well as HUD and cluster API.
 +
 +  *Since Graphic EG is integrated with IC EG, it will be reported within IC EG as necessary.
 +==== February 11, 2020 ====
 +Call on zoom:
 +
 +Attendees: Walt Miner, Jan-Simon, Haraki-san, Scott Murray, Jessie (IVIS), Marius, Dr. Yamaguchi-san,​ Kusakabe, Mitsunari, Nishiguchi
 +
 +  * ELISA update after Brussels workshop
 +    * Attended by Haraki-san, Dr. Yamaguchi, Kusakabe-san,​ Ito-san, ​
 +    * Reviewed the EG IC approach with the ELISA project and we are on a different path than them for now. 
 +    * Longer term we need to keep working with ELISA project on the kernel and user space safety aspects.
 +    * Yamaguchi-san will post link from last Friday'​s ELISA call. 
 +      * At a [[https://​drive.google.com/​drive/​folders/​1dHqox6OB4QVjYgDdC-FT6owwobOlQYJH|QM Qualification of Open Source Software]]. It's one of the quality approach. ​ We should discuss this approach. ​ We may be aiming for the same goal.
 +
 +
 +
 +
 +
 +==== January 28, 2020 ====
 +Call on zoom:
 +
 +Attendees: Walt Miner, Jan-Simon, Haraki-san, Matt Porter, Scott Murray, Jessie (IVIS), Marius, Tanibata-san,​ Dr. Yamaguchi-san
 +
 +  * Status update
 +    * Task list update
 +    * Sub working groups:
 +      * OEM (summarizing requirements)
 +      * Cluster supplier WG
 +      * Technical Workgroup
 +      * Outside cooperation WG
 +
 +
 +
 +
 +==== December 10, 2019 ====
 +Face to face meeting@Suzuki Yokohama
 +
 +Attendees:​TOYOTA,​ DENSO, BOSCH, Panasonic, Continental,​ Aisin-AW, Nippon Seiki, ADIT, Witz, Suzuki
 +
 +  *We shared IC EG updates from last meeting.
 +
 +  *We decide which companies take responsible for each task to work on IC EG.
 +  *There are tasks which need to be funded from AGL. We have to make SOW and RFQ for receiving fund by the middle of January.=>​Next meeting beginning of February.
 +
 +  *To ask Walt-san if mailing list of IC EG can be made.
 +
 +  *We shared information that cooperation with IC EG and ELISA is progressing.
 +
 +
 +{{image=eg-ic%3Aic_eg_task_list_v1.2_r.pdf}}
 +==== October 9, 2019 ====
 +Face to face meeting@Web
 +
 +Attendees:​Komatsu,​Mukawa,​Endo,​Taguchi,​Yamaguchi,​Kusakabe,​Nishikata,​Mitsunari,​Maruyama,​Okii,​Harald,​Axel,​Daniel,​Haraki
 +
 +  * In AMM held in 22-23 days in October, the SUZUKI is going to present a Keynote session about IC EG Yamaguchi-san,​ Tanikawa-san,​ Mitsunari-san are going to present a session about IC EG’s Architecture.
 +
 +  * Going to make a report of Presentation contents in AMM.
 +
 +  * IC EG’s opinion is not unified, therefore We are going to hold a discussion about architecture and functional layout.
 +
 +  *We assigned each operation to each enterprise. But, There is the operation that no one is assigned. If anyone would like to be in charge of an operation, please call to Suzuki.
 +
 +==== August 27, 2019 ====
 +Attendees: Jan-Simon, Haraki-san, Kurokawa-san,​ Scott Murray, Michael, Yamaguchi-san,​ Pierre, Stephane, Johann, Kusakabe-san
 +
 +  * Haraki-san presented a review of August 5th meeting minutes.
 +    * Question is if Secure (ASIL-B) part will be in software/​hypervisor or hardware.
 +    * Discussion about Functional layout and what needs to be monitored by safety side.
 +    * draft of new architecture release to be released before sept. F2F for comments and review during F2F
 +
 +  * Discussion: emulating E3 with m3/h3
 +    * Stephane presented Pierre'​s sandbox ( sandbox/​pmarzin/​e3-emulation )
 +
 +  * State of current cluster demo image, streaming broken (ondemand does not support streaming atm).
 +
 +==== August 5, 2019 ====
 +Face to face meeting@Yokohama
 +
 +Attendees:​Ohiwa,​Komatsu,​Hattori,​Hamaguchi,​Endo,​Taguchi,​Yamaguchi,​Kusakabe,​Mitsunari,​Maruyama,​Haraki
 +
 +  * The EG proceeds with the following steps:
 +      - Define the functional layout of AGL-side and Safety-side. The architecture is designed based on this functional layout.
 +      - Create source code based on architecture,​ target performance,​ reference hardware, requirement specifications,​ reference design.
 +
 +  * The functional layout proceeds as follows.
 +    - It is difficult to implement ASIL-B using only AGL. AGL is QM. ASIL-B is placed in the safety side that is outside of the AGL.
 +    - As for the function layout, start with the function layout on the AGL side as much as possible.
 +
 +  * The architecture proceeds as follows.
 +    - We will create a platform for the architecture,​ and we would like to discuss it based on it.
 +    - It is necessary to define what level the container should be.
 +    - The target performance value is received from each cluster Tier1 company, but there are items that need to be matched.
 +    - A target value for IVI must also be determined and evaluated?
 +    - Is it necessary to create a reference design? ==> Yes, it is necessary.
 +    - A separate discussion is needed on what to do with IC services.
 +
 +  * We will prepare the architecture for the next F2F in Berlin.
 +
 +
 +{{eg-ic:​cluster_eg_4th_en_190804.pdf}}
 ==== June 25, 2019 ==== ==== June 25, 2019 ====
 Face to face meeting@Yokohama Face to face meeting@Yokohama
Line 27: Line 187:
   ​   ​
   * As for functional safety, it is difficult to achieve ASIL-B with only AGL as it is.   * As for functional safety, it is difficult to achieve ASIL-B with only AGL as it is.
-    - To achieve ASIL-B, consider AGL [QM] + Secure World (RTOS / HW etc) [B]. +      * To achieve ASIL-B, consider AGL [QM] + Secure World (RTOS / HW etc) [B]. 
-    ​- ​We need to consider about how to achieve QM with AGL. It is necessary to discuss the target level because each company'​s opinion is different even if it is called QM.+      ​* ​We need to consider about how to achieve QM with AGL. It is necessary to discuss the target level because each company'​s opinion is different even if it is called QM. 
 + 
 +  * For functional safety advances in cooperation with LF and ELISA. If necessary, it is necessary to consider using the outside such as TUV. 
 +   
 +  *What is the ideal architecture for Cluster? Which of the following two is better?  
 +     ​*Optimize current AGL architecture 
 +     ​*Create container architecture ​ =>We will proceed container architecture for Low Spec AGL. 
 + 
 + 
 +{{cluster_eg_3rd_en_190623.pptx}}
 ==== May 30, 2019 ==== ==== May 30, 2019 ====
 Face to face meeting@Nagoya Face to face meeting@Nagoya
eg-ic/meetings.1562031643.txt.gz · Last modified: 2019/07/02 01:40 by ttharaki