8/6/2019 mentorpaper_66510

1/5

e m b e e s f t w a e W

h

i t

e

P

a

P

e

r

w w w . m e n t o r . c o m

a , meeg , a embe el ux ve t cal ma kets

vla buz v, se s ftwa e a ch tectJ h lehma , se v ces ma ket g

me t g aph cs c p at

8/6/2019 mentorpaper_66510

2/5

android, m go, nd e dd d lin in v r i m r

. n or. o2

t uctLinux-based systems have been dominant in enterprise networking for more than a decade. They have beenthe basis of consumer electronics devices dating back to the original TiVo DVR in 1999, and wireless handsetsbeginning with the NEC phones for DoCoMo in 2003. However, many vertical markets are only now seeing newdevices built on open source software. The reasons lie both in the nature of these markets and the specializeddevices themselves, as well as the emergence of advanced pre-configured software stacks like Android andMeeGo.

h w ve t cal ma kets a e ffe e tAlthough devices in vertical specialized markets (like medical or transportation) can work side-by-side, share manyof the same features, or even compete with consumer products, they usually have more stringent requirements, aswell as market-specific functions and features that may be proprietary to the device maker.

By their very nature many of these devices cannot fail. While the failure of a consumer device, like a dropped callon a cell phone can cause annoyance, and occasionally business or personal issues, it is rarely life-critical. However,if a medical device malfunctions, or the infotainment system in a car causes a sudden distraction to the driver, thedevice has the potential to trigger a life-threatening event. Safety, security, and reliability are therefore paramount.Security and high availability have always been a priority for Linux-based network systems, but safety can be a

challenge with some open source software that may not be designed with these requirements in mind.

Code that meets these stringent requirements, as well as market-specific applications and unique differentiatedfeatures, often are found in similar or previous versions of a device. This software needs to be re-purposed andreused whenever possible on new and next generation products. The open source development philosophy isevolutionary by design and moves on quickly to work on the latest and greatest rather than legacy sof twareno matter how valuable it may be for a particular device.

8/6/2019 mentorpaper_66510

3/5

android, m go, nd e dd d lin in v r i m r

. n or. o3

All of the above requirements require extra cycles and ex tensive testing before a device can come to market.Longer development cycles are common, although they grow shorter with every new product, but developmentwill always take longer than consumer devices. This is balanced by typically long product lives, both in the lengthof time a device is sold, and in the time it is in use and supported by the manufacturer. Open source software

change dramatically multiple times during these long life cycles, even during the development phase, and isoften beyond the control of the device maker.

Finally, vertical markets adhere to standards and certification that can be several orders of magnitude morecomplex, costly, and time-consuming than on consumer devices. Certification can dif fer from country to country,and pose a particular set of challenges for devices to be sold globally. The development process itself is of ten partof the certification, which can be a problem when building a solution by integrating and testing existing opensource software, rather than starting from scratch or using pre-certified commercial components. In fact, thecertification process may take longer than the life cycle of a typical electronics product.

Likewise, mixing proprietary and open source licensing requires knowledge and skill to design the system correctly,choose the appropriate models and terms, and apply proper management to ensure the proprietary code s taysproprietary while respecting open source requirements.

the appeal f aIn just a couple of years, wireless handsets using Googles Android have captured the majority share of thesmart-phone market. This market dominance, combined with its royalty-free, open source model and Googlescommitment of resources, have made Android an appealing candidate for use in vertical market devices.Companies like Embedded Alley (acquired by Mentor Graphics in 2009) noticed early the potential for Androidbeyond mobile phones and have been pioneers in helping bring Android to vertical market devices.

Chief among Androids appeal is its fairly mature full-stack integration, updated as often as twice a year by Google. This frequent updating is both an advantage and a problem, since vertical market development cycles oftenoverlap one or more of these releases, and unless the device maker is a member of Googles hand-picked OpenHandset Alliance (OHA), its hard to know what is coming next. Although Android uses open source licensing, it is

controlled and developed by Google, not the open source community, and Google alone decides what featureswill be added or enhanced and when.

In fact, Android is more than an integrated sof tware stack. It is complete development environment with its ownecosystem, including a unique build system, configuration management tools, and a well-defined developmentprocess. While these tools are very ef fective for building an Android-based device, integrating them into a devicemakers development flow can be diff icult.

8/6/2019 mentorpaper_66510

4/5

android, m go, nd e dd d lin in v r i m r

. n or. o4

With the current release of Android, Google has finally made it easier to integrate legacy C/C++ applications, soits important to the reuse model in vertical market devices but other challenges still remain. In spite of its frequentreleases and feature updating, Android still retains some hard wired phone assumptions. For example, Androidrequires real Home and Back buttons, just fine for an Android-based phone, but a real design constraint forin-flight entertainment systems or back-seat in-vehicle infotainment (IVI) consoles where buttons may or may

not be needed for other functions, and space is at a premium.

Getting support for a non-phone development project can also be a challenge because Google has thus faronly shown interest in handsets (and more recently general-purpose tablets and Google TV). Mentor Graphicscan provide commercial support on several key non-handset Android platforms: ARM, MIPS, and PowerArchitectures.

the p m se f meegMeeGo is a much purer open source play. It is developed in the community, building releases by integratingupstream open source projects. Device makers can participate in consensus-driven roadmaps and new releasesprovide few surprises, which can be a very good thing for product development in vertical markets.

MeeGo provides an excellent set of application development tools (QT). The platform development process,however, is less exposed to developers.

Well resourced by the Linux Foundation (which includes Intel who contributed Moblin, its open sourceenvironment for Atom processors and until very recently Nokia, who contributed Maemo and QT), MeeGois a true open source model, not controlled by a single company.

MeeGo is of particular interest in the automotive IVI market since the GENIVI Alliance, an active group of over ahundred of the top automakers and suppliers in the world, has chosen it as the basis of its open source IVIspecifications.

Few MeeGo-based devices have yet to come to market. However, if its sponsors and the community as a whole

continue to embrace MeeGo, it has some key advantages over Android for vertical market devices.

the ve sat l ty f embe e l uxOf course, a device maker could chose to build the entire open source stack themselves. (This had been the onlychoice before Android and MeeGo appeared, and was an important reason why both were developed.) Theunlimited choice and lack of commercial control is a double-edged sword, since the development team must find,evaluate and test the options, then do all the integration and customization themselves, which can add significanttime and cost to product development. Further, open source in the wild rarely has a clear roadmap or timetable.

c clusWhile vertical market devices are a good fit for the advantages of open source sof tware in general, their exactingrequirements, and long development and product life cycles can gain a significant advantage by using theintegrated software stacks of Android or MeeGo. While technical and business challenges may need to beovercome, both can save significant time-to-market and help build better devices more efficiently.

8/6/2019 mentorpaper_66510

5/5

android, m go, nd e dd d lin in v r i m r

2011 m n or gr i cor or ion, ri r r d. t i do n on in in or ion i ro ri r o m n or gr i cor or ion n d i d in o or in r ori in r i i n or in rn in r o on , ro id d i n ir no i r in

n in i do n , r i i n r o r r on or o r n n ori d o i in or ion. a r dn ion d in i do n r r d r o ir r i o n r .

MGC 04-11 teCh9790-w

F o r t h e l a t e s t p r o d u c t i n f o r m a t i o n , c a l l u s o r v i s i t : w w w . m e n t o r . c o m

ab ut the auth s

Vlad Buzov is a Sof tware Architect at Mentor Embedded Professional Services, Vlad Buzov has more than 7 yearsexperience in Embedded Linux programming which includes porting, customizing and optimizing existent products,

and developing new custom solutions based on open source components for Mentor Embedded customers. Prior toMentor, Vlad served as Senior Engineer at Embedded Alley and MontaVista Software. Originally from Russia, where Vladreceived his Master Degree in Computer Science from St. Petersburg State University, he is now based in Silicon Valley.

John Lehmann is responsible for Mentor Embedded Professional Services marketing. He brings over 20 years experiencein Linux and UNIX system software for enterprise computing, consumer electronics, wireless handsets, and embeddeddevices.

android i r dem rk of goo e nc. u e of hi r dem rk i bjec o goo e permi ion . lin x i he re i ered r dem rk of lin torv d in he u.s.nd o her co n rie .