Blog

Many of us are being forced to "go virtual" in our work and even in our interactions with friends and family.  With my adult children spread across four different US states, I've instituted a weekly virtual family gathering to stay in touch and to provide a way of openly sharing our lives while we endure various levels of "quarantine".  While going virtual may be significantly affecting your work lives, the work of GENIVI continues by leveraging online and virtual tooling for our active collaboration.  With that said, we will miss convening face-to-face during the (now rescheduled) All Member Meeting, originally planned for 12-14 May in Leipzig.  We will have to wait a few months (until 26-28 October) for that happy gathering to occur.

In the meantime, GENIVI is proceeding with a Virtual Technical Summit on the original dates of the AMM.  Day one of the Virtual Summit (12 May) will feature a welcome keynote by the GENIVI President followed by brief overviews of active GENIVI technical projects and teams.  The day will close with industry experts presenting "forward looking" topics like cockpit domain consolidation, edge computing in the vehicle and common vehicle interface.   Days 2 and 3 will be given primarily to technical workshops for two active projects including the Android Automotive Special Interest Group (AA SIG) and Cloud and Connected Services.  Day 2 schedule will also include a presentation on shared testing and a presentation on a new security standard (ISO-21434).  Note that all presentations (i.e., all of day 1 and the two presentations on day 2) will be recorded for replay.  Due to the length of and interactive nature of the workshops, these will not be recorded.

During the week of 6 April, GENIVI will post a near-final schedule with session speakers and abstracts for your review and planning.  To make best use of virtual event tooling, we request that you register in advance for the Summit so that you have all of the information for all sessions available on the days of the event.  Registration will also be available next week.  Because of the recent increase in "Zoom-bombing" and other disruptive online behaviors, we will enforce passwords for all sessions, making preregistration all the more important.

For now, please mark your calendars for this important connection point for the GENIVI membership and beyond.  The opening keynote will begin at 1500 CET on 12 May and again, all presentations will be recorded on that day for playback for those who are in time zones that are not convenient for live participation.  Other sessions on subsequent days, like the AA SIG's Audio HAL workshop, will be more conveniently scheduled to an Asia- and Europe-friendly time (i.e., morning CET).  Stay tuned for a full schedule next week and please be safe and well!


GENIVI is actively investigating essential standards and solutions needed to enable a fully data-oriented, connected vehicle architecture.  In just a few years, connected cars will become the predominant form of automotive transportation. A number of actors are working at breaking down the barriers to adoption for mobility services based on automotive data and helping drivers, communities, mobility services, aftermarket and repair services and automotive manufacturers extract the most value from that data. But this has already resulted in a somewhat fragmented ecosystem where different actors are using different solutions to access the data of connected cars.

As an example of the fragmentation, we have identified competing commercial initiatives that are developing mostly proprietary solutions, and more than one partly overlapping collaborative efforts. Several start-ups are already active for delivering data of production vehicles to the market place in the short term. 

As more of the solutions also involve public infrastructure, including the smart cities concept, the time for finding a common approach is imminent. We have gathered a list of collaborative projects that look at various facets of the same topic on a mid to long term.

A priority topic emerging from this analysis is the need to agree on an industry-wide common data model.  GENIVI has already delivered an overview and gap analysis for the different data models used by these collaborative projects. This first deliverable is available here.

In addition to the above usage, more and more automotive functions exchange data with the cloud-based back-end or execute partly using cloud computing. This back-end provides the basis for various innovative applications and functions that can execute with support of the cloud. These functions include autonomous driving, enhanced speech recognition and security-related system behavior analysis, and many more.

GENIVI believes there is a need to join forces and harmonize activities to realize the full data-oriented connected vehicle architecture.

The current alliance work on data-driven connected vehicle software architecture is an important step towards achieving the seamless coupling of the in-vehicle and back-end architectures, and delivering an end-to-end vehicle computing platform. This end-to-end platform leverages existing standards and solutions, but some gaps exist and an overall interoperability is still far from achieved. We are convinced the GENIVI work will help the automotive industry take a big step toward the future when the in-vehicle software, E/E architecture and the back-end architecture will be moving closer together.

