A Standard for Automotive Grade Linux [教程].ppt

A Standard for Automotive Grade Linux Mark Hatle Software Architect, Wind River Overview Market realities Automotive infotainment requirements System design Market Realities Market segments Under the hood – Not Linux Dashboard – Not yet Linux Telematics – Maybe Linux Infotainment – Linux Aftermarket – Linux Market Realities Automotive OEM design cycle Multiple-year planning development cycle Multiple-year product release cycle Over five-year support cycle from last production device Device life cycle can be 15 years or more Tier 1 does the work and takes the liability Design cycle All work is proprietary Any changes require significant resources and costs Market Realities Consumer electronics design cycle Six- to 18-month design cycle Six- to 18-month product release cycle One- to three-year support cycle Device life cycle can be as little as two years Can leverage open source Can leverage multiple ISVs for standard off-the-shelf software Less expensive development and support costs Market Realities Automotive wants some of the benefits of the consumer electronics market but must retain some of its device life cycle Integration, support, and related costs are too expensive Many consumer electronics companies have not yet been in business for 15 years Automotive Infotainment Requirements Must be able to differentiate from competition OS? Doesn’t make sense Middleware? Perhaps, but off-the-shelf is less expensive Applications? Some customizations and custom work User interface? Absolutely Use off-the-shelf software to lower costs Must have a mechanism to update the software in the field (i.e., service bay) Must be able to connect to automotive communication bus Automotive Infotainment Requirements Regulatory requirements Power usage Power state management Fast boot Fast shutdown Consumer electronics device connectivity Bluetooth USB Others System Design System Design This is simply a framework to assist Tier 1 and others in building their products. All