Skip to content

Integrate standalone Embassy through runtime time profiles - #1

Draft
sanchuanhehe wants to merge 2 commits into
mainfrom
refactor/embassy-time-profiles
Draft

sanchuanhehe wants to merge 2 commits into
mainfrom
refactor/embassy-time-profiles

Conversation

@sanchuanhehe

Copy link
Copy Markdown
Contributor

Integrate Embassy through the existing runtime facade instead of a parallel component. The existing embassy profile keeps its single SchedulerPort and 1 ms resolution (1 MHz ABI); experimental embassy-only consumes HAL TIMER/TCXO without compiling the thread scheduler. Both profiles share a bounded queue and one registration. Waker callbacks run outside queue borrows; shared timer generation covers callback reentry.

Validation: independent remote dependency graph, 86 base / 91 shared host tests, 14 standalone tests per chip, UI/doc/negative-feature checks and three-chip target Clippy passed. WS53 normal/fault and WS63/BS21 standalone QEMU passed (old-chip TCXO model fix required). The existing coexist HIL fixture prints the same native_ticks=7 embassy_ticks=7 threshold failure before and after migration in QEMU; it is not qualified here. No hardware operations or release. New HAL/profile and RF contract dependencies remain unpublished; the explicit development lane is not registry release qualification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant