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

How update rboot.bin over the air #17

Closed
fvpalha opened this issue Jul 1, 2016 · 10 comments
Closed

How update rboot.bin over the air #17

fvpalha opened this issue Jul 1, 2016 · 10 comments

Comments

@fvpalha
Copy link

fvpalha commented Jul 1, 2016

Hi.

I have some devices with rboot version v1.3.0.
I build a new firmware with rboot version v1.4.1 (SDK 1.5.4) and I updated the rom0 and rom1 over the air.
But the devices with old rboot.bin version does not change SSID/Password for Station Mode with command "wifi_station_set_config".

Someone can help me?

The device with rboot.bin version v1.4.1 works very well.

I changed the code with this suggestion (without success):
http://bbs.espressif.com/viewtopic.php?f=7&t=1085

@fvpalha
Copy link
Author

fvpalha commented Jul 4, 2016

comparativo_rboot_1 3 0_1 4 1

Comparing versions of rboot.bin 1.3.0 and 1.4.1 - no important difference.

@fvpalha
Copy link
Author

fvpalha commented Jul 4, 2016

I do not understand what is wrong. Why the devices with new roms do not change the router target?

@raburton
Copy link
Owner

raburton commented Jul 5, 2016

I'm in Cambodia at the moment on holiday so can't help you much, but rBoot
does not affect what you can do with WiFi, or anything else, once the
application rom is booted.
On 2 Jul 2016 1:17 a.m., "Fernando Vilmar Palha" notifications@github.com
wrote:

Hi.

I have some devices with rboot version v1.4.0.
I build a new firmware with rboot version v1.4.1 and I updated the rom0
and rom1 over the air.
But the devices with old rboot.bin version does not change SSID/Password
for Station Mode with command "wifi_station_set_config".

Someone can help me?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#17, or mute the thread
https://github.com/notifications/unsubscribe/AAadh-Ke86dVqFBbVKr6IpvzuPIw38vEks5qRVmogaJpZM4JDXpd
.

@fvpalha
Copy link
Author

fvpalha commented Jul 5, 2016

Thank you @raburton
A happy holiday to you.
I will identify the problem and I will find a solution.

@fvpalha
Copy link
Author

fvpalha commented Jul 12, 2016

Hi @raburton

I found the problem and the solution:
Important SDK Patch Released

SDK versions earlier than V1.5.4.1 have the limitation of flash map. It is not clear that which sector of flash is available in users’ systems. Therefore the older SDK versions need to be upgraded. In addition, “esp_init_data_default.bin” has been modified in this release.

@raburton
Copy link
Owner

Sorry about the delay in getting back to you. Is everything working ok now? Is there anything I need to do to accommodate this SDK change?

@fvpalha
Copy link
Author

fvpalha commented Jul 25, 2016

Hi @raburton ,

I found other case: ESP SDK and RBoot Woes

@fvpalha
Copy link
Author

fvpalha commented Jul 26, 2016

Hi @raburton .

At moment I am using SDK 1.5.3 and rBoot 1.3.0 without problems.

Thank you.

@raburton
Copy link
Owner

Tested sdk 1.5.4 this morning and rboot-sampleproject is building, running and OTAing just fine. Pete also has it working now too, he found some odd changes with the SDK he needed to account for, but nothing that needed changing in rBoot: http://tech.scargill.net/esp8266-home-control-update/

@fvpalha
Copy link
Author

fvpalha commented Jul 29, 2016

Hi @raburton .

Now my code works with SDK 1.5.4.1 and rboot v1.4.1

But, the devices with previous roms does not works after remote update.
I am thinking of not maintaining legacy support.

@raburton raburton closed this as completed Sep 3, 2016
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

2 participants