Add the CI runner for the host-native SVD/CMSIS checks landed so far #30

New issue

Closed

opened 2026-07-22 08:31:08 +00:00 by hoogv · 0 comments

hoogv commented

2026-07-22 08:31:08 +00:00

(Migrated from codeberg.org)

Description

Every peripheral landed under the CMSIS register description epic (#4) so far -- ADCBUF (#5), CBUFF (#6), DSS Interrupt Controller (#7) -- wires its own svd_check_<peripheral> test into testing/CMakeLists.txt, and all three pass locally via cmake -S testing -B build && ctest --test-dir build. But .forgejo/workflows/tests.yml (the CI runner that would actually run them automatically) has never been committed -- it was part of the larger, since-abandoned issue #16 PR, which also bundled CI jobs for the real R4F/C6000 cross-toolchain build that still depend on the uncommitted hal/mss/hal/dss driver tree.

This tracks landing just the host-native test job now, decoupled from those toolchain jobs (which land later, once the driver tree they need exists) -- so the SVD/CMSIS checks already merged actually run automatically on every push/PR instead of only when someone remembers to run ctest by hand.

Acceptance Criteria

.forgejo/workflows/tests.yml is committed with a host-tests job that configures/builds/runs testing/'s ctest suite
All svd_check_* tests for peripherals merged so far (ADCBUF, CBUFF, DSS_INTC) pass under that CI job

Functional Impact

None — CI/test-tooling only.

Regulatory Impact

None

QMS Impact

None

Risk Impact

No — existing risk coverage sufficient.

Relates to #16 (the real-toolchain CI jobs remain tracked there, for once the driver tree lands).

### Description Every peripheral landed under the CMSIS register description epic (#4) so far -- ADCBUF (#5), CBUFF (#6), DSS Interrupt Controller (#7) -- wires its own `svd_check_<peripheral>` test into `testing/CMakeLists.txt`, and all three pass locally via `cmake -S testing -B build && ctest --test-dir build`. But `.forgejo/workflows/tests.yml` (the CI runner that would actually run them automatically) has never been committed -- it was part of the larger, since-abandoned issue #16 PR, which also bundled CI jobs for the real R4F/C6000 cross-toolchain build that still depend on the uncommitted `hal/mss`/`hal/dss` driver tree. This tracks landing just the host-native test job now, decoupled from those toolchain jobs (which land later, once the driver tree they need exists) -- so the SVD/CMSIS checks already merged actually run automatically on every push/PR instead of only when someone remembers to run `ctest` by hand. ### Acceptance Criteria - [x] `.forgejo/workflows/tests.yml` is committed with a `host-tests` job that configures/builds/runs `testing/`'s ctest suite - [x] All `svd_check_*` tests for peripherals merged so far (ADCBUF, CBUFF, DSS_INTC) pass under that CI job ### Functional Impact None — CI/test-tooling only. ### Regulatory Impact None ### QMS Impact None ### Risk Impact No — existing risk coverage sufficient. ### Related Issues / PRs Relates to #16 (the real-toolchain CI jobs remain tracked there, for once the driver tree lands).

hoogv self-assigned this

2026-07-23 12:05:05 +00:00

hoogv added this to the Development project

2026-07-23 12:05:08 +00:00

hoogv added the

Rows
Columns