feat(dmm): register description task for Data Movement Manager #11
Labels
No labels
Category
App
Category
Documentation
Category
Firmware
Category
Hardware
Category
Qms
PR_Size
L
PR_Size
M
PR_Size
S
PR_Size
XL
PR_Size
XS
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Very Low Priority
Size
Epic
Size
Feature
Size
Task
Status
Blocked
Status
Draft
Status
Needs-review
Team
Board
Team
Dev
Team
Management
Type
Bug
Type
Capa
Type
Improvement
Type
New-feature
Type
Regulatory
Type
Usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
opendutchsolutions.public/hal_awr6843#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Part of the CMSIS-compliant register description epic (#4): bring the DMM (Data Movement Manager) register block in line with the epic's shared-header and SVD-traceability goals. See #5 (ADCBUF) for the reference implementation of this pattern.
Scope
hal/registers/component/dmm.hincludes the shared CMSIS core/qualifier header (hal/registers/core_cr4f.h, from #5) instead of any local__I/__O/__IOredefinitionhal/registers/svd/AWR6843AOP_MSS.svdhal/registers/component/dmm.handhal/registers/instance/dmm.hare cross-checked against that SVD entry viatools/svd/check_svd.py, wired into ctestFunctional Impact
Low — touches only register-definition headers, no driver logic changes.
Regulatory Impact
None
QMS Impact
None
Risk Impact
No — existing risk coverage sufficient.
Related Issues / PRs
Relates to #4