Please report bugs in esptool.py if you find them.
However, before reporting a bug please check through the following:
-
Troubleshooting Section - common problems and known issues
-
Existing Open Issues - someone might have already encountered this.
If you don't find anything, please open a new issue.
Feel free to post feature requests. It's helpful if you can explain exactly why the feature would be useful.
There are usually some outstanding feature requests in the existing issues list, feel free to add comments to them.
Pull Requests with changes and fixes are also welcome!
esptool.py complies with Flake 8 and is valid Python 2 & Python 3 code (in the same source file.)
When you submit a Pull Request, the Travis automated build system will run automated checks for this, using the flake8 tool. If you want to check your code locally before submitting, you can install flake8 and run python setup.py flake8 to test it.
The test directory contains an integration suite with some integration tests for esptool.py:
-
test_imagegen.pytests the elf2image command and is run automatically by Travis for each Pull Request. You can run this command locally to check for regressions in the elf2image functionality. -
test_esptool.pyis a Python unittest file that contains integration tests to be run against real ESP8266 or ESP32 hardware. These tests need real hardware so are not run automatically by Travis, they need to be run locally:
test_esptool.py takes a command line with the following format:
./test_esptool.py <serial port> <name of chip> <baud rate> [optional test name(s)]
For example, to run all tests on an ESP32 board connected to /dev/ttyUSB0, at 230400bps:
./test_esptool.py /dev/ttyUSB0 esp32 230400
Or to run the TestFlashing suite only on an ESP8266 board connected to /dev/ttyUSB2` at 460800bps:
./test_esptool.py /dev/ttyUSB2 esp8266 460800 TestFlashing
(Note that some tests will fail at higher baud rates on some hardware.)