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

Return to the regular view of this page.

Component Design

Component Design

Module Detailled Design

Component Documentation

1 - CM670A_HwAg1Meas_RSENTPeripheralCfg


Overview

Configuration
Sheet1
Sheet2


Sheet 1: Configuration

RSENT Peripheral Register Configuration
OffsetNameUpdateDescriptionBit #Set/ClearComment
0000HRSENTnTSPCStaticRSENT timestamp register160Master Mode
14-80Tick Multiplier = 1
6-079UTick Prescaler value = 80
0010HRSENTnCCStaticRSENT communication configuration register121SPC Pulse Active low
111Frame Check Against Previous Calibration Pulse
101Slow Channel CRC Check disable
90Fast Channel CRC Check Enable
7-60No Serial Message Extraction
50Puase Pulse for Variable Message Length
40Puase Pulse Absent
3-13U4 data nibble
01SPC mode enable
0014HRSENTnBRPStaticRSENT baud rate prescaler register27-240Tick Time Decimal Fraction = 0.0 us
22-160Time Tick Integer 1us
14-84USample Clock Division Value: 5 (80/5=16)
00Sample Clock Multiplication Value: 1
0018HRSENTnIDEStaticRSENT interrupt/DMA enable register100Slow Channel Encoding Error Interrupt Enable : Disabled
90Slow Channel Message Lost Interrupt Enable : Disabled
80Slow Channel CRC Error Interrupt Enable : Disabled
70No Response Error Interrupt Enable : Disabled
60Calibration Pulse Length Variation Error Interrupt Enable : Disabled
50Calibration Pulse Length Error Interrupt Enable : Disabled
40Fast Channel Nibble Count Error Interrupt Enable : Disabled
30Fast Channel Nibble Encoding Error Interrupt Enable : Disabled
20Fast Channel Message Lost Interrupt Enable : Disabled
10Fast Channel CRC Error Interrupt Enable : Disabled
00Fast Channel Receive Interrupt Enable : Disabled
001CHRSENTnMDCDynamicRSENT Mode Control Register2-0ZZZ0 - Reset
1U- Configuration
5U - Operation Active
0020HRSENTnSPCTStaticRSENT SPC transmission register6-0ZZZ17 Tick = 17 us







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:RSENTn, where n = 2





Sheet 2: Sheet1

HwTqMeas_Register_Configuration






Register NameAbbrevisionAddressBit PositionBit NameFunction to Set
RSENT timestamp registerRSENTnTSPCFFE0 5000+0000H







16TMS0: Master mode
















RSENT timestamp counterRSENTnTSCFFE0 5000+0004H


























RSENT communication configuration registerRSENTnCCFFE0 5000+0010H


























RSENT baud rate prescaler registerRSENTnBRPFFE0 5000+0014H


























RSENT interrupt/DMA enable registerRSENTnIDEFFE0 5000+0018H


























RSENT mode control registerRSENTnMDCFFE0 5000+001CH


RSENT SPC transmission registerRSENTnSPCTFFE0 5000+0020H


RSENT mode status registerRSENTnMSTFFE0 5000+0024H


RSENT communication status registerRSENTnCSFFE0 5000+0028H


RSENT communication status clear registerRSENTnCSCFFE0 5000+002CH


RSENT slow channel receive timestamp registerRSENTnSRTSFFE0 5000+0030H


RSENT slow channel receive data registerRSENTnSRXDFFE0 5000+0034H


RSENT calibration pulse length registerRSENTnCPLFFE0 5000+0038H


RSENT message length registerRSENTnMLFFE0 5000+003CH


RSENT fast channel receive timestamp registerRSENTnFRTSFFE0 5000+0040H


RSENT fast channel receive data registerRSENTnFRXDFFE0 5000+0044H


RSENT timestamp mode selection registerRSENTTSSELFFE0 5000+A000H



Sheet 3: Sheet2

RSENT timestamp registerRSENTnTSPCRSENTn_base>+0000H
RSENT timestamp counterRSENTnTSCRSENTn_base>+0004H
RSENT communication configuration registerRSENTnCCRSENTn_base>+0010H
RSENT baud rate prescaler registerRSENTnBRPRSENTn_base>+0014H
RSENT interrupt/DMA enable registerRSENTnIDERSENTn_base>+0018H
RSENT mode control registerRSENTnMDCRSENTn_base>+001CH
RSENT SPC transmission registerRSENTnSPCTRSENTn_base>+0020H
RSENT mode status registerRSENTnMSTRSENTn_base>+0024H
RSENT communication status registerRSENTnCSRSENTn_base>+0028H
RSENT communication status clear registerRSENTnCSCRSENTn_base>+002CH
RSENT slow channel receive timestamp registerRSENTnSRTSRSENTn_base>+0030H
RSENT slow channel receive data registerRSENTnSRXDRSENTn_base>+0034H
RSENT calibration pulse length registerRSENTnCPLRSENTn_base>+0038H
RSENT message length registerRSENTnMLRSENTn_base>+003CH
RSENT fast channel receive timestamp registerRSENTnFRTSRSENTn_base>+0040H
RSENT fast channel receive data registerRSENTnFRXDRSENTn_base>+0044H
RSENT timestamp mode selection registerRSENTTSSELRSENT0_base>+A000H

