1 - CM200C_DmaCfgAndUse_NexteerDmaRegsh

Nexteer Dma Regs
Field Reg NameDMA ChannelRegisterRegister Field nameField Length ( Bits)
DMASSDTFR99DTFR-32
DMASSDRQC99DTFRRQCDRQC1
DMASSTCC99DCSTCTCC1
DMASSDTE99DCENDTE1
DMASSDRQC1414DTFRRQCDRQC1
DMASSTCC1414DCSTCTCC1
DMASSDTE1414DCENDTE1
DMASSTC1515DCSTTC1
DMASSTCC1515DCSTCTCC1

2 - CM200C_DmaCfgAndUse_PeripheralCfg

DMAC Peripheral Register Configuration (base Address 0xFFFF 8000h)
DMA ChannelConfigurableOffsetNameUpdateDescriptionBit #Set/ClearComment
--0030hDM0CMVDynamicDMAC0 register access protection violation register31-0-protection violation register
--0034hDM1CMVDynamicDMAC1 register access protection violation register31-0-protection violation register
--003ChCMVCStaticRegister access protection violation clear register31-07UClear protection violation register
DMA00Do Not Configure this channel - Reserved for Future Use - MotAg0 Data Read : FromSPI Register (CSIH1) to Local RAM (Motor Control)
DMA01Adc0 Results Read : FromADC Register (ADCD0) to Local RAM (Motor Control)
DMA01No0100h + 4h *1DM01CMStaticDMAC1 Channel Master Setting6-41UChannel Master PEID Setting
3-23UChannel Master SPID setting
10UChannel Master UM setting: Supervisor Mode
0400h + 40h *1DSA1StaticDMAC1 Source Address31-0-Address of (RegInpADCD0DR00)
0404h + 40h *1DDA1StaticDMAC1 Destination Address31-0-[Address of (MotCtrlAdc0RawRes)]
0408h + 40h *1DTC1StaticDMAC1 transfer Count16-310Address Reload Count
0-153UTransfer Count
040Ch + 40h *1DTCT1StaticDMAC1 transfer control270DMA transfer when transfer errored
261UHardware DMA transfer request
18-200No Chain
16-170No Chain
150Disable - Transfer count match interrupt
141UEnable - Transfer Completion interrupt - Trigger Motor Control ISR
131UEnable - Continuous transfer
11-120Disable -Reload function 2
9-103UEnable - Reload function 1(SA, DA, TC reloaded)
7-80Increment -Destinable address count direction
5-60Increment - Source Address count direction
2-44UTransfer Data Size - 128 bit
0-11UBlock transfer 1 by transfer count
0410h + 40h *1DRSA1StaticDMAC1 Reload Source Address31-0-Address of (RegInpADCD0DR00)
0414h + 40h *1DRDA1StaticDMAC1 Reload Destination Address31-0-[Address of (MotCtrlAdc0RawRes)]
0418h + 40h *1DRTC1StaticDMAC1 Reload transfer Count16-310Reload Address reload count
0-153UTransfer Count
0430h + 40h *1DTFR1StaticDMAC1 DTFR Setting1-758UHardware DMA transfer source = INTADCD0I3
01UEnable - Hardware DMA transfer source
0414h + 40h *1DCEN1StaticDMAC1 Channel operation enable setting01UEnable - Channel Operation
DMA02Do Not Configure this channel -Reserved for Future Use - MotAg1 Data Read : FromSPI Register (CSIH3) to Local RAM (Motor Control)
DMA03TSG Update Group 0 : FromLocal RAM (Motor Control) to TSG3 (TSG31)
DMA04TSG Update Group 1 : FromLocal RAM (Motor Control) to TSG3 (TSG31)
DMA05Do not Configure this channel - Reserved for Future Use
DMA06SCI Rx Buffer Data Read- From SCI Rx to Local RAM
DMA07SCI Tx Buffer Data Read- From Local RAM to SCI Tx
DMA10Do not Configure this channel - Reserved for Future Use
DMA112mSec to MotCtrl : FromLocal RAM (Motor Control) to Local RAM
DMA12Do Not Configure this channel - Reserved for Future Use - MotAg1 Spi Start : FromLocal RAM (Motor Control) to SPI Register (CSIH3)
DMA13Do Not Configure this channel - Reserved for Future Use -MotAg1 Reset Read Pointer: From Local RAM (Motor Control) to SPI Register (CSIH3)
DMA14Do Not Configure this channel - Reserved for Future Use - MotAg0 Spi Start : FromLocal RAM (Motor Control) to SPI Register (CSIH1)
DMA15Do Not Configure this channel - Reserved for Future Use - MotAg0 Reset Read Pointer: From Local RAM (Motor Control) to SPI Register (CSIH1)
DMA16Adc1 Results : FromADC Register (ADCD1) to Local RAM (Motor Control)
DMA16No0120h + 4h *6DM16CMStaticDMAC16 Channel Master Setting6-41UChannel Master PEID Setting
3-23UChannel Master SPID setting
11UChannel Master UM setting
0400h + 40h *14DSA14StaticDMAC14 Source Address31-0-Address of (RegInpADCD1DR00)
0404h + 40h *14DDA14StaticDMAC14 Destination Address31-0-Address of (MotCtrlAdc1RawRes)
0408h + 40h *14DTC14StaticDMAC14 transfer Count160Address Reload Count
03UTransfer Count
040Ch + 40h *14DTCT14StaticDMAC14 transfer control270DMA transfer when transfer errored
261UHardware Request
18-207UChain DMAC 1 Channel 7
16-171UChain at last transfer
150Disable - Transfer count match interrupt
140Disable - Transfer Completion interrupt
130Disable - Continuous transfer
11-120Disable -Reload function 2
9-103UEnable - Reload function 1(SA, DA, TC reloaded)
7-80Increment -Destinable address count direction
5-60Increment - Source Address count direction
2-44UTransfer Data Size - 128 bit
0-11UBlock transfer 1 by transfer count
0410h + 40h *14DRSA14StaticDMAC14 Reload Source Address31-0-Address of (RegInpADCD1DR00)
0414h + 40h *14DRDA14StaticDMAC14 Reload Destination Address31-0-Address of (MotCtrlAdc1RawRes)
0418h + 40h *14DRTC14StaticDMAC14 Reload transfer Count16-310Reload Address reload count
0-153UTransfer Count
0430h + 40h *14DTFR14StaticDMAC14 DTFR Setting1-761UHardware DMA transfer source = INTADCD1I1
01UEnable - Hardware DMA transfer source
0414h + 40h *14DCEN14StaticDMAC14 Channel operation enable setting01UEnable - Channel Operation
DMA17MotCtrl to 2mSec : FromLocal RAM (Motor Control) to Local RAM (2ms)









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





