OpenSSL Server Example generates 'Brownout detector was triggered'

[bahans]

Trying to get the OpenSSL_Server example to run. I have tried it with both USB power source and a regulated power source at 3.3V; same issue. Below is the output:

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:0x3fff0008,len:8
load:0x3fff0010,len:4408
load:0x40078000,len:11072
load:0x40080000,len:252
entry 0x40080034
I (45) boot: ESP-IDF v3.0-dev-114-g4ec2abb-dirty 2nd stage bootloader
I (46) boot: compile time 21:54:50
I (49) boot: Enabling RNG early entropy source...
I (65) boot: SPI Speed : 40MHz
I (78) boot: SPI Mode : DIO
I (90) boot: SPI Flash Size : 4MB
I (102) boot: Partition Table:
I (114) boot: ## Label Usage Type ST Offset Length
I (136) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (160) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (183) boot: 2 factory factory app 00 00 00010000 00100000
I (206) boot: End of partition table
I (219) boot: Disabling RNG early entropy source...
I (236) boot: Loading app partition at offset 00010000
I (1319) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1320) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x1b1d8 (111064) map
I (1336) boot: segment 2: paddr=0x0003b1e8 vaddr=0x3ffb0000 size=0x02ebc ( 11964) load
I (1368) boot: segment 3: paddr=0x0003e0ac vaddr=0x40080000 size=0x00400 ( 1024) load
I (1390) boot: segment 4: paddr=0x0003e4b4 vaddr=0x40080400 size=0x12f0c ( 77580) load
I (1453) boot: segment 5: paddr=0x000513c8 vaddr=0x400c0000 size=0x00000 ( 0) load
I (1454) boot: segment 6: paddr=0x000513d0 vaddr=0x00000000 size=0x0ec38 ( 60472)
I (1475) boot: segment 7: paddr=0x00060010 vaddr=0x400d0018 size=0x6a240 (434752) map
I (1501) cpu_start: Pro cpu up.
I (1512) cpu_start: Starting app cpu, entry point is 0x40080eac
I (0) cpu_start: App cpu up.
I (1545) heap_init: Initializing. RAM available for dynamic allocation:
I (1566) heap_init: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM
I (1585) heap_init: At 3FFB81C8 len 00027E38 (159 KiB): DRAM
I (1604) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (1624) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1644) heap_init: At 4009330C len 0000CCF4 (51 KiB): IRAM
I (1663) cpu_start: Pro cpu start user code
I (1722) cpu_start: Starting scheduler on PRO CPU.
I (193) cpu_start: Starting scheduler on APP CPU.
I (223) wifi: wifi firmware version: f092575
I (223) wifi: config NVS flash: enabled
I (223) wifi: config nano formating: disabled
I (223) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (233) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (263) wifi: Init dynamic tx buffer num: 32
I (263) wifi: Init dynamic rx buffer num: 32
I (263) wifi: wifi driver task: 3ffbe7b8, prio:23, stack:4096
I (263) wifi: Init static rx buffer num: 10
I (263) wifi: Init dynamic rx buffer num: 32
I (273) wifi: Init rx ampdu len mblock:7
I (273) wifi: Init lldesc rx ampdu entry mblock:4
I (273) wifi: wifi power manager task: 0x3ffc3b1c prio: 21 stack: 2560
I (283) Openssl_example: start the WIFI SSID:[xxxxxx] password:[xxxxxxxxx]

I (293) wifi: wifi timer task: 3ffc4b88, prio:22, stack:3584

Brownout detector was triggered

[ESP_Sprite]

The brownout detector detects if the 3.3V power supply rails to the ESP32 becomes unacceptably low. In your case, I'd look at your power supply infrastructure: if you are using an existing devboard, usually the USB cable is prime suspect.

[bahans]

That is exactly what it was. Bad cable. I am not using a USB cable instead I am going into a UART to USB converter. Swapped out the cables and did not have any issues.

[dhs2017]

either disable the brownout detection or connect with a external 5V supply.

[ESP_Sprite]

FWIW, disabling the brown-out detector is a bad idea here. A brown-out detector that gets triggered usually means the power supply is inadequate for the ESP. Disabling the brown-out detector may allow you to not get a reset because of this, but there's a high chance of weird crashes or malfunctions later on.