This is the multi-page printable view of this section. Click here to print.
Component Implementation
1 - requirements
FDD | ID | Source | Function | Line(s) | Status | Comment |
---|---|---|---|---|---|---|
.SwFileName | .SwFuncName | .SwLines | .SwStatus | .SwComment | ||
SF005A | 42 | StOutpCtrl.c | StOutpCtrlPer1 | 211 | I | |
SF005A | 50 | StOutpCtrl.c | StOutpCtrlPer1 | 255-269 | I | |
SF005A | 60 | StOutpCtrl.c | StOutpCtrlPer1 | 311-331 | I | |
SF005A | 61 | StOutpCtrl.c | RateSource | 375-405 | I | |
SF005A | 67 | StOutpCtrl.c | StOutpCtrlPer1 | 298 | I | |
SF005A | 68 | StOutpCtrl.c | StOutpCtrlPer1 | 275 | I | |
SF005A | 69 | StOutpCtrl.c | StOutpCtrlPer1 | 286 | I | |
SF005A | 27 | StOutpCtrl.c | StOutpCtrlPer1 | 203 | I | |
SF005A | 44 | StOutpCtrl.c | StOutpCtrlPer1 | 202 | I | |
SF005A | 45 | StOutpCtrl.c | StOutpCtrlPer1 | 338 | I | |
SF005A | 28 | StOutpCtrl.c | StOutpCtrlPer1 | 336 | I | |
SF005A | 43 | StOutpCtrl.c | StOutpCtrlPer1 | 208 | I | |
SF005A | 40 | StOutpCtrl.c | StOutpCtrlPer1 | 210 | I | |
SF005A | 41 | StOutpCtrl.c | StOutpCtrlPer1 | 207 | I | |
SF005A | 39 | StOutpCtrl.c | StOutpCtrlPer1 | 206 | I | |
SF005A | 38 | StOutpCtrl.c | StOutpCtrlPer1 | 209 | I | |
SF005A | 58 | StOutpCtrl.c | StOutpCtrlPer1 | 297-306 | I | |
SF005A | 55 | StOutpCtrl.c | RateSource | 374-404 | I | |
SF005A | 54 | StOutpCtrl.c | RateSource | 373-403 | I | |
SF005A | 57 | StOutpCtrl.c | StOutpCtrlPer1 | 281,296-305 | I | |
SF005A | 51 | StOutpCtrl.c | StOutpCtrlPer1 | 256-270 | I | |
SF005A | 36 | StOutpCtrl.c | StOutpCtrlPer1 | 204 | I | |
SF005A | 53 | StOutpCtrl.c | RateLimit | 425-440 | I | |
SF005A | 52 | StOutpCtrl.c | StOutpCtrlPer1 | 220-235 | I | |
SF005A | 37 | StOutpCtrl.c | StOutpCtrlPer1 | 205 | I |
2 - StOutpCtrl Review
Overview
Summary SheetSynergy Project
Davinci Files
Source Code
MDD
PolySpace
Sheet 1: Summary Sheet

