StHlthSigStc_IntegrationManual

Integration Manual

For

State of Health Signal Statistics

VERSION: 4.0

DATE: 27-Sep-2016

Prepared By:

Software Group,

Nexteer Automotive,

Saginaw, MI, USA

Revision History

Sl. No.DescriptionAuthorVersionDate
1Initial versionAkilan Rathakrishnan1.015-Feb-2016
2EA4#4910 fixAkilan Rathakrishnan2.028-Mar-2016
3EA4#5553 updateAkilan Rathakrishnan3.002-May-2016
4EA4#7307Akilan Rathakrishnan4.027-Sep-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

AbbreviationDescription
DFDDesign functional diagram
MDDModule 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.TitleVersion
<1><FDD - <FDD ES106A_StHlthSigStc_Design>Refer Synergy subproject version

Dependencies

SWCs

ModuleRequired Feature
NoneN/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 FunctionParametersNotes
NONTRUSTED_NtWrapS_StHlthSigStc_UpdNvmPimThis function shall be defined as a non-trusted function call to the application that StHlthSigStc is integrated.
NONTRUSTED_NtWrapS_StHlthSigStc_ClrDataSampleThis function shall be defined as a non-trusted function call to the application that StHlthSigStc is integrated.
NONTRUSTED_NtWrapS_StHlthSigStc_UpdDataSampleThis function shall be defined as a non-trusted function call to the application that StHlthSigStc is integrated.

Configuration REQUIREMeNTS

Build Time Config

ModulesNotes
None

Configuration Files to be provided by Integration Project

StHlthSigStc_Cfg.c

StHlthSigStc_Cfg.h

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

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.

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

Parameter NameParameter Value
OS Application ReferenceApplication in which ES106A scheduled
  1. 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 NameParameter Value
StHlthSigStcCrcStartSymbolApplication CRC symbol name
  1. StHlthSigStcSignalLists: This list shall have one entry for every monitored signal.

Following set of information shall be configured for every signal:

  1. Singal Name: Signal name of the State of Health signal (mentioned in the below table).

  2. 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.

  3. Loop time: Loop time of the task with 1 micro second resolution.

Signal NameFDD
CtrlrTStHlthES210A_EcuTMeas
OutpAssiStHlthES259A_BattVltgCorrln
DigTqSnsrAStHlthES229A_HwTqCorrln
DigTqSnsrBStHlthES229A_HwTqCorrln
DigTqIdptSigStHlthES229A_HwTqCorrln
DutyCycStHlthSF009A_DutyCycThermProtn
EotImpctStHlthSF011A_EotLrng
MotPosStHlthES241A_MotAg2Meas
AbsltMotPosABDifStHlthES249A_MotAgCorrln
AbsltMotPosACDifStHlthES249A_MotAgCorrln
AbsltMotPosBCDifStHlthES249A_MotAgCorrln
CurrMotSumABCStHlthES209A_CurrMeasCorrln
CurrMotSumDEFStHlthES209A_CurrMeasCorrln
PhaAStHlthES320A_MotDrvDiagc
PhaBStHlthES320A_MotDrvDiagc
PhaCStHlthES320A_MotDrvDiagc
PhaDStHlthES320A_MotDrvDiagc
PhaEStHlthES320A_MotDrvDiagc
PhaEStHlthES320A_MotDrvDiagc
RamEccSngBitCorrnStHlthCM103A_RamMem
FricEstimnStHlthSF007A_SysFricLrng
WhlImbMaxCmpStHlthSF015A_WhlImbRejctn

DaVinci Interrupt Configuration Changes

ISR NameVIM #Priority DependencyNotes
N/A

Manual Configuration Changes

ConstantNotesSWC
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.

InitScheduling RequirementsTrigger
StHlthSigStcInit1Invoked by RTE during InitRTE
RunnableScheduling RequirementsTrigger
ClrSigStcHlthData_OperServer RunnableClient Call
GetSigStcHlthData_OperServer RunnableClient Call
StHlthStcPwrDwn_OperServer RunnableClient Call
UpdStHlthStcData_OperServer RunnableClient 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 SectionContentsNotes
None

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

Usage

FeatureRAMROM
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>

Last modified October 12, 2025: Initial commit (1fadfc4)