RTCWDT_RTC_RESET symptom of what kind of error?

onehorse
Posts: 70
Joined: Mon Feb 15, 2016 1:35 am

Re: RTCWDT_RTC_RESET symptom of what kind of error?

Postby onehorse » Tue Dec 06, 2016 2:49 am

Thanks for looking at the schematic; I don't expect I've made an egregious error.

I was simply flashing a blink program using the Arduino IDE. Do you want these binary files?

Is there some place to get the firmware for using the ESP32 flash tool? With no binaries I never got a proper response using this tool, not sure why. At least with the Arduino IDE the flash process seemed to be successful.

If you tell me what to do I will would be happy to have your help to debug this board. Alternatively, I could send it to you to play with, since I have the next version with the smaller but DIO-compatible flash coming soon.

ESP_igrr
Posts: 1675
Joined: Tue Dec 01, 2015 8:37 am

Re: RTCWDT_RTC_RESET symptom of what kind of error?

Postby ESP_igrr » Tue Dec 06, 2016 3:34 am

Yes, please upload the bootloader.bin file which you are flashing using Arduino IDE.

onehorse
Posts: 70
Joined: Mon Feb 15, 2016 1:35 am

Re: RTCWDT_RTC_RESET symptom of what kind of error?

Postby onehorse » Tue Dec 06, 2016 4:54 am

I've attached some files; not sure which ones you need to see.

Simple blink produces this verbose output:

Code: Select all

esptool.py v2.0-dev
Connecting...
Uploading stub...
Running stub...
Stub running...
Attaching SPI flash...
Configuring flash size...
Compressed 5264 bytes to 3363...

