This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Design

1: CM410B_SnsrMeasStrt_PeripheralCfg
2: CM410B_SnsrMeasStrt_FDD_Rev110_Checklist

Component Design

Module Detailled Design

CM410B_SnsrMeasStrt_PeripheralCfg.html

Component Documentation

CM410B_SnsrMeasStrt_FDD_Rev110_Checklist.html

1 - CM410B_SnsrMeasStrt_PeripheralCfg

Overview

Configuration
Sheet1
Sheet2

Sheet 1: Configuration

OSTM Peripheral Register Configuration
*Offset*	*Name*	*Update*	*Configure Order*	*Description*	*Bit #*	*Set/Clear*	*Comment*
00H	OSTM1CMP	Dynamic	-	OSTMn compare register	31-0	zzz	Interval Timer Mode : Count Down Start Value
04H	OSTM1CNT	Dynamic	-	OSTMn counter register	31-0	zzz	Interval Timer Mode : Timer Count Down Value
08H	OSTM1TO	Dynamic	-	OSTMn output register	0	0	Output Signal : Low Level
0CH	OSTM1TOE	Dynamic	-	OSTMn output enable register	0	0	Software Control Mode
10H	OSTM1TE	Dynamic	-	OSTMn counter enable status register	-	-	Status Bit : Disable the counter
14H	OSTM1TS	Dynamic	-	OSTMn counter start trigger register	0	0	Disable the Counter
18H	OSTM1TT	Dynamic	1	OSTMn counter stop trigger register	0	1	Stop the Counter
20H	OSTM1CTL	Static	3	OSTMn control register	1	0	Interval Timer Mode
20H	OSTM1CTL	Static	3	OSTMn control register	0	0	Interupt when counting start are disabled
FFDD6004H	IC0CKSEL1	Static	2	OSTM1 Clock Select Register	15-0	0	PCLK is selected as clock source

Note 1:	ZZZ= Dynamic change value, X = Don’t Care, 1=Set, 0=Clear, -=Loaded Data, unspecified register bits shall have safe default value
Note 2:	OSTMn, where n = 1

Sheet 2: Sheet1

HwTqMeas_Register_Configuration
Register Name	Abbrevision	Address			Bit Position	Bit Name	Function to Set
RSENT timestamp register	RSENTnTSPC	FFE0 5000	+	0000H
					16	TMS	0: Master mode


RSENT timestamp counter	RSENTnTSC	FFE0 5000	+	0004H



RSENT communication configuration register	RSENTnCC	FFE0 5000	+	0010H



RSENT baud rate prescaler register	RSENTnBRP	FFE0 5000	+	0014H



RSENT interrupt/DMA enable register	RSENTnIDE	FFE0 5000	+	0018H



RSENT mode control register	RSENTnMDC	FFE0 5000	+	001CH
RSENT SPC transmission register	RSENTnSPCT	FFE0 5000	+	0020H
RSENT mode status register	RSENTnMST	FFE0 5000	+	0024H
RSENT communication status register	RSENTnCS	FFE0 5000	+	0028H
RSENT communication status clear register	RSENTnCSC	FFE0 5000	+	002CH
RSENT slow channel receive timestamp register	RSENTnSRTS	FFE0 5000	+	0030H
RSENT slow channel receive data register	RSENTnSRXD	FFE0 5000	+	0034H
RSENT calibration pulse length register	RSENTnCPL	FFE0 5000	+	0038H
RSENT message length register	RSENTnML	FFE0 5000	+	003CH
RSENT fast channel receive timestamp register	RSENTnFRTS	FFE0 5000	+	0040H
RSENT fast channel receive data register	RSENTnFRXD	FFE0 5000	+	0044H
RSENT timestamp mode selection register	RSENTTSSEL	FFE0 5000	+	A000H

Sheet 3: Sheet2

RSENT timestamp register	RSENTnTSPC	RSENTn_base>	+	0000H
RSENT timestamp counter	RSENTnTSC	RSENTn_base>	+	0004H
RSENT communication configuration register	RSENTnCC	RSENTn_base>	+	0010H
RSENT baud rate prescaler register	RSENTnBRP	RSENTn_base>	+	0014H
RSENT interrupt/DMA enable register	RSENTnIDE	RSENTn_base>	+	0018H
RSENT mode control register	RSENTnMDC	RSENTn_base>	+	001CH
RSENT SPC transmission register	RSENTnSPCT	RSENTn_base>	+	0020H
RSENT mode status register	RSENTnMST	RSENTn_base>	+	0024H
RSENT communication status register	RSENTnCS	RSENTn_base>	+	0028H
RSENT communication status clear register	RSENTnCSC	RSENTn_base>	+	002CH
RSENT slow channel receive timestamp register	RSENTnSRTS	RSENTn_base>	+	0030H
RSENT slow channel receive data register	RSENTnSRXD	RSENTn_base>	+	0034H
RSENT calibration pulse length register	RSENTnCPL	RSENTn_base>	+	0038H
RSENT message length register	RSENTnML	RSENTn_base>	+	003CH
RSENT fast channel receive timestamp register	RSENTnFRTS	RSENTn_base>	+	0040H
RSENT fast channel receive data register	RSENTnFRXD	RSENTn_base>	+	0044H
RSENT timestamp mode selection register	RSENTTSSEL	RSENT0_base>	+	A000H

2 - CM410B_SnsrMeasStrt_FDD_Rev110_Checklist

Nexteer_Template_V1.0

Overview

Peer Review Instructions
Technical Review Checklist
Template Change Log

Sheet 1: Peer Review Instructions

Instructions for Functional Design Package Peer Review