Note 2:
RSENTn, where n = 0




3 - CM200C_DmaCfgAndUse_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.05







Product NameElectric Power SteeringElectrical Arch.4Review ScopeDefect TypeNumbers




YesClosedFR
Function NameCM200C Dma Configuration And UseRevision1.1.0EA4#8876
- Fault Injection
Requirement0




NoRejectedFDD
AuthorKeyur Patel

Interface0




NAOpenModel


EffortDesign0






FMEA


Review Effort(Hrs.)1.00Standards2






*.m File


Corr+Verf effort(Hrs.)0.00Documentation0






Cal Process


Total Effort (Hrs.)1.00Others0













Total2







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.NoNo

Dma config and use has Motor control Manager inputs and register, which never brought in available nexteer signal nameClosed







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

Dma config and use has Motor control Manager inputs and register, which never brought in available nexteer signal nameClosed







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

It has been uploaded to synergy. This function should be same asCM200A, with removing some functionalityClosed







1.5Confirm Electrical Systems interface map is updated to reflect the FDP (signal IO)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.1Have functions depending upon system state been reviewed for need to be executed at the 2ms rate to avoid system lag issues?YesYes











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











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

there is no requirement associate with this design modelClosed







3.4Has the requirements traceability report been verified to only contain ONLY requirements from the FR.NANAwhen ever requirement available need to revisit this
there is no requirement associate with this design modelClosed







3.5Confirm that all PIM that does NOT have an initialization value of zero is initialized in an INIT function.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.1VerifyDD report error*.m File
Model is not runnable and software doesn't need model runnable, because they will hand code this CDD componentStandardsThe design has configurable structure which is not recognized by the tool, so considering deadline & reviewer comment, didn't run CreateDD & VerifyDD tool. M file has been created based on previous versionClosed







4.2Model advisor report not runModel
Model is not runnable, so no model advisor reportStandardsIntent of this model to show function. There is no calculation, All the function try to access register data to & from, so model is not runnableClosed







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 Patel12/9/2016YesYes










Peer Reviewer*AvinashYes










EPDT Engineer












ES Engineer












Software Lead












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