ESP32-SOLO-1 on DevKitC_V4 not working

angelsinacento
Posts: 3
Joined: Tue Sep 18, 2018 8:30 am

ESP32-SOLO-1 on DevKitC_V4 not working

Postby angelsinacento » Tue Sep 18, 2018 9:06 am

Dear ESP32 forum members,

We recently got some ESP32-SOLO-1 chips on the ESP32_DevKitC_V4 board. We got these from Mouser Electronics in the Netherlands.
I have tried for several days without success to flash an example program, like the hello_world provided within ESP_IDF.

The make all command seems to work fine. The make flash command also seems to work fine (please see below):
  • s164904@s164904 MINGW32 ~/esp/hello_world
    $ python /home/s164904/esp/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32 --port COM9 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 /home/s164904/esp/hello_world/build/bootloader/bootloader.bin 0x10000 /home/s164904/esp/hello_world/build/hello-world.bin 0x8000 /home/s164904/esp/hello_world/build/partitions_singleapp.bin
    esptool.py v2.5.0
    Serial port COM9
    Connecting.....
    Chip is ESP32D0WDQ5 (revision 1)
    Features: WiFi, BT, Single Core
    MAC: 24:0a:c4:85:c6:14
    Uploading stub...
    Running stub...
    Stub running...
    Configuring flash size...
    Auto-detected Flash size: 4MB
    Flash params set to 0x0220
    Compressed 22800 bytes to 13462...
    Wrote 22800 bytes (13462 compressed) at 0x00001000 in 1.2 seconds (effective 152.8 kbit/s)...
    Hash of data verified.
    Compressed 151744 bytes to 73195...
    Wrote 151744 bytes (73195 compressed) at 0x00010000 in 6.5 seconds (effective 187.1 kbit/s)...
    Hash of data verified.
    Compressed 3072 bytes to 103...
    Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 1273.6 kbit/s)...
    Hash of data verified.

    Leaving...
    Hard resetting via RTS pin...
