Node MCU infinite reboot
Posted: Mon Apr 23, 2018 11:20 pmI have the kit
https://www.amazon.com/HiLetgo-Internet ... B010O1G1ES
Even though it says ESP8266, I was fortunate to get the kit with a ESP32, at least that is what it says when I read the flash_id
So, i tried following the instructions at
https://nodemcu.readthedocs.io/en/master/en/flash/
I erased the chip and here is the command and the output
I used both the cloud service and the docker to build my images. In both the cases they were basic images with default selected packages.
My initial error was
When I tried connecting using ESPlorer, I got the following error
I then searched around in the forums and found out that the error was simple and it was looking for the firmware at address 0x1000 and so I should flash, with that address.
So, after erasing the chip once again successfully with the same result as above, i tried this
Now here is where it just reboots infinitely, as in the below image
With this section repeating again and again,
i looked at the issues on Git and on other forums, made sure the flash mode is "dio" (when reading the flash id it said dual core, so was confident about this). Also tried the flash size of 4m, that didn't work either. Last but not the least tried different cables, yet the same result.
If you need any further information let me know.
Thank you in advance.
PS - Sorry about the long post, wanted to make sure I give you all the information.
https://www.amazon.com/HiLetgo-Internet ... B010O1G1ES
Even though it says ESP8266, I was fortunate to get the kit with a ESP32, at least that is what it says when I read the flash_id
Code: Select all
sid@sid-laptop:~/project/nodemcu-firmware$ esptool.py v2.3.1
Connecting........_
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Manufacturer: c8
Device: 4016
Detected flash size: 4MB
Hard resetting via RTS pin...So, i tried following the instructions at
https://nodemcu.readthedocs.io/en/master/en/flash/
I erased the chip and here is the command and the output
Code: Select all
sid@sid-laptop:~/project/nodemcu-firmware$ esptool.py --port /dev/ttyUSB0 erase_flash
esptool.py v2.3.1
Connecting........_
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 0.5s
Hard resetting via RTS pin...I used both the cloud service and the docker to build my images. In both the cases they were basic images with default selected packages.
My initial error was
Code: Select all
sid@sid-laptop:~/project/nodemcu-firmware$ esptool.py --port /dev/ttyUSB0 write_flash -fm dio 0x00000 ./bin/nodemcu_integer_master_20180424-0332.bin
esptool.py v2.3.1
Connecting........_
Detecting chip type... ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 425952 bytes to 274058...
Wrote 425952 bytes (274058 compressed) at 0x00000000 in 24.2 seconds (effective 140.6 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...When I tried connecting using ESPlorer, I got the following error
I then searched around in the forums and found out that the error was simple and it was looking for the firmware at address 0x1000 and so I should flash, with that address.
So, after erasing the chip once again successfully with the same result as above, i tried this
Code: Select all
sid@sid-laptop:~/project/nodemcu-firmware$ esptool.py --port /dev/ttyUSB0 write_flash -fm dio 0x01000 ./bin/nodemcu_integer_master_20180424-0332.bin
esptool.py v2.3.1
Connecting........_
Detecting chip type... ESP32
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 425952 bytes to 274058...
Wrote 425952 bytes (274058 compressed) at 0x00001000 in 24.3 seconds (effective 140.4 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...Now here is where it just reboots infinitely, as in the below image
With this section repeating again and again,
Code: Select all
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x01,hd_drv:0x00,wp_drv:0x04
mode:DIO, clock div:2
load:0x260513e7,len:0
load:0x46007200,len:65534
1162 mmu set 00010000, pos 00010000
load:0x65920020,len:-491131
1162 mmu set 00020000, pos 00020000
1162 mmu set 00030000, pos 00030000
1162 mmu set 00040000, pos 00040000
1162 mmu set 00050000, pos 00050000
1162 mmu set 00060000, pos 00060000
1162 mmu set 00070000, pos 00070000
1162 mmu set 00080000, pos 00080000
1162 mmu set 00090000, pos 00090000
1162 mmu set 000a0000, pos 000a0000
1162 mmu set 000b0000, pos 000b0000
ets Jun 8 2016 00:22:57
i looked at the issues on Git and on other forums, made sure the flash mode is "dio" (when reading the flash id it said dual core, so was confident about this). Also tried the flash size of 4m, that didn't work either. Last but not the least tried different cables, yet the same result.
If you need any further information let me know.
Thank you in advance.
PS - Sorry about the long post, wanted to make sure I give you all the information.