Most recent activity
-
Thanks AkosLukacs.
I've tried with many different cables including a very short one (14 cm) without success.
In addition I've tried all the releases since the 1.96 up to the last and every old release older than the 2.00 work fine. Therefore I do not think the issue is caused by random element like a cable quality o board specific configuration.
More probably from the 2.1 on the bootloader or the main image contains some code that can cause the issue systematically. It is clear that there must be a specific reason on my board, but it was there since the the earlier version.
-
-
UPDATE: installing a very old kit (1.96 release) ESP boot properly.
Installing then the bin of a newer release do not help.
So I can confirm the the newer version of the bootloader contain some incompatibility at least with my board.
I'll try to find the last working kit to help the devs to find the bug.
-
I guess the error comes from the Arduino bootload config/build. But in any case I was not looking to run the Espruino in this way. This is only to show that the bin flashing process works and so there must be a bug in the Espruino bootloader.bin
Otherwise I can't understand why with the Arduino boot loader, Espruino boots correctly.
-
-
-
I've followed your suggestion, but I get the same result:
C:\esptool\espruino_2v05.15_esp32> espruino_2v05.15_esp32>esptool.py --chip esp32 --port COM4 erase_flash
esptool.py v2.8
Serial port COM4
Connecting........__
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 160MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 84:0d:8e:11:2f:94
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 6.8s
Hard resetting via RTS pin...C:\esptool\espruino_2v05.15_esp32>esptool.py --port COM4 --baud 921600 write_flash -z 0x1000 bootloader.bin 0x10000 espruino_esp32.bin 0x8000 partitions_espruino.bin
esptool.py v2.8
Serial port COM4
Connecting........__
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 160MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 84:0d:8e:11:2f:94
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 15392 bytes to 10130...
Wrote 15392 bytes (10130 compressed) at 0x00001000 in 0.1 seconds (effective 954.7 kbit/s)...
Hash of data verified.
Compressed 1377824 bytes to 891085...
Wrote 1377824 bytes (891085 compressed) at 0x00010000 in 11.8 seconds (effective 938.0 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 166...
Wrote 3072 bytes (166 compressed) at 0x00008000 in 0.0 seconds (effective 1893.8 kbit/s)...
Hash of data verified.Leaving...
Hard resetting via RTS pin...C:\esptool\espruino_2v05.15_esp32>
IDE output is identical to the previously uploaded.
The fact that flashing with the Arduino IDE and then replacing the bin, the Espruino code boot and work for some seconds before to crash, make me think that the bootloader provided in the Espruino kit is bugged.
I've tried some old version with no luck. Can someone share the working kit version?
Thanks. -
SOLVED:
I've opened an issue on githup: https://github.com/espruino/Espruino/issues/1804
From version 2.01 on the board running with 160 MHz clock are no more supported by Espruino, and this is the case of my board.