feat: CBUFF driver implementation and host unit tests #87
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#87
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/mss/cbuff/hal_cbuff.c/.h— the CBUFF (Common Buffer / High-Speed Interface) driver: controller reset + sticky-status clear on init, single-linklist-entry session configuration (LVDS/CSI-2 interface select, sample format, size, CRC enable, HW/SW trigger source), software session-start trigger, an approximate session-active poll, and the two raw device handlers (CBUFF_IRQHandler/CBUFF_ERR_IRQHandler) decodingSTAT_CBUFF_REG0/STAT_CBUFF_REG1to a weak, application-overridablehal_cbuff_irq_handler()hook.Deliberately minimal scope (documented in
hal_cbuff.h's top-of-file comment): one linklist entry per session, no chained linklist/multi-virtual-channel/LVDS-lane-clocking configuration, and no EDMA-side data feeding.Use Case / Rationale
As a firmware developer, I need a
hal_cbuff_*API to configure and trigger a basic single-source CBUFF streaming session, following the same driver pattern established by GPIO, ESM, UART, I2C, SPI, and ADCBUF.As a QMS reviewer, I need a host-native Catch2 test suite (
testing/mss/unit/hal_functionality/test_cbuff.c) covering session configuration validation, the read-modify-write-free trigger sequencing, and both IRQ handlers, runnable in CI without target hardware.Acceptance Criteria
hal/mss/cbuff/hal_cbuff.c/.himplemented against this project's currenthal/registers/component/cbuff.h/instance/cbuff.htesting/mss/unit/hal_functionality/test_cbuff.cpasses underctestFunctional Impact
None — self-contained addition alongside the already-landed GPIO/ESM/UART/I2C/SPI/ADCBUF drivers.
Regulatory Impact
None
QMS Impact
None
Risk Impact
No — existing risk coverage sufficient.
Related Issues / PRs
Relates to #4, relates to #75, relates to #77, relates to #79, relates to #81, relates to #83, relates to #85