Category
Hardware Compatibility
Hardware
Other - Heltec V4 HTIT-WB32LAF
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.11.ee68575
Description
Trying to flash Heltec V4 HTIT-WB32LAF which has ESP32-S3 (link). Tried to use web flasher and did not work so I moved to CLI. Made sure that I could talk to board - some esptool results:
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (revision v0.2)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 80:f1:b2:a7:e4:ac
Uploading stub...
Running stub...
Stub running...
Warning: ESP32-S3 has no Chip ID. Reading MAC instead.
MAC: 80:f1:b2:a7:e4:ac
I am on macos, and installed the driver needed.
Chose 2.7.11.ee68575 release since the previous 2.6 did not have heltec v4. But It seems to be the exact firmware so I ran the install and got:
./device-install.sh -f firmware-heltec-v4-2.7.11.ee68575.bin
Error: file bleota.bin wasn't found. Terminating.
Most likely a small scripting error here. I naively fiddled with the script to make it use belota-s3 and also tried renaming bleota-s3 to bleota, but the script runs into failed esptool calls.
Category
Hardware Compatibility
Hardware
Other - Heltec V4 HTIT-WB32LAF
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.11.ee68575
Description
Trying to flash Heltec V4 HTIT-WB32LAF which has ESP32-S3 (link). Tried to use web flasher and did not work so I moved to CLI. Made sure that I could talk to board - some esptool results:
I am on macos, and installed the driver needed.
Chose 2.7.11.ee68575 release since the previous 2.6 did not have heltec v4. But It seems to be the exact firmware so I ran the install and got:
Most likely a small scripting error here. I naively fiddled with the script to make it use belota-s3 and also tried renaming bleota-s3 to bleota, but the script runs into failed esptool calls.