The Cloud & Connected Services (CCS) project team has made a major step forward during Q1, 2020 with the initial design of an end-to-end vehicle-to-cloud communication framework. This framework incorporates technology components identified by various collaborative projects such as W3C Gen 2 protocol built on VSS2, GraphQL, ISO Extended Vehicle Neutral Server. It clarifies connections to in-car technologies such as AUTOSAR-defined SOME/IP and several others.

The team plans to implement a proof-of-concept demonstrator in order to validate the reference architecture of the communication framework. There is work breakdown structure for this work available here.  We are now in the process of recruiting volunteers to help with the development activities.

The CCS proof-of-concept project roadmap is organized around 4 demonstrable milestones:

  • milestone #1 - GENIVI Virtual Summit (12-13 May)
  • milestone #2 – Internal project milestone (Q3 - July)
  • milestone #3 - Fall All Member Meeting (27-29 October)
  • milestone #4 - CES 2021 (January 2021).

All contributors are welcome! Now is the right time to join the team and share your expertise in some implementation and test activities. For questions about how to join the team, please contact GENIVI PMO Lead or GENIVI Development Lead.

The GENIVI Alliance Board met on 17 March to discuss the current coronavirus situation and how it affects the planned GENIVI All Member Meeting scheduled for 12-14 May in Leipzig, Germany.   Following recommended guidelines from global and national health organizations, the Board made two decisions.

First, the Board decided to postpone the physical (face-to-face) event to the fall with a new target date of 27-29 October, which will be confirmed with the Marriott Leipzig.  Once the dates have been confirmed, we will communicate the new plan by email and on the website.  The scope and purposes of the all member meeting, including its member showcase and the open community element that encourages participation by non-members, will continue as was originally planned for the May event.  

An important second decision reached by the Board was to proceed with a slightly reduced scope Summit in May using virtual technologies to allow for program sessions to proceed as planned, though not in person.  The details for this virtual approach are being finalized by GENIVI staff, but at a minimum, the program will support interactive participation and have the following elements:

  • President's Keynote and Board "Town Hall" meeting
  • Presentations on 1-2 trends affecting current and future E/E Architecture (topics to be announced)
  • Status updates on GENIVI collaborative projects (including those with planned sessions later in the event)
  • Android Automotive SIG Workshop (multiple sessions)
  • Cloud and Connected Services Project Workshop (multiple sessions)
  • Hypervisor Usage and the Automotive Virtualization Platform Specification Workshop (multiple sessions).

The Board also made a request to explore holding a one-hour, virtual showcase during which sponsoring organizations would have a brief slot to introduce their products and services to a virtual audience and have the ability to set up offline conversations with interested attendees.  Virtual beer and snacks will be served. (smile)  More information on how this will be executed will be made in another blog post and through Mike Nunnery, GENIVI Marketing Manager.

While many of us would have enjoyed being face-to-face, we will have to wait until the fall to do so.  But in the meantime, keep your calendars marked for 12-14 May for the first ever, GENIVI Virtual Summit.  If you have any questions about this event, please contact me (scrumb at genivi dot org).

Stay healthy and safe and I wish you all the best during these challenging times.

Automotive OEMs are increasingly adopting Android(tm) Automotive embedded as a solution for their IVI stack. This adoption has introduced a series of challenges around integrating the Android Automotive embedded solution into existing legacy software and into other systems present in the vehicle.

Through a GENIVI-hosted Android Automotive Special Interest Group (AASIG), OEMs, their suppliers and the broader cockpit software ecosystem can discuss requirements, identify gaps and provide an aligned, community voice for discussion with the Google Android Automotive team. There are currently two active projects under the GENIVI AASIG umbrella: the Vehicle Hardware Abstraction Layer (VHAL) / Vehicle Data APIs project and the Audio Hardware Abstraction Layer (Audio HAL) project.  Android-related discussions are also occurring in other GENIVI projects.

The AASIG VHAL / Vehicle Data APIs project has recently detailed a delivery roadmap for its initial deliverables.  During a successful face-to-face meeting hosted at the beginning of February by BMW in Munich, the project team identified four proof-of-concept (coding projects) corresponding the various software architectural options that have been debated since last November’s GENIVI Technical Summit, held in Troy, Michigan.  

