TG0WDT_SYS_RESET triggered multiple times when connected to epaper and waking up from deep sleep
Posted: Mon Oct 26, 2020 6:43 pm
I'm a newbie - and so far I've been able to solve most of the issues with the ESP32. This one I have no idea what to do and Googling doesn't give me any ideas.
I have this Waveshar ESP32, plugged into this epaper 12inch module.
I am running code on the ESP32 to render a calendar on the screen. It wakes up every 10 minutes from deep sleep and polls the server for any changes to the calendar and, renders if there are and then goes back to sleep again.
All works on a 7.5inch screen, but when connected to the 12inch module the ESP32 when coming out of deep sleep starts to reboot (sometimes endlessly) like this:
I've tried the following to no avail:
1. Clear the flash
2. Connected a different ESP32 to the e-paper module
I've been able to pin down the problem to this call (if I test a simple program without that call this issue does not occur, the call added to the simple program, the issue does occur):
Any thoughts what could be happening here?
I have this Waveshar ESP32, plugged into this epaper 12inch module.
I am running code on the ESP32 to render a calendar on the screen. It wakes up every 10 minutes from deep sleep and polls the server for any changes to the calendar and, renders if there are and then goes back to sleep again.
All works on a 7.5inch screen, but when connected to the 12inch module the ESP32 when coming out of deep sleep starts to reboot (sometimes endlessly) like this:
Code: Select all
rst:0x5 (DEEPSLEEP_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:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ets Jun 8 2016 00:22:57
rst:0x7 (TG0WDT_SYS_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:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6352
entry 0x400806b8
ets Jun 8 2016 00:22:57
rst:0x7 (TG0WDT_SYS_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:1
load:0x3fff0018,leets Jun 8 2016 00:22:57
rst:0x7 (TG0WDT_SYS_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:1
load:0x3fff0018,len:4
load:0xf30fc0f1,len:4194556
ets Jun 8 2016 00:22:57
1. Clear the flash
2. Connected a different ESP32 to the e-paper module
I've been able to pin down the problem to this call (if I test a simple program without that call this issue does not occur, the call added to the simple program, the issue does occur):
Code: Select all
void GPIO_Config(void)
{
// SPI
pinMode(EPD_SCK_PIN, OUTPUT);
pinMode(EPD_MOSI_PIN, OUTPUT);