Writing at 0x00001000... (100 %) 
Wrote 5264 bytes (3363 compressed) at 0x00001000 in 0.3 seconds (effective 141.8 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 78...

Writing at 0x00008000... (100 %) 
Wrote 3072 bytes (78 compressed) at 0x00008000 in 0.0 seconds (effective 1638.4 kbit/s)...
Hash of data verified.
Compressed 225808 bytes to 67939...

Writing at 0x00010000... (20 %) 
Writing at 0x00014000... (40 %) 
Writing at 0x00018000... (60 %) 
Writing at 0x0001c000... (80 %) 
Writing at 0x00020000... (100 %) 
Wrote 225808 bytes (67939 compressed) at 0x00010000 in 6.3 seconds (effective 286.9 kbit/s)...
Hash of data verified.

Leaving...
which looks OK, but I get no blinking led and restarts every second.

Please let me know if I got the wrong files...
Attachments
partitions_singleapp.zip
bootloader.bin in esp32/tools/sdk/bin
(3.59 KiB) Downloaded 163 times
build.options.zip
tmp build files
(3.1 MiB) Downloaded 152 times

ESP_igrr
Posts: 1675
Joined: Tue Dec 01, 2015 8:37 am

Re: RTCWDT_RTC_RESET symptom of what kind of error?

Postby ESP_igrr » Tue Dec 06, 2016 10:20 am

Thanks. The files look correct. I have flashed your bootloader to my DevKitC board and unfortunately, it worked fine (if it didn't, troubleshooting would probably be very trivial).

Could you please try replacing bootloader.bin file in your "arduino-esp32/tools/sdk/bin/" directory with the one attached? Then flash the board again. Thanks.
Attachments
bootloader.zip
bootloader with DIO mode and 40MHz
(5.17 KiB) Downloaded 185 times

onehorse
Posts: 70
Joined: Mon Feb 15, 2016 1:35 am

Re: RTCWDT_RTC_RESET symptom of what kind of error?

Postby onehorse » Wed Dec 07, 2016 8:35 pm

Took me a day to figure out how to get the ESP32 to compile on Windows 10. I tried your bootloader (with DOUT flash mode) and it is working! Led is flashing and serial is outputting. Will you add DOUT to the flash options like you did for the ESP8285 and ESP8266 so I don't have to use a special bootloader when the core is updated? Thank you for your help!

Here is the output in case you put some diagnostics into the bootloader:

Code: Select all

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun  8 2016 00:22:57

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:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3ffc0008,len:0
load:0x3ffc0008,len:3868
load:0x40078000,len:5028
load:0x40080000,len:260
entry 0x40080034
[0;32mI (19) boot: Espressif ESP32 2nd stage bootloader v. V0.1[0m
[0;32mI (24) boot: compile time 18:15:32[0m
D (28) esp_image: reading image header @ 0x1000[0m
D (32) boot: magic e9[0m
D (35) boot: segments 04[0m
D (37) boot: spi_mode 03[0m
D (40) boot: spi_speed 00[0m
D (42) boot: spi_size 01[0m
[0;32mI (45) boot: SPI Speed      : 40MHz[0m
[0;32mI (49) boot: SPI Mode       : DOUT[0m
[0;32mI (53) boot: SPI Flash Size : 2MB[0m
[0;32mI (57) boot: Partition Table:[0m
[0;32mI (61) boot: ## Label            Usage          Type ST Offset   Length[0m
D (68) bootloader_flash: mmu set paddr=00000000 count=1[0m
D (73) boot: mapped partition table 0x8000 at 0x3f408000[0m
D (79) boot: load partition table entry 0x3f408000[0m
D (84) boot: type=1 subtype=2[0m
[0;32mI (87) boot:  0 nvs              WiFi data        01 02 00009000 00006000[0m
D (94) boot: load partition table entry 0x3f408020[0m
D (99) boot: type=1 subtype=1[0m
[0;32mI (102) boot:  1 phy_init         RF data          01 01 0000f000 00001000[0m
D (110) boot: load partition table entry 0x3f408040[0m
D (114) boot: type=0 subtype=0[0m
[0;32mI (118) boot:  2 factory          factory app      00 00 00010000 00100000[0m
D (125) boot: load partition table entry 0x3f408060[0m
D (130) boot: type=ff subtype=ff[0m
[0;32mI (133) boot: End of partition table[0m
[0;32mI (138) boot: Loading app partition at offset 00010000[0m
D (143) esp_image: reading image header @ 0x10000[0m
D (148) esp_image: reading 9 image segments[0m
D (152) bootloader_flash: mmu set paddr=00010000 count=2[0m
D (228) bootloader_flash: mmu set paddr=00020000 count=1[0m
D (243) bootloader_flash: mmu set paddr=00020000 count=1[0m
D (254) bootloader_flash: mmu set paddr=00020000 count=1[0m
D (256) bootloader_flash: mmu set paddr=00020000 count=2[0m
D (337) bootloader_flash: mmu set paddr=00030000 count=1[0m
D (339) bootloader_flash: mmu set paddr=00030000 count=2[0m
D (374) bootloader_flash: mmu set paddr=00040000 count=1[0m
D (434) bootloader_flash: mmu set paddr=00040000 count=1[0m
D (434) esp_image: reading checksum block at 0x4d5e0[0m
D (435) esp_image: reading image header @ 0x10000[0m
D (438) boot: bin_header: 233 9 2 0 40080c18[0m
[0;32mI (442) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
D (450) boot: found drom segment, map from 00020010 to 3f400010[0m
[0;32mI (456) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x031f4 ( 12788) map[0m
[0;32mI (465) boot: segment 2: paddr=0x00023204 vaddr=0x3ffc2c40 size=0x02528 (  9512) load[0m
D (473) bootloader_flash: mmu set paddr=00020000 count=1[0m
[0;32mI (483) boot: segment 3: paddr=0x00025734 vaddr=0x40080000 size=0x00400 (  1024) load[0m
D (487) bootloader_flash: mmu set paddr=00020000 count=1[0m
[0;32mI (493) boot: segment 4: paddr=0x00025b3c vaddr=0x40080400 size=0x126c8 ( 75464) load[0m
D (501) bootloader_flash: mmu set paddr=00020000 count=2[0m
[0;32mI (546) boot: segment 5: paddr=0x0003820c vaddr=0x400c0000 size=0x00000 (     0) load[0m
D (546) bootloader_flash: mmu set paddr=00030000 count=1[0m
[0;32mI (549) boot: segment 6: paddr=0x00038214 vaddr=0x00000000 size=0x07df4 ( 32244) [0m
D (557) boot: found irom segment, map from 00040018 to 400d0018[0m
[0;32mI (562) boot: segment 7: paddr=0x00040010 vaddr=0x400d0018 size=0x0d5c0 ( 54720) map[0m
[0;32mI (571) boot: segment 8: paddr=0x0004d5d8 vaddr=0x50000000 size=0x00008 (     8) load[0m
D (579) bootloader_flash: mmu set paddr=00040000 count=1[0m
D (585) boot: configure drom and irom and start[0m
D (589) boot: start: 0x40080c18[0m
ÿtest blue
test blue
test blue
test blue
test blue
test blue

ESP_igrr
Posts: 1675
Joined: Tue Dec 01, 2015 8:37 am

Re: RTCWDT_RTC_RESET symptom of what kind of error?

Postby ESP_igrr » Thu Dec 08, 2016 2:59 am

Great to know that it works!
DOUT is already available as one of the modes in menuconfig.

Edit: reading this again, i think you meant adding DOUT as an Arduino option. Yes, we should, once we figure out how to build enough of ESP-IDF in Arduino IDE to make such configuration possible.

Who is online

Users browsing this forum: No registered users and 17 guests