The four proof-of-concepts include:

  1. External Data Server (EDS) proof-of-concept: One rationale for extending Android access to vehicle data is that the number of vehicle properties currently defined in standard Android is very limited as compared to the thousands of vehicle-related signals OEMs are considering for their connected vehicles. Although the project could propose to expand the standard vehicle property list in Android, the integration of Android into a complex electrical and connected vehicle architecture suggests a bigger picture to consider.  Standard data access methods should be applied in the entire vehicle and in cloud connected services.  This EDS proof-of-concept intends to validate the concept of a data server accessing the vehicle dataset as described by VSS (Vehicle Signal Specification standard), which is used also in W3C Automotive Group, and enabling authenticated Android apps to access the vehicle data through a web socket protocol. The actual values of the vehicle signals will be queried / updated thanks to a VSS feeder that will connect to the rest of the vehicle using, for example, Some/IP.
  2. Internal Data Server proof-of-concept is only a variant of the External Data Server above, where the data server is inside the Android Automotive framework.
  3. SomeIP stack inside the Framework proof-of-concept relates to a Some/IP stack running in the Android Automotive framework. It is worth noting that in the GENIVI github repository there is on-going contribution for porting the vsomeip component to Android Automotive.
  4. Google VHAL + OEM Extensions inside proof-of-concept explores the coexistence at the VHAL level of a Google-certified/compliant implementation of the vehicle properties as well as the access to the extended data as defined by the rest of the vehicle architecture and as needed by OEMs as explained above.

The AASIG VHAL project team has decided to implement first the External Data Server proof-of-concept because it relies on a very limited coupling of the Android Automotive side and the Vehicle side and can be implemented with available technologies like GraphQL, Node.JS and VSS data server.

The team has developed a complete work breakdown structure for the EDS proof-of-concept which is available here. We are now in the process of recruiting volunteers to help with the development activities.

The EDS proof-of-concept project roadmap is organized around four milestones, each representing a demonstrator deliverable:

  • milestone #1 - Spring AMM (12-14 May)
  • milestone #2 – Present findings to Android Automotive experts for validation (early Q3)
  • milestone #3 - Fall tech summit (Q4 – November)
  • milestone #4 - CES 2021 (January 2021).

All contributors are welcome! Now is the right time to join the team and share your expertise in the project's implementation and test activities. For questions about how to join the team, please contact GENIVI PMO Lead or GENIVI Development Lead.

On 6 March, GENIVI received word that the below mentioned Automotive Cybersecurity Event was officially postponed to 22-24 June.  Since then, the leadership of the GENIVI Security Team has decided to also postpone the planned face-to-face workshop and reception to align with the June schedule.  As logistics for this workshop are finalized, GENIVI will announce the new schedule and location (if changed).  

--------

Vehicle cybersecurity continues to be a very hot topic in the industry and third-party events seem to be a great place to advance the dialogue about how automakers and suppliers should collaborate on standard approaches for reducing security threats. 

The GENIVI Security Team has chosen the week of the upcoming Automotive Cybersecurity Event in Detroit (30 March - 1 April) to continue the discussions started during last November's workshop during the GENIVI Technical Summit.  The Security Team, under the leadership of Joby Jester from Irdeto, is planning three activities during the days of this event.  The Automotive Cybersecurity Event, presented by IQPC, is a for-pay event and attendees must register to attend here

On 30 March (8:30 am), as part of the "training day" of the IQPC program, GENIVI will lead a workshop entitled "Product Security Evaluation Workshop - How to Get Ready for ISO/SAE 21434".  Future rules and regulations like ISO/SAE 21434 will require automotive manufacturers to perform and document cybersecurity risk assessments for each product.  This session will help participants interpret and implement this emerging standard.

Also on 30 March (2:00- 5:00 pm) in Novi (suburb of Detroit), the GENIVI Security Team will hold a face-to-face workshop and reception with the following agenda:

  • Introduction to the GENIVI Security Team
  • ISO 21434 - How to Handle a Changing Cybersecurity Landscape (Bill Mazzara, FCA, will be a guest speaker)
  • Cybersecurity Requirements - How to Keep Security Controls Updated
  • Collaboration - Is this the Future Model of Automotive Cybersecurity?
  • Interactive Discussions, Feedback and Opportunities
  • Walk-in Topics from Attendees
  • Wrap-Up and Social Networking with Food/Beverage.