2 - CM670A_HwAg1Meas_FDD_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 OwnerConfirm that requirements are reviewed and approved PRIOR to the FDP peer review

Function OwnerStart with latest version of the template for any "first reviews" - Continue to use existing temmplate for re-reviews

Function OwnerProvide the functional design package (changed documents) to the invited attendees 1-2 working days in advance of review

Function OwnerNotify the assigned peer reviewer and make sure they are prepared to do their function in the meeting

Function OwnerIdentify necessary attendance and invite to meeting

Function OwnerComplete the "Author" column information for sections 1 through 3 prior to the review

Function OwnerComplete the attendance invitation list in section 5

Function OwnerFor Re-reviews only: Complete the column "remarks by author" to identify actions taken to address items found in earlier reviews.



DURING MEETING


Function OwnerPresent document changes to the review team

Peer ReviewerCapture attendance of the review

Peer ReviewerCapture 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 OwnerFollow up on all "open" items. Update "Summary of Resolution" to indicate what was done or decided.

Function OwnerSchedule follow up review OR review open items with peer reviewer and obtain agreement to close

Peer ReviewerClose 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.09







Product NameElectric Power SteeringElectrical Arch.4Review ScopeDefect TypeNumbers




YesClosedFR
Function NameCM670A Handwheel Angle 1 MeasurementVersion1.8.0Change Control #: WCR-EA4#6132
Description:
- Throughput Improvement
Requirement0




NoRejectedFDD
AuthorMuragesh Asundi

Interface0




NAOpenModel


EffortDesign0






FMEA


Review Effort(Hrs.)0.25Standards0






*.m File


Corr+Verf effort(Hrs.)
Documentation0






Cal Process


Total Effort (Hrs.)0.25Others0













Total0







Checklist No.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1Section 1: TECHNICAL CHECK













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











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











1.3Confirm 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.YesYes











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











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











1.6Confirm that Static Register evaluation has been completed and updated for any register data that is written to.NANA











1.7Have calibration default values been reviewed for correctness?NANA











2Section 2: Safety CHECKAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







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











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











3Section 3: Lessons LearnedAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







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











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











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











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











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











3.06Confirm if NVM is used, the NVM is defined in structuresNANA











3.07If the function uses NVM, confirm that the m file uses the SetBlockStatus to indicate a write at powerdownNANA











3.08Confirm NTCs are not set within an IRQ (not related to the typical periodic OS)YesYes











3.09Confirm NTCs are not set or read in a periodic rate faster than 2 ms (ex. Motor Control Loop)YesYes











3.10Constants check: Do all constants have the correct scope (local, global) and are they defined in the correct location (this FDD, ES/SF/AR999)?YesYes











3.11Confirm all calibrations are required (ie they cannot be constants)YesYes











4Section 4: Issues / Actions IdentifiedDocumentReferenceSummary of resolutionAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














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














5Section 5: APPROVALS













RoleFirst ReviewDateAttendanceApproval?










Function Owner*Keyur Patel6/10/2016YesYes










Peer Reviewer*TravisYes










EPDT Engineer












ES Engineer












Software Leadkrishna anneYes










Hardware Lead












Test Lead












Safety Lead












RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>











EPDT Engineer<Name - if invited>











ES Engineer<Name - if invited>











Software Lead<Name - if invited>











Hardware Lead<Name - if invited>











Test Lead<Name - if invited>











Safety Lead<Name - if invited>











RoleThird Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>











EPDT Engineer<Name - if invited>











ES Engineer<Name - if invited>











Software Lead<Name - if invited>











Hardware Lead<Name - if invited>











Test Lead<Name - if invited>











Safety Lead<Name - if invited>











RoleFourth Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>











EPDT Engineer<Name - if invited>











ES Engineer<Name - if invited>











Software Lead<Name - if invited>











Hardware Lead<Name - if invited>











Test Lead<Name - if invited>











Safety Lead<Name - if invited>











RoleAdd more if necessaryDateAttendanceApproval?










































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

RevChangeAuthor
01.00.05Added lesson learned #3.5MDK
01.00.06Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models.MDK
01.00.07Clarified 3.6 and 3.7
Added lessons learned for NTCs not being set in IRQs or periodics faster than 2ms/
MDK
01.00.08Added section 1.6 to look for critical static register analysisMDK
01.00.09Added two checks - default cals and are all cals really required to be a calibrationMDK