Closed ldismo closed 1 year ago
One of two things are wrong: You are using the wrong com port or your platform does not support NodeMCU programming via the UART control pins and you need to put your device into programming mode manually.
Can you post a screenshot of the COM ports available in the drop down of the flash tool?
Thank you for the reply. I'm confident in the port because there is only one listed and it matches the port in Device Manager /Ports.
How do I manually put the D1 Mini in programming mode? It has a reset button and I've tried various ways but could use a definitive process
On Sun, Oct 30, 2022 at 10:14 AM Martin Mueller @.***> wrote:
One of two things are wrong: You are using the wrong com port or your platform does not support NodeMCU programming via the UART control pins and you need to put your device into programming mode manually.
— Reply to this email directly, view it on GitHub https://github.com/forkineye/ESPixelStick/issues/573#issuecomment-1296270334, or unsubscribe https://github.com/notifications/unsubscribe-auth/A34PPARUTCBTY6U6RL7OOXDWFZ7FHANCNFSM6AAAAAARR623A4 . You are receiving this because you authored the thread.Message ID: @.***>
Please send a link to the device you purchased. There are many products that go by the name of "D1 Mini"
When you press the reset button, do you see anything in the serial output window? Something could have happened to the Wemos. If you can, send me your order number. thanks, -shelby
Order# 112-6918992-9279414 There is no display on the D1 Mini.... do you mean on the ESPFlash Tool?
On Mon, Oct 31, 2022 at 9:31 AM Shelby Merrick @.***> wrote:
When you press the reset button, do you see anything in the serial output window? Something could have happened to the Wemos. If you can, send me your order number. thanks, -shelby
— Reply to this email directly, view it on GitHub https://github.com/forkineye/ESPixelStick/issues/573#issuecomment-1297096774, or unsubscribe https://github.com/notifications/unsubscribe-auth/A34PPAXMHPXBCB4T6X6ENITWF7C4JANCNFSM6AAAAAARR623A4 . You are receiving this because you authored the thread.Message ID: @.***>
He is asking this:
What
Interesting, the string is odd. bd cl�r{l cd�s� ��c� ��c ���;� l � �od�s� � 'og c �lc
[image: image.png]
On Mon, Oct 31, 2022 at 12:59 PM Martin Mueller @.***> wrote:
He is asking this:
- Connect the USB cable from the PC to the ESP
- Start up the flash tool
- On the flash tool:
- Set the port to the correct COM value
- Set the Firmware selection to the proper value
- On the ESP, press the reset button
- On the flash tool console (lower window), you should see some output. Paste it to this message chain
What
— Reply to this email directly, view it on GitHub https://github.com/forkineye/ESPixelStick/issues/573#issuecomment-1297390604, or unsubscribe https://github.com/notifications/unsubscribe-auth/A34PPAUKV3DN5G4SN7HSELTWF73GVANCNFSM6AAAAAARR623A4 . You are receiving this because you authored the thread.Message ID: @.***>
The attachment didn't come through, but it sounds like the module is alive. Does the string repeat each time you press the reset button?
The string is shown below and was also in the screenshot. Is this normal? bd cl�r{l cd�s� ��c� ��c ���;� l � �od�s� � 'og c �lc
[image: image.png]
On Wed, Nov 2, 2022 at 9:45 AM Shelby Merrick @.***> wrote:
The attachment didn't come through, but it sounds like the module is alive. Does the string repeat each time you press the reset button?
— Reply to this email directly, view it on GitHub https://github.com/forkineye/ESPixelStick/issues/573#issuecomment-1300428319, or unsubscribe https://github.com/notifications/unsubscribe-auth/A34PPAV62HESDPAA5VBXHO3WGJV7VANCNFSM6AAAAAARR623A4 . You are receiving this because you authored the thread.Message ID: @.***>
Something may have happened to the Wemos. Have you tried another one, and does it do the same? Is it still flashed from before / can you access it via the web?
I tried another Wemos and was able to flash it. Thanks... I guess the first one is toast.
On Wed, Nov 2, 2022 at 11:48 AM Shelby Merrick @.***> wrote:
Something may have happened to the Wemos. Have you tried another one, and does it do the same? Is it still flashed from before / can you access it via the web?
— Reply to this email directly, view it on GitHub https://github.com/forkineye/ESPixelStick/issues/573#issuecomment-1300730536, or unsubscribe https://github.com/notifications/unsubscribe-auth/A34PPAQ2JOY5ESHA72O4NKTWGKELLANCNFSM6AAAAAARR623A4 . You are receiving this because you authored the thread.Message ID: @.***>
This looks to have been a hardware issue.
Ok, thanks.
On Fri, Nov 4, 2022 at 10:42 AM Martin Mueller @.***> wrote:
This looks to have been a hardware issue.
— Reply to this email directly, view it on GitHub https://github.com/forkineye/ESPixelStick/issues/573#issuecomment-1303664653, or unsubscribe https://github.com/notifications/unsubscribe-auth/A34PPAXYMGMPB4PRGCHCXGLWGUOE5ANCNFSM6AAAAAARR623A4 . You are receiving this because you authored the thread.Message ID: @.***>
--------- Instructions -------- Please provide answers directly below each section. --------- Instructions ---------
ESPixelStick Firmware Version ESPixelStick_Firmware-3.2
Hardware Version ESPixelStick v3.0
**Binary release or compiled yourself? Just trying to load the basics
Operating System (and version) Windows 11
Web Browser (and version) Chrome
Access Point Issue Loading from PC
Describe the bug I'm trying to use the ESPixelStick Flash Tool to flash the latest version and configure it for my network. I get this error. -= Building SPIFFS Image =- bin/win32/esp8266/mkspiffs -c spiffs/ -p 256 -b 4096 -s 131072 firmware/spiffs.bin /config.json /www/esps.css.gz /www/esps.js.gz /www/index.html.gz Done
-= Programming ESP8266 =- bin/win32/python3/python bin/upload.py --chip auto --baud 115200 --port COM5 --before default_reset --after hard_reset write_flash 0x0 firmware/pixel-3.2-1m128k.bin 0xDB000 firmware/spiffs.bin esptool.py v2.8 Serial port COM5 Connecting........____.............................. Traceback (most recent call last): File "bin/upload.py", line 19, in
esptool.main(sys.argv)
File "C:/Users/dismo/Downloads/ESPixelStick_Firmware-3.2/ESPixelStick_Firmware-3.2/bin/esptool\esptool.py", line 2883, in main
esp = ESPLoader.detect_chip(each_port, initial_baud, args.before, args.trace)
File "C:/Users/dismo/Downloads/ESPixelStick_Firmware-3.2/ESPixelStick_Firmware-3.2/bin/esptool\esptool.py", line 274, in detect_chip
detect_port.connect(connect_mode)
File "C:/Users/dismo/Downloads/ESPixelStick_Firmware-3.2/ESPixelStick_Firmware-3.2/bin/esptool\esptool.py", line 483, in connect
raise FatalError('Failed to connect to %s: %s' % (self.CHIP_NAME, last_error))
esptool.FatalError: Failed to connect to Espressif device: Timed out waiting for packet header
Done