Context
simple-someip's actual production target is Infineon AURIX TriCore. The current bare-metal compile gate uses thumbv7em-none-eabihf (cortex-m4f) as a no_std proxy because mainline Rust + LLVM don't have a TriCore backend.
CI runs the cortex-m4f matrix on every PR, but a TriCore-specific regression (alignment, calling convention, target-feature interaction) wouldn't be caught until firmware integration.
Blocking dependency
Add a CI runner once one of the following becomes accessible:
- HighTec's commercial Rust-for-TriCore distribution becomes runnable in our CI environment, OR
- Upstream Rust nightly + LLVM-IR proxy toolchain stabilizes for TriCore (currently the halo PR #4429 path).
Goal
Add a CI job that runs cargo build --target tc1.6.x-... --no-default-features --features client,server,bare_metal (or the codec-FFI-only equivalent, depending on the TC4D scope decision) on every PR.
Context
simple-someip's actual production target is Infineon AURIX TriCore. The current bare-metal compile gate uses
thumbv7em-none-eabihf(cortex-m4f) as a no_std proxy because mainline Rust + LLVM don't have a TriCore backend.CI runs the cortex-m4f matrix on every PR, but a TriCore-specific regression (alignment, calling convention, target-feature interaction) wouldn't be caught until firmware integration.
Blocking dependency
Add a CI runner once one of the following becomes accessible:
Goal
Add a CI job that runs
cargo build --target tc1.6.x-... --no-default-features --features client,server,bare_metal(or the codec-FFI-only equivalent, depending on the TC4D scope decision) on every PR.