-
Notifications
You must be signed in to change notification settings - Fork 93
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
Update embedded svc #84
Conversation
Thanks for your contribution! I thought about doing this, once things upstream settle a bit but great you took this over. Regarding their I guess we can just keep |
Yeah I thought of dhcp because the Wifi trait in svc doesn't mean it has osi 2 support. That's what the other trait is for. But keeping it where it is is also ok. Btw forgot to update examples, reminding myself. |
@bjoernQ Done. |
8d16b5d
to
001dbfb
Compare
Not unexpected ... but yeah definitely a good thing to do There is one thing to keep in mind and why I am very cautious when even changing small things: we still see miscompilations for Xtensa which are sometimes triggerd by something like moving a static to a different file .... things got much, much better but still. Just mentioning - not to apologize but to explain |
clippy warnings are mostly things like needing to do a let if instead of checking if a result |
@bjoernQ I'm getting a broken pipe in Linux when doing |
I also tested this in main branch and it still happens :/, can you see if the same happens to you? I suspect its somewhere in |
I tested this on all targets via USB-to-UART bridge (on the dev-board) and it worked well (besides the coex example which needs to get adapted) BUT I also tried on the ESP32-C3-DevKit-RUST-1 (which you probably also use) and see the same problem (even more problems since I'm on Windows and have trouble to get it to even flash) I have no idea what could cause this but at least I'm pretty sure it gets until @jessebraham do you remember testing it on ESP32-C3-DevKit-RUST-1 earlier? |
Seems I found a commit that works for me on the DevKit-RUST-1: 7bd2487 |
Created issue #85 for this IMHO we could still merge this once the |
The ESP32-C3-DevKit-RUST-1 issue should be fixed with #86 - maybe you can test that on your side |
001dbfb
to
ef1aacc
Compare
rebased because im using my branch currently lol |
@bjoernQ I'm unable to get an IP address from the DHCP now, I also tested in the main branch. I tested with a fortigate router and an iOS hotspot.
|
but from the stack trace it seems like it dies when allocating memory - you can try to increase HEAP_SIZE in my Rust compiler version is |
Yeah code works, but DHCP never ends so I get stuck in there waiting for an IP. I will try what you just said. Still, do you know why DHCP never gets resolved, or does it work in your side? |
It completely works on my side (only tested ESP32-C3 today) - I remember there were some issues with DHCP in the past which should be resolved There is also the |
So, I have tried many things, for some reason when I have wifi_logs it gets stuck after noticing the auth is not none. |
as mentioned in #88 we had similar problems before which were related to wrong timestamp calculations which shouldn't be the case now (unfortunately I was never able to reproduce it with any of my APs) Important thing to know: which was the last commit which worked for you? No need to git-bisect - just a commit that works would be a good hint |
Can we merge this meanwhile? |
Generally yes - but the CoEx example needs to get fixed |
oops |
I don't want to be annoying but unfortunately the coex example doesn't compile yet
Deleting line 163 should fix that |
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.
LGTM - thanks for your contribution
This is based on the #82 branch, so until that's merged this is blocked.
I only implemented the
Wifi
trait on theWifi
struct, but where should I implement theInterface
trait. This contains the actual IP info, should I directly implement it intoWifi
or should we change places intoNetwork
, what should we do with thepoll_dhcp
function then inWifi
Closes #83