When I run the make monitor command, I get the following:
  • $ make monitor
    Python requirements from C:/msys32/home/s164904/esp/esp-idf/requirements.txt are satisfied.
    MONITOR
    --- idf_monitor on COM9 115200 ---
    --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
    ets Jun 8 2016 00:22:57

    rst:0x1 (POWERON_RESET),boot:0x13 (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:0x3fff0018,len:4
    load:0x3fff001c,len:6172
    load:0x40078000,len:9392
    load:0x40080400,len:7128
    entry 0x400807a0
    I (28) boot: ESP-IDF v3.2-dev-1039-geea49d250 2nd stage bootloader
    I (28) boot: compile time 10:40:01
    I (28) boot: Enabling RNG early entropy source...
    I (34) boot: SPI Speed : 40MHz
    I (39) boot: SPI Mode : DIO
    I (43) boot: SPI Flash Size : 4MB
    I (47) boot: Partition Table:
    I (50) boot: ## Label Usage Type ST Offset Length
    I (57) boot: 0 nvs WiFi data 01 02 00009000 00006000
    I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000
    I (72) boot: 2 factory factory app 00 00 00010000 00100000
    I (80) boot: End of partition table
    I (84) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x077b0 ( 30640) map
    I (104) esp_image: segment 1: paddr=0x000177d8 vaddr=0x3ffb0000 size=0x0212c ( 8492) load
    I (107) esp_image: segment 2: paddr=0x0001990c vaddr=0x3ffb212c size=0x00000 ( 0) load
    I (111) esp_image: segment 3: paddr=0x00019914 vaddr=0x40080000 size=0x00400 ( 1024) load
    0x40080000: _WindowOverflow4 at C:/msys32/home/s164904/esp/esp-idf/components/freertos/xtensa_vectors.S:16
    85

    I (120) esp_image: segment 4: paddr=0x00019d1c vaddr=0x40080400 size=0x062f4 ( 25332) load
    I (139) esp_image: segment 5: paddr=0x00020018 vaddr=0x400d0018 size=0x123f0 ( 74736) map
    0x400d0018: _flash_cache_start at ??:?

    I (166) esp_image: segment 6: paddr=0x00032410 vaddr=0x400866f4 size=0x02c7c ( 11388) load
    0x400866f4: xRingbufferSend at C:/msys32/home/s164904/esp/esp-idf/components/freertos/ringbuf.c:992

    I (171) esp_image: segment 7: paddr=0x00035094 vaddr=0x400c0000 size=0x00000 ( 0) load
    I (172) esp_image: segment 8: paddr=0x0003509c vaddr=0x50000000 size=0x00000 ( 0) load
    I (187) boot: Loaded app from partition at offset 0x10000
    I (187) boot: Disabling RNG early entropy source...
    I (193) cpu_start: Pro cpu up.
    I (197) cpu_start: Starting app cpu, entry point is 0x40080ea0
    0x40080ea0: call_start_cpu1 at C:/msys32/home/s164904/esp/esp-idf/components/esp32/cpu_start.c:228
So I assume that there is indeed communication between the board and the laptop through the COM port. However, nothing else happens, there is no Hello World is printed on the monitor. After a few seconds the watchdog timer seems to generate a reset:
  • ets Jun 8 2016 00:22:57

    rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (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:0x3fff0018,len:4
    load:0x3fff001c,len:6172
    load:0x40078000,len:9392
    load:0x40080400,len:7128
    entry 0x400807a0
    I (28) boot: ESP-IDF v3.2-dev-1039-geea49d250 2nd stage bootloader
    I (29) boot: compile time 10:40:01
    I (29) boot: Enabling RNG early entropy source...
    I (35) boot: SPI Speed : 40MHz
    I (39) boot: SPI Mode : DIO
    I (43) boot: SPI Flash Size : 4MB
    I (47) boot: Partition Table:
    I (50) boot: ## Label Usage Type ST Offset Length
    I (58) boot: 0 nvs WiFi data 01 02 00009000 00006000
    I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000
    I (73) boot: 2 factory factory app 00 00 00010000 00100000
    I (80) boot: End of partition table
    I (84) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x077b0 ( 30640) map
    I (104) esp_image: segment 1: paddr=0x000177d8 vaddr=0x3ffb0000 size=0x0212c ( 8492) load
    I (108) esp_image: segment 2: paddr=0x0001990c vaddr=0x3ffb212c size=0x00000 ( 0) load
    I (111) esp_image: segment 3: paddr=0x00019914 vaddr=0x40080000 size=0x00400 ( 1024) load
    0x40080000: _WindowOverflow4 at C:/msys32/home/s164904/esp/esp-idf/components/freertos/xtensa_vectors.S:16
    85

    I (120) esp_image: segment 4: paddr=0x00019d1c vaddr=0x40080400 size=0x062f4 ( 25332) load
    I (139) esp_image: segment 5: paddr=0x00020018 vaddr=0x400d0018 size=0x123f0 ( 74736) map
    0x400d0018: _flash_cache_start at ??:?

    I (166) esp_image: segment 6: paddr=0x00032410 vaddr=0x400866f4 size=0x02c7c ( 11388) load
    0x400866f4: xRingbufferSend at C:/msys32/home/s164904/esp/esp-idf/components/freertos/ringbuf.c:992

    I (171) esp_image: segment 7: paddr=0x00035094 vaddr=0x400c0000 size=0x00000 ( 0) load
    I (173) esp_image: segment 8: paddr=0x0003509c vaddr=0x50000000 size=0x00000 ( 0) load
    I (187) boot: Loaded app from partition at offset 0x10000
    I (188) boot: Disabling RNG early entropy source...
    I (193) cpu_start: Pro cpu up.
    I (197) cpu_start: Starting app cpu, entry point is 0x40080ea0
    0x40080ea0: call_start_cpu1 at C:/msys32/home/s164904/esp/esp-idf/components/esp32/cpu_start.c:228
This reset happens again and again and I never get the expected Hello World output. I really have no idea on what the problem might be. I tried several times to follow the getting started guide in the ESP32 website, but it just doesn't work. Some things that I found weird are:

Notice that the last message in the monitor is
  • entry 0x400807a0
, and this is always the last message before the watchdog timer resets the board.
Moreover, notice that the monitor also shows
  • 0x400d0018: _flash_cache_start at ??:?
. Is this a problem?

I also tried flashing Arduino examples for ESP32 without success.
I would very much appreciate some help or direction into which I could proceed to troubleshoot this issue.

Kind regards,
Angel Molina

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

Re: ESP32-SOLO-1 on DevKitC_V4 not working

Postby ESP_igrr » Tue Sep 18, 2018 3:18 pm

ESP32-SOLO is a single core module, so you need to enable "Run FreeRTOS on first core only" option in menuconfig, under component config > freertos.

angelsinacento
Posts: 3
Joined: Tue Sep 18, 2018 8:30 am

Re: ESP32-SOLO-1 on DevKitC_V4 not working

Postby angelsinacento » Wed Sep 19, 2018 3:37 pm

How come I didn't think of that.
Thank you! I'll give it a try

Who is online

Users browsing this forum: Bing [Bot] and 9 guests