Sheet 2: Synergy Project
Sheet 3: Davinci Files
Sheet 4: Source Code
Rev 1.2 | 8-Jun-15 | |||||||||||||||||||||||
Peer Review Meeting Log (Source Code Review) | ||||||||||||||||||||||||
Source File Name: | StOutpCtrl.c | Source File Revision: | 3 | |||||||||||||||||||||
Header File Name: | N/A | Header File Revision: | ||||||||||||||||||||||
MDD Name: | StOutpCtrl_MDD.docx | Revision: | 2 | |||||||||||||||||||||
FDD/SCIR/DSR/FDR/CM Name: | SF005A_StOutpCtrl_Design | Revision: | 1.3.0 | |||||||||||||||||||||
Quality Check Items: | ||||||||||||||||||||||||
Rationale is required for all answers of No | ||||||||||||||||||||||||
Working EA4 Software Naming Convention followed: | ||||||||||||||||||||||||
for variable names | Yes | Comments: | ||||||||||||||||||||||
for constant names | N/A | Comments: | ||||||||||||||||||||||
for function names | N/A | Comments: | ||||||||||||||||||||||
for other names (component, memory | N/A | Comments: | ||||||||||||||||||||||
mapping handles, typedefs, etc.) | ||||||||||||||||||||||||
All paths assign a value to outputs, ensuring | N/A | Comments: | ||||||||||||||||||||||
all outputs are initialized prior to being written | ||||||||||||||||||||||||
Requirements Tracability tags in code match the requirements tracability in the FDD | Comments: | |||||||||||||||||||||||
requirements tracability in the FDD | need to be done | |||||||||||||||||||||||
All variables are declared at the function level. | N/A | Comments: | ||||||||||||||||||||||
Synergy version matches change history | Yes | Comments: | ||||||||||||||||||||||
and Version Control version in file comment block | ||||||||||||||||||||||||
Change log contains detailed description of changes | Yes | Comments: | ||||||||||||||||||||||
and Work CR number | ||||||||||||||||||||||||
Code accurately implements FDD (Document or Model) | Yes | Comments: | ||||||||||||||||||||||
Verified no Compiler Errors or Warnings | Yes | Comments: | ||||||||||||||||||||||
Component.h is included | N/A | Comments: | ||||||||||||||||||||||
All other includes are actually needed. (System includes | N/A | Comments: | ||||||||||||||||||||||
only allowed in Nexteer library components) | ||||||||||||||||||||||||
Software Design and Coding Standards followed: | Version: 2.1 | |||||||||||||||||||||||
Code comments are clear, correct, and adequate | N/A | Comments: | ||||||||||||||||||||||
and have been updated for the change: [N40] and | ||||||||||||||||||||||||
all other rules in the same section as rule [N40], | ||||||||||||||||||||||||
plus [N75], [N12], [N23], [N33], [N37], [N38], | ||||||||||||||||||||||||
[N48], [N54], [N77], [N79], [N72] | ||||||||||||||||||||||||
Source file (.c and .h) comment blocks are per | N/A | Comments: | ||||||||||||||||||||||
standards and contain correct information: [N41], [N42] | ||||||||||||||||||||||||
Function comment blocks are per standards and | N/A | Comments: | ||||||||||||||||||||||
contain correct information: [N43] | ||||||||||||||||||||||||
Code formatting (indentation, placement of | N/A | Comments: | ||||||||||||||||||||||
braces, etc.) is per standards: [N5], [N55], [N56], | ||||||||||||||||||||||||
[N57], [N58], [N59] | ||||||||||||||||||||||||
Embedded constants used per standards; no | N/A | Comments: | ||||||||||||||||||||||
"magic numbers": [N12] | ||||||||||||||||||||||||
Memory mapping for non-RTE code | N/A | Comments: | ||||||||||||||||||||||
is per standard | ||||||||||||||||||||||||
All execution-order-dependent code can be | N/A | Comments: | ||||||||||||||||||||||
recognized by the compiler: [N80] | ||||||||||||||||||||||||
All loops have termination conditions that ensure | N/A | Comments: | ||||||||||||||||||||||
finite loop iterations: [N63] | ||||||||||||||||||||||||
All divides protect against divide by zero | N/A | Comments: | ||||||||||||||||||||||
if needed: [N65] | ||||||||||||||||||||||||
All integer division and modulus operations | N/A | Comments: | ||||||||||||||||||||||
handle negative numbers correctly: [N76] | ||||||||||||||||||||||||
All typecasting and fixed point arithmetic, | N/A | Comments: | ||||||||||||||||||||||
including all use of fixed point macros and | ||||||||||||||||||||||||
timer functions, is correct and has no possibility | ||||||||||||||||||||||||
of unintended overflow or underflow: [N66] | ||||||||||||||||||||||||
All float-to-unsiged conversions ensure the. | N/A | Comments: | ||||||||||||||||||||||
float value is non-negative: [N67] | ||||||||||||||||||||||||
All conversions between signed and unsigned | N/A | Comments: | ||||||||||||||||||||||
types handle msb==1 as intended: [N78] | ||||||||||||||||||||||||
All pointer dereferencing protects against | N/A | Comments: | ||||||||||||||||||||||
null pointer if needed: [N70] | ||||||||||||||||||||||||
Component outputs are limited to the legal range | N/A | Comments: | ||||||||||||||||||||||
defined in the FDD DataDict.m file : [N53] | ||||||||||||||||||||||||
All code is mapped with FDD (all FDD | N/A | Comments: | ||||||||||||||||||||||
subfunctions and/or model blocks identified | ||||||||||||||||||||||||
with code comments; all code corresponds to | ||||||||||||||||||||||||
some FDD subfunction and/or model block): [N40] | ||||||||||||||||||||||||
Review did not identify violations of other | Yes | Comments: | ||||||||||||||||||||||
coding standard rules | ||||||||||||||||||||||||
Anomaly or Design Work CR created | N/A | Comments: List Anomaly or CR numbers | ||||||||||||||||||||||
for any FDD corrections needed | ||||||||||||||||||||||||
General Notes / Comments: | ||||||||||||||||||||||||
Reviewed only he delta changes between 1.2.0 and 1.3.0 | ||||||||||||||||||||||||
Change Owner: | Basavaraja Ganeshappa | Review Date : | 03/30/16 | |||||||||||||||||||||
Lead Peer Reviewer: | Rijvi | Approved by Reviewer(s): | Yes | |||||||||||||||||||||
Other Reviewer(s): | ||||||||||||||||||||||||
Sheet 5: MDD
Sheet 6: PolySpace
3 - StOutpCtrl_IntegrationManual
Integration Manual
For
StOutpCtrl
VERSION: 1.0
DATE: 02-June-2015
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 | Akilan Rathakrishnan | 1.0 | 02-June-2015 |
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 |
<ADD more to the table if applicable> | |
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 - <FDD SF005A_StOutpCtrl_Design> | Refer Synergy subproject version |
Dependencies
SWCs
Module | Required Feature |
None | N/A |
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
< Global function (except the ones that are defined in RTE modules) that is defined in this component but used by other function
Configuration REQUIREMeNTS
Build Time Config
Modules | Notes | |
None |
Configuration Files to be provided by Integration Project
None
Da Vinci Parameter Configuration Changes
Parameter | Notes | SWC |
N/A |
DaVinci Interrupt Configuration Changes
ISR Name | VIM # | Priority Dependency | Notes |
N/A |
Manual Configuration Changes
Constant | Notes | SWC |
N/A |
Integration DATAFLOW REQUIREMENTS
Required Global Data Inputs
Refer SF005A_StOutpCtrl_DataDict.m file
Required Global Data Outputs
Refer SF005A_StOutpCtrl_DataDict.m file
Specific Include Path present
No
Runnable Scheduling
This section specifies the required runnable scheduling.
Init | Scheduling Requirements | Trigger |
StOutpCtrlInit1 | None | RTE Init |
Runnable | Scheduling Requirements | Trigger |
StOutpCtrlPer1 | None | RTE 2ms Task |
.
Memory Map REQUIREMENTS
Mapping
Memory Section | Contents | Notes |
None | ||
* Each …START_SEC… constant is terminated by a …STOP_SEC… constant as specified in the AUTOSAR Memory Mapping requirements.
Usage
Feature | RAM | ROM |
None |
Table 1: ARM Cortex R4 Memory Usage
Non RTE NvM Blocks
Block Name |
None |
Note : Size of the NVM block if configured in developer
RTE NvM Blocks
Block Name |
None |
Note : Size of the NVM block if configured in developer
Compiler Settings
Preprocessor MACRO
None
Optimization Settings
None
Appendix
<This section is for appendix>
4 - StOutpCtrl_MDD
Module Design Document
For
StOutpCtrl
VERSION: 2.
DATE: 29-Mar-2016
Prepared By:
Akilan Rathakrishnan
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 | Akilan Rathakrishnan | 1.0 | 02-June-2015 |
2 | Implementation of input name change | Basavaraja Ganeshappa | 2.0 | 30-June-2016 |
Table of Contents
3 StOutpCtrl - High-Level Description 7
4 Design details of software module 8
4.1 Graphical representation of StOutpCtrl 8
5.1 User defined typedef definition/declaration 9
5.2 Variable definition for enumerated types 9
6.1 Program(fixed) Constants 10
6.1.2 Module specific Lookup Tables Constants 10
7 Software Module Implementation 11
7.1.1 Initialization Functions 11
7.1.1.1 INIT: StOutpCtrlInit1 11
7.1.1.3 Store Module Inputs to Local copies 11
7.1.1.4 (Processing of function)……… 11
7.1.1.5 Store Local copy of outputs into Module Outputs 11
7.1.2.1 Per: StOutpCtrlPer1 11
7.1.2.3 Store Module Inputs to Local copies 11
7.1.2.4 (Processing of function)……… 11
7.1.2.5 Store Local copy of outputs into Module Outputs 11
7.3 Serial Communication Functions 11
7.4 Local Function/Macro Definitions 12
7.4.1 Local Function #1: RateLimit 12
7.4.2 Local Function #1: RateSource 12
7.5 GLObAL Function/Macro Definitions 12
8 Known Limitations With Design 14
Abbrevations And Acronyms
Abbreviation | Description |
DFD | Design functional diagram |
MDD | Module design Document |
<ADD more to the table if applicable> | |
References
This section lists the title & version of all the documents that are referred for development of this document
Sr. No. | Title | Version |
<1> | <MDD Guidelines> | Process 4.02.01 |
<2> | <Software Naming Conventions> | Process 4.02.01 |
<3> | <Coding standards> | Process 4.02.01 |
<4> | <FDD SF005A_StOutpCtrl_Design> | See Synergy Subproject version |
<Add if more available> |
StOutpCtrl - High-Level Description
Refer FDD
Design details of software module
Graphical representation of StOutpCtrl
Data Flow Diagram
N/A
Module level DFD
N/A
Sub-Module level DFD
N/A
COMPONENT FLOW DIAGRAM
N/A
Variable Data Dictionary
User defined typedef definition/declaration
<This section documents any user types uniquely used for the module.>
Typedef Name | Element Name | User Defined Type | Legal Range (min) | Legal Range (max) |
N/A | ||||
Variable definition for enumerated types
Enum Name | Element Name | Value |
N/A |
Constant Data Dictionary
Program(fixed) Constants
Embedded Constants
< All program specific constants will be defined in detail >
Local
Constant Name | Resolution | Units | Value |
N/A |
Global
<This section lists the global constants used by the module. For details on global constants, refer to the Data Dictionary for the application>
Constant Name |
N/A |
Module specific Lookup Tables Constants
<(This is for lookup tables (arrays) with fixed values, same name as other tables)>
Constant Name | Resolution | Value | Software Segment |
<Refer Constant name qualified in [2]> | <Refer MDD guidelines [1]> | <Refer MDD guidelines [1]> | <Refer MDD guidelines [1]> |
Software Module Implementation
Sub-Module Functions
None
Initialization Functions
INIT: StOutpCtrlInit1
Design Rationale
None
Store Module Inputs to Local copies
Refer to FDD
(Processing of function)………
Refer to FDD
Store Local copy of outputs into Module Outputs
Refer to FDD
PERIODIC FUNCTIONS
(Note: For multiple periodic functions, insert new headers at the “Header 2” level – subset of “7.1.2 Periodic Functions” and follow the same sub-section design shown below). If none required, place the text “None”)>
Per: StOutpCtrlPer1
Design Rationale
None
Store Module Inputs to Local copies
Refer to FDD
(Processing of function)………
Refer to FDD
Store Local copy of outputs into Module Outputs
Refer to FDD
Interrupt Functions
None
Serial Communication Functions
None
Local Function/Macro Definitions
<If these are numerous and defined in a separate source file then reference the source file only.>
Local Function #1: RateLimit
Function Name | RateLimit | Type | Min | Max |
Arguments Passed | SysOperRampRate_UlspS_T_f32 | float32 | 0.1 | 500.0 |
LoaRateLim_UlspS_T_f32 | float32 | 0.1 | 500.0 | |
VehStrtStopRampRate_UlspS_T_f32 | float32 | 0.1 | 500.0 | |
Return Value | SelRampRate_UlspS_T_f32 | float32 | 0.1 | 500.0 |
Description
Implements "Rate Limit" model block in FDD -- selects ramp rate from input rate limits.
Design Rationale
FDD does not show a default case on the switch/case block in this function because none is required – all possible values of the switch variable (which is internal to this component) are covered by the cases shown. However a default clause is required by MISRA Rule 15.3. Therefore the default label was placed with the final case label in the code; this is functionally equivalent to the FDD and satisfies the MISRA rule.
Local Function #1: RateSource
Function Name | RateSource | Type | Min | Max |
Arguments Passed | SysOperMotTqCmdSca_Uls_T_f32 | float32 | 0.0 | 1.0 |
LoaSca_Uls_T_f32 | float32 | 0.0 | 1.0 | |
VehStrtStopMotTqCmdSca_Uls_T_f32 | float32 | 0.0 | 1.0 | |
SelectedState_Cnt_T_u08 | uint8 | 1 | 3 | |
Return Value | SelectedTqCmdSca_Uls_T_f32 | float32 | 0.0 | 1.0 |
Description
Implements "Rate Source" model block in FDD -- selects scale factor from input rate scales.
Design Rationale
FDD does not show a default case on the switch/case block in this function because none is required – all possible values of the switch variable (which is internal to this component) are covered by the cases shown. However a default clause is required by MISRA Rule 15.3. Therefore the default label was placed with the final case label in the code; this is functionally equivalent to the FDD and satisfies the MISRA rule.
GLObAL Function/Macro Definitions
GLObAL Function #1
Function Name | (Exact name used) | Type | Min | Max |
Arguments Passed | None | <Refer MDD guidelines[1]> | <Refer MDD guidelines[1]> | <Refer MDD guidelines[1]> |
Return Value | N/A |
Description
N/A
TRANSIENT FUNCTIONS
None
Known Limitations With Design
None
UNIT TEST CONSIDERATION
None
Appendix
None