PRE-MEETING
	Function Owner	Confirm that requirements are reviewed and approved PRIOR to the FDP peer review
	Function Owner	Start with latest version of the template for any "first reviews" - Continue to use existing temmplate for re-reviews
	Function Owner	Provide the functional design package (changed documents) to the invited attendees 1-2 working days in advance of review
	Function Owner	Notify the assigned peer reviewer and make sure they are prepared to do their function in the meeting
	Function Owner	Identify necessary attendance and invite to meeting
	Function Owner	Complete the "Author" column information for sections 1 through 3 prior to the review
	Function Owner	Complete the attendance invitation list in section 5
	Function Owner	For Re-reviews only: Complete the column "remarks by author" to identify actions taken to address items found in earlier reviews.

DURING MEETING
	Function Owner	Present document changes to the review team
	Peer Reviewer	Capture attendance of the review
	Peer Reviewer	Capture actions and issues in section 4. Identify issue summary, Document type, Reference (Requirement ID, section number, etc), Defect Type and indicate status as "OPEN"

POST MEETING
	Function Owner	Follow up on all "open" items. Update "Summary of Resolution" to indicate what was done or decided.
	Function Owner	Schedule follow up review OR review open items with peer reviewer and obtain agreement to close
	Peer Reviewer	Close change request in system and confirm all associated tasks are complete. Upload peer review checklist (this document) with any FDP updates

Sheet 2: Technical Review Checklist

Technical Review Checklist - Template Version 01.00.05

Product Name

Electric Power Steering

Electrical Arch.

Review Scope

Defect Type

Numbers

Yes

Closed

Function Name

CM410B Sensor Measurement Start

Revision

1.1.0

EA4#8515

Requirement

Rejected

FDD

Author

Keyur Patel

Interface

Open

Model

Effort

Design

FMEA

Review Effort(Hrs.)

1.00

Standards

*.m File

Corr+Verf effort(Hrs.)

0.00

Documentation

Cal Process

Total Effort (Hrs.)

1.00

Others

Total

Checklist No.

Description of Check

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. Author

Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. Reviewer

Author: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewer

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

Section 1: TECHNICAL CHECK

1.1

Confirm that all signal inputs into the FDP (Functional Design Package) are contained within and exactly named as the "Available_Nexteer_Signals.m" states.

Yes

1.2

Confirm any removed signal inputs from the design have been removed from the "Available_Nexteer_Signals.m" file.

1.3

Confirm all signals and parameters (outputs, calibrations, constants, non-volatile memory) used in the *.m file and the design conform to the AutoSAR naming convention documentation.

Yes

1.4

Confirm *.m file has been provided to the "Available_Signal_Names" Author.

Yes

1.5

Confirm Electrical Systems interface map is updated to reflect the FDP (signal IO)

Yes

Section 2: Safety CHECK

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. Author

Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. Reviewer

Author: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewer

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

2.1

Confirm that the functional DFMEA is up to date based on the design in the current package.

2.2

Confirm that Safety requirements (ASIL A - D) are referenced in the design documents.

Yes

Section 3: Lessons Learned

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. Author

Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. Reviewer

Author: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewer

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

3.1

Have functions depending upon system state been reviewed for need to be executed at the 2ms rate to avoid system lag issues?

Yes

Closed

3.2

Have all diagnostics (NTCs) been confirmed to show logic to invoke a diagnostic "PASS" for control of the status byte at the customer level.

3.3

Has the requirements traceability steps used the RMI steps as defined in the FDD authoring spec to generate the traceability report?

3.4

Has the requirements traceability report been verified to only contain ONLY requirements from the FR.

3.5

Confirm that all PIM that does NOT have an initialization value of zero is initialized in an INIT function.

Yes

Section 4: Issues / Actions Identified

Document

Reference

Summary of resolution

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

4.1

Model Doesn't execute

Model

Model don't need to be MIL modeled, because It touch CDD - Register & Interrupt, so considered during the review, not required to have run.

Design

Matlab has no clear way or I don't have guideline how to handle Interrupt trigger the server client

Closed

4.2

4.3

4.4

4.5

4.6

4.7

4.8

4.9

4.10

4.11

4.12

4.13

4.14

4.15

4.16

4.17

4.18

4.19

4.20

4.21

4.22

4.23

4.24

4.25

Section 5: APPROVALS

Role

First Review

Date

Attendance

Approval?

Function Owner*

Keyur Patel

11/22/2016

Yes

Peer Reviewer*

Samanth

Yes

EPDT Engineer

ES Engineer

Software Lead

Selva, Shruti

Yes

Hardware Lead

Test Lead

Safety Lead

Role

Second Review (if required)

Date

Attendance

Approval?

Function Owner*

Peer Reviewer*

<Name>

EPDT Engineer

ES Engineer

Software Lead

Hardware Lead

Test Lead

Safety Lead

Role

Third Review (if required)

Date

Attendance

Approval?

Function Owner*

Peer Reviewer*

<Name>

EPDT Engineer

ES Engineer

Software Lead

Hardware Lead

Test Lead

Safety Lead

Role

Fourth Review (if required)

Date

Attendance

Approval?

Function Owner*

Peer Reviewer*

<Name>

EPDT Engineer

ES Engineer

Software Lead

Hardware Lead

Test Lead

Safety Lead

Role

Add more if necessary

Date

Attendance

Approval?

P.S.:

Yes indicates adherence

No indicates non-adherence, reviewer shall provide suitable comments at the end of this document for each point.

NA indicates not applicable

Sheet 3: Template Change Log

Rev	Change	Author
01.00.05	Added lesson learned #3.5	MDK