feat: CMSIS register description — CBUFF #6

New issue

Closed

opened 2026-07-21 14:07:18 +00:00 by hoogv · 0 comments

hoogv commented

2026-07-21 14:07:18 +00:00

(Migrated from codeberg.org)

Description

Part of the CMSIS-compliant register description epic (#4): bring the CBUFF (streaming/capture buffer) register block in line with the epic's shared-header and SVD-traceability goals.

Scope

hal/registers/component/cbuff.h includes the shared CMSIS core/qualifier header (from #4) instead of any local __I/__O/__IO redefinition
A CMSIS-SVD (or equivalent machine-readable) entry exists for this register block
The hand-rolled structs in hal/registers/component/cbuff.h and hal/registers/instance/cbuff.h are cross-checked against that SVD entry

Functional Impact

Low — touches only register-definition headers, no driver logic changes.

Regulatory Impact

None

QMS Impact

None

Risk Impact

No — existing risk coverage sufficient.

Relates to #4

### Description Part of the CMSIS-compliant register description epic (#4): bring the CBUFF (streaming/capture buffer) register block in line with the epic's shared-header and SVD-traceability goals. ### Scope - [x] `hal/registers/component/cbuff.h` includes the shared CMSIS core/qualifier header (from #4) instead of any local `__I`/`__O`/`__IO` redefinition - [x] A CMSIS-SVD (or equivalent machine-readable) entry exists for this register block - [x] The hand-rolled structs in `hal/registers/component/cbuff.h` and `hal/registers/instance/cbuff.h` are cross-checked against that SVD entry ### Functional 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