XcpIf_Integration_Manual

Integration Manual

For

XCP Interfrace (XcpIf)

VERSION: 1.00

DATE: 19-Jan-2018

Prepared By:

ESG Software,

Nexteer Automotive,

Saginaw, MI, USA

Document Change History

Note:

This version 1.00 was baselined without requirements or a design finalized.

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 Non RTE NvM Blocks 10

7.4 RTE 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

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

The following functions need to be defined as non-trusted.

• CopyCalPageReq_Oper

• SetCalPageReq_Oper

• Xcp_Event

The following function needs to be defined as trusted:

• XcpAppl_CalibrationWriteTrustd

Configuration REQUIREMeNTS

Build Time Config

Configuration Files to be provided by Integration Project

Da Vinci Parameter Configuration Changes

DaVinci Interrupt Configuration Changes

Manual Configuration Changes

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

None

Required Global Data Outputs

None

Specific Include Path present

Yes

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

*See DataDict.m

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

XCP Configuration

Below are the following options that need to be enabled for the component to properly work.

<< ADD XCP NOTES >>>

XCP Configuration

Based on the XCP settings for the DAQ lists, components descriptions (arxml), source files (.c), and m-files are created based on the configuration. These compoents will also need to be imported into the project.

Key items

• DAQ runnables should be placed in the lowest priority task for a given runnable rate. This should be called before the checkpoint. This will ensure a good sample and avoid lag for a given runnable rate.

• Multiple DAQs can be configured to run at different rates. Each DAQ list will have its own set of description, source, and m-files to be integrated.

Integration Compatibility with ES400A

If this component is used with ES400A version 2.0.0 or earlier will require a header file to be created to map constants that are defined in ES400A to the values used by ES104B. These values are different then where defined in ES104A. Below is a sample template that can be used:

File Name: CDD_XcpIf.h

File Contents:

Template Change History