|
@ -233,12 +233,32 @@ If all went well, the final log output in esphome-flasher looks somewhat like th |
|
|
|
|
|
|
|
|
<img src="images/17_flash_ready.png" width="400"> |
|
|
<img src="images/17_flash_ready.png" width="400"> |
|
|
|
|
|
|
|
|
If you want to flash with esptool, you can use: |
|
|
|
|
|
|
|
|
If you want to flash with esptool, you can use the following command. |
|
|
|
|
|
|
|
|
|
|
|
*Note: This is probably not correct to get the lamp fully operational. This |
|
|
|
|
|
does not update partition table and the bootloader, which are also needed to |
|
|
|
|
|
get a functioning ESPHome device. Unless you know exactly what you're doing |
|
|
|
|
|
with esptool here, I recommend to use the esphome-flasher instead.* |
|
|
|
|
|
|
|
|
``` |
|
|
``` |
|
|
python.exe .\esptool.py --chip esp32 --port COM3 --baud 115200 write_flash 0x1000 <path\to\yourfirmware.bin> |
|
|
python.exe .\esptool.py --chip esp32 --port COM3 --baud 115200 write_flash 0x1000 <path\to\yourfirmware.bin> |
|
|
``` |
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
*The following is a bit more in the direction of the required command |
|
|
|
|
|
for flashing. If you have some definitive info on how to handle this best, |
|
|
|
|
|
please let me know.* |
|
|
|
|
|
|
|
|
|
|
|
``` |
|
|
|
|
|
python esptool.py --chip esp32 \ |
|
|
|
|
|
-p /dev/ttyUSB0 --baud 115200 \ |
|
|
|
|
|
--before default_reset --after hard_reset \ |
|
|
|
|
|
write_flash -z --flash_mode dout --flash_freq 40m --flash_size detect \ |
|
|
|
|
|
0x1000 bootloader_dout_40m.bin \ |
|
|
|
|
|
0x8000 partitions.bin \ |
|
|
|
|
|
0xe000 boot_app0.bin \ |
|
|
|
|
|
0x10000 ~/Downloads/firmware.bin |
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
After flashing, power down the lamp, disconnect `GPIO0` from GND and |
|
|
After flashing, power down the lamp, disconnect `GPIO0` from GND and |
|
|
reconnect the power to boot into the new ESPHome firmware. |
|
|
reconnect the power to boot into the new ESPHome firmware. |
|
|
|
|
|
|
|
|