GuardCfgAndDiagc Integration Manual
Integration Manual
For
GuardCfgAndDiagc
VERSION: 1
DATE: 02/16/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. | Description | Author | Version | Date |
| 1 | Initial version | Avinash James | 1 | 02/16/16 |
Table of Contents
3.2 Global Functions(Non RTE) to be provided to Integration Project 6
4 Configuration REQUIREMeNTS 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
Abbrevations And Acronyms
| Abbreviation | Description |
| DFD | Design functional diagram |
| MDD | Module design Document |
| FDD | Functional Design Document |
References
This section lists the title & version of all the documents that are referred for development of this document
| Sr. No. | Title | Version |
| 1 | FDD – CM107A GuardCfgAndDiagc | See Synergy subproject version |
| 2 | Software Naming Conventions | Process 04.02.00 |
| 3 | Software Coding Standards | Process 04.02.00 |
Dependencies
SWCs
| Module | Required Feature |
| AR202A MicroCtrlrSuprt | NxtrMcuSuprtLib functions and register definitions |
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
GuardCfgAndDiagcInit1 - Non-RTE function so that guard protection can be initialized and enabled before the RTE is started
IpgInin - To be configured as a trusted function because it needs to run in supervisor mode
GuardCfgAndDiagcInit3 - Non-RTE function so that guard startup test can be run before the RTE is started
Configuration REQUIREMeNTS
Build Time Config
| Modules | Notes | |
| None |
Configuration Files to be provided by Integration Project
Da Vinci Parameter Configuration Changes
| Parameter | Notes | SWC |
DaVinci Interrupt Configuration Changes
| ISR Name | VIM # | Priority Dependency | Notes |
Manual Configuration Changes
| Constant | Notes | SWC |
| None |
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.
| Init | Scheduling Requirements | |
| GuardCfgAndDiagcInit1 | Non-RTE Init, Called in Startup Sequence* | Function call in Startup Sequence |
| GuardCfgAndDiagcInit2 | RTE | Once At Init (RTE) |
| GuardCfgAndDiagcInit3 | Non-RTE Init, Called in Startup Sequence* | Function call in Startup Sequence |
*Refer CM100A for the start up sequence
| Runnable | Scheduling Requirements | Trigger |
.
Memory Map REQUIREMENTS
Mapping
| Memory Section | Contents | Notes |
| CDD_GuardCfgAndDiagc_START_SEC_CODE | ||
* Each …START_SEC… constant is terminated by a …STOP_SEC… constant as specified in the AUTOSAR Memory Mapping requirements.
Usage
| Feature | RAM | ROM |
Table 1: ARM Cortex R4 Memory Usage
NvM Blocks
Compiler Settings
Preprocessor MACRO
None
Optimization Settings
None
Appendix
None