Brownout detection doesn't set reason code [BUG?]

[0xffff]

is this a bug that I should report or is cause known?

Code: Select all

[2018-11-09T00:22:05.003] [ALL] USB -
[2018-11-09T00:22:05.005] [ALL] USB - Brownout detector was triggered
[2018-11-09T00:22:05.006] [ALL] USB -
[2018-11-09T00:22:05.009] [ALL] USB - ets Jun  8 2016 00:22:57
[2018-11-09T00:22:05.010] [ALL] USB -
[2018-11-09T00:22:05.014] [ALL] USB - rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
[2018-11-09T00:22:05.015] [ALL] USB - configsip: 0, SPIWP:0xee
[2018-11-09T00:22:05.022] [ALL] USB - clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[2018-11-09T00:22:05.024] [ALL] USB - mode:DIO, clock div:2
[2018-11-09T00:22:05.026] [ALL] USB - load:0x3fff0010,len:4

I have brownout detection set and it says it was triggered, but I would imagine the reset code to be 0xF mapping to RTCWDT_BROWN_OUT_RESET but it is actually a standard software reset

[ESP_igrr]

This is because brownout reset is handled in software, so from the perspective of the ROM code this is a software reset. However if you call esp_reset_reason function after such reset, it will return the correct reset reason.