-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat(xtensa): add support for esp32s3 with xtensa arch #399
Conversation
@elenaf9 do you mind rebasing this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase (again), and squash. and probably, do a cargo update
, I added a commit to our embasssy fork to use the old waker code, which the current xtensa compiler needs.
I've added installing the xtensa toolchain for esp32s3 to CI, also building for the IMO this is good to go, apart from the CI (unrelated?) errors and the |
Description
xtensa
arch inriot-rs-threads
esp32s3
chip inriot-rs-embassy
(cc @ROMemories given that these are minimal changes, I don't think there will be many merge conflicts with refactor(embassy)!: extractarch
modules as crates #392. I'll rebase once that PR is in)espressif-esp32-s3-wroom-1
boardlaze-project.yml
based on prio work from @kaspar030.Testing
Rust on xtensa requires the installation of the esp toolchain and setting up the environment correctly. See the Rust on ESP Book. It can then be run as usual with
Issues/PRs references
Fixes #359.
Open TODOs
There are still linker issues that have to be fixed. Right now I simply worked around them by commenting out the conflicting parts, and somehow it worked. See self-review.
Change checklist