Installing on Heltec Wireless Stick Lite (V3) - Unsuccessful due to baud rate setting

[PaulSchulz]

The script 'rebuild-esp32s3-linux-wifi.sh' runs successfully to competion, but the flash step fails.
(This can be fixed by removing the baud rate setting)

When run, the USB port (/dev/ttyUSB0) is correctly detected, but I get the following error..

esptool.py --chip esp32s3 -p /dev/ttyUSB0 -b 2000000 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 8MB 0x0 bootloader/bootloader.bin 0x10000 network_adapter.bin 0x8000 partition_table/partition-table.bin
esptool.py v4.8.0
Serial port /dev/ttyUSB0
Connecting....
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded Flash 8MB (GD)
Crystal is 40MHz
MAC: 64:e8:33:64:c7:a8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 2000000
Changed.

A fatal error occurred: Unable to verify flash chip connection (No serial data received.).

I was able to fix this by installing esptool (with venv) and rerunning the command above without the baud setting.

cd  ./build/esp-hosted/esp_hosted_ng/esp/esp_driver/network_adapter/build/
esptool.py --chip esp32s3 -p /dev/ttyUSB0 -b 2000000 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 8MB 0x0 bootloader/bootloader.bin 0x10000 network_adapter.bin 0x8000 partition_table/partition-table.bin

[jcmvbkbc]

I was able to fix this by installing esptool (with venv) and rerunning the command above without the baud setting.

A bit simpler approach would be to edit the script and set an appropriate baud rate and then re-running it like this: $ keep_toolchain=y keep_rootfs=y keep_buildroot=y keep_bootloader=y ./rebuild-esp32s3-linux-wifi.sh

[PaulSchulz]

Hi , Thankyou for your reply. Yes. I have figured some of that out. Also, the baud rate to connect after installation is 115200. eg. screen /dev/ttyUSB0 115200 I then get errors about 'no attached PSRAM'. I suspect that I need to setup a board configuration fior the Heltec Wireless Stick Lite V3. The version of the ESP32S3 is ESP32-S3 (QFN56) (revision v0.2) (Features: WiFi, BLE, Embedded Flash 8MB (GD)') Is xtensa the place to look? I have been using this board with ESPHome which used platformio and j'just worked' after I set the board to: esp32-s3-devkitc-1 I will continue reading.. thanks,

…

On Sat, 21 Sept 2024 at 19:10, Max Filippov ***@***.***> wrote: I was able to fix this by installing esptool (with venv) and rerunning the command above without the baud setting. A bit simpler approach would be to edit the script and set an appropriate baud rate and then re-running it like this: $ keep_toolchain=y keep_rootfs=y keep_buildroot=y keep_bootloader=y ./rebuild-esp32s3-linux-wifi.sh — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAVLAPCWGZXYCW4SFRPB6DZXU5HDAVCNFSM6AAAAABOQ5KYAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGEYTKMRUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jcmvbkbc]

I then get errors about 'no attached PSRAM'.
I suspect that I need to setup a board configuration fior the Heltec Wireless Stick Lite V3.

According to the description here there's no PSRAM in the esp32s3 module used in that thing, so there's nothing to configure.

[PaulSchulz]

Yes. So I need to turn something off.

[jcmvbkbc]

I'm not sure I understand. linux will not be able to run on an esp32s3 module without PSRAM, there's no configuration that may change that.

[PaulSchulz]

Ok. Thanks. I wasn't aware of that.