ESP32 WROVER-IE module doesn't boot

I try to use module ESP32 WROVER-IE (with 4Mb PsRAM chip) instead of my ESP32 WROOM32d with Mongoose OS. I wanted to test it, using simple project, like a “Hello world”, but afrer flashing and reboot, in output I see this information:

[Dec 24 20:06:57.404] ��������ښ�j%�(91) boot:  2 app_0            OTA app          00 10 00010000 00180000 00000001e[0m
[Dec 24 20:06:57.420] e[0;32mI (99) boot:  3 fs_0             FS               01 82 00190000 00040000 00000000e[0m
[Dec 24 20:06:57.420] e[0;32mI (107) boot:  4 app_1            OTA app          00 11 001d0000 00180000 00000001e[0m
[Dec 24 20:06:57.451] e[0;32mI (116) boot:  5 fs_1             FS               01 82 00350000 00040000 00000000e[0m
[Dec 24 20:06:57.451] e[0;32mI (124) boot: End of partition tablee[0m
[Dec 24 20:06:57.451] e[0;32mI (128) boot: OTA data 0: seq 0x00000001, st 0x10, CRC 0x157a2b85, valid? 1e[0m
[Dec 24 20:06:57.451] e[0;32mI (136) boot: OTA data 1: seq 0x00000000, st 0x00, CRC 0x00000000, valid? 0e[0m
[Dec 24 20:06:57.467] e[0;32mI (144) boot_comm: chip revision: 3, min. application chip revision: 0e[0m
[Dec 24 20:06:57.467] e[0;32mI (151) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x221b0 (139696) mape[0m
[Dec 24 20:06:57.528] e[0;32mI (200) esp_image: segment 1: paddr=0x000321d8 vaddr=0x3ffb0000 size=0x036fc ( 14076) loade[0m
[Dec 24 20:06:57.528] e[0;32mI (205) esp_image: segment 2: paddr=0x000358dc vaddr=0x40080000 size=0x0a73c ( 42812) loade[0m
[Dec 24 20:06:57.528] e[0;32mI (222) esp_image: segment 3: paddr=0x00040020 vaddr=0x400d0020 size=0x9cd30 (642352) mape[0m
[Dec 24 20:06:57.721] e[0;32mI (410) esp_image: segment 4: paddr=0x000dcd58 vaddr=0x4008a73c size=0x0ba20 ( 47648) loade[0m
[Dec 24 20:06:57.752] e[0;32mI (438) boot: Loaded app from partition at offset 0x10000e[0m
[Dec 24 20:06:57.752] e[0;32mI (438) boot: Disabling RNG early entropy source...e[0m
[Dec 24 20:06:57.752] e[0;32mI (439) cpu_start: Pro cpu up.e[0m
[Dec 24 20:06:57.800] e[0;32mI (442) cpu_start: Application information:e[0m
[Dec 24 20:06:57.800] e[0;32mI (447) cpu_start: Project name:     test-overload-temperature-e[0m
[Dec 24 20:06:57.800] e[0;32mI (454) cpu_start: App version:      2.20.0e[0m
[Dec 24 20:06:57.800] e[0;32mI (459) cpu_start: Compile time:     Dec 24 2022 17:01:59e[0m
[Dec 24 20:06:57.800] e[0;32mI (465) cpu_start: ELF file SHA256:  f20f7dda70baa341...e[0m
[Dec 24 20:06:57.800] e[0;32mI (471) cpu_start: ESP-IDF:          4.2-r8e[0m
[Dec 24 20:06:57.800] e[0;32mI (476) cpu_start: Starting app cpu, entry point is 0x400807ace[0m
[Dec 24 20:06:57.800] e[0;32mI (0) cpu_start: App cpu up.e[0m
[Dec 24 20:06:57.800] e[0;32mI (486) heap_init: Initializing. RAM available for dynamic allocation:e[0m
[Dec 24 20:06:57.816] e[0;32mI (493) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAMe[0m
[Dec 24 20:06:57.816] e[0;32mI (499) heap_init: At 3FFCDC80 len 00012380 (72 KiB): DRAMe[0m
[Dec 24 20:06:57.832] e[0;32mI (505) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAMe[0m
[Dec 24 20:06:57.832] e[0;32mI (512) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAMe[0m
[Dec 24 20:06:57.832] e[0;32mI (518) heap_init: At 4009615C len 00009EA4 (39 KiB): IRAMe[0m
[Dec 24 20:06:57.893] e[0;32mI (524) cpu_start: Pro cpu start user codee[0m
[Dec 24 20:06:57.893] e[0;32mI (542) spi_flash: detected chip: generice[0m
[Dec 24 20:06:57.893] e[0;32mI (542) spi_flash: flash io: dioe[0m
[Dec 24 20:06:57.893] e[0;32mI (542) cpu_start: Starting scheduler on PRO CPU.e[0m
[Dec 24 20:06:57.893] e[0;32mI (0) cpu_start: Starting scheduler on APP CPU.e[0m
[Dec 24 20:06:57.893] 
[Dec 24 20:06:57.893] 
[Dec 24 20:06:57.893] mgos_freertos.c:155     test-overload-temperature- 1.0 (20221224-170431)
[Dec 24 20:06:57.893] mgos_freertos.c:157     Mongoose OS 2.20.0 (20221224-170431/2.20.0-g1885c0f)
[Dec 24 20:06:57.893] mgos_freertos.c:161     CPU: 160 MHz, FreeRTOS 8.2.0, heap: 209428 total, 177484 free
[Dec 24 20:06:57.893] mgos_freertos.c:163     Newlib 3.0.0
[Dec 24 20:06:57.895] esp32_main.c:65         ESP-IDF 4.2-r8
[Dec 24 20:06:57.940] esp32_main.c:68         Boot partition: app_0; flash: 4M
[Dec 24 20:06:57.940] mongoose.c:15766        Mongoose 6.18, LwIP 2.1.3
[Dec 24 20:06:57.940] mongoose.c:4932         mbed TLS 2.16.11-cesanta1
[Dec 24 20:06:57.940] mgos_vfs_dev.c:73       nvs: esp32part ({"label": "nvs"}), size 16384
[Dec 24 20:06:57.940] mgos_vfs_dev.c:73       otadata: esp32part ({"label": "otadata"}), size 8192
[Dec 24 20:06:57.940] mgos_vfs_dev.c:73       fs_0: esp32part ({"label": "fs_0"}), size 262144
[Dec 24 20:06:57.940] mgos_vfs_dev.c:73       fs_1: esp32part ({"label": "fs_1"}), size 262144
[Dec 24 20:06:57.942] mgos_vfs.c:174          /: SPIFFS @ fs_0, opts {"bs":4096,"ps":256,"es":4096}
[Dec 24 20:06:58.381] mgos_vfs.c:347          /: size 233681, used: 33383, free: 200298
[Dec 24 20:06:58.601] mgos_sys_config.c:470   MAC: b8:d6:1a:ab:1d:b4
[Dec 24 20:06:58.601] mgos_sys_config.c:478   WDT: 30 seconds
[Dec 24 20:06:58.601] mgos_wifi.c:307         WiFi mode: AP
[Dec 24 20:06:58.650] I (1317) wifi:wifi driver task: 3ffcfbfc, prio:23, stack:6656, core=0
[Dec 24 20:06:58.650] I (1327) wifi:wifi firmware version: df5b09d
[Dec 24 20:06:58.650] I (1337) wifi:wifi certification version: v7.0
[Dec 24 20:06:58.650] I (1337) wifi:config NVS flash: enabled
[Dec 24 20:06:58.650] I (1337) wifi:config nano formating: disabled
[Dec 24 20:06:58.650] I (1347) wifi:Init data frame dynamic rx buffer num: 16
[Dec 24 20:06:58.650] I (1347) wifi:Init management frame dynamic rx buffer num: 16
[Dec 24 20:06:58.680] I (1357) wifi:Init management short buffer num: 32
[Dec 24 20:06:58.680] I (1357) wifi:Init dynamic tx buffer num: 16
[Dec 24 20:06:58.680] I (1367) wifi:Init static rx buffer size: 1600
[Dec 24 20:06:58.680] I (1367) wifi:Init static rx buffer num: 4
[Dec 24 20:06:58.680] I (1377) wifi:Init dynamic rx buffer num: 16
[Dec 24 20:06:58.680] e[0;32mI (1377) wifi_init: rx ba win: 4e[0m
[Dec 24 20:06:58.680] e[0;32mI (1377) wifi_init: tcpip mbox: 32e[0m
[Dec 24 20:06:58.680] e[0;32mI (1387) wifi_init: udp mbox: 6e[0m
[Dec 24 20:06:58.696] e[0;32mI (1387) wifi_init: tcp mbox: 6e[0m
[Dec 24 20:06:58.696] e[0;32mI (1397) wifi_init: tcp tx win: 5744e[0m
[Dec 24 20:06:58.696] e[0;32mI (1397) wifi_init: tcp rx win: 5744e[0m
[Dec 24 20:06:58.696] e[0;32mI (1397) wifi_init: tcp mss: 1440e[0m
[Dec 24 20:06:58.712] e[0;32mI (1407) wifi_init: WiFi IRAM OP enablede[0m
[Dec 24 20:06:58.712] e[0;32mI (1407) wifi_init: WiFi RX IRAM OP enablede[0m
[Dec 24 20:06:58.712] esp32_wifi.c:483        WiFi AP: SSID Mongoose_AB1DB4, channel 6
[Dec 24 20:06:59.191] esp32_wifi.c:663        WiFi AP: protocol BGN (0x7)
[Dec 24 20:06:59.222] e[0;32mI (1897) phy_init: phy_version 4660,0162888,Dec 23 2020e[0m
[Dec 24 20:06:59.222] e[0;33mW (1907) phy_init: failed to load RF calibration data (0x1102), falling back to full calibratione[0m
read err Access is denied.

Serial ports changed!
Ports available:
COM1

Serial ports changed!
Ports available:
COM1
COM8

Serial ports changed!
Ports available:
COM1

Serial ports changed!
Ports available:
COM1
COM8

Serial ports changed!
Ports available:
COM1

Serial ports changed!
Ports available:
COM1
COM8

After this my COM port is like in circle rebooting.
I use this firmware with ESP32 WROOM32d - everything is ok.
I try to flash ESP32 WROVER-IE module in Arduino IDE - it works.

Can ESP32 WROVER-IE module works with Mongoose OS? May be I need to use some parameters when I flash it? Or is there some nuances using Mongoose Os, because of PsRAM chip on the board?

Dear mgos developers, please, reply…
Can I use mgos for ESP32 WROVER-IE???

Have you had a look at any of the other threads in the forum talking about PSRAM?
Just saw this response by nliviu talking about working config for PSRAM.

I recall seeing some conversation about 4MB causing some things to fail, maybe this comment will lead you in the right direction around partition sizes

1 Like

Thanks for your reply! I looked for request like “WROVER”, but I forgot and didn’t even think that a “PSRAM” request would be better! Great thanks!)

You might have a power supply problem. The USB cable too long and/or the power wires to thin.

I tried to use another USB cable, and another PC, but the problem was not solved.