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

Firmware updating doesn't works with huge partition table #234

Closed
Vano3d opened this issue Nov 1, 2024 · 3 comments
Closed

Firmware updating doesn't works with huge partition table #234

Vano3d opened this issue Nov 1, 2024 · 3 comments
Labels

Comments

@Vano3d
Copy link

Vano3d commented Nov 1, 2024

Hello,
I'm using huge partition csv:
Name, Type, SubType, Offset, Size, Flags
nvs, data, nvs, 0x9000, 0x5000,
otadata, data, ota, 0xe000, 0x2000,
app0, app, ota_0, 0x10000, 0x300000,
spiffs, data, spiffs, 0x310000,0xF0000,

And I use a lot of another libs in my project:

gyverlibs/GyverOLED@^1.6.1
gyverlibs/EncButton@^3.6.0
gyverlibs/GyverTimer@^3.2
gyverlibs/GyverBlinker@^1.1.0
bblanchon/ArduinoJson@^7.0.0
mathieucarbou/AsyncTCP @ 3.2.10
https://github.com/ayushsharma82/ElegantOTA#3.1.6
adafruit/Adafruit ADS1X15@^2.5.0
bodmer/TFT_eSPI@^2.5.43
gyverlibs/GyverSegment@^1.4.5
build_flags = -DELEGANTOTA_USE_ASYNC_WEBSERVER=1

ElegantOTA stops updating on 14%, then ESP32 rebooting ((
With standard partition or without updating working perfectly, but I have a big project.

Thanks for assistance!

@mathieucarbou
Copy link
Contributor

mathieucarbou commented Nov 1, 2024

I am in the same use case as you, that's why I did MycilaSafeBoot: a recovery partition allowing to flash a bigger app partition. You can learn more at:

https://github.com/mathieucarbou/MycilaSafeBoot

ElegantOTA requires a standard partition model where you have two app partitions: ota_0 and ota1 with the same size for both.

Copy link

github-actions bot commented Dec 2, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Dec 2, 2024
Copy link

github-actions bot commented Dec 8, 2024

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants