FEATUREAT


EMBEDDED TECHNOLOGY


LIK


Within the auto anomaly-free c


KE A SEC


specialist at LDR , looks at newly dev MISRA and AUT


omotive industry, ther ode, ensuring a clean RA


AUTOSAR I


t is an unfortunate fact that the C++ programming language includes features t hat are prone to causing problems. A long established approach to avoiding these problems is t o apply a language subset (sometimes known as a ‘coding standard’ or ‘guidelines’) to ensure that developers don’t use any t roublesome features. N MISRA and AUT


Now MISRA d AU OSAR, two


consortia committed t o supporting the improvement of embedded software, have teamed up t o integrate t heir respective C++ guidelines into a unified publication. A de facto C++ language subset has been long overdue and the automotive development world will welcome the clarit y it brings.


A TALE OF TWO C++ CODI NG STANDARDS COLLABORAT


TA ATING


AUTOSAR is an initiative o automotive OEMs and sup to address growing compl vehicles by developing a r


of leading


architecture for ECU softw On the other hand, MISR collaboration between ma


ppliers, aiming lexity in modern reference ware.


RA, as a anufacturers, TOSAR that aim to eas


component supp consultancies, pr software-intensi What led to the two platforms? I to cater to high AUTOSAR annou platform’ to com offering, the ‘cla U lik h l


Unlike the latte


COND LA


re’s a growing pressure stream of data. Howe veloped C++ program se this tension


pliers and engineering romotes practices for ions.


ive applicat


e synergy between these n response to a need performance ECUs, unced t he ‘adaptive


mplement its t raditional ssic platform’. h i f


i


time constraints, the adapt supports safety- driving assistanc autonomous car and POSIX-comp For that, AUTOSA


er, with its focus on real- , the adapt ive platform -related advanced


l


subset to support C++14. But that MISRA C++: of the language


AUTOSAR subsequent to devise a comp guidelines, to “to


ce sy stems (ADAS) and applications, using C++ pliant R TOS platforms. AR required a language rt C++14. But they found :2008 supports versions only up to C++03. sequent ly sought plementary set of


by supporting later language features. In the meantime working on its ow


C++:2008. Subsequent collaboration between MISRA decision to integ


op up” MISRA C++:2008 ter language features. e, MISRA was already wn update t o MISRA equent collaboration and AUTOSAR led to a grate the two together.


ANGUAGE


e on programmers to ever, Mark Pitchford, techn ming language subset


provide


technical ts from


A LABYRINTH OF STAND ARDS In spite of this impro language subsets acr platforms, AUTOSAR developers have plen


Adherence to the requirement


oved alignment of ross t he AUTOSAR R application


either AUTOSAR platforms, for example, do not imply in themselves t objectives of ISO 26262, specificat f


nty t o contend with. equirements of tforms, for example, mselves that the


on functional safetyi l f


also met. Both the new ISO 26262:2018 standard and the more familiar 2011 release, collate hund


dozens of tables, designed t process to ensure that a safe product arises from complian For today’s connec more so for tomorro vehicles, functional safety


provides guidance on best practices from a cybersecurity


An examp existing A guidelines


ple of how the AUTOSAR C++ s are applied


the story. SAE J3061 can be considered complementary to IS


262, specifications in road vehicles, are new ISO 26262:2018 ore familiar 2011 dreds of topics into signed to outline a at a safe product nt development. ted car, and even ow’s autonomous safety is only half can be considered SO 26262 in that it n best development


perspective, just as ISO 26262 provides guidance on practices to address functional safety.


SO 26262 provides es to address


Consequently, AUT applications will need t


TOSAR classic


demands of the MISRA C:2012 language subset, the ISO 26262 funct standard, the SAE J3061 cybersecurit guidelines, the AUTO l d fi d b


protocols defined by st andard itself.


For any adaptive development team looking to efficiently collection of demands, object restrictions incumbe


evelopment team y negotiate the


ds, objectives and ent on today’s


automotive development, t


of a definitive C++ language subset clearly helps, despite objectives and requirement as outlined above.


LDRA www.ldra.com Tel: +44 (0)151 649 9300 9 9300


ment, the emergence anguage subset e the labyrinth of


rement s left to fulfill,


d t o comply with the RA C:2012 language 62 functional safety 061 cybersecurity OSAR OS and the y t he AUTOSAR


32


MAY 2019 | ELECTRONICS


/ ELECTRONICS


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44