There is no charge for this GENIVI-hosted gathering (held at the Sidecar Slider Bar restaurant in Novi), but for planning purposes, GENIVI requests registering here (use passcode "collaboration").  To be clear, this workshop is not directly associated with the IQPC event.

Returning to the IQPC event program in downtown Detroit, on 31 March (1:30pm), GENIVI will moderate a panel entitled, "A 'Commodity Approach' Toward Automotive Cybersecurity".  This panel seeks to answer the question, "Can automakers and suppliers benefit from a shared, commodity approach toward delivering relevant cybersecurity technologies?"  Cybersecurity experts from GM, Visteon and Harman will discuss how to engage more openly on cybersecurity challenges.  This panel along with the workshop planned on on the morning of 30 March are for pay activities of the IQPC Automotive Cybersecurity Event in downtown Detroit.  Registration for this event can be found here

Questions about the GENIVI Security Team activities can be sent to joby dot jester at irdeto dot com or to gandersson at genivi dot org.  Questions about the offsite workshop and reception can be sent to mikenunnery at comcast dot net.  You can also email Mike If you are a GENIVI member and want to benefit from a 20% discount for the IQPC event negotiated by GENIVI.  

If you are local to the Detroit/Novi area or have plans to participate in the IQPC event, please make sure to include these GENIVI-led activities in your plans.



The news about the spread of the coronavirus (COVID-19) is changing daily leaving many of us with concern for those infected and for the potential of the virus increasingly affecting our business and personal lives.  Rest assured that GENIVI leadership is tracking developments and commits to consistent communication about upcoming gatherings like the GENIVI All Member Meeting, scheduled for 12-14 May 2020 in Leipzig, Germany.

Until GENIVI has reason to postpone or cancel the event, which will be communicated immediately if that decision is made, the All Member meeting will proceed as planned.

GENIVI recognizes that many organizations already have travel restrictions associated with the COVID-19 virus in place and these may become more or less restrictive as time goes on.  

Please know that we are monitoring the situation and health notices closely.  The health and safety of our members is our highest priority and we will continue to monitor this dynamic situation and communicate any new or significant updates.

Please contact me (scrumb at genivi dot org) with any questions or concerns about the upcoming GENIVI All Member meeting or other planned GENIVI gatherings at related industry events.

           

           


