Not sure if this would help analyse especially this problem.
There are 24 MHz 8 channel logic analysers to buy that work very well un conjuction with a freeware called PusleView. This freeware PulseView can analyse and decode a lot of protocols
As they cost only 7 to 10 euros it is worth the price.
best regards Stefan
I have downloaded 1.8.13 as you suggested, also deleted the other version along with its ArduinoData folder and setup everything from the start. The result was same:
Executable segment sizes:
ICACHE : 32768 - flash instruction cache
IROM : 231756 - code in flash (default or ICACHE_FLASH_ATTR)
IRAM : 26777 / 32768 - code in IRAM (IRAM_ATTR, ISRs...)
DATA : 1496 ) - initialized variables (global, static) in RAM/HEAP
RODATA : 876 ) / 81920 - constants (global, static) in RAM/HEAP
BSS : 25608 ) - zeroed variables (global, static) in RAM/HEAP
Sketch uses 260905 bytes (24%) of program storage space. Maximum is 1044464 bytes.
Global variables use 27980 bytes (34%) of dynamic memory, leaving 53940 bytes for local variables. Maximum is 81920 bytes.
esptool.py v3.0
Serial port COM5
Connecting......
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: 9c:9c:1f:47:b5:35
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Traceback (most recent call last):
File "C:\Users\erelo\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.0.0/tools/upload.py", line 66, in <module>
esptool.main(cmdline)
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 3599, in main
detect_flash_size(esp, args)
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 2848, in detect_flash_size
flash_id = esp.flash_id()
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 688, in flash_id
return self.run_spiflash_command(SPIFLASH_RDID, b"", 24)
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 948, in run_spiflash_command
old_spi_usr = self.read_reg(SPI_USR_REG)
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 562, in read_reg
val, data = self.command(self.ESP_READ_REG, struct.pack('<I', addr))
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 386, in command
p = self.read()
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 331, in read
return next(self._slip_reader)
File "C:/Users/erelo/AppData/Local/Arduino15/packages/esp8266/hardware/esp8266/3.0.0/tools/esptool\esptool.py", line 2636, in slip_reader
raise FatalError("Timed out waiting for packet %s" % waiting_for)
esptool.FatalError: Timed out waiting for packet header
esptool.FatalError: Timed out waiting for packet header
I am starting to think the device is malfunctioned or something. I ordered it Thursday and just got it today around 14:00 pm. Ever since I got it, I've been trying to get it working. I really don't know what to do.
Both tried, doesn't work
Our entire settings are the same at the moment.
I got suspicious of flash button and tried to do it by plugging D3 pin to GND but it did not work.
You could try adding a big capacitor (1000µF) or even bigger between GND and 3.3V an a 100 nF capacitor in parallel. Both as esptool.FatalError: Timed out waiting for packet headerr-i as possible to the pins.
If it is a power-issue this should help.
I would order two additional boards from a quality manufacturer.
I have refunded it today and looking for a new device to buy. My actual intention is to send a bunch of sensor data (DHT11 and HC-SR04) to my HTTP server. Do you have any suggestions about the device that will do the trick of connecting to internet? Maybe wemos? or just a brand new nodeMCU v3 module?
At first, I was trying to use ESP8266-01 with Arduino Uno but then I decided to switch to an ESP development board due to ESP-01 being a problematic chip.
If you have the choice I would buy a ESP32 which is the successor of the ESP8266.
Same basic principle WiFi onboard additional bluetooth onboard (but using bluetooth needs a lot of memory)
More ADC-Pins, pure software deepsleep-modes that require zero hardware to wake up
Touch-IO-pins
RTC onboard
second hardware serial interface
UPDATE: I bought an ESP32 CH340 model (my old one was CP2102) and it has just arrived. I installed the driver, plugged it in, uploaded an empty sketch and voila! IT WORKED!!! Without pressing or holding any button!
This confirms our suspicions about the old one's hardware issues. Thank you a lot for your time.
