This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Implementation

1: requirements
2: StHlthSigStc Review
3: StHlthSigStc_IntegrationManual
4: StHlthSigStc_MDD

Component Implementation

Component Documentation

1 - requirements

FDD	ID	Source	Function	Line(s)	Status	Comment
		.SwFileName	.SwFuncName	.SwLines	.SwStatus	.SwComment
ES106A	42	StHlthSigStc.c	StHlthStcPwrDwn_Oper,StHlthSigStc_UpdNvmPim	563-572,864-886	I
ES106A	22	StHlthSigStc.c	StHlthStcPwrDwn_Oper,StHlthSigStc_GetSigStHlthData,StHlthSigStc_UpdDataSample	507,561,760-809,917-953	I
ES106A	24	StHlthSigStc.c	StHlthStcPwrDwn_Oper,StHlthSigStc_UpdNvmPim	562-571,863-885	I
ES106A	26	StHlthSigStc.c	StHlthStcPwrDwn_Oper	486-581	I
ES106A	20	StHlthSigStc.c	StHlthSigStcInit1	412-421	I
ES106A	21	StHlthSigStc.c	StHlthStcPwrDwn_Oper,StHlthSigStc_GetSigStHlthData,StHlthSigStc_UpdDataSample	506,560,759-808,916-952	I
ES106A	48	StHlthSigStc.c	StHlthSigStcInit1	358-391	I
ES106A	49	StHlthSigStc.c	StHlthSigStcInit1	372-375	I
ES106A	44	StHlthSigStc.c	StHlthSigStcInit1	398-406	I
ES106A	45	StHlthSigStc.c	StHlthStcPwrDwn_Oper	502	I
ES106A	28	StHlthSigStc.c	StHlthStcPwrDwn_Oper	487-582	I
ES106A	43	StHlthSigStc.c	StHlthSigStcInit1	349-392	I
ES106A	40	StHlthSigStc.c	ClrSigStcHlthData_Oper,StHlthSigStc_ClrDataSample	216-232,676-707	I
ES106A	5	StHlthSigStc.c	StHlthSigStc_UpdNvmPim	147	I
ES106A	7	StHlthSigStc.c	StHlthSigStc_UpdNvmPim	149	I
ES106A	6	StHlthSigStc.c	StHlthSigStc_UpdNvmPim	148	I
ES106A	8	StHlthSigStc.c	StHlthSigStc_UpdNvmPim	150	I
ES106A	11	StHlthSigStc.c	UpdStHlthStcData_Oper	632-648	I
ES106A	39	StHlthSigStc.c	ClrSigStcHlthData_Oper,StHlthSigStc_ClrDataSample	215-231,675-706	I
ES106A	12	StHlthSigStc.c	StHlthStcPwrDwn_Oper	463-580	I
ES106A	15	StHlthSigStc.c	StHlthStcPwrDwn_Oper,StHlthSigStc_GetSigStHlthData,StHlthSigStc_UpdDataSample	504,558,757-806,914-950	I
ES106A	14	StHlthSigStc.c	StHlthSigStcInit1	410-419	I
ES106A	17	StHlthSigStc.c	StHlthSigStcInit1	411-420	I
ES106A	33	StHlthSigStc.c	StHlthStcPwrDwn_Oper	491-586	I
ES106A	32	StHlthSigStc.c	StHlthStcPwrDwn_Oper	490-585	I
ES106A	31	StHlthSigStc.c	StHlthStcPwrDwn_Oper	489-584	I
ES106A	30	StHlthSigStc.c	StHlthStcPwrDwn_Oper	488-583	I
ES106A	37	StHlthSigStc.c	StHlthSigStc_GetSigStHlthData	737-843	I
ES106A	50	StHlthSigStc.c	StHlthSigStcInit1	383-389	I
ES106A	35	StHlthSigStc.c	UpdStHlthStcData_Oper	633-649	I
ES106A	52	StHlthSigStc.c	StHlthSigStcInit1	394-422	I
ES106A	18	StHlthSigStc.c	StHlthStcPwrDwn_Oper,StHlthSigStc_GetSigStHlthData,StHlthSigStc_UpdDataSample	505,559,758-807,915-951	I

2 - StHlthSigStc Review

Overview

Summary Sheet
Synergy Project
Davinci Files
Source Code
MDD
PolySpace
Integration Manual

Sheet 1: Summary Sheet

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. ES106A_StHlthSigStc_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. ES106A_StHlthSigStc_Impl_2.2.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. Akilan Rathakrishnan

Work CR ID:

EA4#7836

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:

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.

Sheet 2: Synergy Project

Peer Review Meeting Log (Component Synergy Project Review)

Quality Check Items:

Rationale is required for all answers of No

New baseline version name from Summary Sheet follows

Yes

Comments:

naming convention

Project contains necessary subprojects

Yes

Comments:

Project contains the correct version of subprojects

Yes

Comments:

Design subproject is correct version

Yes

Comments:

General Notes / Comments:

LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:

Change Owner:

Akilan Rathakrishnan

Review Date :

12/09/16

Lead Peer Reviewer:

Rijvi Ahmed

Approved by Reviewer(s):

Other Reviewer(s):

Sheet 3: Davinci Files

Rev 1.2

8-Jun-15

Peer Review Meeting Log (Davinci Review)

Quality Check Items:

Rationale is required for all answers of No

Only StdDef Port types are used

Yes

Comments:

For components not using application data types, do all

Yes

Comments:

port interface names end in PortIf and a sequence number

Non-program-specific components saved

Yes

Comments:

in Autosar 4.0.3 format

*Cfg.arxml.TT: Verfied Davinci Configurator imported the

N/A

Comments:

change correctly

*Cfg.h.TT: Verfied Davinci Configurator generates

Yes

Comments:

the configuration header(s) file correctly

kzshz2: Either a generic sandbox or a baselined integration project can be used to verify

All changed files have been compared against previous

Yes

Comments:

versions (If available)

kzshz2: Intended Use: Identify if previous version was compared and only the expected change(s) was present. This is for text files only, not binary or GUIs Rationale: This is helpful in identifying unapproved (intended or mistaken) changes.

Automated validation check is performed

Yes

Comments:

Naming conventions followed. All names should

Yes

Comments:

Only for the changes

match DataDict.m

Sender/Receiver port properties match DataDict.m

N/A

Comments:

file (use .m file helper tool)

Calibration port properties match DataDict.m

N/A

Comments:

file (use .m file helper tool)

Components using application data types:

Sender/Receiver port initialization values match

N/A

Comments:

DataDict.m file

Calibration port initialization values match

N/A

Comments:

DataDict.m file

Components not using application data types:

Sender/Receiver port initialization values match

Yes

Comments:

DataDict.m file and have been converted to counts

for fixed point types

Calibration port initialization values match

N/A

Comments:

DataDict.m file and have been converted to counts

for fixed point types

Mapping set and all unused items have been

N/A

Comments:

removed

All sender/receiver port read/writes using direct

Yes

Comments:

Only for the changes

read/writes(List justification if not)

Runnable calling frequencies match FDD

N/A

Comments:

DataDict.m display variables: created as

N/A

Comments:

PerInstanceMemory. Matches the FDD

Component is correct component type

Yes

Comments:

General Notes / Comments:

1. Local implementation datatype definition allowed ? - Moved to Stddef - done 12/9/2016

2. Check cal access for nvm pim in other components - Changed to all ReadOnly - done 12/9/2016

Change Owner:

Akilan Rathakrishnan

Review Date :

12/09/16

Component Type :

Application

Lead Peer Reviewer:

Rijvi Ahmed

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 4: Source Code

Rev 1.2

8-Jun-15

Peer Review Meeting Log (Source Code Review)

Source File Name:

StHlthSigStc.c

Source File Revision:

Header File Name:

StHlthSigStc.h

Header File Revision:

kzshz2: Intended Use: Identify which version of the source file is being review. Rationale: Required for traceability between source code and review. Auditors will likely require this. 1

MDD Name:

StHlthSigStc_MDD.doc

Revision:

FDD/SCIR/DSR/FDR/CM Name:

ES106A_StHlthSigStc_Design

Revision:

2.4.0

Quality Check Items:

Rationale is required for all answers of No

Working EA4 Software Naming Convention followed:

for variable names

Yes

Comments:

for constant names

Yes

Comments:

for function names

N/A

Comments:

for other names (component, memory

Yes

Comments:

mapping handles, typedefs, etc.)

All paths assign a value to outputs, ensuring

N/A

Comments:

all outputs are initialized prior to being written

Requirements Tracability tags in code match the requirements tracability in the FDD

