-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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 to SDK 2.1.0 #3215
Comments
Because of fixing ARP issue, It's important to upgrade to this SDK, |
@alirezza updating libraries should probably take a couple of hours (there's usually some breakage, SDK archives repackaging, and LD script hacking involved). As for the other parts of the checklist, depends, I wouldn't venture a guess. Also I must mention that the top priority now is to clear all the blocking issues and push a new stable release, even if it doesn't include an SDK update. Feel free however to contribute to this issue if you find it important. |
How about combining your top priority with the new SDK. Possibly one could help the other? |
@igrr How's it going? Could you please implement this for the next version 2.4.0-RC2 ? Thanks! |
+1 from me for getting the 2.1.0 SDK in the next release! |
+1 because of the fixed ARP bug (#2330). To get rid of this would be very important. |
Created #3278. Only ran webserver, PWM, and OTA tests. Folks interested in SDK 2.1.0 are encouraged to try that branch and report what works and what doesn't. To use that PR, follow instructions for installing git version (remove the version installed using boards manager first). Then check out the PR by doing |
I have a sketch that uses:
Everything work fine since several days. |
Next release please use esp-mesh by this newest version esp-mesh on sdk2.1.0 still not update. |
@igrr what do you need to move forward with this? My knowledge of what is required is pretty much nullptr, but I'm willing to help out as I can starting this coming weekend. |
Thanks @devyte. Do any of the to-do items listed in the PR (#3278 (comment)) make sense to you? I think testing whether new SDK implementation of wifi reconnect works with WiFiManager is something you could help with. |
@igrr most don't. I'm sorry, I'm a higher level code developer, since decades, so my low level skills are beyond rusty. |
Also, i am not sure about merging SDK2.1.0 into 2.4.0. Pretty hard to say what might get broken. Should not prevent finishing work on SDK2.1.0 though... |
(also, probably OT here, but maybe some items in the "pending/todo" columns of https://github.com/esp8266/Arduino/projects/1 might make sense to you — once these are resolved, we can release 2.4.0 or at least -rc2). |
@igrr I just looked at the 2.1.0 changelist, and there are some rather important fixes in there, such as a fix for connecting to a wifi with hidden ssid, and the UDP broadcast extra bytes issue. You said:
The only change in the reconnect behavior of the wifi mentioned in the changelist is when trying to connect to an AP that doesn't exist. I do see mentions of changes in the wifi events, though. |
Should we consider pulling the latest git NONOS?
Good point, I will update the changeset based on latest git of the SDK.
Should I just test whether the wifimanager works as expected?
Yes, that would be great, thank you!
…On Wed, Sep 27, 2017, 02:37 Develo ***@***.***> wrote:
@igrr <https://github.com/igrr> I just looked at the 2.1.0 changelist,
and there are some rather important fixes in there, such as a fix for
connecting to a wifi with hidden ssid, and the UDP broadcast extra bytes
issue.
Also, there are 10 commits to the espressif github after the 2.1.0
release. Some of them seem to be fixes to outstanding issues, like the wpa2
enterprise identity api, and a fix for long time deep sleep. There are some
iram optimizations as well.
Should we consider pulling the latest git NONOS? I think it merits at
least exploring. If not for the release, then at least to be merged into
master right after.
You said:
testing whether new SDK implementation of wifi reconnect works with
WiFiManager
The only change in the reconnect behavior of the wifi mentioned in the
changelist is when trying to connect to an AP that doesn't exist. I do see
mentions of changes in the wifi events, though.
Should I just test whether the wifimanager works as expected?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3215 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEJcep-c40eBXGL4K_kN5dJOTi-MMPNjks5smUROgaJpZM4NTx2B>
.
|
I just looked at SDK 2.1 update because I needed new header definitions which were not in SDK 2.0. |
does anyone know how to install this? I have downloaded the zip file but dont know how to install in my system. Please help me. |
@igrr I've been testing the WiFiManager examples for a while now, and tbh I don't really see any difference. The only issue I encountered is that the scan-related page loads fail sometimes. From what I can tell, it's due to one of the following:
So I don't think the WiFiManager behavior is impacted, at least as far as I can tell. |
I've been testing 2.1.0-rc2 WPS functionality to see if it fixed WPS with modern (802.11ac) routers and unfortunately it still does not work although it works perfectly with older 802.11b/g/n routers. |
How can I upload to a new SDK? should I use ESP FLASH DOWNLOAD TOOL? |
non-OS SDK 2.1.0 has been released, with support for 16 MB flash size, support for broadcast packets in ESP-NOW, fixes for ARP, UDP broadcast, and other issues.
The text was updated successfully, but these errors were encountered: