Hi ESP32 experts,
I am designing our hardware and software such that I am relying on storing 2MBytes of data on our ESP32 SPI Flash which is a total of 4MBytes. So half for the ESP32 code and half for my application code.
At present this is working however I am not sure how the flash will be used when OTA support for upgrading the ESP32 is available.
Can someone working on OTA please confirm that I will be able to restrict the ESP32 code + data to use the first 2 MBytes? Assuming ofcourse that our ESP32 image is under 1MByte.
Many Thanks
Imtiaz
OTA support and SPI Flash usage
Re: OTA support and SPI Flash usage
Good news is bootloader & partition table is all open source. So you can customize it to your needs.
Re: OTA support and SPI Flash usage
You can define flash layout in the partition table, and bootloader/OTA library will follow the layout you have defined.
Aside from the secure boot sector (at 0x0000), 2nd stage bootloader (at 0x1000), and partition table (at 0x8000), SDK does not have any hard-wired addresses.
Aside from the secure boot sector (at 0x0000), 2nd stage bootloader (at 0x1000), and partition table (at 0x8000), SDK does not have any hard-wired addresses.
Re: OTA support and SPI Flash usage
Hello,
is the OTA process similar to the ESP8266 SDK NON-OS OTA process? (Server simply sends a file as answer to an HTTP request)
or do i need new code on Server and ESP32? Can i reuse code or do i need new code?
is the OTA process similar to the ESP8266 SDK NON-OS OTA process? (Server simply sends a file as answer to an HTTP request)
or do i need new code on Server and ESP32? Can i reuse code or do i need new code?
Creator of Smart Connected Devices - for EcSUHA.de Project
Who is online
Users browsing this forum: jsmith56x and 291 guests