cpq / esputil Goto Github PK

esputil is always showing "Error connecting. The blue LED of my NodeMCU-ESP32 blinks a few times and then that error is shown.

Tested with esptool.py and it reads/writes just fine.

MCU: ESP32
Board: NodeMCU-ESP32 DEVKITV1

Is there anything I should try?

I tried to flash my spiffs image (spiffs.bin created with platformio) to my esp32-s3. It needs to go at 0x210000. I receive the following error:

../../toolchains/esputil/esputil -fp 0x24f -p /dev/cu.usbserial-110 flash 0x210000 spiffs.bin
Using flash params 0x24f
Erasing 2097152 bytes @ 0x210000error 6: Failed to act on received message

I can flash the bootloader.bin (0x0), paritions.bin (0x8000) and firmware.bin (0x10000) without problem using esputil. I also tried with -fp 0x240. Same effect, bootloader, partition and firmware works, spiffs does not.

I can successfully upload the flash image with esptool.py without problem:

esptool.py --no-stub --chip esp32s3 --port "/dev/cu.usbserial-110" --baud 460800 --before default_reset --after hard_reset write_flash -z 0x210000 spiffs.bin
esptool.py v4.7.0
Serial port /dev/cu.usbserial-110
Connecting....
Chip is ESP32-S3 (QFN56) (revision v0.1)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_3v3)
Crystal is 40MHz
MAC: 34:85:18:9c:9f:10
Changing baud rate to 460800
Changed.
Enabling default SPI flash mode...
Configuring flash size...
Flash will be erased from 0x00210000 to 0x0040ffff...
Erasing flash...
Compressed 2097152 bytes to 155894...
Took 3.23s to erase flash block
Wrote 2097152 bytes (155894 compressed) at 0x00210000 in 12.2 seconds (effective 1371.7 kbit/s)...
Hash of data verified.

Any idea what I am doing wrong?

Hi, I am trying the example/blinky and it seems that it builds with no problem but then it stops after
"esputil flash 0 firmware.bin" and hangs there forever.

firmware.bin is generated with no issues

I tried on two different esp32c3 boards, but the same result. So I am stuck with ideas on what to do next.

What is it waiting for when it is trying to flash the chip?
Where could be my next step in debugging this?

Thank you.

hi, this is not be able to burn the chip, win10 used, esp32-WROOM module, any hints,
thanks

the same hex is used esptool.exe to burn the same chip, it was ok.

dosbox and console output as following,

xiao$ esputil mkhex 0x1000 ESP32_40MHZ_counter.ino.bootloader.bin 0x8000 ESP32_40MHZ_counter.ino.partitions.bi
n 0xe000 boot_app0.bin 0x10000 ESP32_40MHZ_counter.ino.bin 1>firmware.hex

xiao$ rem esputil -v -b 921600 -p COM5 -fp 0x220 flash 4096 firmware.hex

xiao$ esputil -v -b 921600 -p COM5 -fp 0x220 flash 0xe000 boot_app0.bin
SYNC [44 bytes]
0000 00 08 24 00 00 00 00 00 07 07 12 20 55 55 55 55 ..$........ UUUU
0010 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUUUUUU
0020 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUU

SYNC [44 bytes]
0000 00 08 24 00 00 00 00 00 07 07 12 20 55 55 55 55 ..$........ UUUU
0010 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUUUUUU
0020 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUU

SYNC [44 bytes]
0000 00 08 24 00 00 00 00 00 07 07 12 20 55 55 55 55 ..$........ UUUU
0010 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUUUUUU
0020 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUU

SYNC [44 bytes]
0000 00 08 24 00 00 00 00 00 07 07 12 20 55 55 55 55 ..$........ UUUU
0010 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUUUUUU
0020 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUU

SYNC [44 bytes]
0000 00 08 24 00 00 00 00 00 07 07 12 20 55 55 55 55 ..$........ UUUU
0010 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUUUUUU
0020 55 55 55 55 55 55 55 55 55 55 55 55 UUUUUUUUUUUU

--SLIP_RESPONSE: [12 bytes]
0000 01 08 04 00 12 20 55 55 00 00 00 00 ..... UU....

READ_REG [12 bytes]
0000 00 0a 04 00 00 00 00 00 00 10 00 40 ...........@

Error reading chip ID

xiao$ pause
Press any key to continue . . .

I've written a similar ESP32 loader as part of a STM32 firmware.

For me a practical solutions was to wrap all bin files within uImage header+crc (I my case w/o compression). Because of my limited time I can't add this now.

A valid image can be easy generated like

mkimage -A xtensa -C none -T firmware -a 10000 -e 10000 -nFACTORY <ImageName> -d<BinaryImage.bin> <uImageName>

If no flash address is given, your esputil can check if a uImage header is present - no need to use a fixed file suffix.

I'm using esp8266-12E for this project but when I use esputil I've this issue:

F:\Users\Nhat Pham\Downloads\esputil\windows>esputil -p COM12 flash 4m.hex monitor
Using flash params 0
Erasing 589824 bytes @ 0x370000error 6: Failed to act on received message

erase failed

F:\Users\Nhat Pham\Downloads\esputil\windows>esputil -p COM12 -fp 0x220 flash 4m.hex
Using flash params 0x220
Erasing 589824 bytes @ 0x370000error 6: Failed to act on received message

erase failed

F:\Users\Nhat Pham\Downloads\esputil\windows>esputil -p COM12 -fp 0x200 flash 4m.hex
Using flash params 0x200
Erasing 589824 bytes @ 0x370000error 6: Failed to act on received message

erase failed

Can anyone help me ?