I love when things are made simple for me.  Maybe I'm lazy, but I love summaries.  So this blog is about summaries - the top five things in GENIVI-Land that you should know about.  So, here goes:

  1. The All Member Meeting (12-14 May) is coming and you should decide to attend soon.  Visit this blog for more information, get registered and reserve your hotel as room blocks close early.
  2. GENIVI will actively participate in the upcoming IQPC Automotive Cybersecurity Detroit event (30 March - 1 April 2020) and the TU-Automotive Detroit event (2-4 June 2020).  The GENIVI Networking Reception at the TU-Automotive event is a must-make event with hundreds in attendance. (See #3)
  3. If your company is looking to represent your product or services to a highly targeted gathering of automotive contacts, consider sponsoring or showcasing at one or more of our upcoming events (AMM, TU-Automotive Detroit).  Contact Mike Nunnery (mike at comcast dot net) for more information.
  4. If you weren't able to attend the recent Automotive World webinar presenting the GENIVI work on an Automotive Virtualization Platform (a standards-based approach for deploying hypervisors in a vehicle), visit the AW site to get the slides and listen to the recording.
  5. If you have a session idea for the upcoming All Member Meeting program, please contact me (scrumb at genivi dot org).  The program is coming together but we want to consider your ideas too.  Marketing pitches are not appropriate for the stage, but are welcome in our showcase room.

Short and sweet.  Enjoy!

Beyond IVI and into the Connected Cockpit

On 12-14 May 2020, GENIVI will gather for its next member meeting to explore trends affecting vehicle software solutions and to engage in discussions related to the expanded scope that includes integration of multiple operating environments present in the centralized and connected vehicle cockpit.  Non-members interested in this expanded scope and in participating in GENIVI projects are also welcome to attend.

Anchoring the technical program will be updates and working sessions of active GENIVI projects including:

  • Android™ Automotive SIG
  • Cloud and Connected Services project
  • Hypervisor project
  • Adaptive AUTOSAR integration activities
  • Security Team.

A new project under consideration in the area of in-vehicle payments may also hold its first official meeting during the event. 

In addition to these technical activities, invited speakers will present industry trends affecting the future automotive software landscape.  And finally, during the evening of the 13th, GENIVI will hold its very popular Showcase and Reception where members can present their products and services to event attendees while enjoying light snacks and drinks.  Mike Nunnery (mikenunnery at comcast dot net) is taking member inquiries for event sponsorship and showcase participation so please contact him directly.

Coming off of a highly productive 2019 and a very successful set of activities at CES 2020, GENIVI is looking forward to bringing the community together to hear updates, recruit participation for new and active projects and continue the great networking that GENIVI events are know for.  

The event will be held at the Marriott Leipzig Hotel, located just a block away from the Leipzig central train station. 

Event registration details and details for securing a hotel room can be found here.


Wards Auto Video

I can't help but to share an excellent video shot by Wards Auto during the GENIVI CES 2020 Showcase and Reception.  The brief video does two things really well.  First, it highlights that the work of GENIVI has moved "beyond IVI" and into the centralized and connected vehicle cockpit.  Second, the footage shows the popularity of this event, which has become an essential stop for many automotive stakeholders during the week of CES.  Take 93 seconds of your day to take a look at how GENIVI continues to bring together the global automotive industry at events like CES (link to video: https://t.co/IcyT4CtEkG?amp=1).  And feel free to pass this link on to your colleagues.

"Watching" this Blog

The GENIVI blog has a feature that you can "turn on" to proactively make you aware of when a new blog post has occurred.  For those who have credentials to log into the wiki (more on how to get those in a second), once you have authenticated, a link appears on the top right of the blog page that says, "Watch this Blog” and pressing it will result in notifications coming to the email associated with your login, whenever a new blog is posted.  This feature is only available for those who have login credentials to this public wiki (which is different than the member-only wiki).  If your credentials do not work or you have forgotten them, please email help at genivi dot org for support in getting your credentials sorted.  GENIVI intends to regularly post important information on this blog so save yourself some effort and hit the "Watch this blog" link today.



GENIVI invites you to learn more about a recent GENIVI deliverable on hypervisors and virtualization in a vehicle context through an upcoming webinar, “Hypervisors in the vehicle: A standards-based approach to virtualization”.  The webinar will be held on 13 February at 1700 Central Europe Time (11:00 am US EST) in partnership with Automotive World.  Attendees of the webinar will hear from Tero Salminen, Senior Director Product, Virtualization at OpenSynergy and GENIVI Technical Lead Gunnar Andersson, about the benefits of standardization in the use of in-vehicle hypervisors.

Hypervisors and virtualization solutions are prevalent in IT and have found their way into many vertical industries.  Some hypervisor solutions are also being deployed in vehicle systems, but do these deployments allow the flexibility and interoperability that standards-based approaches typically offer for other software in the vehicle? Is there a need for a more standards-based approach for deploying hypervisors in the vehicle that has the potential to ensure that automotive requirements are met, to reduce risk and concerns among adopters of virtualization, promote portability, and to minimize system integration effort?  These and many other questions will be answered during this informative webinar.

To register for this webinar, please visit the Automotive World webinar site.  And stay tuned to other GENIVI webinars in coming months hosted by Automotive World. 


In this blog, I will highlight an important software project funded by GENIVI and completed in 2019 that aids in the interoperability of Adaptive AUTOSAR systems with systems running Franca IDL, an interface description language used by CommonAPI and other software solutions in the vehicle.

The tool, nicknamed FARACON,  uses model-to-model transformation to achieve a compatible code generation on both sides of ARA::COM (the communication layer of Adaptive AUTOSAR) and Franca IDL.  When combined with CommonAPI bindings and ARA::COM runtime, this achieves a runtime translation between ECUs. The alternative to this would be a manual translation that is not only tedious, but prone to human errors.

Using such a tool makes it possible to have a specification in a single format (GENIVI proposes Franca IDL for this), and yet to use the full advantage of both technologies on both sides of the communication.  Enabling interoperability between heterogeneous systems using model-to-model transformation methods can improve software quality and reduce development time and engineering costs.

The FARACON tool implements transformations from Adaptive AUTOSAR models to Franca IDL and vice versa. These transformations can be used as part of any current Eclipse IDE. For build automation and Continuous Integration (CI), it is also useful to deploy the transformations as a command-line tool.  

The goal of the automatic transformations is to apply code generation by AUTOSAR-compatible code generators as well as Franca-compatible generators (e.g., CommonAPI C++) in a way that leads to transparent communication between both systems at runtime. Therefore, the tooling is based on a proper mapping between Adaptive AUTOSAR concepts and Franca IDL concepts. For example, each operation on an AUTOSAR service interface is mapped to a method in Franca IDL.

The diagram above shows how the transformation tooling interacts with the code generators. The generated code on the AUTOSAR and Linux-based subsystems (like GENIVI) is using the SOME/IP protocol for communication. As the subsystems are integrated on model level, the communication is automatically compatible.

A clear advantage of following this approach is that there is no need to define the same interface twice in Franca IDL and AUTOSAR ARXML. This reduces errors coming from manually maintaining the service interfaces by having only one source of origin.

GENIVI is proud to have funded the FARACON tool through Itemis and Version 1.0 (open source licensed), which achieves a near production-ready quality, is available here: https://github.com/GENIVI/franca_ara_tools.  The delivery of this useful tool to the industry is one evidence that GENIVI has moved beyond IVI and is actively working on the integration of multiple operating systems in the connected and centralized vehicle cockpit.

Many thanks to GENIVI members Itemis, Renault and Visteon for their work to oversee, develop, test and publish the tool.

Welcome to the New Year and to a new model of communicating about GENIVI plans, activities and deliverables.  GENIVI is phasing out the newsletter and will begin using this blog (coordinated with email blasts) to inform members of the alliance and nonmembers about important topics.  Future blogs will be more often and shorter to facilitate a quick read.  Please feel free to pass on a link of this blog to your colleagues to keep them aware of all that is going on in GENIVI.  In this blog, I will briefly describe the awesome outcome of the GENIVI activities at the CES 2020 show and also recap some of the latest deliverables of the alliance.  Stay tuned to this blog for more details in the coming weeks.

CES 2020 Highlights

The best way to describe the outcome of the CES 2020 Showcase and Reception is to reprint a quote from a participating member company that had a table presence at the showcase:

"I wanted to tell you that we absolutely LOVED the GENIVI reception.  My team felt your event ALONE was worth the plane tickets from Finland to CES.  It was a fantastic venue and we had so much interest and traction there...We had a great time and had a lot of great talks and leads."  

I was fortunate to receive many such remarks during the closing of the reception from almost everyone I talked to.  Big kudos to Mike Nunnery (GENIVI Mike) for his hard work planning and executing this event!  Once again it broke all previous records for registration (2,000), actual participation (roughly 1,400),  as well as numbers of sponsors and organizations taking tables during the reception.  This is one way that GENIVI  brings our members together and provides a productive environment for business interactions with a well-qualified audience of automotive decision makers from around the globe.  Pictures of the reception can be found here

Two more opportunities for similar interaction are coming, one being the All Member Meeting (targeted for the week of 11 May in a European location TBC) and the TU-Automotive Detroit event (3-4 June).  For details about sponsoring or showcasing at either event, please contact Mike at mikenunnery at comcast.net.  

Two other quick notes on CES 2020.  GENIVI teamed with SAE to produce the Connect2Car program during CES and all the panels coordinated by GENIVI enjoyed full rooms of eager listeners.  John Ellis led a panel on Connected Services and Matt Jones led an interesting discussion on Electrification and Autonomy.  Pictures of these panels can be found here.  

Latest Deliverables from GENIVI

CES 2020 also provided a nice milestone for several GENIVI projects to deliver on work completed in 2019.  This wiki page provides an overview and links to each delivery, but let me highlight a few here.  

Vehicle Data Models - Overview and Gap Analysis

Everyone is talking about vehicle data, but the industry is not aligned on a standard data model or common approach for moving vehicle data to/from the back-end cloud.  Step one in this essential model alignment is to understand existing approaches and the gaps present in them.  The Cloud and Connected Services project recently published a “Vehicle Data Models - Overview and Gap Analysis” that provides readers important information for the future data-oriented strategies of OEMs and their suppliers.  The project now turns toward designing an end-to-end reference architecture during its next "sprint".  At this point, the project is open to members and nonmembers so if you would like to get involved, contact Philippe Robin, GENIVI PMO lead at philippe.robin at technoveo.com.  

Automotive Virtualization Specification 

As I stood at the GENIVI table during the CES reception, I was amazed at the interest in another recent deliverable of the Hypervisor Project, an Automotive Virtualization Specification.  Hypervisors and virtualization solutions are prevalent in IT and have found their way into many vertical industries.  Some hypervisor solutions are also being deployed in vehicle systems, but do these deployments allow the flexibility and interoperability that standards-based approaches typically offer for other software in the vehicle? GENIVI believes that there is a need for a more standards-based approach for deploying hypervisors in the vehicle.  This has the potential to ensure that automotive requirements are met, to reduce risk and concerns among adopters of virtualization, promote portability, and to minimize system integration effort.   This is the motivation behind the Automotive Virtualization Specification, recently delivered by GENIVI (special thanks to OpenSynergy and Gunnar Andersson).  The specification is considered a "release candidate" meaning that you have the opportunity to contribute your thoughts to a final release.  Contact Gunnar to give your input at gandersson at genivi.org. GENIVI will hold a webinar on this subject in mid-February and the details will be announced soon.  

There is so much more to share, but I promised to keep it short.  But stay tuned for our next blog as we will make at least two very important announcements in the days ahead.

All the best in this New Year,

Steve Crumb

Executive Director, GENIVI Alliance


With the recent release of meta-ivi v15.0.x the Genivi Baseline was re-based on Yocto Project 2.6 (Thud). It's therefore a good time to write a blog about support for it and GDP on Renesas R-Car Gen 3.

R-Car Gen 3 Community Yocto BSP v3.15.0/v3.19.0 for YP 2.6 (Thud)

Yocto BSP v3.15.0 was used during the majority of the development cycle for meta-ivi v15.0.x and has therefore received the most testing. At the end of the cycle v3.19.0 was released upstream and I have sanity checked that it works.

At the time of writing the meta-ivi CI and GDP sub-modules point at Yocto BSP v3.15.0. I will be updating both to v3.19.0 soon.

Developer Summary

PurposeRepository locationBranch
Upstream Yocto BSP supporthttps://github.com/renesas-rcar/meta-renesas.gitthud-dev

Adapt Yocto BSP (meta-renesas) to Genivi Yocto Baseline (meta-ivi)

https://github.com/GENIVI/meta-ivi-renesas.git15.x-thud

Documentation

I continue to maintain pages discussing the building of Genivi s/w for R-Car in the meta-ivi Yocto BSP wiki area. From there you can find a link to a new page covering building Genivi 15 for YP 2.6 (Thud).

Genivi Yocto Baseline

I have successfully sanity tested building the 15.0.x Genivi Yocto Baseline using the Community YBSP v3.15.0 and v3.19.0 for Thud on the M3 Starter Kit. Testing of the other boards will follow, but I do not expect any issues and see no reason for you to wait before trying them.

See the Documentation section above on how to build it.

GDP

GDP is in the process of being rebased on Thud in Github PR 231. I have posted Github PR #9 to update GDP to use the R-Car Thud support.

Although we knew that GDP could be built for the Renesas R-Car Gen 3 Salvator-X(S) boards they were not supported in the GDP init mechanism that sets up GDP for you. You typically asked GDP init to setup for one of the R-Car Starter Kit boards and manually made the changes to build for Salvator-X.

Between Gunnar and I we have now added Salvator-X(S) support directly into the init mechanism on the GDP master, 14.0.x-rocko and 14.1.x-sumo branches.


To initiate the build environment for M3 Salvator-X(S) use the command:

source init.sh r-car-m3-salvator-x


To initiate the build environment for H3 Salvator-X(S) use the command:

source init.sh r-car-h3-salvator-x


I have successfully tested the mechanism on M3 Salvator-X and H3 Salvator-XS.

With the recent release of meta-ivi v14.50.x and GDP v14.1 the Genivi platforms were re-based on Yocto Project 2.5 (Sumo). It's therefore a good time to write a blog about support for them on Renesas R-Car Gen 3.

R-Car Gen 3 Community Yocto BSP v3.9.0 for YP 2.5 (Sumo)

Back in August I blogged about the customer Yocto BSP v3.9.0 for YP 2.4 (Rocko). The customer BSP typically updates Yocto Project once a year. To help support the community Renesas is re-basing these releases on Sumo to create a community Yocto BSP.

Developer Summary

PurposeRepository locationBranch
Upstream Community Yocto BSP supporthttps://github.com/renesas-rcar/meta-renesas.gitsumo-dev

Adapt Yocto BSP (meta-renesas) to Genivi Yocto Baseline (meta-ivi)

https://github.com/GENIVI/meta-ivi-renesas.gitgenivi-14.x-sumo

Migration Guide

If you wish to use the "click through" licensed gfx/mmp packages that requires no NDA then please download the packages for YBSP v3.9.0 and Wayland 1.14 / Weston 3.0 from the section for YP 2.5 (Sumo) from here.

If you are updating from an earlier BSP version then the new Yocto BSP release introduces updates to various Yocto BSP packages including the kernel, Initial Program Loader (IPL) and u-boot. The kernel and op-tee updates include mitigations for Spectre/Meltdown.

Please flash the updated IPL/u-boot to your board. Instructions for doing that can be found on elinux.org in the "Flashing Firmware" section of the M3 Starter Kit and H3 Starter Kit board pages. For Salvator-X(S) and Ebisu boards please refer to the documentation that came with the customer Yocto BSP.

There has been no change to the example local.confs.

Details of the Yocto BSP changes can be found in the git commit messages. Here is a log between v3.9.0 (Rocko) and v3.9.0 (Sumo) using the github compare function.

The community v.3.9.0 (Sumo) BSP uses the upstream (Poky) Weston 3.0 implementation and therefore only supports the gl-renderer which uses the GPU for h/w acceleration.

The dtb filenames have not changed since the last blog but here is the table again for reference. Please refer to the table below for the correct dtb to use for your board and SoC:

BoardSoCDTB filename
EbisuE3Image-r8a77990-ebisu.dtb
M3 Starter KitM3

Image-r8a7796-m3ulcb.dtb

Salvator-XM3Image-r8a7796-salvator-x.dtb
Salvator-XSM3Image-r8a7796-salvator-xs.dtb
Salvator-XM3N 1.1Image-r8a77965-salvator-x.dtb
Salvator-XSM3N 1.1Image-r8a77965-salvator-xs.dtb
H3 Starter KitH3 1.0, 1.1Image-r8a7795-es1-h3ulcb.dtb
H3 Starter KitH3 2.0Image-r8a7795-h3ulcb.dtb
Salvator-XH3 1.0, 1.1Image-r8a7795-es1-salvator-x.dtb
Salvator-XH3 2.0Image-r8a7795-salvator-x.dtb
Salvator-XS 4GByteH3 2.0, 3.0Image-r8a7795-salvator-xs.dtb
Salvator-XS 8GByteH3 3.0Image-r8a7795-salvator-xs-4x2gb.dtb

Documentation

I continue to maintain pages discussing the building of Genivi s/w for R-Car in the meta-ivi Yocto BSP wiki area. I have created a new page covering R-Car Gen 3 builds for Genivi-14 (Pulsar) for YP 2.5 (Sumo).

Genivi Yocto Baseline

I have successfully sanity tested building the 14.50.x Genivi Yocto Baseline using the Community YBSP v3.9.0 for Sumo on the M3 and H3 Starter Kits. Testing of the other boards will follow, but I do not expect any issues and see no reason for you to wait before trying them.

See the Documentation section above on how to build it.

GDP

The GDP Master and 14.1.x-sumo branches have been updated to use the Community Yocto BSP v3.9.0 for Sumo. I have also updated the corresponding build instructions of the GDP Master wiki page. Finally, I have successfully sanity tested it on the M3 and H3 Starter Kits. As with the Baseline testing of the other boards will follow.