Restore the TI mmWave SDK comparison test scaffolding (testing/mss/unit/ti_hal_comparison) #32

New issue

Closed

opened 2026-07-22 09:09:39 +00:00 by hoogv · 0 comments

hoogv commented

2026-07-22 09:09:39 +00:00

(Migrated from codeberg.org)

Description

Before this repo's driver/register tree was landed incrementally, testing/mss/unit/ti_hal_comparison held a suite of Catch2 tests comparing this project's from-scratch register headers against TI's own CSL headers and sys_common_xwr68xx_{mss,dss}.h base addresses (offsetof/sizeof comparisons, gated on a local TI mmWave SDK install being found, skipped gracefully otherwise). That scaffolding was never re-committed after PR #10 trimmed testing/CMakeLists.txt down to just the CMSIS-SVD check.

The original 12 test files (DMA, EDMA, GPIO, MCAN, Mailbox, TOPRCM, ESM, RCM, UART, I2C, SPI, QSPI) all target peripherals whose register headers aren't landed on dev yet, so they can't come back as-is right now. This tracks restoring just the shared scaffolding -- the TI_MMWAVE_SDK_PATH auto-detection block and the add_ti_comparison_test() helper -- with no test files wired in yet. Each peripheral's own future landing PR (once its register headers exist) adds its matching test_<peripheral>.c, same one-thing-at-a-time pattern as the CMSIS/SVD work.

Acceptance Criteria

testing/CMakeLists.txt restores the TI_MMWAVE_SDK_PATH detection block and add_ti_comparison_test() function
testing/mss/unit/ti_hal_comparison/CMakeLists.txt exists (empty for now, ready for per-peripheral test files as they land)
Configuring with a local TI mmWave SDK present still succeeds (no test files needed yet for this to pass)

Functional Impact

None — test scaffolding only, no product code.

Regulatory Impact

None

QMS Impact

None

Risk Impact

No — existing risk coverage sufficient.

Relates to #16.

### Description Before this repo's driver/register tree was landed incrementally, `testing/mss/unit/ti_hal_comparison` held a suite of Catch2 tests comparing this project's from-scratch register headers against TI's own CSL headers and `sys_common_xwr68xx_{mss,dss}.h` base addresses (offsetof/sizeof comparisons, gated on a local TI mmWave SDK install being found, skipped gracefully otherwise). That scaffolding was never re-committed after PR #10 trimmed `testing/CMakeLists.txt` down to just the CMSIS-SVD check. The original 12 test files (DMA, EDMA, GPIO, MCAN, Mailbox, TOPRCM, ESM, RCM, UART, I2C, SPI, QSPI) all target peripherals whose register headers aren't landed on `dev` yet, so they can't come back as-is right now. This tracks restoring just the shared scaffolding -- the `TI_MMWAVE_SDK_PATH` auto-detection block and the `add_ti_comparison_test()` helper -- with no test files wired in yet. Each peripheral's own future landing PR (once its register headers exist) adds its matching `test_<peripheral>.c`, same one-thing-at-a-time pattern as the CMSIS/SVD work. ### Acceptance Criteria - [x] `testing/CMakeLists.txt` restores the `TI_MMWAVE_SDK_PATH` detection block and `add_ti_comparison_test()` function - [x] `testing/mss/unit/ti_hal_comparison/CMakeLists.txt` exists (empty for now, ready for per-peripheral test files as they land) - [x] Configuring with a local TI mmWave SDK present still succeeds (no test files needed yet for this to pass) ### Functional Impact None — test scaffolding only, no product code. ### Regulatory Impact None ### QMS Impact None ### Risk Impact No — existing risk coverage sufficient. ### Related Issues / PRs Relates to #16.

hoogv added this to the Development project

2026-07-23 12:04:51 +00:00

hoogv self-assigned this

2026-07-23 12:04:52 +00:00

hoogv added the

Rows
Columns