ESP32 Forum

hello
I'm having a problem with using the WIFI from the ESP-WROOM32.
file:smart_config
burning with make flash
ESP32-DevKitC can be used normally.
But when the ESP32 module is used, it is constantly restarted.


phy_init: failed to load RF calibration data

rst:0xc (SW_CPU_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:5724
load:0x40078000,len:0
load:0x40078000,len:13804
entry 0x40079030
I (68) boot: Detected ESP32
I (32) boot: ESP-IDF v3.0-dev-1321-ge43ac33-dirty 2nd stage bootloader
I (32) boot: compile time 10:50:54
I (33) boot: Enabling RNG early entropy source...
I (39) boot: SPI Speed : 40MHz
I (43) boot: SPI Mode : DIO
I (47) boot: SPI Flash Size : 4MB
I (51) boot: Partition Table:
I (55) boot: ## Label Usage Type ST Offset Length
I (62) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (69) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (77) boot: 2 factory factory app 00 00 00010000 00100000
I (84) boot: End of partition table
I (88) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x0fa84 ( 64132) map
I (120) esp_image: segment 1: paddr=0x0001faac vaddr=0x3ffb0000 size=0x00564 ( 1380) load
I (120) esp_image: segment 2: paddr=0x00020018 vaddr=0x400d0018 size=0x5730c (357132) map
0x400d0018: _stext at ??:?

I (250) esp_image: segment 3: paddr=0x0007732c vaddr=0x3ffb0564 size=0x02bec ( 11244) load
I (255) esp_image: segment 4: paddr=0x00079f20 vaddr=0x40080000 size=0x00400 ( 1024) load
0x40080000: _iram_start at /home/markin/esp/esp-idf/components/freertos/./xtensa_vectors.S:1685

I (257) esp_image: segment 5: paddr=0x0007a328 vaddr=0x40080400 size=0x1020c ( 66060) load
I (293) esp_image: segment 6: paddr=0x0008a53c vaddr=0x400c0000 size=0x00000 ( 0) load
I (303) boot: Loaded app from partition at offset 0x10000
I (303) boot: Disabling RNG early entropy source...
I (305) cpu_start: Pro cpu up.
I (308) cpu_start: Starting app cpu, entry point is 0x40080f28
0x40080f28: call_start_cpu1 at /home/markin/esp/esp-idf/components/esp32/./cpu_start.c:222

I (299) cpu_start: App cpu up.
I (319) heap_init: Initializing. RAM available for dynamic allocation:
I (326) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (332) heap_init: At 3FFB8F48 len 000270B8 (156 KiB): DRAM
I (338) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (345) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (351) heap_init: At 4009060C len 0000F9F4 (62 KiB): IRAM
I (357) cpu_start: Pro cpu start user code
I (39) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (101) wifi: wifi firmware version: 59e5fab
I (101) wifi: config NVS flash: enabled
I (101) wifi: config nano formating: disabled
I (101) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (111) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (141) wifi: Init dynamic tx buffer num: 32
I (141) wifi: Init data frame dynamic rx buffer num: 32
I (141) wifi: Init management frame dynamic rx buffer num: 32
I (141) wifi: wifi driver task: 3ffc03d0, prio:23, stack:4096
I (151) wifi: Init static rx buffer num: 10
I (151) wifi: Init dynamic rx buffer num: 32
I (151) wifi: wifi power manager task: 0x3ffc5010 prio: 21 stack: 2560
W (161) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration

markin wrote: ESP32-DevKitC can be used normally.
But when the ESP32 module is used, it is constantly restarted.


phy_init: failed to load RF calibration data

Restarts during full RF calibration are almost always due to power stability (or power supply capacitance) problems.

ESP-WROOM32 modules are not made to be used standalone. They are designed to be integrated on a PCB with an adequate 3.3V supply on the board and at least 10uF + 0.1uF (or more) capacitors on the power input.

If you're using the ESP-WROOM32 module standalone, you'll need to work out how to achieve this (shorter/thicker power leads, soldering low ESR high value capacitors to the power pins on the module).

If this module is on a PCB design, revise the PCB design based on the schematic shown in the ESP-WROOM32 datasheet "Peripheral Schematics" section (and/or by reviewing Espressif's development board designs).


Angus

this module is on a PCB design .And the PIN VDD is 3.28v,10uf+0.1uf capacitors on the power input.

When I use this module on a PCB design burned esp-idf/examples/get-started/hello_world,it can be uesd normally NOT restart.

PIN VDD is 3.28V,10uf+0.1uf cap on the power input.

The module burned fileexamples/get-started/hello_world, it worked normally.

I am sure it does; those examples do not use WiFi and WiFi is the peripheral that draws the power that makes the ESP32 brown out.

Again: check your power supply. If the PCB design has an LDO, see if it can source 500mA or more. If the power comes over the USB lead, remove (non-powered) USB hubs and make sure the USB cable you're using is a high-quality one.

markin wrote:PIN VDD is 3.28V,10uf+0.1uf cap on the power input.

Something else to keep in mind is that WiFi is "bursty" in its power usage. So VDD may look stable when WiFi is not transmitting, but if you watch the VDD pin on an oscilloscope you will see short dips when calibration is running (or when connected to a WiFi network).

THANKS.

The original LDO current is too small, only 150MA.

After changing LDO, the problem is solved.

Same problem here as well. I've upgraded my ESP-WROVER-KIT V3 with an LDL1117S33R and everything worked out like a charm. You can always add some capacitance in order to help with the voltage dips.