ESP8266 – ESPtool-ck (build helper)
Esptool is a tool to create firmware files for the ESP8266 chip and flash the firmware to the chip over serial port. Esptool runs on Windows, Linux and Mac OS X.
Esptool reads the compiled program in ELF format, extracts code and data sections, and either dumps a section to a file or assembles the firmware file from several segments. Esptool also communicates with the ESP8266 bootloader to upload firmware files to flash. Esptool can automatically put the board into UART bootloader mode using a variety of methods.
The program interprets the arguments given on the command line, and in the order they are given. The following commands are currently available:
|Opens an ELF object file, parses it and caches some of the information found therein. Only works if there is no ELF file currently opened.
-es <section> <filename>
|Reads the given section from the ELF file and makes a raw dump into the specified file.
|Closes the currently opened ELF file
|Prepares an firmware file in the format that is understood by the ESP chip. Only works if an ELF file is opened, and if no firmware file is prepared yet. Upon -bo the tool will start out with an empty image where only the main header is set up. The result of the operations done on the firmware image are saved when the it is finally closed using -bc command.
|Set the flash chip interface mode. Default is QIO. This parameter is stored in the binary image header, along with the flash size and flash frequency. The ROM bootloader in the ESP8266 uses the value of these parameters in order to know how to talk to the flash chip.
|Set the flash chip size. Default is 512K.
|Set the flash chip frequency, in MHz. Default is 40M.
|Reads the specified section from the ELF file and appends it to the firmware image. Sections will appear in the firmware image in the exact same order as the -bs commands are executed.
|Closes the firmware image and saves the result as file to disk.
|Increase verbosity level of the tool. Add more v’s to increase it even more, e.g. -vv, -vvv.
|Disable most of the output.
|Select the serial port device to use for communicating with the ESP. Default is /dev/ttyUSB0 on Linux, COM1 on Windows, /dev/tty.usbserial on Mac OS X.
|Select the reset method to use for resetting the board. Currently supported methods are listed below.
|Select the baudrate to use, default is 115200.
|Address in flash memory to upload the data to. This address is interpreted as hexadecimal. Default is 0x00000000.
|Upload the file to flash. Parameters that set the port, baud rate, and address must preceed the -cf command.
|No DTR/RTS manipulation
|RTS controls RESET or CH_PD, DTR controls GPIO0
|TXD controls GPIO0 via PNP transistor and DTR controls RESET via a capacitor
|GPIO0 and RESET controlled using two NPN transistors as in NodeMCU devkit.
app_40000.bin. Note the option for 4M flash size.
esptool -bz 4M -eo app.elf -bo app_00000.bin -bs .text -bs .data -bs .rodata -bc -ec -eo app.elf -es .irom0.text app_40000.bin -ec
esptool -cp COM5 -cd none -cb 115200 -ca 0x00000 -cf 00000.bin -ca 0x40000 -cf 40000.bin
esptool -cp COM5 -cf 00000.bin -ca 0x40000 -cf 40000.bin
Add script to test failure rate
Don't use character timeouts on Linux and macOS
Fix compilation for FreeBSD
Split upload progress into multiple lines
Add command line option to reset the chip
Fix some debug output
fix uploading with CH340
fix handling of flash size/mode/frequency commands
package linux and osx archives as tar.gz
Fix handling of sync packet reply. Sync command actually causes the bootloader to send not one, but eight reply packets. Ignoring this fact caused sync issues and messages like "espcomm cmd: wrong direction/command"
OS X: allow baud rates for which constants are not defined (230400, 460800, 921600)
Add support for setting flash chip size, mode, and frequency options in the binary image file.
Add workaround for SPIEraseArea bug
Add support for higher baud rates on Windows