-
Notifications
You must be signed in to change notification settings - Fork 20
Support native simulator. #31
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.
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
Comments
Rust llvm target x86_64-unknown-none,I actually tested it and it works. |
I'm trying to figure out how to support and Rust target. |
Any idea how well the various tests work? |
native_sim/native/64 with x86_64-unknown-none No problem. native_sim with i686-unknown-linux-gnu or i686-unknown-linux-musl there is a compilation error.
I hacked it and it works fine.
there are no other problems, but I don't know how to integrate it better. So there is no pr. |
I also briefly tested the esp series chips and there were no problems. The esp chip involves the esp toolchain, and the addition of the native simulator does not involve anything else. In fact, supporting esp chips only requires a small modification after enabling the esp rust toolchain.
|
Also, I'll be real curious if the embassy executor I've added will work. As long as |
x86_64-unknown-linux-gnu also works, so long as you conditionally don't overwrite the panic handler in the zephyr crate and change samples to use std. e.g.
Part of me thinks targets with std support might be better for native_sim since I think you'd still be able to develop no_std crates / applications, but allow yourself to make simulation backends and stuff using std, but maybe it feels a little messy. This issue was vaguely worded but I think to some level though it is done/landed, yes? |
https://docs.zephyrproject.org/latest/boards/native/native_sim/doc/index.html
The text was updated successfully, but these errors were encountered: