Page 1 of 2

esp32 Update from spiffs

Posted: Fri Jun 12, 2020 5:36 am
by Swagger
Hi, I am trying to update esp32 from the spiffs. I had stored a bin file in the spiffs which will be used to update the esp32.

the update is almost getting finished but ended up in a strange problem.

I (14464) OTA: esp_ota_begin succeeded
I (16664) OTA: Total Write binary data length: 11139072
E (16674) boot_comm: mismatch chip ID, expected 0, found 13115
E (16674) boot_comm: can't run on lower chip revision, expected 1, found 50
E (16684) OTA: esp_ota_end failed!
E (16684) OTA: Exiting task due to fatal error...

I am not sure how this can be resolved. any idea guys.

........................................................................................................................
attaching my partition table also. I am not sure whether this has anything to do with the problem, just providing the details.

nvs data nvs 0x4000
otadata data ota 0x2000
phy_init data phy 0x1000
factory app factory 1M
ota_0 app ota_0 0x8000
ota_1 app ota_1 0x8000
storage data spiffs 0xF0000
...........................................................................................................................................

Re: esp32 Update from spiffs

Posted: Sun Jun 14, 2020 7:44 am
by Swagger
any idea? iam really stuck here.

Re: esp32 Update from spiffs

Posted: Sun Jun 14, 2020 8:15 am
by ESP_Sprite
Why are your OTA partitions only 32K? No way your app fits in that.

Re: esp32 Update from spiffs

Posted: Sun Jun 14, 2020 8:49 am
by Swagger
It would be really appreciated if you could explain a little more in detail. I am a bit confused here.

Re: esp32 Update from spiffs

Posted: Mon Jun 15, 2020 2:38 am
by Swagger
ESP_Sprite wrote:
Sun Jun 14, 2020 8:15 am
Why are your OTA partitions only 32K? No way your app fits in that.
It would be really appreciated if you could explain a little more in detail. I am a bit confused here.
I tried with the below partition also but ended with the same result.

# Name Type SubType Offset Size Flags
# Note: if you have increased the bootloader size make sure to update the offsets to avoid overlap
nvs data nvs 0x9000 0x4000
otadata data ota 0xd000 0x2000
phy_init data phy 0xf000 0x1000
factory app factory 0x10000 1M
ota_0 app ota_0 1M
ota_1 app ota_1 1M
storage data spiffs 0xF0000

Re: esp32 Update from spiffs

Posted: Mon Jun 15, 2020 10:10 am
by ESP_Sprite
How much flash does your module have?

Re: esp32 Update from spiffs

Posted: Mon Jun 15, 2020 10:38 am
by Swagger
ESP_Sprite wrote:
Mon Jun 15, 2020 10:10 am
How much flash does your module have?
Hi, Total 4 MB

Re: esp32 Update from spiffs

Posted: Tue Jun 16, 2020 8:32 am
by Swagger
Is this partition table configuration is causing the problem? or is it something else?

Re: esp32 Update from spiffs

Posted: Tue Jun 16, 2020 11:17 am
by kubera
I too have the same issue. I am also trying to update OTA from spiffs but encountered the same problem. not sure if it is causing due to partition table because it seems to be working fine when OTA over WiFi is being done with the same partition table. Does anybody have any idea?

Re: esp32 Update from spiffs

Posted: Tue Jun 16, 2020 2:10 pm
by ESP_Sprite
FYI, the partition table would be *a* reason why this could not work, but given that you now corrected it and you still have the error, it's not that. Perhaps you can show the code you're using? Maybe that helps us.