-
Notifications
You must be signed in to change notification settings - Fork 0
EEF files
Andre H edited this page Jun 23, 2021
·
1 revision
.eef files are json files, which contains the parameter sets for the esptool. If eef files are available in the EEF path the files will be shown in the GUI otherwise the GUI will shown the bin files.
Have a look to the following examples of eef file content. Attention: Do not add the --port parameter to the command list, this will be handled by the ESPEasyFlasher tool
{
"command": ["--baud", "460800", "write_flash", "0x0", "ESP8266_Blink.bin"]
}
Content of ESP8266_Blink.eef from the binary examples
{
"command": ["--baud", "460800", "write_flash", "0x0", "ESP8266_jQuery_Mobile_Interface.ino.d1_mini.bin", "0x200000", "ESP8266_jQuery_Mobile_Interface.mklittlefs.bin"]
}
Content of ESP8266_jQuery_Mobile_Interface.eef from the binary examples
{
"command": ["--chip", "esp32", "--baud", "921600", "--before", "default_reset", "--after", "hard_reset", "write_flash", "-z", "--flash_mode", "dio", "--flash_freq", "80m", "--flash_size", "detect", "0xe000", "boot_app0.bin", "0x1000", "bootloader_qio_80m.bin", "0x10000", "ESP32_Blink.ino.bin", "0x8000", "ESP32_Blink.ino.partitions.bin"]
}
Content of ESP32_Blink.eef from the binary examples