Skip to content
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

Native OTA and simple OTA (GIT8266O-298) #713

Closed
dipendra77 opened this issue Sep 26, 2019 · 4 comments
Closed

Native OTA and simple OTA (GIT8266O-298) #713

dipendra77 opened this issue Sep 26, 2019 · 4 comments

Comments

@dipendra77
Copy link

Hi,
Can anyone tell me the differences between native OTA and simple OTA support for ESP8266 and in what context of Over the Air upgrade are they used ? I just want to upgrade the firmware on the device with a new binary file? which one should I opt for ?

Thank you in advance.

@github-actions github-actions bot changed the title Native OTA and simple OTA Native OTA and simple OTA (GIT8266O-298) Sep 26, 2019
@xuhongv
Copy link

xuhongv commented Sep 26, 2019

simple OTA maybe is the best for you

@ustccw
Copy link
Collaborator

ustccw commented Sep 27, 2019

@dipendra77 please take a look at pinned issue if you are interested in native OTA:
#489

In short, you only need to care about simple OTA if you set up your projects after SDK version 3.x

@dipendra77
Copy link
Author

simple OTA maybe is the best for you

Can you please explain the difference ? On what basis should we decide whether to goo with simple ota or native ota?

@27-301
Copy link

27-301 commented Sep 29, 2019

native ota may need to use the esp_ota, partition, http, etc. API directly, but simple ota does a wrap, so you can just call esp_https_ota, it's simple.

@FayeY FayeY closed this as completed Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants