fix(ci): wire up the TI mmWave SDK path baked into the ccstudio image #43

Merged

hoogv merged 1 commit from refs/pull/43/head into dev

2026-07-22 13:19:58 +00:00

hoogv commented

2026-07-22 13:19:05 +00:00

(Migrated from codeberg.org)

Description

Wires the TI mmWave SDK path baked into the ccstudio CI image into testing/CMakeLists.txt's auto-detection, so ti_hal_comparison actually runs on CI instead of always skipping.

Why

Change justification per ISO 9001 section 7.5.2: TI_MMWAVE_SDK_PATH auto-detection only checked a few local dev-machine paths, none of which exist on the actual ccstudio CI runner, so ti_hal_comparison always skipped on CI (confirmed in #40's log: no local TI mmWave SDK found) — meaning a whole class of tests was never actually validating anything in the automated pipeline.

Closes #42

Type of Change

Bug fix / nonconformity resolution

Impact Assessment

Functional impact: None — CI/build-tooling only, no product/driver code changes.
Regulatory impact: None.
QMS impact: None.
Risk impact: No — existing risk coverage sufficient.

Testing

CI pipeline passes (compile, unit tests, integration tests, static analysis)
Manually tested: verified end-to-end inside the real whuzfb/ccstudio:20.2-ubuntu24.04-mmw image, not just locally — mounted this repo read-only into a container run of that exact image, installed cmake/python3 the same way tests.yml does, configured, built, and ran ctest — all 25 tests (6 svd_check_* + 19 ti_hal_comparison) pass.
No regressions observed in related areas

PR Size

S (10–50 lines)

Checklist

Commit messages follow type(scope): description convention with Relates to #<issue> footer
PR template filled in completely
No unverified external binaries introduced (see QMS-GITFLOW-001 Binary Security section)
All commits leave the codebase in a compilable, passing-tests state (Commit Integrity Rule)

Summary

Inspected the whuzfb/ccstudio:20.2-ubuntu24.04-mmw image directly (docker run --rm --entrypoint sh whuzfb/ccstudio:20.2-ubuntu24.04-mmw -c 'find / -maxdepth 6 -iname "*mmwave_sdk*" -type d') and confirmed the SDK is baked in at /opt/ti/mmwave_sdk_03_06_02_00-LTS, with packages/ti/common/sys_common.h present — exactly the file the existing candidate-search logic checks for. Added that path to testing/CMakeLists.txt's TI_MMWAVE_SDK_PATH candidate list.

## Description Wires the TI mmWave SDK path baked into the `ccstudio` CI image into `testing/CMakeLists.txt`'s auto-detection, so `ti_hal_comparison` actually runs on CI instead of always skipping. ## Why Change justification per ISO 9001 section 7.5.2: `TI_MMWAVE_SDK_PATH` auto-detection only checked a few local dev-machine paths, none of which exist on the actual `ccstudio` CI runner, so `ti_hal_comparison` always skipped on CI (confirmed in #40's log: `no local TI mmWave SDK found`) — meaning a whole class of tests was never actually validating anything in the automated pipeline. ## Related Issue Closes #42 ## Type of Change - [x] Bug fix / nonconformity resolution ## Impact Assessment - **Functional impact:** None — CI/build-tooling only, no product/driver code changes. - **Regulatory impact:** None. - **QMS impact:** None. - **Risk impact:** No — existing risk coverage sufficient. ## Testing - [x] CI pipeline passes (compile, unit tests, integration tests, static analysis) - [x] Manually tested: verified end-to-end inside the real `whuzfb/ccstudio:20.2-ubuntu24.04-mmw` image, not just locally — mounted this repo read-only into a container run of that exact image, installed `cmake`/`python3` the same way `tests.yml` does, configured, built, and ran `ctest` — all 25 tests (6 `svd_check_*` + 19 `ti_hal_comparison`) pass. - [x] No regressions observed in related areas ## PR Size - [x] S (10–50 lines) ## Checklist - [x] Commit messages follow `type(scope): description` convention with `Relates to #<issue>` footer - [x] PR template filled in completely - [x] No unverified external binaries introduced (see QMS-GITFLOW-001 Binary Security section) - [x] All commits leave the codebase in a compilable, passing-tests state (Commit Integrity Rule) ## Summary Inspected the `whuzfb/ccstudio:20.2-ubuntu24.04-mmw` image directly (`docker run --rm --entrypoint sh whuzfb/ccstudio:20.2-ubuntu24.04-mmw -c 'find / -maxdepth 6 -iname "*mmwave_sdk*" -type d'`) and confirmed the SDK is baked in at `/opt/ti/mmwave_sdk_03_06_02_00-LTS`, with `packages/ti/common/sys_common.h` present — exactly the file the existing candidate-search logic checks for. Added that path to `testing/CMakeLists.txt`'s `TI_MMWAVE_SDK_PATH` candidate list.

hoogv added the

Rows
Columns