feat(dmm): DMM driver implementation and host unit tests #92
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!92
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/91-dmm-driver"
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
Adds
hal/mss/dmm/hal_dmm.c/.h— the DMM (Data Modification Module) driver: reset/known-state bring-up, Direct Data Mode circular-buffer configuration (DMMDDMDEST/DMMDDMBL, rejecting an unsupported blocksize or a busy module), enable/disable, and the four raw device handlers (DMM1_LVL0_IRQHandler/DMM1_LVL1_IRQHandler/DMM2_LVL0_IRQHandler/DMM2_LVL1_IRQHandler) decodingDMMOFF1/DMMOFF2to a weak, application-overridablehal_dmm_irq_handler()hook. Both DMM instances supported (register-identical per TRM Chapter 20). Self-contained — no cross-module dependency.Trace Mode is not implemented at all (only Direct Data Mode), and DMM pin functional-mode muxing (
DMMPC0-8) is left entirely to the caller/board — documented inhal_dmm.h's top-of-file comment.Why
Continues the driver-implementation phase started by GPIO (#75/#76), ESM (#77/#78), UART (#79/#80), I2C (#81/#82), SPI (#83/#84), ADCBUF (#85/#86), CBUFF (#87/#88), and HWA (#89/#90).
Related Issue
Closes #91
Type of Change
Impact Assessment
Testing
testing/mss/unit/hal_functionality/test_dmmlocally (20 test cases, 92 assertions, all passing) alongside the full existingctestsuite (279/279 passing, no regressions); ran a full MISRA C:2025 pass (0 unsuppressed findings,-DENABLE_DMM_MODULEadded); reformatted and re-verified against the exact clang-format 18.1.3 the CI runner uses; sanity-checked by changing the 1024-byteDMMDDMBLblocksize encoding from0x6to0x7, confirming the test suite fails (2 test cases, 2 assertions), then reverting.PR Size
Size justification / exemption (if L or XL):
790 raw lines across 9 files, all hand-reviewed (no mechanically-generated content). Not split further — the driver (
hal_dmm.c/.h, 473 lines) and its comprehensive Catch2 spec (test_dmm.c, 300 lines, covering both instances, the busy-rejection path, the blocksize-encoding validation, and all four IRQ handlers) don't decompose into independently-reviewable sub-PRs, same rationale as prior driver PRs (#78, #80, #82, #84, #86, #88, #90). The remaining files are small CMake/Kconfig/MISRA wiring diffs, also not independently reviewable apart from the driver they enable.Checklist
type(scope): descriptionconvention withRelates to #<issue>footerSummary
hal/mss/dmm/hal_dmm.c/.h: DMM driver (reset/bring-up, Direct Data Mode config, enable/disable, IRQ handlers) — Trace Mode out of scope, documented in the header's top-of-file commenttesting/mss/unit/hal_functionality/test_dmm.c(+CMakeLists.txt): Catch2 functional test suite. No naming collision — noti_hal_comparison/test_dmm.cexists (DMM has no TI CSL header to cross-check against at all).zephyr/Kconfig/zephyr/CMakeLists.txt/hal/util/hal_config_mss.h:HAL_AWR6843_DMMKconfig option andENABLE_DMM_MODULEbridge, same pattern as every other landed drivertools/misra/run_misra.sh:-DENABLE_DMM_MODULEadded