![]() ![]() Enabling the CONFIG_BOOTLOADER_OTA_DATA_ERASE option will cause the device to boot from the default "factory" app partition after a factory reset (or if there is no factory app partition in the partition table then the default ota app partition is selected instead). Partitions of type "app" cannot be specified here.īoot from "factory" app partition. Make sure that the names of partitions specified in the option are the same as those found in the partition table. Users can specify the names of partitions as a comma-delimited list with optional spaces for readability. The CONFIG_BOOTLOADER_DATA_FACTORY_RESET option allows users to specify which data partitions will be erased when the factory reset is executed. The factory reset mechanism allows the device to be factory reset in two ways:Ĭlear one or more data partitions. To roll back to the original "factory" device configuration and clear any user settings, configure the config item CONFIG_BOOTLOADER_FACTORY_RESET in the bootloader. Sometimes it is desirable to have a way for the device to fall back to a known-good state, in case of some problem with an update. Reducing bootloader log verbosity can improve the overall project boot time by a small amount. This log level is separate from the log level used in the app (see Logging library). By setting the CONFIG_BOOTLOADER_LOG_LEVEL option, it is possible to increase or decrease this level. The default bootloader log level is "Info". To maintain compatibility with older bootloaders, the app re-initializes the flash settings during app startup using the configuration found in the app header. This allows an OTA update to change the SPI flash settings in use.īootloaders prior to ESP-IDF V4.0 used the bootloader's own header to configure the SPI flash, meaning these values could not be changed in an update. When the Second Stage Bootloader then runs, it will reconfigure the flash using values read from the currently selected app binary's header (and NOT from the Second Stage Bootloader header). However, at this time the system clock speed is lower than configured and not all flash modes are supported. The First Stage Bootloader in ROM reads the Second Stage Bootloader header information from flash and uses this infomation to load the rest of the Second Stage Bootloader from flash. These are used to configure the SPI flash during boot. bin file contains a header with CONFIG_ESPTOOLPY_FLASHMODE, CONFIG_ESPTOOLPY_FLASHFREQ, CONFIG_ESPTOOLPY_FLASHSIZE embedded in it. SPI Flash Configuration Įach ESP-IDF application or bootloader. When using a bootloader from these ESP-IDF versions and building a new app, you should not use this option. Before ESP-IDF V5.1 īootloaders built from versions of ESP-IDF prior to V5.1 do not support CONFIG_ESP_SYSTEM_ESP32_SRAM1_REGION_AS_IRAM. When using a bootloader from these ESP-IDF versions and building a new app, enable the config option CONFIG_APP_COMPATIBLE_PRE_V3_1_BOOTLOADERS. Before ESP-IDF V3.1 īootloaders built from versions of ESP-IDF before V3.1 do not support MD5 checksums in the partition table binary. ![]() When using a bootloader from these early ESP-IDF versions and building a new app, enable the config option CONFIG_APP_COMPATIBLE_PRE_V2_1_BOOTLOADERS. Before ESP-IDF V2.1 īootloaders built from very old versions of ESP-IDF (before ESP-IDF V2.1) perform less hardware configuration than newer versions. If testing an OTA update for an existing product in production, always test it using the same ESP-IDF bootloader binary that is deployed in production. When updating ESP-IDF manually on an existing product that might need to downgrade the app to an older version, keep using the older ESP-IDF bootloader binary as well. The bootloader does not support booting apps from older versions of ESP-IDF. ![]() For this reason, the bootloader supports booting apps built from newer versions of ESP-IDF. The OTA (over the air) update process can flash new apps in the field but cannot flash a new bootloader. It is recommended to update to newer versions of ESP-IDF: when they are released. Load this image to RAM (IRAM & DRAM) and transfer management to the image that was just loaded.īootloader is located at the address 0x1000 in the flash.įor a full description of the startup process including the ESP-IDF bootloader, see Application Startup Flow. Select the application partition to boot, based on the partition table and ota_data (if any) Initialize Flash Encryption and/or Secure features, if configured Minimal initial configuration of internal modules The ESP-IDF Software Bootloader performs the following functions: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |