feat: DSS ADCBUF driver implementation and host unit tests #105
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#105
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
Adds
hal/dss/adcbuf/hal_dss_adcbuf.c/.h— the DSS-side counterpart of the already-landed MSS ADCBUF driver (#85/#86). ADCBUF is physically dual-mapped (same register block and sample-data memory window visible at different base addresses depending on which core accesses them), so this driver targets the DSS-visibleDSS_ADCBUF_CFG/DSS_ADCBUF_ECC/DSS_ADCBUF_MEMaddresses with the identical register semantics and functional scope as the MSS driver: channel-enable/real-only/IQ-swap configuration, per-channel sample-address configuration (read-modify-write-guarded), chirp-count configuration, sample-buffer pointer accessor, and ECC enable (boundedINITDONEpoll)/clear-error for both ping and pong banks.Does not configure the radar front end (BSS) that performs the actual analog-to-digital conversion — that's a separate subsystem reached over mailbox/mmWaveLink-style messaging, out of scope for this HAL.
Use Case / Rationale
As a firmware developer, I need a DSS-side
hal_dss_adcbuf_*API mirroring the MSS one, continuing the DSS-side driver batch (Mailbox, EDMA, VIM already landed).As a QMS reviewer, I need a host-native Catch2 test suite (
testing/dss/adcbuf/test_dss_adcbuf.c) covering channel configuration, address read-modify-write isolation, and the ECC init/enable sequence, runnable in CI without target hardware — same coverage shape as the MSS driver's own test suite.Acceptance Criteria
hal/dss/adcbuf/hal_dss_adcbuf.c/.himplemented against this project's currenthal/registers/component/adcbuf.h/instance/adcbuf.htesting/dss/adcbuf/test_dss_adcbuf.cpasses underctestFunctional Impact
None — self-contained addition alongside the already-landed Mailbox/EDMA/VIM drivers.
Regulatory Impact
None
QMS Impact
None
Risk Impact
No — existing risk coverage sufficient.
Related Issues / PRs
Relates to #4, relates to #85, relates to #99, relates to #101, relates to #103