Option to reduce baud rate for burning firmware

[mfhepp]

Thanks for this great tool! When trying to burn the firmware to an Adafruit Feather board, I was running into continuous problems. It turned out that some USB chips require a slower baud rate, like 115200 baud, see also here: cnlohr/espusb#8

It would thus be good to be able to set the baud rate in the configuration, so that you can use e.g.

$ esptool.py --port /dev/cu.SLAB_USBtoUART --baud **115200** write_flash --flash_size=detect 0 ~/.upiot/firmwares/esp8266/esp8266-20180511-v1.9.4.bin 2>&1

Before report an issue, please make sure it hasn't been reported before.

Operating system

OSX 10.11.6

Board used

Adafruit Feather

Description of problem

Burning firmware fails due to too high baud rate.

Error(s) in ST Console? (View > Show Console)

Running esptool.py --port /dev/cu.SLAB_USBtoUART --baud 460800 write_flash --flash_size=detect 0 ~/.upiot/firmwares/esp8266/esp8266-20180511-v1.9.4.bin 2>&1

esptool.py v2.2
Connecting........_
Detecting chip type... ESP8266
Chip is ESP8266EX
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...

A fatal error occurred: Timed out waiting for packet header

[Finished in 7.0s with exit code 2]

Steps to Reproduce

Actual Results

Expected Results

Additional info

You can edit the text above according to your need

[gepd]

A quick solution would be locate the json file located in uPiotMicroPythonTool/boards an edit the --baud parameter manually. You should edit the file corresponding to your board/firmware

[mfhepp]

Thanks, I found that in parallel and tried, but it did not really help. Currently, ampy on the command-line works fine, but the same functionality inside Sublime Text does not.

That is a pity, because in theory this plug-in is exactly what I need - a Sublime-based integrated workflow for MicroPython development that works via the USB UART.

Has anybody this running with Adafruit Feather boards (ESP8266)?

[gepd]

This plugin uses a modified version of ampy, but it shouldn't be a problem.

You are having problem to burn the firmware or to run the ampy commands?