Flashing command #129
-
At #building-squeezelite-esp32 the following flashing command is given:
If I try this on a WROVER that had previously been flashed with the Arduino IDE with a standard Blink example, then the ESP boots into the Blink example. The Blink example has an esptool command line that contains four parts: two boot loader files, a partition list, and the Blink executable itself (at least, this is what I think they are). Also the example at https://docs.espressif.com/projects/esptool/en/latest/esp32s3/esptool/flashing-firmware.html#flashing shows multiple parts (three, in that case). How should this work in the case of squeezelite? Is the command line above missing some parts? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
It's not visible in the README, but there is more detail here: https://forums.slimdevices.com/showthread.php?112697-ANNOUNCE-Squeezelite-ESP32-(dedicated-thread) There are two notable things:
And an update: As of #144, there is a web installer that does not need any of the |
Beta Was this translation helpful? Give feedback.
It's not visible in the README, but there is more detail here: https://forums.slimdevices.com/showthread.php?112697-ANNOUNCE-Squeezelite-ESP32-(dedicated-thread)
There are two notable things:
esptool
does not seem to throw an error if it fills the module's RAM and there's still more file to write.python ${IDF_PATH}/components/esptool_py/esptool/esptool.py --chip esp32 --port ${ESPPORT} --baud ${ESPBAUD} --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0xd000 ota_data…