N/A

Comments:

requirements tracability in the FDD

All variables are declared at the function level.

Yes

Comments:

Synergy version matches change history

kzshz2: Intended Use: Indicate that the the versioning was confirmed by the peer reviewer(s). Rationale: There have been many occassions where versions were not updated in files and as a result Unit Test were referencing wrong versions. This often time leads to the need to re-run of batch tests.

Yes

Comments:

and Version Control version in file comment block

Change log contains detailed description of changes

Yes

Comments:

and Work CR number

Code accurately implements FDD (Document or Model)

Yes

Comments:

Functionally matches the FDD

Verified no Compiler Errors or Warnings

KMC: Intended Use: To confirm no compiler errors or warnings exist for the code under review (warnings from contract header files may be ignored). Rationale: This is needed to ensure there will be no errors discovered at the time of integration. A Sandox project should be used; QAC can find compiler errors but not warnings.

Yes

Comments:

Component.h is included

Yes

Comments:

All other includes are actually needed. (System includes

Yes

Comments:

only allowed in Nexteer library components)

Software Design and Coding Standards followed:

Version: 2.1

Code comments are clear, correct, and adequate

Yes

Comments:

and have been updated for the change: [N40] and

all other rules in the same section as rule [N40],

plus [N75], [N12], [N23], [N33], [N37], [N38],

[N48], [N54], [N77], [N79], [N72]

Source file (.c and .h) comment blocks are per

Yes

Comments:

standards and contain correct information: [N41], [N42]

Function comment blocks are per standards and

Yes

Comments:

contain correct information: [N43]

Code formatting (indentation, placement of

Yes

Comments:

braces, etc.) is per standards: [N5], [N55], [N56],

[N57], [N58], [N59]

Embedded constants used per standards; no

Yes

Comments:

"magic numbers": [N12]

Memory mapping for non-RTE code

Yes

Comments:

is per standard

All execution-order-dependent code can be

Yes

Comments:

recognized by the compiler: [N80]

All loops have termination conditions that ensure

N/A

Comments:

finite loop iterations: [N63]

All divides protect against divide by zero

Yes

Comments:

if needed: [N65]

All integer division and modulus operations

N/A

Comments:

handle negative numbers correctly: [N76]

All typecasting and fixed point arithmetic,

Yes

Comments:

including all use of fixed point macros and

timer functions, is correct and has no possibility

of unintended overflow or underflow: [N66]

All float-to-unsiged conversions ensure the.

Yes

Comments:

float value is non-negative: [N67]

All conversions between signed and unsigned

N/A

Comments:

types handle msb==1 as intended: [N78]

All pointer dereferencing protects against

Yes

Comments:

null pointer if needed: [N70]

Component outputs are limited to the legal range

N/A

Comments:

defined in the FDD DataDict.m file : [N53]

All code is mapped with FDD (all FDD

Yes

Comments:

subfunctions and/or model blocks identified

with code comments; all code corresponds to

some FDD subfunction and/or model block): [N40]

Review did not identify violations of other

Yes

Comments:

coding standard rules

Anomaly or Design Work CR created

Yes

Comments:

for any FDD corrections needed

General Notes / Comments:

Reviewed only the changes

Change Owner:

Akilan Rathakrishnan

Review Date :

12/09/16

Lead Peer Reviewer:

Rijvi Ahmed

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 5: MDD

Rev 1.2

8-Jun-15

Peer Review Meeting Log (MDD Review)

MDD Name:

StHlthSigStc_MDD.doc

MDD Revision:

Source File Name:

StHlthSigStc.c

Source File Revision:

Source File Name:

Source File Revision:

Source File Name:

Source File Revision:

Quality Check Items:

Rationale is required for all answers of No

Synergy version matches document

Yes

Comments:

Change log contains detailed description of changes

Yes

Comments:

Changes Highlighted (for Unit Tester)

Yes

Comments:

Diagrams have been included per MDD Guideline

Yes

Comments:

and reviewed

All Design Exceptions and Limitations are listed

Yes

Comments:

Design rationale given for all global

N/A

Comments:

data not communicated through RTE ports, per

Design and Coding Standards rules [N9] and [N10].

All implementation details that differ from the FDD are

N/A

Comments:

noted and explained in Design Rationale

All Unit Test Considerations have been described

N/A

Comments:

General Notes / Comments:

Change Owner:

Akilan Rathakrishnan

Review Date :

09/30/16

Lead Peer Reviewer:

Rijvi Ahmed

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 6: PolySpace

Rev 1.2

8-Jun-15

Peer Review Meeting Log (QAC/PolySpace Review)

Source File Name:

StHlthSigStc.c

Source File Revision:

Source File Name:

StHlthSigStc_Cfg.c

Source File Revision:

Source File Name:

Source File Revision:

EA4 Static Analysis Compliance Guideline version:

01.01.00

Poly Space version:

Windows User: eg. 2013b R2013b

Polyspace sub project version:

Windows User: eg. TL108a_PolyspaceSuprt_1.0.0 Not released

QAC version:

Windows User: eg 8.1.1-R 8.1.1-R

QAC sub project version:

Windows User: eg. TL_100A_1.1.0 TL100A_QACSuprt_1.2.0

Quality Check Items:

Rationale is required for all answers of No

Contract Folder's header files are appropriate and

kzshz2: Intended Use: Identify that the contract folder contains only the information required for this component. All other variables, constants, function prototypes, etc. should be removed. Rationale: This will help avoid unit testers having to considers object not used. It will also avoid having other files required for QAC.

Yes

Comments:

function prototypes match the latest component version

100% Compliance to the EA4 Static Analysis

Yes

Comments:

Compliance Guideline

Are previously added justification and deviation

Yes

Comments:

comments still appropriate

Do all MISRA deviation comments use approved

Yes

Comments:

deviation tags

Cyclomatic complexity and Static path count OK

Creager, Kathleen: use Browse Function Metrics, STCYC and STPTH

Yes

Comments:

for all functions in the component per Design

and Coding Standards rule [N47]

General Notes / Comments:

1. Warnings under MISRA 17.1, 17.4, 21.1 , 11.4, 16.7 - All these warnings requires deviation - Open 2/15/2016

2. Please add deviation rationale in the source file for the following MISRA rules:
11.4, 16.7, 17.4, 8.9 - Comment added for 11.4. For other warning there is no deviation tag available. It shall be done once draft version is released - Open 12/12/2016

3. MISRA warning 12.12 is observed, because of the typecasting of the pointer to a floating point pointer to a floating point array type. Deviation comment is required.

4. MISRA 17.1: pointer arithmatic needed in this component - Deviation required

Change Owner:

Akilan Rathakrishnan

Review Date :

12/12/16

Lead Peer Reviewer:

Rijvi Ahmed

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 7: Integration Manual

Rev 1.2

8-Jun-15

Peer Review Meeting Log (Integration Manual Review)

Integration Manual Name:

kzshz2: Intended Use: Identify which file is being reviewed Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form. StHlthSigStc_IntegrationManual.doc

Integration Manual Revision:

kzshz2: Intended Use: Identify which version of the integration manual has been reviewed. Rationale: Required for traceability between the MDD and review. Auditors will likely require this. 5

Quality Check Items:

Rationale is required for all answers of No

Synergy version matches header

Yes

Comments:

Latest template used

Yes

Comments:

Change log contains detailed description of changes

Yes

Comments:

Changes Highlighted (for Integrator)

Yes

Comments:

General Notes / Comments:

Change Owner:

Akilan Rathakrishnan

Review Date :

12/12/16

Lead Peer Reviewer:

Selva

Approved by Reviewer(s):

Yes

Other Reviewer(s):

3 - StHlthSigStc_IntegrationManual

Integration Manual

For

State of Health Signal Statistics

VERSION: 5.0

DATE: 12-Dec-2016

Prepared By:

Software Group,

Nexteer Automotive,

Saginaw, MI, USA

Revision History

Sl. No.	Description	Author	Version	Date
1	Initial version	Akilan Rathakrishnan	1.0	15-Feb-2016
2	EA4#4910 fix	Akilan Rathakrishnan	2.0	28-Mar-2016
3	EA4#5553 update	Akilan Rathakrishnan	3.0	02-May-2016
4	EA4#7307	Akilan Rathakrishnan	4.0	27-Sep-2016
5	EA4#7836 – added note for regenerating cfg files	Akilan Rathakrishnan	5.0	12-Dec-2016

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 8

4.5 Manual Configuration Changes 8

5 Integration DATAFLOW REQUIREMENTS 9

5.1 Required Global Data Inputs 9

