ESP32 boards
Moderators: Voyager, BertB, grovkillen, Stuntteam, LisaM
Re: ESP32 boards
I have about 50 devices here, all connected via WIFI.
None of it is completely reliable. Some run a few weeks, some a few months. Suddenly a device stops sending because it is no longer on the network.
I will test the solution over LAN.
Is the STM32F405RGT6 and the W5500 ethernet card recommended?
The STM32F405RGT6 has little memory.
Or are there better solutions?
Greetings Peter
None of it is completely reliable. Some run a few weeks, some a few months. Suddenly a device stops sending because it is no longer on the network.
I will test the solution over LAN.
Is the STM32F405RGT6 and the W5500 ethernet card recommended?
The STM32F405RGT6 has little memory.
Or are there better solutions?
Greetings Peter
Re: ESP32 boards
Have these 'stalled' devices been up like 49.7 days?
If so. please test with one of the last builds for ESPeasy.
I've added some patches to prevent such crashes.
If so. please test with one of the last builds for ESPeasy.
I've added some patches to prevent such crashes.
Re: ESP32 boards
Yes, they are always on.
It is the latest version from the Git. I always flash about 5 devices with the current version.
They have stayed in the network so far. I would have to watch it longer.
One Device with BME280 VEML6040 MH-Z19 TVoc CSS811 SDS021 loses the CSS811, BME280 and the VEML6040 after a few hours. After a reset, the sensors stay away.
Only switching off and then switching on the supply voltage brings it back to life.
There are 2x 10k terminators on the I2C bus. The device ran before with an ESP-32 always without problems. I have no idea why the I2C bus suddenly stops working.
It is the latest version from the Git. I always flash about 5 devices with the current version.
They have stayed in the network so far. I would have to watch it longer.
One Device with BME280 VEML6040 MH-Z19 TVoc CSS811 SDS021 loses the CSS811, BME280 and the VEML6040 after a few hours. After a reset, the sensors stay away.
Only switching off and then switching on the supply voltage brings it back to life.
There are 2x 10k terminators on the I2C bus. The device ran before with an ESP-32 always without problems. I have no idea why the I2C bus suddenly stops working.
Re: ESP32 boards
Lisa,
here you can compare the performance of my installation. ESP-210 is the Arduino version, ESP-01 is the Python version. The Python version sometimes hangs for a few seconds.
Greetings Peter
here you can compare the performance of my installation. ESP-210 is the Arduino version, ESP-01 is the Python version. The Python version sometimes hangs for a few seconds.
Greetings Peter
- Attachments
-
- Performance ESPEasy.zip
- (1.59 MiB) Downloaded 699 times
Re: ESP32 boards
Peter,
Am i correct to notice that the uPyEasy performance is good, besides the hardware tab?
Cheers,
Lisa
Re: ESP32 boards
Yes, the orange/raspberry pi which have it all, loads of memory and ethernet and wifi, however they have a tradeoff in terms of latency. Besides that, i haven't found so far an I2C python library for the pi's which can be used with micropython.
Re: ESP32 boards
Yes Lisa, most of the time the performance is good.
But there is also a break in between, then it takes a little longer.
But there is also a break in between, then it takes a little longer.
Re: ESP32 boards
But real python is running on the Pi.
Also with I2C.
I had built some devices with sensors and PWM for my LEDs a long time ago.
They also did not run so reliably. Often there were problems with the microSD.
The Card was suddenly unreadable.
With my PI3s I booted over a USB stick, that was little better.
Overall, I was not satisfied.
I think the most important thing in lighting control or in sensor devices is reliability. They should never fail.
Also with I2C.
I had built some devices with sensors and PWM for my LEDs a long time ago.
They also did not run so reliably. Often there were problems with the microSD.
The Card was suddenly unreadable.
With my PI3s I booted over a USB stick, that was little better.
Overall, I was not satisfied.
I think the most important thing in lighting control or in sensor devices is reliability. They should never fail.
Re: ESP32 boards
The STM32's are build for industrial purposes, expensive but very reliable. That's why they have a very low latency, a ton of sensor inputs en low memory. They run in factories and buildings for decades without hickup. The ESP's are build for consumers, cheap and a lot of memory.micropet wrote: ↑02 Feb 2018, 13:01 But real python is running on the Pi.
Also with I2C.
I had built some devices with sensors and PWM for my LEDs a long time ago.
They also did not run so reliably. Often there were problems with the microSD.
The Card was suddenly unreadable.
With my PI3s I booted over a USB stick, that was little better.
Overall, I was not satisfied.
I think the most important thing in lighting control or in sensor devices is reliability. They should never fail.
Re: ESP32 boards
So STM boards ...
I just got a PYBv1.1 with STM32F405RG and flashed it with normal MicroPython .
My machine immediately detected an additional drive with boot.py and main.py.
Wow, great.
Can I simply copy the .py files from your github to this drive?
Unfortunately, I have no experience with microPython.
Greetings Peter
I just got a PYBv1.1 with STM32F405RG and flashed it with normal MicroPython .
My machine immediately detected an additional drive with boot.py and main.py.
Wow, great.
Can I simply copy the .py files from your github to this drive?
Unfortunately, I have no experience with microPython.
Greetings Peter
Re: ESP32 boards
Lisa,
if I flash the file upyeasy_v020_test_20180128_stm32-pybv3_1024.dfu on the PYBv1.1 the COM port is gone.
I'm flashing on Windows with dfu-util - old 0 -D upyeasy_v020_test_20180128_stm32-pybv3_1024.dfu
If I flash the original MicroPython, the COM port is back.
That's not right or?
if I flash the file upyeasy_v020_test_20180128_stm32-pybv3_1024.dfu on the PYBv1.1 the COM port is gone.
I'm flashing on Windows with dfu-util - old 0 -D upyeasy_v020_test_20180128_stm32-pybv3_1024.dfu
If I flash the original MicroPython, the COM port is back.
That's not right or?
Re: ESP32 boards
You can't copy the uPyEasy python files over to the STM flash drive, because it ain't big enough. The uPyEasy files are 'frozen', meaning they are part of the firmware. You need to flash the STM again using these instructions: viewtopic.php?f=22&t=3905micropet wrote: ↑02 Feb 2018, 17:20 So STM boards ...
I just got a PYBv1.1 with STM32F405RG and flashed it with normal MicroPython .
My machine immediately detected an additional drive with boot.py and main.py.
Wow, great.
Can I simply copy the .py files from your github to this drive?
Unfortunately, I have no experience with microPython.
Greetings Peter
Re: ESP32 boards
Did you turn the STM on/off? Did the com port disappear completely or did it change numbers?micropet wrote: ↑02 Feb 2018, 18:50 Lisa,
if I flash the file upyeasy_v020_test_20180128_stm32-pybv3_1024.dfu on the PYBv1.1 the COM port is gone.
I'm flashing on Windows with dfu-util - old 0 -D upyeasy_v020_test_20180128_stm32-pybv3_1024.dfu
If I flash the original MicroPython, the COM port is back.
That's not right or?
Please continue the STM thread in the STM32 topic.
Re: ESP32 boards
The board has been restarted several times.
The Comport remains completely gone.
But an "unknown device" emerges
An error occurred while requesting the USB device descriptor.
If I flash the original Python, Comport is back.
Sorry listen now in STM thread in the STM32 topic
The Comport remains completely gone.
But an "unknown device" emerges
An error occurred while requesting the USB device descriptor.
If I flash the original Python, Comport is back.
Sorry listen now in STM thread in the STM32 topic
Re: ESP32 boards
Hi Lisa,
I'm sorry to report that I'm having a problem with Beta version v.0.2.1. on ESP32 boards
I downloaded the binary from the releases page, and installed it per the instructions in post 1 (I tried with and without an erase first). it's getting into a reboot loop when it starts. The log shows
repeated endlessly. This is happening on two different ESP32 boards, one is a Lolin32 Lite, the other a Lolin32 Pro.
I tried it a few times with the same result, then went back to v54 and it works fine.
Am I missing something?
Regards
Andrew.
I'm sorry to report that I'm having a problem with Beta version v.0.2.1. on ESP32 boards
I downloaded the binary from the releases page, and installed it per the instructions in post 1 (I tried with and without an erase first). it's getting into a reboot loop when it starts. The log shows
Code: Select all
rst:0x10 (RTCWDT_RTC_RESET),boot:0x3f (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
I tried it a few times with the same result, then went back to v54 and it works fine.
Am I missing something?
Regards
Andrew.
Re: ESP32 boards
Hello
I have the same problem.
Look here:
http://www.letscontrolit.com/forum/view ... 869#p24927
Best regards
I have the same problem.
Look here:
http://www.letscontrolit.com/forum/view ... 869#p24927
Best regards
Re: ESP32 boards
Hello @CHK_BLN,
Thanks for that, it's comforting to know I'm not alone!
Were you able to find any solution?
Best wishes
Andrew
Thanks for that, it's comforting to know I'm not alone!
Were you able to find any solution?
Best wishes
Andrew
Re: ESP32 boards
I have the same problem with this release.
too dumb to check it
hi,
I am trying to get upyeasy on a esp32. after installing python, first hurdler taken, I had to install pyserial and finally got it done, but it took me some time to get there.
next hurdle: I want to start Firmware install on esp32 by:
esptool.py --port COM4 write_flash --baud 460800 --compress 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
but I get back:
usage: esptool write_flash [-h] [--flash_freq {keep,40m,26m,20m,80m}]
[--flash_mode {keep,qio,qout,dio,dout}]
[--flash_size FLASH_SIZE]
[--spi-connection SPI_CONNECTION] [--no-progress]
[--verify] [--compress | --no-compress]
<address> <filename> [<address> <filename> ...]
esptool write_flash: error: argument <address> <filename>: Must be pairs of an address and the binary filename to write there
can someone help me to do it right...
lisam: you are doing a really really great Job, many thanks! but can you pleeeease create a routine like for espeasy which is really idiotic-proof... ie. for me
many thanks
karl
I am trying to get upyeasy on a esp32. after installing python, first hurdler taken, I had to install pyserial and finally got it done, but it took me some time to get there.
next hurdle: I want to start Firmware install on esp32 by:
esptool.py --port COM4 write_flash --baud 460800 --compress 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
but I get back:
usage: esptool write_flash [-h] [--flash_freq {keep,40m,26m,20m,80m}]
[--flash_mode {keep,qio,qout,dio,dout}]
[--flash_size FLASH_SIZE]
[--spi-connection SPI_CONNECTION] [--no-progress]
[--verify] [--compress | --no-compress]
<address> <filename> [<address> <filename> ...]
esptool write_flash: error: argument <address> <filename>: Must be pairs of an address and the binary filename to write there
can someone help me to do it right...
lisam: you are doing a really really great Job, many thanks! but can you pleeeease create a routine like for espeasy which is really idiotic-proof... ie. for me
many thanks
karl
Re: ESP32 boards
I've got it running by using this string, which I found after searching through the thread:
E:\>esptool.py -p COM4 --baud 115200 write_flash --compress 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
E:\>esptool.py -p COM4 --baud 115200 write_flash --compress 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
Re: ESP32 boards
I am getting permanent reboots...
I am using an esp32 wroom module and no wrover, can this be a reason?
Regards
Karl
I am using an esp32 wroom module and no wrover, can this be a reason?
Regards
Karl
Re: ESP32 boards
@LisaM
This is all it does:
On the ESP32:
ESP32-WROVER
FCC ID2AC7Z-ESP32WROVER
This is all it does:
On the ESP32:
ESP32-WROVER
FCC ID2AC7Z-ESP32WROVER
rst:0x1 (POWERON_RESET),boot:0x3f (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x3f (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x3f (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
Re: ESP32 boards
Me too
Re: ESP32 boards
nd I have the same with a ESP-WROOM-32
Re: ESP32 boards
I've my working setup attached. I'm using this one: https://www.aliexpress.com/item/Officia ... 21054.html
Can you post a picture of your setup and a link to where you bought it?
I have also these in stock:
https://www.aliexpress.com/item/ESP32-B ... 25963.html (didn't work so far)
https://www.aliexpress.com/item/LOLIN32 ... 682537.htm (it has 4MB of PsRam and is really different)
https://www.aliexpress.com/item/ESP-32S ... 38946.html (not soldered yet)
Please also try this (non-upyeasy) firmware: http://micropython.org/download#esp32 to see if it's something in uPyEasy ESP32 firmware or if it's the ESP32 board itself.
There seems to be a lot of different ESP32 board going around, which are all different..
Cheers,
Lisa
Can you post a picture of your setup and a link to where you bought it?
I have also these in stock:
https://www.aliexpress.com/item/ESP32-B ... 25963.html (didn't work so far)
https://www.aliexpress.com/item/LOLIN32 ... 682537.htm (it has 4MB of PsRam and is really different)
https://www.aliexpress.com/item/ESP-32S ... 38946.html (not soldered yet)
Please also try this (non-upyeasy) firmware: http://micropython.org/download#esp32 to see if it's something in uPyEasy ESP32 firmware or if it's the ESP32 board itself.
There seems to be a lot of different ESP32 board going around, which are all different..
Cheers,
Lisa
- Attachments
-
- IMG_4103.JPG (2.18 MiB) Viewed 88814 times
Re: ESP32 boards
I have these two:
https://nl.aliexpress.com/item/Lolin-ES ... 0.0.0c92Eb
and:
https://nl.aliexpress.com/item/LOLIN32- ... 0.0.0c92Eb
The Oled one has no further devices attached and is directly connected to the USB of my PC.
The other one only has a BME/BMP 280 and a DS18B20
https://nl.aliexpress.com/item/Lolin-ES ... 0.0.0c92Eb
and:
https://nl.aliexpress.com/item/LOLIN32- ... 0.0.0c92Eb
The Oled one has no further devices attached and is directly connected to the USB of my PC.
The other one only has a BME/BMP 280 and a DS18B20
Re: ESP32 boards
On both boards, the first version of upyeasy works.
Re: ESP32 boards
That's very interesting! The first version was a 4MB version, while later ones are 2MB versions.
I've added a 4MB version (upyeasy_v021_20180318_test_esp32_4096.bin) to the release dir: https://github.com/letscontrolit/uPyEasy/releases
Can you try the 4MB version?
Cheers,
Lisa
Re: ESP32 boards
I am using this esp32 board
https://www.aliexpress.com/item/Wireles ... 0.0.gYWUKY
it is an esp32 wroom. I will give it a try with the 4MB version.
I'll keep you posted
I also have ordered esp32 wrover boards to see whether it works or not.. I really would love to see it running
regards
karl
https://www.aliexpress.com/item/Wireles ... 0.0.gYWUKY
it is an esp32 wroom. I will give it a try with the 4MB version.
I'll keep you posted
I also have ordered esp32 wrover boards to see whether it works or not.. I really would love to see it running
regards
karl
Re: ESP32 boards
Hi all,
I have (or had) three ESP32 boards:-
1. Lolin32 Lite: bought from Aliexpress, https://www.aliexpress.com/item/WEMOS-L ... 0.0.O82kUi
Now disconnected, but it had a BME280 and a DS18B20 connected. This is now my main ESP32 board (for the time being).
2. Lolin32 pro WROVER with 4Mb PSRAM: also from Aliexpress: https://www.aliexpress.com/item/LOLIN32 ... 0.0.O82kUi.
This one seems to have died just recently, it got very hot and now refuses to connect! (I hear that this version can suffer from this problem and that Wemos have withdrawn it from sale - although some other sellers are still offering it.)
3. DOIT ESP32 DEVKIT V1: Rev 0 chip. bought when ESP32 first came out (can't find where I bought it now). I've more or less abandoned this board, as it has a very unreliable USB socket.
Lisa, you are right when you say there is a variety of ESP32 boards out there!! And I think they can have various differences, particularly the peripheral components used, which may affect tolerances, timings etc. To make life harder, the reliability of at least some of the variants seems to be questionable.
As others have reported, I was getting the repeated boot loops with boards 1. and 2. when I used the bin file from the releases page of Github. Interestingly, more recently I built uPyEasy from source, using the recently issued instructions, and it worked! (no bootloop) Yay!
Could be something in the flash settings of the Makefile vs. esp flash tool?? I haven't looked into this yet.
I have (or had) three ESP32 boards:-
1. Lolin32 Lite: bought from Aliexpress, https://www.aliexpress.com/item/WEMOS-L ... 0.0.O82kUi
Now disconnected, but it had a BME280 and a DS18B20 connected. This is now my main ESP32 board (for the time being).
2. Lolin32 pro WROVER with 4Mb PSRAM: also from Aliexpress: https://www.aliexpress.com/item/LOLIN32 ... 0.0.O82kUi.
This one seems to have died just recently, it got very hot and now refuses to connect! (I hear that this version can suffer from this problem and that Wemos have withdrawn it from sale - although some other sellers are still offering it.)
3. DOIT ESP32 DEVKIT V1: Rev 0 chip. bought when ESP32 first came out (can't find where I bought it now). I've more or less abandoned this board, as it has a very unreliable USB socket.
Lisa, you are right when you say there is a variety of ESP32 boards out there!! And I think they can have various differences, particularly the peripheral components used, which may affect tolerances, timings etc. To make life harder, the reliability of at least some of the variants seems to be questionable.
As others have reported, I was getting the repeated boot loops with boards 1. and 2. when I used the bin file from the releases page of Github. Interestingly, more recently I built uPyEasy from source, using the recently issued instructions, and it worked! (no bootloop) Yay!
Could be something in the flash settings of the Makefile vs. esp flash tool?? I haven't looked into this yet.
Re: ESP32 boards
Bingo, I do have the DOIT DEVKIT V1 ESP32 module with WROOM32. I just tried to flash it with the 4MB firmware and it doesn't work either
Now I am going to try the stm32 module. Last time I had Trouble to wire up the Ethernet module but got some hints.
reagards
karl
Now I am going to try the stm32 module. Last time I had Trouble to wire up the Ethernet module but got some hints.
reagards
karl
Re: ESP32 boards
With the 4M bin, I get this
rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429368
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429368
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429368
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429368
ets Jun 8 2016 00:22:57
Re: ESP32 boards
Interesting! I'm happy the dev guide worked by the way!AndrewJ wrote: ↑18 Mar 2018, 20:56 Hi all,
I have (or had) three ESP32 boards:-
1. Lolin32 Lite: bought from Aliexpress, https://www.aliexpress.com/item/WEMOS-L ... 0.0.O82kUi
Now disconnected, but it had a BME280 and a DS18B20 connected. This is now my main ESP32 board (for the time being).
2. Lolin32 pro WROVER with 4Mb PSRAM: also from Aliexpress: https://www.aliexpress.com/item/LOLIN32 ... 0.0.O82kUi.
This one seems to have died just recently, it got very hot and now refuses to connect! (I hear that this version can suffer from this problem and that Wemos have withdrawn it from sale - although some other sellers are still offering it.)
3. DOIT ESP32 DEVKIT V1: Rev 0 chip. bought when ESP32 first came out (can't find where I bought it now). I've more or less abandoned this board, as it has a very unreliable USB socket.
Lisa, you are right when you say there is a variety of ESP32 boards out there!! And I think they can have various differences, particularly the peripheral components used, which may affect tolerances, timings etc. To make life harder, the reliability of at least some of the variants seems to be questionable.
As others have reported, I was getting the repeated boot loops with boards 1. and 2. when I used the bin file from the releases page of Github. Interestingly, more recently I built uPyEasy from source, using the recently issued instructions, and it worked! (no bootloop) Yay!
Could be something in the flash settings of the Makefile vs. esp flash tool?? I haven't looked into this yet.
The makefile says:
Code: Select all
BAUD ?= 460800
FLASH_MODE ?= dio
FLASH_FREQ ?= 40m
sudo python esptool.py --chip esp32 --port /dev/ttyUSB0 -b 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_vXX_2018YYZZ_test_esp32_2048.bin
Does that work for you @bert @karl?
Re: ESP32 boards
For me it’s a bit too technical. My knowledge is exhausted with cop/paste of instructions...
@abert: can you please share the .bin file...
Thx
Karl
@abert: can you please share the .bin file...
Thx
Karl
Re: ESP32 boards
I am coming closer
btw. I have received an esp32 wrover module now and tried to test it
I've tried this but it doesn't work:
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180318_test_esp32_4096.bin
can you please double check what's wrong with it?
thx
karl
btw. I have received an esp32 wrover module now and tried to test it
I've tried this but it doesn't work:
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180318_test_esp32_4096.bin
can you please double check what's wrong with it?
thx
karl
Re: ESP32 boards
Try to remove the baud part. it causes problems here.karl222 wrote: ↑20 Mar 2018, 17:47 I am coming closer
btw. I have received an esp32 wrover module now and tried to test it
I've tried this but it doesn't work:
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180318_test_esp32_4096.bin
can you please double check what's wrong with it?
thx
karl
In my Win10 pc I entered D:\Program Files\Python\Python36>python esptool-master\esptool.py --chip esp32 --port COM5 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 D:\Tools\uPython\upyeasy-esp32\upyeasy_v021_2.bin
The ESP is getting programmed, but I still have this continuous loop.
Re: ESP32 boards
Hi Karl,karl222 wrote: ↑20 Mar 2018, 17:47 I am coming closer
btw. I have received an esp32 wrover module now and tried to test it
I've tried this but it doesn't work:
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180318_test_esp32_4096.bin
can you please double check what's wrong with it?
thx
karl
Interested to hear you've received the esp32 wrover module. Could you post a link to the one you have, please?
When you say the command "esptool.py.........4096.bin" doesn't work, what exactly happens - do you see any error messages? These may make it easier to help.
Some thoughts/ideas in the meantime...
- You might need to put "python " in front of esptool.py..... I'm working on Linux now, but I started off on Windows and found that was necessary on my machine.
- I've also hit problems at times with the bit that says "--baud 460800". I even got it to work on one occasion by just leaving this out! Alternatively, you could try a lower speed, 115200.
- I haven't tried yet with the 4096.bin version yet, all my successes until now have been with 2048.bin versions.
Good luck!!
Andrew
Re: ESP32 boards
several attempts, no success:
bullshit, had not plugged in usb cable (but just this time)... will Report shortly...
bullshit, had not plugged in usb cable (but just this time)... will Report shortly...
Re: ESP32 boards
still no success:
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 115200 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
E:\esp32>esptool.py --chip esp32 --port COM7 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 115200 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
E:\esp32>esptool.py --chip esp32 --port COM7 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting........_____....._____....._____....._____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
Re: ESP32 boards
Breakthrough!
googling here and googling there... you have to press the boot button before you plug the esp32 in to usb and Keep it pressed. then start Flash sequence and tataaaaa, flashing runs through easily
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 115200 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0220
Compressed 1146384 bytes to 688849...
Wrote 1146384 bytes (688849 compressed) at 0x00001000 in 64.9 seconds (effective 141.3 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
googling here and googling there... you have to press the boot button before you plug the esp32 in to usb and Keep it pressed. then start Flash sequence and tataaaaa, flashing runs through easily
E:\esp32>esptool.py --chip esp32 --port COM7 --baud 115200 write_flash --flash_freq 40m --flash_mode dio -z 0x1000 upyeasy_v021_20180218_test_esp32_2048.bin
esptool.py v2.3.2-dev
Connecting....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0220
Compressed 1146384 bytes to 688849...
Wrote 1146384 bytes (688849 compressed) at 0x00001000 in 64.9 seconds (effective 141.3 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
Re: ESP32 boards
aaaaargh, bootloop.... damn!
rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
same problem with the 4MB version....
rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
ets Jun 8 2016 00:22:57
rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3f400020,len:429240
same problem with the 4MB version....
Re: ESP32 boards
That looks similar to one I have just ordered, but mine is from AlliExpress. I'll be interested to see how yours goes!karl222 wrote: ↑20 Mar 2018, 20:56 I've got this module now:
https://www.ebay.de/itm/TTGO-ESP32-WROV ... 2749.l2649
Andrew
Re: ESP32 boards
it does not go, thats the problem
Re: ESP32 boards
Found it!
It's a building firmware bug, fixed it!
I've uploaded two new versions into the https://github.com/letscontrolit/uPyEas ... s/tag/BETA section, can you download the 4096 version and try it again? If it doesn't work, you can try the 2048 version.
esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio --flash_size 2MB -z 0x1000 upyeasy_v021_20180321_test_esp32_4096.bin
Cheers,
Lisa
Re: ESP32 boards
Hi, karl222! I was able to build and deploy firmware following the instructions. I've little problems, but now seems ok.
You can see my post here: http://www.letscontrolit.com/forum/view ... =23&t=3903
I hope this my post helps you.
Regards
You can see my post here: http://www.letscontrolit.com/forum/view ... =23&t=3903
I hope this my post helps you.
Regards
Regards from Bulgaria.
raptor
raptor
Re: ESP32 boards
Hi, see my changed remark above:
Cheers,
Lisa
Code: Select all
It's a building firmware bug, fixed it!
I've uploaded two new versions into the https://github.com/letscontrolit/uPyEas ... s/tag/BETA section, can you download the 4096 version and try it again? If it doesn't work, you can try the 2048 version.
esptool.py --chip esp32 --port COM7 --baud 460800 write_flash --flash_freq 40m --flash_mode dio --flash_size 2MB -z 0x1000 upyeasy_v021_20180321_test_esp32_4096.bin
Lisa
Re: ESP32 boards
The build & deploy doesn't change, it's only my 'how to get the damn binary to github script which was pulling the wrong binary...'raptor wrote: ↑21 Mar 2018, 21:14 Hi, karl222! I was able to build and deploy firmware following the instructions. I've little problems, but now seems ok.
You can see my post here: http://www.letscontrolit.com/forum/view ... =23&t=3903
I hope this my post helps you.
Regards
Ps. i'm happy the guide worked for you!
Cheers,
Lisa
Who is online
Users browsing this forum: No registered users and 31 guests