The scope of this Recommended Practice encompasses the following objectives: Concentrate on general best practices for vehicular embedded software design. Establish programming language-independent best practices. Establish hardware/software interface best practices. Establish multi-threaded system best practices. Provide verification criteria to evaluate product compliance with this best practice. Changes were made based on the feedback from the previously balloted document. Changes include consistent terminology usage and spelling mistakes in the following section; 3. Definitions 5.1.2 Use of Interrupts Caused by Module Input Signals (1-2) 5.1.3 Bounding Interrupt Overhead (1-3) 5.1.4 Use of Nested Interrupts (1-4) 5.2.1 Worst-Case CPU Load Measurement (2-1) 5.2.4 Use of Software Wait Loops (2-4) 5.3.1 Initialization of All Control Registers (3-1) 5.3.2 Refreshing Control Registers (3-2) 5.3.3 Clock Prescaler and Pll (3-3) 5.5.2 Unused Memory (5-2) 5.5.4.4 Data Integrity – Recovery (5-6) 5.5.4.6 Non-Volatile Memory Initialization (5-8) Appendix A – Discussion on System Design Interactions


    Access

    Check access

    Check availability in my library

    Order at Subito €


    Export, share and cite



    Title :

    General Automotive Embedded Software Design Requirements


    Publication date :

    2008-10-13



    Type of media :

    Conference paper


    Type of material :

    Print


    Language :

    English





    Requirements Engineering for Automotive Embedded Systems

    Staron, Miroslaw | Springer Verlag | 2019


    Model-Based Testing Design for Embedded Automotive Software

    Mjeda, Anila / Ryan, Kevin / McElligott, Pat et al. | SAE Technical Papers | 2009


    Model-based testing design for embedded automotive software

    Mjeda,A. / McElligott,P. / Ryan,K. et al. | Automotive engineering | 2009


    Hardware/Software Co-Design of an Automotive Embedded Firewall

    Pesé, Mert D. / Schmidt, Karsten / Zweck, Harald | British Library Conference Proceedings | 2017