![]()
Just after the creation of the MISRA C/C++ standard by the automotive industry as a guideline for writing C code for safety-critical applications, Embedded.com in 2002 ran one of the first tutorials on the guidelines, titled “Introduction to MISRA C.”
Since then we have regularly published information on the standard and how to use it as it evolved and matured. Some of the more recent design articles, webinars, tech papers, product and news stories are included in this week’s Embedded Tech Focus newsletter on “MISRA C and safety-critical design.” The reason we have continued to focus so much on this standard over the years is that the need for such a disciplined approach is growing more necessary as embedded devices move into areas beyond automotive, military/aerospace and medical equipment to automate more and more aspects of our lives.
Embedded
The LDRA Compliance Management System (LCMS), a resource for developing infrastructure that supports DO-178B/C, DO-278A, and DO-254 compliancy, has been released by LDRA. LCMS ensures certification readiness through a process that includes LDRA Certification Services (LCS) professionals support from development and production through the maintenance lifecycle.
Certification of avionics projects is a requirement. It is not an easy one to meet and the enumerable artifacts and procedures are necessary. LDRA’s Compliance Management System (LCMS) is designed to provide part of the infrastructure necessary for companies to deliver projects that are compliant with standards like:
Certification of avionics projects is a requirement. It is not an easy one to meet and the enumerable artifacts and procedures are necessary. LDRA’s Compliance Management System (LCMS) is designed to provide part of the infrastructure necessary for companies to deliver projects that are compliant with standards like:
johndayautomotivelectronics.com
LDRA, a provider of standards compliance, automated software verification, source code analysis, and test tools, offers verification of the model via integration with MATLAB and Simulink.
To boost the quality and efficiency of safety-critical design, the LDRA tool suite now analyzes, instruments, and assesses code coverage of source and object code during the model phase of development.
http://www.avionics-intelligence.com/
The integration enables the LDRA tool suite to perform verification to the object code level through Simulink-based testing. The LDRA tool suite then can verify that any discrepancies between source and object code caused by compiler or program optimization are corrected in the model. Because the developers are working in the model, the relationships between application components and data elements are transparent. In addition, direct integration of object code coverage enables developers to perform DO-178C object code verification early in the development process.
http://www.avionics-intelligence.com/
Les technologies de LDRA, travaillant ici comme une couche logicielle indépendante, peuvent ainsi vérifier automatiquement que les écarts, variations et différences entre le code source et le code objet, tous liés aux transformations opérées par le compilateur et les programmes d’optimisation du code, sont bien corrigés au niveau du modèle. L’intégration des techniques de couverture de code au niveau du code objet permet en outre aux développeurs de dérouler des opérations de vérification du code conformément aux règles de la DO-178C, et ce très tôt dans le cycle de développement d’une application. Dans le même temps, cette automatisation des tâches de vérification garantit une diminution des temps de process de certification vis-à-vis de la DO-178 C niveau A, en prouvant que le code a bien été développé conformément aux exigences de la norme, du modèle jusqu’au code objet .
LDRA now offers unprecedented verification of the model through a sophisticated integration with MATLAB and Simulink. The LDRA tool suite can now use real-world data from MATLAB that's connected to a Simulink model in order to fully verify the application at a source and object code level.
The original MISRA C, published in 1998, was called Guidelines for the Use of the C Language in Vehicle Based Software. It started from the premise that it was possible to write C code that was legal and that compiles, but that could be unpredictable in operation. The intention was that people would use the guidelines to develop coding standards for their projects. What actually happened was that companies developing code analysis tools tried to develop MISRA C compliance checkers to check that the guidelines were being followed. In doing so they discovered areas of ambiguity. The committee producing the guidelines thought they had been explicit or unambiguous, but trying to check the rules through a machine forces a close examination of the exact meaning of a rule, and this revealed a series of issues.
Electronic Engineering Journal
C is the most widely used programming language—and can be quite complex.
A standard set of rules is available to avoid any inherent ambiguities
and to help programmers steer a course to reliable code.
| Email: | info@ldra.com |
| Tel EMEA: | + 44 (0) 151 649 9300 |
| Tel USA: | (650) 583 8880 |
| Tel India: | +91 80 4080 8707 |