Component Implementation

• 1: HwAg0Meas_DesignReview
• 2: HwAg0Meas_IntegrationManual
• 3: HwAg0Meas_MDD
• 4: requirements

1 - HwAg0Meas_DesignReview

Rev 1.2

8-Jun-15

Peer Review Summary Sheet

Synergy Project Name:

kzshz2: Intended Use: Identify which component is being reviewed. This should be the Module Short Name from Synergy Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. CM690A_HwAg0Meas_Impl

Revision / Baseline:

kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.8.1

Change Owner:

kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Krishna Anne

Work CR ID:

EA4#6436

kzshz2: Intended Use: Intended to identify at a high level to the reviewers which areas of the component have been changed. Rationale: This will be good information to know when ensuring appropriate reviews have been completed. Modified File Types:

kzshz2: Intended Use: Identify who where the reviewers, what they reviewed, and if the reviewed changes have been approved to release the code for testing. Comments here should be at a highlevel, the specific comments should be present on the specific review form sheet. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. ADD DR Level Move reviewer and approval to individual checklist form Review Checklist Summary:

Reviewed:

Yes

MDD

Yes

Source Code

Yes

PolySpace

Yes

Integration Manual

Yes

Davinci Files

Comments:

Reviewed changes only, made port interface correction for a client, no functional changes

General Guidelines: - The reviews shall be performed over the portions of the component that were modified as a result of the Change Request. - New components should include FDD Owner and Integrator as apart of the Group Review Board (Source Code, Integration Manual, and Davinci Files) - Enter any rework required into the comment field and select No. When the rework is complete, review again using this same review sheet and select Yes. Add date and additional comment stating that the rework is completed. - To review a component with multiple source code files use the "Add Source" button to create a Source code tab for each source file. - .h file should be reviewed with the source file as part of the source file.

2 - HwAg0Meas_IntegrationManual

Integration Manual

For

HwAg0Meas

VERSION: 5.0

DATE: 21-Jun-2016

Prepared By:

TATA ELXSI

Chennai Location: The official version of this document is stored in the Nexteer Configuration Management System.

Revision History

Table of Contents

1 Abbrevations And Acronyms 4

2 References 5

3 Dependencies 6

3.1 SWCs 6

3.2 Global Functions(Non RTE) to be provided to Integration Project 6

4 Configuration REQUIREMeNTS 7

4.1 Build Time Config 7

4.2 Configuration Files to be provided by Integration Project 7

4.3 Da Vinci Parameter Configuration Changes 7

4.4 DaVinci Interrupt Configuration Changes 7

4.5 Manual Configuration Changes 7

5 Integration DATAFLOW REQUIREMENTS 8

5.1 Required Global Data Inputs 8

5.2 Required Global Data Outputs 8

5.3 Specific Include Path present 8

6 Runnable Scheduling 9

7 Memory Map REQUIREMENTS 10

7.1 Mapping 10

7.2 Usage 10

7.3 NvM Blocks 10

8 Compiler Settings 11

8.1 Preprocessor MACRO 11

8.2 Optimization Settings 11

9 Appendix 12

Abbrevations And Acronyms

References

This section lists the title & version of all the documents that are referred for development of this document

Dependencies

SWCs

Global Functions(Non RTE) to be provided to Integration Project

None

Configuration REQUIREMeNTS

Build Time Config

Configuration Files to be provided by Integration Project

HwAg0Meas_Cfg.h

Da Vinci Parameter Configuration Changes

DaVinci Interrupt Configuration Changes

Manual Configuration Changes

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer DataDict.m file in the FDD

Required Global Data Outputs

Refer DataDict.m file file in the FDD

Specific Include Path present

’

No

Runnable Scheduling

This section specifies the required runnable scheduling.

.

Memory Map REQUIREMENTS

Mapping

* Each …START_SEC… constant is terminated by a …STOP_SEC… constant as specified in the AUTOSAR Memory Mapping requirements.

Usage

Table 1: ARM Cortex R4 Memory Usage

NvM Blocks

RTE NvM Blocks

Note : Size of the NVM block if configured in developer

Compiler Settings

Preprocessor MACRO

None.

Optimization Settings

None.

Appendix

Refer CM10 for SPCO port configuration (SENT4SPCO shall be Port level High). Port Configuration SENT4SPCO output:

Port (that’s needs to be configured as SENT4SPCO) should be initialized as input DIO with level high.

The client call IoHwAb_SetFctPrphlHwAg0_Oper will reset the pin to output Alterante mode for SENT4SPCO.

Design Recommandation :

- Port Config RSENT2 IO pin shall setup default input.

- Schedule execution of tasks as per below order at the end of 2ms task

1. "HwAg0MeasPer2"

2. "HwAg0MeasPer3"

