CmnMfgSrvIf_IntegrationManual

Integration Manual

For

CmnMfgSrvIf

VERSION: 1.0

DATE: 5-Jan-2018

Prepared By:

Jared Julien,

Nexteer Automotive,

Saginaw, MI, USA

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

Revision History

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

Many global functions are generated by this component during integration, however, none of them are prodided by static code within this component. See appendix for additional information.

Configuration REQUIREMeNTS

Build Time Config

Configuration Files to be provided by Integration Project

None

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

No

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

None

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

This component is primarily used to generate a configuration source file that provides all of it’s functionality. The purpose of this component is to bridge the gap between the AUTOSAR DCM and NM001A (common manufacturing services). To accomplish this, the component produces two¹ outputs when generation is invoked through Configurator by an integrator, a .c source file and an .arxml config file, both located in the generate folder of the integration project.

The .arxml file is titled CmnMfgSrvIf_DemCfg.arxml. The file contains the necessary DCM settings for Nexteer services only. The integrator must manually merge these settings with their DCM settings being sure to include any additional or changed services with CmnMfgSrvIf in the name while retaining all of their exisiting customer service configurations. The integrator should be especially careful with the removal section as Configurator will suggest “removal” of any setting that is not defined in the generated ARXML file but is present in the project. This includes customer services as well as general DCM settings. As a general rule of thumb it is safe to remove anything with CmnMfgSrvIf in the name.

The .c file requires nothing from the integrator. During the initial integration it must be added to the corresponding generate.gpj file for the project but once that is complete and on every subsequent update no action needs to be taken.

This component takes only a single input in the form of an ODX file containing a list of all Nexteer manufacturing services that are enabled for the program. This file, titled EnadMfgSrv.odx-d, is expected to be located in the typical location in the generate folder of the integration project. Because this component uses this file and the file is generated during the integration of NM001A of NM010x this component should be regenerated AFTER making changes to NM001A or NM010x.

A DataDict.m file is generated in addition to the source and ARXML files. This file is not needed by the integration project or integrator. It is generated to be provided to the software architecture team for use with creating a system architecture specific to the project.