Skip to content

phase 19g: SOME/IP Client+Server roundtrip over embassy-net loopback #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
JustinKovacich wants to merge 1 commit into
base: feature/phase19f_server_local_bounds
Choose a base branch
from
Draft

phase 19g: SOME/IP Client+Server roundtrip over embassy-net loopback #103

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions simple-someip-embassy-net/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,20 @@ embassy-sync = "0.6"
heapless = "0.9"

[dev-dependencies]
# Re-pin `simple-someip` with `std` enabled for the host-side test
# harness. Production builds of this adapter still pull in
# `simple-someip` with `default-features = false`, so the adapter
# library itself stays no_std. The dev-dep override only widens
# what the *tests* can import — `RawPayload`, `VecSdHeader`, and
# the `Arc<Mutex<E2ERegistry>>` / `Arc<RwLock<…>>` default
# handle impls — all of which are gated on `feature = "std"` in
# the parent crate.
simple-someip = { path = "..", default-features = false, features = [
"client",
"server",
"bare_metal",
"std",
] }
# Host-side tests run two embassy-net stacks bridged by a software
# `LoopbackDriver` pair (no kernel TUN, no privilege requirement).
# `critical-section/std` provides a host platform impl so embassy-sync
Expand Down
Loading