3. "HwAg0MeasPer4"

4. "HwAg0MeasPer1"

- Schedule "HwAg0MeasPer4" & "HwAg0MeasPer1" shall at least 110us apart.

3 - HwAg0Meas_MDD

Module Design Document

For

HwAg0Meas

Jun 21, 2016

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

TATA ELXSI

Chennai
Change History

Table of Contents

1 Introduction 6

1.1 Purpose 6

1.2 Scope 6

2 HwAg0Meas High-Level Description 7

3 Design details of software module 8

3.1 Graphical representation of HwAg0Meas 8

3.2 Data Flow Diagram 8

3.2.1 Component level DFD 8

3.2.2 Function level DFD 8

4 Constant Data Dictionary 9

4.1 Program (fixed) Constants 9

4.1.1 Embedded Constants 9

5 Software Component Implementation 10

5.1.1 Sub-Module Functions 10

5.1.2 Interrupt Service Routines 11

5.1.3 Server Runnable Functions 11

5.1.4 Module Internal (Local) Functions 11

5.1.4.1 Local Function #1 11

5.1.4.2 Description 12

5.1.5 Transition Functions 12

6 Known Limitations with Design 13

7 UNIT TEST CONSIDERATION 14

Appendix A Abbreviations and Acronyms 15

Appendix B Glossary 16

Appendix C References 17

Introduction

Purpose

Scope

HwAg0Meas High-Level Description

Refer to FDD

Design details of software module

Graphical representation of HwAg0Meas

Data Flow Diagram

Component level DFD

Refer FDD

Function level DFD

Refer FDD

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Software Component Implementation

Sub-Module Functions

Initialization sub-module {_Init()}

HwAg0MeasInit1 (Refer FDD for details)

Periodic sub-module {_Per()}

HwAg0MeasPer1 (Refer FDD for details)

Periodic sub-module {_Per()}

HwAg0MeasPer2 (Refer FDD for details)

Periodic sub-module {_Per()}

HwAg0MeasPer3 (Refer FDD for details)

Periodic sub-module {_Per()}

HwAg0MeasPer4 (Refer FDD for details)

Periodic sub-module {_Per()}

HwAg0MeasPer5 (Refer FDD for details)

Design Rationale:

The implementation brings in the block “HwAg0Final” inside the True Condition of the “finalAbsAg” as the other error condition will just retain the previous value and rolling counter will not change. It saves extra instructions in the implementation to the match the FDD. Final Functionality is still the same.

Interrupt Service Routines

None

Server Runnable Functions

Server Runnable: HwAg0MeasHwAg0AutTrim

Refer FDD for details

Server Runnable: HwAg0MeasHwAg0ClrTrim

Refer FDD for details

Server Runnable: HwAg0MeasHwAg0ReadTrim

Refer FDD for details

Server Runnable: HwAg0MeasHwAg0TrimPrfmdSts

Refer FDD for details

Server Runnable: HwAg0MeasHwAg0WrTrim

Refer FDD for details

Module Internal (Local) Functions

Local Function #1

Description

The implementation deviates from the FDD block “Intpn” block. The implementation finds the minimum of absolute values of the difference between HwAg0Step with all the values from the Calibration table and find the index associated with minimum value of the difference in the calibration table.

Local Function #2

Design Rationale

This function can be used both for read-and-use and for read-and-discard

Transition Functions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

• Roll Over is intentional for

  • *Rte_Pim_HwAg0Snsr0ComStsErrCntr()

  • *Rte_Pim_HwAg0Snsr0IdErrCntr()

  • *Rte_Pim_HwAg0Snsr0IntSnsrErrCntr()

  • *Rte_Pim_HwAg0Snsr0NoMsgErrCntr()

  • *Rte_Pim_HwAg0Snsr1ComStsErrCntr()

  • *Rte_Pim_HwAg0Snsr1IdErrCntr()

  • *Rte_Pim_HwAg0Snsr1IntSnsrErrCntr()

  • *Rte_Pim_HwAg0Snsr1NoMsgErrCntr()

  • (*Rte_Pim_HwAg0PrevRollCnt).

• Thus counter acts in circular

Abbreviations and Acronyms

Glossary

Note: Terms and definitions from the source “Nexteer Automotive” take precedence over all other definitions of the same term. Terms and definitions from the source “Nexteer Automotive” are formulated from multiple sources, including the following:

• ISO 9000

• ISO/IEC 12207

• ISO/IEC 15504

• Automotive SPICE® Process Reference Model (PRM)

• Automotive SPICE® Process Assessment Model (PAM)

• ISO/IEC 15288

• ISO 26262

• IEEE Standards

• SWEBOK

• PMBOK

• Existing Nexteer Automotive documentation

References

4 - requirements