5.2 Required Global Data Outputs 9

5.3 Specific Include Path present 9

6 Runnable Scheduling 10

7 Memory Map REQUIREMENTS 11

7.1 Mapping 11

7.2 Usage 11

7.3 Non RTE NvM Blocks 11

7.4 RTE NvM Blocks 11

8 Compiler Settings 12

8.1 Preprocessor MACRO 12

8.2 Optimization Settings 12

9 Appendix 13

Abbrevations And Acronyms

Abbreviation	Description
DFD	Design functional diagram
MDD	Module design Document
	<ADD more to the table if applicable>

References

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

Sr. No.	Title	Version
<1>	<FDD - <FDD ES106A_StHlthSigStc_Design>	Refer Synergy subproject version

Dependencies

SWCs

Module	Required Feature
None	N/A

Note : Referencing the external components should be avoided in most cases. Only in unavoidable circumstance external components should be referred. Developer should track the references.

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

See section 6. Please note the server runnables listed can be used as needed in the integration project and can be called via the RTE or outside of the RTE as required

Non-Trusted Function	Parameters	Notes
NONTRUSTED_NtWrapS_StHlthSigStc_UpdNvmPim		This function shall be defined as a non-trusted function call to the application that StHlthSigStc is integrated.
NONTRUSTED_NtWrapS_StHlthSigStc_ClrDataSample		This function shall be defined as a non-trusted function call to the application that StHlthSigStc is integrated.
NONTRUSTED_NtWrapS_StHlthSigStc_UpdDataSample		This function shall be defined as a non-trusted function call to the application that StHlthSigStc is integrated.

Configuration REQUIREMeNTS

Build Time Config

Modules	Notes
None

Configuration Files to be provided by Integration Project

StHlthSigStc_Cfg.c

StHlthSigStc_Cfg.h

Note 1: Include “StHlthSigStc_Cfg.h” in the “Rte_UserTypes.h” file since user defined typedefs are generated in this file.

Note 2: Configuration files “StHlthSigStc_Cfg.c” and “StHlthSigStc_Cfg.h”

shall be regenerated whenever there is a change in text template files StHlthSigStc_Cfg.c.tt and StHlthSigStc_Cfg.h.tt.

Da Vinci Parameter Configuration Changes

Following configurations shall be made in DaVinci configurator for the component.

There are three containers that need to be instantiated for this components configuration.

StHlthSigStcApplicationConfigs : OS application in which this component is scheduled to run shall be configured in this container.

Parameter Name	Parameter Value
OS Application Reference	Application in which ES106A scheduled

StHlthSigStcCrConfigLists: List of CRC constants that are need to be checked for NvM validation shall be configured in this container. Each CRC constant shall have one entry.

Below table indicates list of CRC values currently considered.

Parameter Name	Parameter Value
StHlthSigStcCrcStartSymbol	Application CRC symbol name

StHlthSigStcSignalLists: This list shall have one entry for every monitored signal.

Following set of information shall be configured for every signal:

Singal Name: Signal name of the State of Health signal (mentioned in the below table).
Task Id: Task id of the task in which the periodic(s) from the FDD, mentioned against respective signal in the below table, is scheduled.
Loop time: Loop time of the task with 1 micro second resolution.

Signal Name	FDD
CtrlrTStHlth	ES210A_EcuTMeas
OutpAssiStHlth	ES259A_BattVltgCorrln
DigTqSnsrAStHlth	ES229A_HwTqCorrln
DigTqSnsrBStHlth	ES229A_HwTqCorrln
DigTqIdptSigStHlth	ES229A_HwTqCorrln
DutyCycStHlth	SF009A_DutyCycThermProtn
EotImpctStHlth	SF011A_EotLrng
MotPosStHlth	ES241A_MotAg2Meas
AbsltMotPosABDifStHlth	ES249A_MotAgCorrln
AbsltMotPosACDifStHlth	ES249A_MotAgCorrln
AbsltMotPosBCDifStHlth	ES249A_MotAgCorrln
CurrMotSumABCStHlth	ES209A_CurrMeasCorrln
CurrMotSumDEFStHlth	ES209A_CurrMeasCorrln
PhaAStHlth	ES320A_MotDrvDiagc
PhaBStHlth	ES320A_MotDrvDiagc
PhaCStHlth	ES320A_MotDrvDiagc
PhaDStHlth	ES320A_MotDrvDiagc
PhaEStHlth	ES320A_MotDrvDiagc
PhaEStHlth	ES320A_MotDrvDiagc
RamEccSngBitCorrnStHlth	CM103A_RamMem
FricEstimnStHlth	SF007A_SysFricLrng
WhlImbMaxCmpStHlth	SF015A_WhlImbRejctn

