ExcpnHndlg Integration Manual

Integration Manual

For

ExcpnHndlg

VERSION: 4

DATE: 04/05/16

Prepared By:

Software Group,

Nexteer Automotive,

Saginaw, MI, USA

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

Revision History

Sl. No.DescriptionAuthorVersionDate
1Initial versionLucas Wendling1.001/19/16
2Updated for ChkForStrtUpTest() functions and Clock Monitor FEAvinash James2.002/10/16
3Updated for DTS RAM Double bit ECC error from FENMI to SYSERRAvinash James3.003/22/16
4Updates for New FENMI Handlers for mode error and removed SPI Dbt Bit handlerAvinash James4.004/05/16

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 8

4.1 Build Time Config 8

4.2 Configuration Files to be provided by Integration Project 8

4.3 Da Vinci Parameter Configuration Changes 8

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 NvM Blocks 11

8 Compiler Settings 12

8.1 Preprocessor MACRO 12

8.2 Optimization Settings 12

9 Appendix 13

Abbrevations And Acronyms

AbbreviationDescription

References

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

Sr. No.TitleVersion

Dependencies

SWCs

ModuleRequired Feature

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

SetMcuDiagcIdnData – Non-Rte Server Interface (called as needed)

GetMcuDiagcIdnData – Non-Rte Server Interface (called as needed)

SysErrIrq/Patched_SysErrIrq – Interrupt Handler Routine (triggered by Interrupt)

FpuErrIrq/Patched_FpuErrIrq – Interrupt Handler Routine (triggered by Interrupt)

AlgnErrIrq – Interrupt Handler Routine (triggered by Interrupt)

ResdOperIrq – Interrupt Handler Routine (triggered by Interrupt)

ExcpnHndlgInit1 – Non-RTE initialization function (called during startup before RTE is initialized)

FeNmiPeg – Callout function for interrupt response handling (to be called by FENMI Interrupt handler)

FeNmiDmaTrf – Callout function for interrupt response handling (to be called by FENMI Interrupt handler)

FeNmiDmaRegAcsProtnErr – Callout function for interrupt response handling (to be called by FENMI Interrupt handler)

FeNmiEcmMstChkrCmp – Callout function for interrupt response handling (to be called by FENMI Interrupt handler)

FeNmiWdg – Callout function for interrupt response handling (to be called by FENMI Interrupt handler)

ProcUkwnExcpnErr – Callout function for OS error response handling (to be called by OS error handler)

ProcMpuExcpnErr – Callout function for OS error response handling (to be called by OS error handler)

ProcPrvlgdInstrExcpnErr – Callout function for OS error response handling (to be called by OS error handler)

ProcPrmntOsErr – Callout function for OS error response handling (to be called by OS error handler)

ProcNonCritOsErr – Callout function for OS error response handling (to be called by OS error handler)

ChkForStrtUpTest_Oper – (called as needed from both RTE and non-RTE context))

FeNmiClkMonr0RtLowrLimFlt – Callout function responding to Clock Monitor 0 Runtime Lower Limit Failure(to be called by FENMI Interrupt handler)

FeNmiClkMonr0RtUpprLimFlt – Callout function responding to Clock Monitor 0 Runtime Upper Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiClkMonr1RtLowrLimFlt – Callout function responding to Clock Monitor 1 Runtime Lower Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiClkMonr1RtUpprLimFlt – Callout function responding to Clock Monitor 1 Runtime Upper Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiClkMonr2RtLowrLimFlt – Callout function responding to Clock Monitor 2 Runtime Lower Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiClkMonr2RtUpprLimFlt – Callout function responding to Clock Monitor 2 Runtime Upper Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiClkMonr3RtLowrLimFlt – Callout function responding to Clock Monitor 3 Runtime Lower Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiClkMonr3RtUpprLimFlt – Callout function responding to Clock Monitor 3 Runtime Upper Limit Failure

(to be called by FENMI Interrupt handler)

FeNmiOperModErrSngChipInactv – Callout function responding to Single Chip Mode inactive in Single chip mode (to be called by FENMI Interrupt handler)

FeNmiOperModErrFlsProgmModStrtd – Callout function responding to Flash programming Mode active in Single chip mode (to be called by FENMI Interrupt handler)

FeNmiOperModErrTestModStrtd – Callout function responding to Test Mode active in Single chip mode (to be called by FENMI Interrupt handler)

Configuration REQUIREMeNTS

Build Time Config

ModulesNotes

Configuration Files to be provided by Integration Project

N/A

Da Vinci Parameter Configuration Changes

ParameterNotesSWC

DaVinci Interrupt Configuration Changes

ISR NameNotes
Patched_SysErrIrqThe ExcpnHndlg module implements an interrupt that needs a patch for a hardware problem that exists on the P1M hardware (see Renesas Technical Update TN-RH8-S001A/E). Nexteer has created the appropriate workaround that subsequently calls the normal interrupt handler code. Therefore, when configuring the SysErrIrq interrupt in the O/S the interrupt handler name should be configured to the Nexteer code with the workaround (“Patched_SysErrIrq”) instead of directly referencing the normal interrupt handler code.
Patched_FpuErrIrqThe ExcpnHndlg module implements an interrupt that needs a patch for a hardware problem that exists on the P1M hardware (see Renesas Technical Update TN-RH8-S001A/E). Nexteer has created the appropriate workaround that subsequently calls the normal interrupt handler code. Therefore, when configuring the FpuErrIrq interrupt in the O/S the interrupt handler name should be configured to the Nexteer code with the workaround (“Patched_FpuErrIrq”) instead of directly referencing the normal interrupt handler code.

Manual Configuration Changes

ConstantNotesSWC

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Required Global Data Outputs

Specific Include Path present

Yes

Runnable Scheduling

API usage and scheduling of BSW components expected to be captured at a project architectural level and is beyond the scope of this document. Third party documentation can be referenced as needed.

InitScheduling RequirementsTrigger
ExcpnHndlgInit1Pre-RTE initializatonOnce at init
ExcpnHndlgInit2After diagnostic manager is initialized and NTCs can be setRTE initialization
RunnableScheduling RequirementsTrigger
ExcpnHndlgPer12ms

.

Memory Map REQUIREMENTS

Mapping

Memory SectionContentsNotes

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

Usage

FeatureRAMROM

NvM Blocks

Compiler Settings

Preprocessor MACRO

Optimization Settings

Appendix

<This section is for appendix>

Last modified October 12, 2025: Initial commit (312cf32)