Problem with ESP-WROVER-KIT-VB

#1

If you are asking a question, please follow this template:

  1. My goal is: Getting started with ESP32 with MongooseOS
  2. My actions are:
  • bought the ESP-WROVER-KIT-VB
  • installed MOS on Linux (Fedora)
  • followed the instructions to build the demo-js app.
  • flashed the firmware.
  • crashes.
    Repeated also for demo-c from Github. Same result, crashes, panic.
  1. The result I see is: crashed.
    This is the log of the demo-c app from mos console, repeating endlessly:
    [Jul 23 08:30:14.115] Rebooting...
    [Jul 23 08:30:14.115] ets Jun  8 2016 00:22:57
    [Jul 23 08:30:14.130] 
    [Jul 23 08:30:14.130] rst:0xc (SW_CPU_RESET),boot:0x1e (SPI_FAST_FLASH_BOOT)
    [Jul 23 08:30:14.130] configsip: 0, SPIWP:0xee
    [Jul 23 08:30:14.130] clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    [Jul 23 08:30:14.130] mode:DIO, clock div:1
    [Jul 23 08:30:14.146] load:0x3fff0018,len:4
    [Jul 23 08:30:14.146] load:0x3fff001c,len:6188
    [Jul 23 08:30:14.146] load:0x40078000,len:9588
    [Jul 23 08:30:14.146] load:0x40080400,len:6968
    [Jul 23 08:30:14.146] entry 0x40080740
    [Jul 23 08:30:14.146] I (29) boot: ESP-IDF v3.2-r6 2nd stage bootloader
    [Jul 23 08:30:14.162] I (29) boot: compile time 15:26:14
    [Jul 23 08:30:14.162] I (29) boot: Enabling RNG early entropy source...
    [Jul 23 08:30:14.162] I (34) qio_mode: Enabling default flash chip QIO
    [Jul 23 08:30:14.178] I (39) boot: SPI Speed      : 80MHz
    [Jul 23 08:30:14.178] I (43) boot: SPI Mode       : QIO
    [Jul 23 08:30:14.178] I (47) boot: SPI Flash Size : 4MB
    [Jul 23 08:30:14.178] I (51) boot: Partition Table:
    [Jul 23 08:30:14.194] I (55) boot: ## Label            Usage          Type ST Offset   Length   Flags
    [Jul 23 08:30:14.194] I (63) boot:  0 nvs              WiFi data        01 02 00009000 00004000 00000000
    [Jul 23 08:30:14.210] I (71) boot:  1 otadata          OTA data         01 00 0000d000 00002000 00000000
    [Jul 23 08:30:14.210] I (79) boot:  2 app_0            OTA app          00 10 00010000 00180000 00000000
    [Jul 23 08:30:14.226] I (87) boot:  3 fs_0             SPIFFS           01 82 00190000 00040000 00000000
    [Jul 23 08:30:14.226] I (96) boot:  4 app_1            OTA app          00 11 001d0000 00180000 00000000
    [Jul 23 08:30:14.242] I (104) boot:  5 fs_1             SPIFFS           01 82 00350000 00040000 00000000
    [Jul 23 08:30:14.242] I (112) boot: End of partition table
    [Jul 23 08:30:14.242] I (117) boot: OTA data 0: seq 0x00000001, st 0x10, CRC 0x157a2b85, valid? 1
    [Jul 23 08:30:14.258] I (124) boot: OTA data 1: seq 0x00000000, st 0x00, CRC 0x00000000, valid? 0
    [Jul 23 08:30:14.258] I (132) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x41d80 (269696) map
    [Jul 23 08:30:14.338] I (211) esp_image: segment 1: paddr=0x00051da8 vaddr=0x3ffbdb60 size=0x029ec ( 10732) load
    [Jul 23 08:30:14.338] I (214) esp_image: segment 2: paddr=0x0005479c vaddr=0x40080000 size=0x00400 (  1024) load
    [Jul 23 08:30:14.354] I (218) esp_image: segment 3: paddr=0x00054ba4 vaddr=0x40080400 size=0x0b46c ( 46188) load
    [Jul 23 08:30:14.354] I (241) esp_image: segment 4: paddr=0x00060018 vaddr=0x400d0018 size=0x10f2d4 (1110740) map
    [Jul 23 08:30:14.658] I (531) esp_image: segment 5: paddr=0x0016f2f4 vaddr=0x4008b86c size=0x09c34 ( 39988) load
    [Jul 23 08:30:14.674] I (555) boot: Loaded app from partition at offset 0x10000
    [Jul 23 08:30:14.690] I (555) boot: Disabling RNG early entropy source...
    [Jul 23 08:30:14.690] I (556) cpu_start: Pro cpu up.
    [Jul 23 08:30:14.690] I (559) cpu_start: Single core mode
    [Jul 23 08:30:14.690] I (564) heap_init: Initializing. RAM available for dynamic allocation:
    [Jul 23 08:30:14.706] I (571) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
    [Jul 23 08:30:14.706] I (577) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
    [Jul 23 08:30:14.722] I (583) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
    [Jul 23 08:30:14.722] I (589) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAM
    [Jul 23 08:30:14.722] I (595) heap_init: At 3FFCFA10 len 000105F0 (65 KiB): DRAM
    [Jul 23 08:30:14.738] I (601) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM
    [Jul 23 08:30:14.738] I (608) heap_init: At 40078000 len 00008000 (32 KiB): IRAM
    [Jul 23 08:30:14.754] I (614) heap_init: At 400954A0 len 0000AB60 (42 KiB): IRAM
    [Jul 23 08:30:14.754] I (620) cpu_start: Pro cpu start user code
    [Jul 23 08:30:14.754] Guru Meditation Error: Core  0 panic'ed (IllegalInstruction). Exception was unhandled.
    [Jul 23 08:30:14.770] Memory dump at 0x400d10bc: 9e27fff0 00000000 00000000
    [Jul 23 08:30:14.770] Core 0 register dump:
    [Jul 23 08:30:14.770] PC      : 0x400d10c1  PS      : 0x00060d30  A0      : 0x80080557  A1      : 0x3ffe3bf0  
    [Jul 23 08:30:14.786] A2      : 0x00000000  A3      : 0x3ffc75d4  A4      : 0x3ffbe51c  A5      : 0x3ffc75b8  
    [Jul 23 08:30:14.786] A6      : 0x3ffc75b8  A7      : 0x3ffe3b64  A8      : 0x800d10b5  A9      : 0x3ffe3bd0  
    [Jul 23 08:30:14.802] A10     : 0x3ffbe51c  A11     : 0x0100000c  A12     : 0x40080bac  A13     : 0x40080714  
    [Jul 23 08:30:14.802] A14     : 0x00000000  A15     : 0x00000400  SAR     : 0x00000017  EXCCAUSE: 0x00000000  
    [Jul 23 08:30:14.818] EXCVADDR: 0x00000000  LBEG    : 0x400d12e9  LEND    : 0x400d1302  LCOUNT  : 0x00000007  
    [Jul 23 08:30:14.818] 
    [Jul 23 08:30:14.818] Backtrace: 0x400d10c1 0x40080554 0x400806bb 0x40078eba 0x400792bd 0x4008078e 0x40007c31 0x4000073d
    [Jul 23 08:30:14.834] 
    [Jul 23 08:30:14.834] --- BEGIN CORE DUMP ---
    [Jul 23 08:30:14.834] mos: catching core dump
    [Jul 23 08:30:14.850] ---- END CORE DUMP ----
    [Jul 23 08:30:14.851] mos: wrote to /home/mos/mos/app2/core-app2-esp32-20190723-083014.112170879 (135 bytes)
    [Jul 23 08:30:14.851] mos: analyzing core dump
    Core dump by app2/esp32 1.0 20190723-152655
    Using ELF file at: /home/mos/mos/app2/build/objs/app2.elf
    Using Docker image: docker.io/mgos/esp32-build:3.2-r6
    Running docker run --rm -v /home/mos/mos/app2/build/objs/app2.elf:/fw.elf -v /home/mos/mos/app2/core-app2-esp32-20190723-083014.112170879:/core -v /home/mos/mos/app2:/home/mos/mos/app2 docker.io/mgos/esp32-build:3.2-r6 bash -c /usr/local/bin/serve_core.py --rom=/opt/Espressif/rom/rom.bin --rom_addr=0x40000000 --xtensa_addr_fixup=true /fw.elf /core & $MGOS_TARGET_GDB /fw.elf -ex 'target remote 127.0.0.1:1234' -ex 'set confirm off' -ex bt -ex quit
    [Jul 23 08:30:14.851] mos: exec: "docker": executable file not found in $PATH
    [Jul 23 08:30:14.851] Rebooting...
  1. My expectation & question is: The demo app should just work.
#2

Same result here but with Debian 10, chip espressif esp32-wroom-32, tried also building locally with docker, same result, Guru Meditation Error: Core 0 panic’ed (IllegalInstruction). Exception was unhanded

#3

Are you also seeing this on the ESP-WROVER-KIT? Mine is the latest version which uses the ESP32-WROVER-B chip.

I also have another board, DevKitC-v2, which uses ESP-WROOM-32 chip, but that one is running just fine.

The ESP-WROVER-KIT-VB is a much newer board than the DevKitC-v2, so it seems Mongoose-OS needs to be ported to the board correctly?

#4

This is my chip info and link when I bought it

sptool.py v2.7-dev
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…_____…
Detecting chip type… ESP32
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 24:6f:28:02:d1:38