DaVinci Interrupt Configuration Changes

ISR Name	VIM #	Priority Dependency	Notes
N/A

Manual Configuration Changes

Constant	Notes	SWC
N/A

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer DataDict.m file

Required Global Data Outputs

Refer DataDict.m file

Specific Include Path present

Yes

Runnable Scheduling

This section specifies the required runnable scheduling.

Init	Scheduling Requirements	Trigger
StHlthSigStcInit1	Invoked by RTE during Init	RTE

Runnable	Scheduling Requirements	Trigger
ClrSigStcHlthData_Oper	Server Runnable	Client Call
GetSigStcHlthData_Oper	Server Runnable	Client Call
StHlthStcPwrDwn_Oper	Server Runnable	Client Call
UpdStHlthStcData_Oper	Server Runnable	Client Call
NONTRUSTED_NtWrapS_StHlthSigStc_ClrDataSample	Non-Tusted function definition (Index: NtWrapS_StHlthSigStc_ClrDataSample)	On Event
NONTRUSTED_NtWrapS_StHlthSigStc_UpdNvmPim	Non-Tusted function definition (Index: NtWrapS_StHlthSigStc_UpdNvmPim)	On Event
NONTRUSTED_NtWrapS_StHlthSigStc_UpdDataSample	Non-Tusted function definition (Index: NtWrapS_StHlthSigStc_UpdDataSample)	On Event

Memory Map REQUIREMENTS

Mapping

Memory Section	Contents	Notes
None

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

Usage

Feature	RAM	ROM
None

Table 1: ARM Cortex R4 Memory Usage

Non RTE NvM Blocks

Block Name

None

Note : Size of the NVM block if configured in developer

RTE NvM Blocks

Block Name

SigStcHistDataAry

Note : Size of the NVM block if configured in developer

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

<This section is for appendix>

4 - StHlthSigStc_MDD

Module Design Document

For

State of Health Signal Statistics

Dec 07, 2016

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Software Group,

Nexteer Automotive,

Saginaw, MI, USAChange History

Sl. No.	Description	Author	Version	Date
1	Initial Version	Akilan Rathakrishnan	1.0	15-Feb-2016
2	Updated for EA4#5553	Akilan Rathakrishnan	2.0	04-May-2016
3	Updated for EA4#7307	Akilan Rathakrishnan	3.0	27-Sep-2016
4	Updated for EA4#7836	Akilan Rathakrishnan	4.0	07-Dec-2016

Table of Contents

1 StHlthSignStc High-Level Description 5

2 Design details of software module 6

Graphical representation of StHlthSigStc 6

Data Flow Diagram 6

2.1.1 Component level DFD 6

2.1.2 Function level DFD 6

3 Variable Data Dictionary 7

3.1 User defined typedef definition/declaration 7

3.2 Variable definition for enumerated types 7

4 Constant Data Dictionary 8

Program (fixed) Constants 8

4.1.1 Embedded Constants 8

4.1.1.2 Global 8

4.1.2 Module specific Lookup Tables Constants 8

5 Software Module Implementation 9

5.1 Sub-Module Functions 9

5.1.1 Initialization Functions: StHlthSigStcInit1 9

5.1.2 PERIODIC FUNCTIONS 9

5.1.3 Interrupt Functions 9

5.1.4 Server Runnable Functions 9

5.1.4.1 ClrSigStcHlthData_Oper 9

5.1.4.2 GetSigStcHlthData_Oper 9

5.1.4.3 StHlthStcPwrDwn_Oper 9

5.1.4.4 UpdStHlthStcData_Oper 9

5.1.5 Module Internal (Local) Functions 9

5.1.5.1 Local Function #1 9

5.1.5.1.1 Description 9

5.1.5.2 Local Function #2 9

5.1.5.2.1 Description 10

5.1.5.3 Local Function #3 10

5.1.5.3.1 Description 10

5.1.5.4 Local Function #4 10

5.1.5.4.1 Description 10

5.1.6 Transition Functions 10

