Cd_uDiag_Integration_Manual

1 Dependencies 2

1.1 SWCs 2

1.2 Functions to be provided to Integration Project 2

2 Configuration 3

2.1 Build Time Config 3

2.2 Configuration Files to be provided by Integration Project 3

2.2.1 Da Vinci Parameter Configuration Changes 4

2.2.2 DaVinci Interrupt Configuration Changes 5

2.2.3 Manual Configuration Changes 5

3 Integration 5

3.1 Required Global Data Inputs 5

3.2 Optional Global Data Inputs 5

3.3 Specific Include Path present 5

4 Runnable Scheduling 5

5 Memory Mapping 7

5.1 Mapping 7

5.2 Usage 7

5.3 NvM Blocks 7

6 Compiler Settings 7

6.1 Preprocessor MACRO 7

6.2 Optimization Settings 7

7 Revision Control Log 8

Dependencies

NOTE – the TMS570_uDiag component includes both uDiag and FlsTst functionality. For complete integration information on the TMS570_uDiag component, also see the FlsTst integration manual (in the TMS570_uDiag\doc folder).

SWCs

NOTES:

*When uDiagEnableFPUDiag is set to STD_OFF, the floating point exception diagnostic is disabled and EnableVFPInterrupt() is optional.

**_fiqhandler needed only if configuring Mcu_FpuIrq as an interrupt (see section 2.2.2).

*** EnableESMLInterrupt() is now called from a function in the TMS570_uDiag component, as of component version FDD32B_TMS570_uDiag_000.23. When using component version FDD32B_TMS570_uDiag_000.23 or later, any other call(s) to the EnableESMLInterrupt() function, e.g. in EcuStartup, must be removed. This fixes anomaly 6133.

Functions to be provided to Integration Project

< Global function (except the ones that are defined in RTE modules) that is defined in this component but used by other function>

FUNC(void, CD_UDIAG_APPL_CODE) uDiagFPU_Init1(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagFPU_Init2(void);

UDIAG_COMPILER_ISR void Mcu_FpuIrq(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagCCRM_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagClockMonitor_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagECC_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagESM_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagIOMM_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagParity_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagStaticRegs_Init(void);

FUNC(void, CD_UDIAG_APPL_CODE) uDiagVIM_Init(void);

Configuration

Build Time Config

Configuration Files to be provided by Integration Project

uDiag_Cfg.c generated from uDiag_Cfg.c.tt

uDiag_Cfg.h generated from uDiag_Cfg.h.tt

Da Vinci Parameter Configuration Changes

*The uDiagGladiatorCompatible parameter selects ESM Group 1 Channel 7 (as used on Gladiator) vs Group 1 Channel 34 (as used on Champion) for NHET2 Parity Error. On programs where code compatibility is required, the Gladiator ESM configuration must be used, because the Champion configuration enables an interrupt that is Reserved for Gladiator. NOTE that on Champion parts running code configured as Gladiator-compatible, an NHET2 RAM Parity Error will trigger only a Critical Registers Verification Fault , with no NHET2 RAM Fault diagnostic.

DaVinci Interrupt Configuration Changes

Manual Configuration Changes

Integration

Required Global Data Inputs

<Mention any global variable that this component requires for other components>

ResetCause_Cnt_Enum

Optional Global Data Inputs

<Mention any global variable that this component requires for other components>

Specific Include Path present

<Yes>

Runnable Scheduling

This section specifies the required runnable scheduling.

*NOTE: When uDiagEnableFPUDiag is set to STD_OFF, the floating point exception diagnostic is disabled and the calls to uDiagFPU_Init1() and uDiagFPU_Init2() are optional.

Memory Mapping

Mapping

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

Usage

NvM Blocks

Note : Size of the NVM block if configured in developer

Compiler Settings

Preprocessor MACRO

<Define all the preprocessor Macros needed and conditions when needed>.

Optimization Settings

Revision Control Log