1 - CM660A_HwTq1Meas_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
100Slow Channel CRC Check Enable
90Fast Channel CRC Check Enable
7-61UShort Serial Message Format
50Puase Pulse for Variable Message Length
40Puase Pulse Absent
3-12U3 data nibble
01SPC mode enable
0014HRSENTnBRPStaticRSENT baud rate prescaler register27-242UTick Time Decimal Fraction = 0.2 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-016U17 Tick => 1.22*17 = 20.74us







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





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 - CM660A_HwTq1Meas_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 NameCM660A Handwheel Torque 1 MeasurementVersion
Change Control #: 4928
Description:
Function block "HwTq1MeasTrigStrt" modifed to fix anomaly CR EA4#4799
Changes are highlighted in red foreground color
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*Muragesh Asundi3/24/2016YesYes










Peer Reviewer*Keyur PatelYes










EPDT Engineer












ES Engineer












Software LeadRijvi AhmedYes










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











































































3 - CM660A_HwTq1Meas_FuncReq

IDBaselined v1.1 and ReleasedIs Requirement?.ASIL.ReqCatReview DateReview ActionReview Action Status
CM660A_1PurposeFALSE




CM660A_4Intention of this document to capture requirements for Handwheel Torque 1 Measurement for EA4 onwards.FALSE




CM660A_2Interface RequirementsFALSE




CM660A_5DefinitionsFALSE




CM660A_6InputsFALSE




CM660A_9HwTq1Polarity: Count Input signal, -1 indicate reverse Polarity and 1 indicate positive polarity of Handwheel Torque Sensor 1.FALSE




CM660A_10HwTq1Phy : Physical input signal, Digital SENT message received from Sensor 1.FALSE




CM660A_7OutputsFALSE




CM660A_11HwTq1: Handwheel Torque Sensor 1 Output signal.FALSE




CM660A_12HwTq1Qlfr : Enumeration Output Signal, indicates : NO Result, NTC Pass and NTC Fail, from protocol evaluation of Hand Wheel Torque Sensor 1.FALSE




CM660A_13HwTq1RollgCntr: Count output signal, use as instantaneous indicator of fault evaluation pass test or not of hand wheel torque sensor 1.FALSE




CM660A_72RackLimrEotSig1Avl: Boolean output signal, 1 indicate RickLimrCwEotSig1 and RickLimrCcwEotSig1 signals are available and 0 indicates RickLimrCwEotSig1 and RickLimrCcwEotSig1 signals are not available.FALSE




CM660A_73RickLimrCwEotSig1: Rack Limiter Clockwise End of travel Signal 1 output signal.FALSE




CM660A_74RickLimrCcwEotSig1: Rack Limiter Counter Clockwise End of travel Signal 1 output signal.FALSE




CM660A_8Internally Defined TermsFALSE




CM660A_3RequirementsFALSE




CM660A_14Primary Functional RequirementsFALSE




CM660A_26The HwTq1Meas Function shall provide measured sensor signal output in Engineering Unit in range of ±10 HwNm with 0.00488 resolution.TRUEDDirect6/30/2015
Closed
CM660A_27The HwTq1Meas Function shall detect protocol error.TRUEDDirect6/30/2015
Closed
CM660A_28The HwTq1Meas Function shall provide mechanism to detect any Sensor self internal diagnostic.TRUEDDirect6/30/2015
Closed
CM660A_29The HwTq1Meas Function shall hold previous known good value in the event of error detected.TRUEDDirect6/30/2015
Closed
CM660A_30The HwTq1Meas Function shall provide qualified status of the protocol fault.TRUEDDirect6/30/2015
Closed
CM660A_31The HwTq1Meas Function shall provide instantaneous status of the protocol fault.TRUEDDirect6/30/2015
Closed
CM660A_32The HwTq1Meas Function shall provide mechanism for correction of Handwheel Torque Output based on sensor polarity.TRUEDDirect6/30/2015
Closed
CM660A_33The HwTq1Meas Function shall post Torque data no later than 200us (CBE) from the time torque data being sampled by the sensor (Historically 400us was allocated for total time estimation from the sample torque data to ePWM toggle output using same the sample torque data ).TRUEDDirect6/30/2015
Closed
CM660A_70The HwTq1Meas Function shall provide sensor scratchpad signals, Rack ClockWise End Of Travel and Rack Counter Clock Wise End Of Travel, output in engieering unit in the range of 0 to 800 HwDeg with 2 HwDeg of Resolution.TRUEDDirect8/20/2015
Closed
CM660A_71The HwTq1Meas Function shall provide Rack ClockWise End Of Travel positive and Rack Counter ClockWise End Of Travel signal negative output signals.TRUEDDerived8/20/2015
Closed
CM660A_75The HwTq1Meas Function shall provide available signal true, when Rack ClockWise End Of Travel and Rack Counter ClockWise End Of Travel valid signals available.TRUEDDirect8/20/2015
Closed
CM660A_15Hardware RequirementsFALSE