5.1.7 Global Function/Macro Definitions 10

5.1.7.1 Global Function #1 10

5.1.7.1.1 Description 10

5.1.7.2 Global Function #2 11

5.1.7.2.1 Description 11

5.1.7.3 Global Function #3 11

5.1.7.3.1 Description 11

6 Known Limitations with Design 12

7 UNIT TEST CONSIDERATION 13

Appendix A Abbreviations and Acronyms 14

Appendix B Glossary 15

Appendix C References 16

StHlthSignStc High-Level Description

This component shall collect State of Health data signals from other component(s) and shall compute following statistical values for each signal: Minimum, Maximum, Average and Life Cycle Sample counter. This component shall provide statistical data for ignition cycle and for life cycle for each signal upon request.

Design details of software module

See FDD.

Graphical representation of StHlthSigStc

Data Flow Diagram

See FDD.

Component level DFD

See FDD.

Function level DFD

See FDD.

Variable Data Dictionary

User defined typedef definition/declaration

<This section documents any user types uniquely used for the module.>

Typedef Name	Element Name	User Defined Type	Legal Range (min)	Legal Range (max)
Ary1D_u8_ StHlthSigStc1	Array	uint8	0	65535
Ary1D_u32_ StHlthSigStc1	Array	uint32	0	65535
Ary1D_f32_ StHlthSigStc1	Array	Float32	0	65535
StHlthSigStcPrmRec1	GetStHlthDataOper	uint8 (*GetDataOper)(void )	0	4294967295
	SamplePerSec	uint16	0	65535
	TaskRef	TaskType	0	255
	RamStorgOffs	uint8	0	255
	NvmStorgOffs	uint8	0	255
StHlthSigStcCrcAdrRec1	* CrcStrtAdr	uint32	0	4294967295
StHlthSigStcPrmRec1	*SigPrm	StHlthSigStcPrmRec1	0	4294967295
	*CrcAdr	StHlthSigStcCrcAdrRec1	0	4294967295

Ary1D_u8_StHlthSigStc1 – Typedef for Ram buffer where State of Health Statistical data is kept for the current Ignition cycle. Size of this array is configurable.

Ary1D_u32_ StHlthSigStc1 – Typedef for Ignition cycle sample counter. Size of this array is configurable.

Ary1D_f32_ StHlthSigStc1 – typedef for Signal Average value. Size of this array is configurable.

Variable definition for enumerated types

Enum Name	Element Name	Value
See DataDict.m file

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Constant Name	Resolution	Units	Value
See DataDict.m file
CRCBUFSIZE_CNT_U08	1	Cnt	(WORDSIZE_CNT_U08*NROFCRCAREA_CNT_U08)
STHLTHMAXVAL_CNT_F32	Single precision float	Cnt	100.0
STHLTHMINVAL_CNT_F32	Single precision float	Cnt	0.0

* Also see see FDD ES106A_StHlthSigStc_DataDict.m file

Global

Constant Name

See DataDict.m file

Module specific Lookup Tables Constants

<(This is for lookup tables (arrays) with fixed values, same name as other tables)>

Constant Name	Resolution	Value	Software Segment
StHlthSigStcCfgRecInst	StHlthSigStcCfgRec1	Configured	StHlthSigStc_CONST

Software Module Implementation

Sub-Module Functions

None

Initialization Functions: StHlthSigStcInit1

See DataDict.m file and model. This function exists in “StHlthSigStc.c” file.

PERIODIC FUNCTIONS

None

Interrupt Functions

None

Server Runnable Functions

ClrSigStcHlthData_Oper

See DataDict.m file and model. This function exists in “StHlthSigStc.c” file.

GetSigStcHlthData_Oper

See DataDict.m file and model. This function exists in “StHlthSigStc.c” file.

StHlthStcPwrDwn_Oper

See DataDict.m file and model. This function exists in “StHlthSigStc.c” file.

UpdStHlthStcData_Oper

See DataDict.m file and model. This function exists in “StHlthSigStc.c” file.

Module Internal (Local) Functions

Local Function #1

Function Name	StHlthSigStc_ClrDataSample	Type	Min	Max
Arguments Passed	TarSel_Uls_T_logl	boolean	FALSE	TRUE
Return Value	None	N/A	N/A	N/A

Description

This function implements “StHlthStcPwrDwn” function in the FDD.

Local Function #2

Function Name	StHlthSigStc_GetSigStHlthData	Type	Min	Max
Arguments Passed	SigId_Uls_T_enum	StHlthMonSig3	0	21
	TarAdr	uint8*	0x0000000	0xFFFFFFFF
Return Value	None	N/A	N/A	N/A

Description

This function implements “GetSigStcHlthData” function in the FDD.

Local Function #3

Function Name	StHlthSigStc_UpdNvmPim	Type	Min	Max
Arguments Passed	NvmPim_Ptr_T_u08	uint8*	0x0000000	0xFFFFFFFF
	NvmMaxVal_Uls_T_u08	uint8	0	100
	NvmMinVal_Uls_T_u08	uint8	0	100
	NvmAvrgVal_Uls_T_u7p9	u7p9	0	65535
	NvmSampleCnt_Uls_T_u32	Uint32	0	Max of u32
Return Value	None	N/A	N/A	N/A

Description

This function implements “Update Nvm” function in the FDD.

Local Function #4

Function Name	StHlthSigStc_UpdDataSample	Type	Min	Max
Arguments Passed	TaskRef_Uls_T_u08	uint8	0	255
Return Value	None	N/A	N/A	N/A

Description

This function implements “Update Nvm” function in the FDD.

Transition Functions

None.

Global Function/Macro Definitions

Global Function #1

Function Name	NONTRUSTED_NtWrapS_StHlthSigStc_UpdDataSample	Type	Min	Max
Arguments Passed	FunctionIndex	NonTrustedFunctionIndexType	0	65535
	FunctionParams	NonTrustedFunctionParameterRefType	0	0xFFFFFF
Return Value	void

Description

Implements Nontrusted function wrapper for UpdDataSample. This will be called from UpdStHlthStcData_Oper upon client invocation.

Global Function #2

Function Name	NONTRUSTED_NtWrapS_StHlthSigStc_UpdNvmPim	Type	Min	Max
Arguments Passed	FunctionIndex	NonTrustedFunctionIndexType	0	65535
	FunctionParams	NonTrustedFunctionParameterRefType	0	0xFFFFFF
Return Value	void

Description

Implements Nontrusted function wrapper for UpdNvmPim. This will be called from StHlthStcPwrDwn_Oper upon client invocation.

Global Function #3

Function Name	NONTRUSTED_NtWrapS_StHlthSigStc_ClrDataSample	Type	Min	Max
Arguments Passed	FunctionIndex	NonTrustedFunctionIndexType	0	65535
	FunctionParams	NonTrustedFunctionParameterRefType	0	0xFFFFFF
Return Value	void

Description

Implements Nontrusted function wrapper for UpdNvmPim. This will be called from ClrSigStcHlthData_Oper upon client invocation.

Known Limitations with Design

Following constants are not used in the implementation even though they defined in the .m file. It is only used for the purpose of model simulation.

SHIFTFAC16_ULS_U08
SHIFTFAC24_ULS_U08
SHIFTFAC8_ULS_U08

Number of signals that can be supported for State of Health monitoring is limited NVM block size. Currently State of Health NVM block size is set to 225 bytes. With each signal occupying 8 bytes, 1 byte for CRC, current design can support upto 28 signals.
Implementation uses different name for following PIM variables that are defined in .m file:
1. SigStcPrmInst
2. CrcInst

UNIT TEST CONSIDERATION

Config files in the contract folder are for a test project with sample configurations for two monitored signals CtrlrTStHlth and OutpAssiStHlth.
Signal related configurations are generated out of Configurator. Hence, none of the configuration values shall be hand-modified to cover legal range of underlying parameter. If complete range need to be supported, then make configuration, and generate the cfg files accordingly.

Abbreviations and Acronyms

Abbreviation or Acronym	Description
DFD	Design functional diagram
MDD	Module design Document
FDD	Functional Design Document

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

Term	Definition	Source
MDD	Module Design Document
DFD	Data Flow Diagram

References

Ref. #	Title	Version
1	AUTOSAR Specification of Memory Mapping (Link:AUTOSAR_SWS_MemoryMapping.pdf)	v1.3.0 R4.0 Rev 2
2	MDD Guideline	EA4 01.00.00
3	Software Naming Conventions.doc	1.0
4	Software Design and Coding Standards.doc	2.0
5	FDD: ES106A_StHlthSigStc_Design	See Synergy subproject version