feat(dma): CMSIS core header, SVD entries, and TI comparison tests #37
No reviewers
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!37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/37/head"
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?
Lands MSS DMA under the CMSIS register description epic (#4). This one's a bigger jump in scale than ADCBUF/CBUFF/DSS_INTC/DSSREG -- two physically separate register blocks in the same header:
Dma(76 control registers) andDmaRam(32-channel control-packet RAM, its own base address). Confirmed with the user up front to keep both in this one PR rather than splitting further.hal/registers/component/dma.hnow includescore_cr4f.hinstead of a local qualifier redefinition.DMA,DMARAM) added tohal/registers/svd/AWR6843AOP_MSS.svd, cross-checked via newsvd_check_dma/svd_check_dmaramctests.testing/mss/unit/ti_hal_comparison/test_dma.cextended: this file already existed (it's this project's own stated exemplar/template for the wholeti_hal_comparisonsuite) but only coveredDma. Switched its include from theregisters/awr.haggregator tocomponent/dma.h+instance/dma.hdirectly (same fix as every other peripheral in this suite --awr6843aop.hunconditionally includes all 22 peripherals, most not yet landed), and addedDmaRamvs TI'sDMARAMRegscoverage.On the SVD entries' scale: given 76+9 registers (several times larger than anything landed so far), the two
<peripheral>blocks were generated by a script parsing this project's own header macros (_OFFSET/_RESETVALUE/_Pos/_Msk) rather than hand-transcribed one register at a time -- then spot-checked against the header/TRM afterward, same diligence as every prior peripheral, just applied via script given the register count.Verified locally: full suite builds and all 21 tests pass. Also sanity-checked that the TI comparison test actually catches drift -- deliberately broke the DMA1 RAM base-address comparison, confirmed it failed, then reverted and confirmed green again.
Closes #9