CM660A_34The HwTq1Meas Function shall provide power to the torque sensor within the range of 4.5V (Min) to 5.5V (Max).TRUEDDerived6/30/2015
Closed
CM660A_35The HwTq1Meas Function shall require a logic high signal to be higher than 3.0V in magnitude for the read Torque information as input.TRUEDDerived6/30/2015
Closed
CM660A_36The HwTq1Meas Function shall require a logic Low signal to be lower than 0.1V in magnitude for the Torque Sensor Trigger information as output.TRUEDDerived6/30/2015
Closed
CM660A_37The HwTq1Meas Function shall provide an open collector pull high design as an interface to the sensor input.TRUEDDerived6/30/2015
Closed
CM660A_16Software / Algorithm RequirementsFALSE




CM660A_17Special Execution RequirementsFALSE




CM660A_76The HwTq1Meas Function shall provide Rack Limiter End Of Travel output signals once at Ignition cycle.TRUEDDirect8/20/2015
Closed
CM660A_18Software Algorithm DecomopositionFALSE




CM660A_19Diagnostic RequirementsFALSE




CM660A_20Tq Sensor 1 Protocol Fault (0x075)FALSE




CM660A_21Required Debounce StrategyFALSE




CM660A_38The HwTq1Meas Function shall use the ISO based error accumulator strategy for NTC 0x075.TRUEDDerived6/30/2015
Closed
CM660A_22Requirements to Perform Diagnostic Test ConditionsFALSE




CM660A_39The HwTq1Meas Function shall activate NTC 0x075 in states defined while the operating system is available.TRUEDDerived6/30/2015
Closed
CM660A_23Test Condition Negative RequirementsFALSE




CM660A_40The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "Synchronization and calibration" Tick count is measured outside of 56 ticks ± 20%.TRUEDDerived6/30/2015
Closed
CM660A_41The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "Status and Communication" data falls outside the range of 12 <Tick counts <=27.TRUEDDerived6/30/2015
Closed
CM660A_42The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "Data 0" falls outside the range of 12 <Tick counts <=27.TRUEDDerived6/30/2015
Closed
CM660A_43The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "Data 1" falls outside the range of 12 <Tick counts <=27.TRUEDDerived6/30/2015
Closed
CM660A_44The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "Data 2" falls outside the range of 12 <Tick counts <=27.TRUEDDerived6/30/2015
Closed
CM660A_45The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "CRC" falls outside the range of 12 <Tick counts <=27.TRUEDDerived6/30/2015
Closed
CM660A_46The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame "CRC" field doesn't match with CRC calculated.TRUEDDerived6/30/2015
Closed
CM660A_47The HwTq1Meas Function test condition result shall indicate negative, when the Sensor misses a new message received (with coherent data in the SENT frame).TRUEDDerived6/30/2015
Closed
CM660A_48The HwTq1Meas Function test condition result shall indicate negative, when the Sensor SENT frame field "Status and Communication" data falls data >12 tick (means indicatation of Temporary or Critical sensor internal diagnostic error).TRUEDDerived6/30/2015
Closed
CM660A_24Test Condition Positive RequirementsFALSE




CM660A_49The HwTq1Meas Function shall provide a positive result to the test condition for NTC 0x075 when none of the negative result requirements are satisfied.TRUEDDerived6/30/2015
Closed
CM660A_59Tq Sensor 1 Mfg Fault (0x1E1)FALSE




CM660A_60Required Debounce StrategyFALSE




CM660A_61The HwTq1Meas Function shall use the Immediate fault strategy for NTC 0x1E1.TRUEQMDerived6/30/2015
Closed
CM660A_62Requirements to Perform Diagnostic Test ConditionsFALSE




CM660A_63The HwTq1Meas Function shall activate NTC 0x1E1 in states defined while the operating system is available.TRUEQMDerived6/30/2015
Closed
CM660A_64Test Condition Negative RequirementsFALSE




CM660A_65The HwTq1Meas Function test condition result shall indicate negative, when the handwheel Torque 1 offset trim service not performed.TRUEQMDerived6/30/2015
Closed
CM660A_66Test Condition Positive RequirementsFALSE




CM660A_67The HwTq1Meas Function shall provide a positive result to the test condition for NTC 0x1E1 when none of the negative result requirements are satisfied.TRUEQMDerived6/30/2015
Closed
CM660A_25Manufacturing RequirementsFALSE




CM660A_50The HwTq1Meas Function shall provide mechanism store HwTq1 Offset trim performed status in persistent storage.TRUEQMDirect6/30/2015
Closed
CM660A_51The HwTq1Meas Function shall store Auto offset trim to persistent storage.TRUEQMDirect6/30/2015
Closed
CM660A_52The HwTq1Meas Function shall provide mechanism report the value of HwTq1 Offset Trim stored in persistent storage, on request.TRUEQMDirect6/30/2015
Closed
CM660A_53The HwTq1Meas Function shall provide mechanism report the value of HwTq1 Offset Trim performed status stored in persistent storage, on request.TRUEQMDirect6/30/2015
Closed
CM660A_54The HwTq1Meas Function shall provide mechanism clear HwTq1 Offset Trim stored in persistent storage to zero, on request.TRUEQMDirect6/30/2015
Closed
CM660A_55The HwTq1Meas Function shall provide mechanism manual write HwTq1 Offset Trim stored in persistent storage, on request.TRUEQMDirect6/30/2015
Closed
CM660A_56The HwTq1Meas Function shall provide mechanism Auto Learn write HwTq1 Offset Trim stored in persistent storage, on request.TRUEQMDirect6/30/2015
Closed