-
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
initial esp support #121
initial esp support #121
Conversation
acb572c
to
5c9b624
Compare
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.
Cool stuff! I think a few things could be factored in the wifi
module
8b2d9bc
to
61933e8
Compare
@ROMemories I think I got most of your review comments. (sorry for already squashing, I had trouble absorbing the fixes into the right commits) |
How is exception/ interrupt handling implementing in I have only started looking into this, but it might be that this PR will conflict with a Interrupts/ traps in RISC-V are handled by writing the address of the trap entry function into a CSR ( Footnotes
|
9e202f6
to
5efc4b4
Compare
This PR adds initial esp32 support.
Currently, this adds support for a random esp32c3 (RISC-V based) board, the necessary infra for esp-hal, and esp-wifi.
There's no preemptive scheduling (riot-rs-threads) yet.
A single thread-mode executor is used.
edit
I'm testing with:
This implies connecting to wifi but using the hard-coded IP address. to make the esp use dhcp, remove the "override-network-config" from
examples/embassy-http-server/Cargo.toml
.Ah, it needs some toolchain support.
At least
laze b install-toolchain
andcargo install espflash
.