I’ve just bought a ESP32-S3-DevKitC-1 Board. I’ve had a few other binaries running on it successfully (e.g., tasmota, using the tasmota web installer), so the board is fine. But I can’t manage to get Theengs installed and running.
My first attempt was to use the web installer (i.e., (Option 1) Upload from the web | OpenMQTTGateway v1.7.0 ) with esp32s3-dev-c1-ble
. It reports an initialisation error, but doesn’t give any clue what is actually going wrong. Other online installers work fine (e.g., tasmota, espressif esp-tool).
Next I tried the off line esptool, using the following command line:
esptool.py --chip esp32-s3 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dout --flash_size detect 0xe000 boot_app0.bin 0x1000 esp32s3-dev-c1-ble-bootloader.bin 0x8000 esp32s3-dev-c1-ble-partitions.bin 0x10000 esp32s3-dev-c1-ble-firmware.bin
(copying the addresses from the (Option 2) Upload ready-to-go binaries | OpenMQTTGateway v1.7.0 page and modifying to point at what I think are the correct binaries).
After the first reset the board will reboot every few seconds, and attaching a serial console to it shows that it is reporting a checksum failure.
I suspect I am loading the wrong combination of files with esptool, so can please can someone confirm what 4 files/addresses I use for that board?
Can you try the development version
One gateway, many technologies: MQTT gateway for ESP8266 or ESP32 with bidirectional 433mhz/315mhz/868mhz, Infrared communications, BLE, LoRa, beacons detection, mi flora / mi jia / LYWSD02/ Mi Scale compatibility, SMS & LORA.
The dev version worked and I configured the gateway successfully. Many thanks for the prompt response.
1 Like
BTW, was I passing the wrong arguments into the command-line esp flash tool? I want to upload my own binary so that I can enable AWS support. Thanks.
Using Platform IO would be the easiest if you want to configure the board for AWS.
Here are the parameters used by the web uploader for binary upload.
{
"name": "OpenMQTTGateway",
"new_install_prompt_erase": true,
"builds": [
{
"chipFamily": "ESP32-S3",
"improv": false,
"parts": [
{ "path": "/dev/firmware_build/esp32s3-dev-c1-ble-bootloader.bin", "offset": 0 },
{ "path": "/dev/firmware_build/esp32s3-dev-c1-ble-partitions.bin", "offset": 32768 },
{ "path": "/dev/firmware_build/boot_app0.bin", "offset": 57344 },
{ "path": "/dev/firmware_build/esp32s3-dev-c1-ble-firmware.bin", "offset": 65536 }
]
}
]
}
You have to convert to hexadecimal
davlaw
September 28, 2024, 8:22pm
6
Saw the S3 listed, was hoping. But mine is a waveshare ESP32 S3 Zero. No joy.
+1 for dev when you see a chance
ESP32 S3 should work from the development branch
One gateway, many technologies: MQTT gateway for ESP8266 or ESP32 with bidirectional 433mhz/315mhz/868mhz, Infrared communications, BLE, LoRa, beacons detection, mi flora / mi jia / LYWSD02/ Mi Scale compatibility, SMS & LORA.